Skip to content
Tessen
THE TESSEN ECOSYSTEM
01HEROThe Intelligence02CODEAI software development03BROWSER EXTENSIONTessen across the web04ORBITTessen’s intelligent browser05NODELocal, private and distributed computeHWKERNHardware · in development
ModelsResearchDevelopersEnterpriseAcademy — in development
Company ⌄
TESSEN, INC.AboutSolutionsNewsCareersPartnersSecurityLegalContactAcademyIn development
Open Tessen ↗
PRODUCTSHero01Code02Browser Extension03Orbit04Node05KERNHardware · in development
ModelsResearchDevelopersEnterpriseCompanyDownloadAcademyIn development
Open Tessen ↗
Legal Center /V1 REVIEW DRAFT · 5 OCTOBER 2026

Project Zero Preview Terms

Proposed rules for capacity-limited developer preview access and Node participation.

Download draft
Not effective · Not represented as attorney-reviewed. Drafting markers identify decisions or facts required before adoption.
CONTENTS
1. Program and draft status2. Eligibility and authentication3. Shared capacity and request outcomes4. Allowances and credits5. Permitted developer use6. Node relationship7. Data and feedback8. Changes, suspension and termination9. Support and related documents
All legal documents
Contents
1. Program and draft status2. Eligibility and authentication3. Shared capacity and request outcomes4. Allowances and credits5. Permitted developer use6. Node relationship7. Data and feedback8. Changes, suspension and termination9. Support and related documents

1. Program and draft status

Project Zero is Tessen’s developer intelligence preview direction. These V1 draft terms supplement the Terms, Developer Terms and, where applicable, Node Terms. They do not announce that preview access is enabled for all users or that production capacity is available.

The program’s approved message is “THE ZERO POOL IS OPEN. MORE DEVELOPERS. MORE NODES. MORE INTELLIGENCE.” That messaging is not a guarantee of an individual entitlement, successful request or permanent free service. Program availability must be separately and truthfully presented in the access flow.

2. Eligibility and authentication

Access requires the identity, developer eligibility and entitlement checks actually implemented for the program. Device authorization must identify the requesting application and obtain valid approval. Do not approve a code you did not request or share credentials produced by an exchange.

Accounts may be restricted based on lawful program conditions, abuse prevention or available capacity. [COMPANY DETAIL REQUIRED: final eligibility, geographic restrictions, enrollment process and program availability.] Do not present planned enrollment as an established public launch.

3. Shared capacity and request outcomes

Preview requests share limited resources. A request may be queued, rate-limited, refused or fail when free capacity is unavailable. No specific model, token pool size, reset hour, throughput or uptime is guaranteed by these terms. Displayed accounting must be matched to server-authoritative program rules.

The intended preview is a zero-paid-routing program. Any fallback to a paid product requires separate, clear authorization under its commercial conditions; preview consent is not permission to silently charge. [COMPANY DETAIL REQUIRED: validated capacity rules, routing safeguards, reset accounting and user-visible failure behavior.]

4. Allowances and credits

Allowances are program benefits subject to eligibility and use conditions, not a deposit, cash balance, transferable asset or investment. Do not promise redemption, exchange value or earnings without an actual approved commercial arrangement. Different preview and paid balances must be clearly distinguished.

[LEGAL REVIEW REQUIRED: exact entitlement, allowance lifecycle, credit issuance/expiry, transfer restrictions, corrections and any Node-linked incentives.] This draft inserts no numerical pool, payment rate or cash-out policy. Correcting an accounting error must be transparent and consistent with lawful accrued rights.

5. Permitted developer use

Use the preview for authorized development and evaluation within the Acceptable Use Policy and actual limits. Do not multiply accounts, spoof participation, manipulate metering or resell program access. Do not route around a capacity refusal or entitlement denial to unauthorized providers or paid services.

Evaluate generated code and protect project credentials. Free access does not mean data is public or that safety and privacy requirements are suspended. Production commitments to your customers must not rely on uncontracted preview capacity.

6. Node relationship

Voluntary Node participation may support the wider intelligence ecosystem or program incentives where implemented. It is not mandatory unless an actual, disclosed eligibility rule says so. Participating requires authorization to use the machine, energy and network resources involved.

Node terms govern resource use, privacy modes, workload handling and any approved credit mechanism. Project Zero membership does not authorize Tessen to execute arbitrary local workloads. Do not describe the program as cryptocurrency mining, guaranteed passive income or employment.

7. Data and feedback

Preview Input, Output and metadata are governed by the Privacy Notice, Developer Terms and any executed DPA. Model-provider conditions and content logging must be disclosed according to actual implementation. These terms provide no additional model-training permission and make no unverified promise about training exclusions.

Feedback should omit secrets, unnecessary personal data and customer-confidential information. [LEGAL REVIEW REQUIRED: final feedback rights and preview-specific evaluation disclosures.] A voluntary bug report is not unrestricted consent to reuse its content.

8. Changes, suspension and termination

Preview models, limits and availability may change, subject to applicable notice obligations. Tessen may pause access for security, misuse, technical constraints or program closure. Urgent protective suspension may be necessary; users should receive a review route where appropriate and lawful.

[LEGAL REVIEW REQUIRED: program-change notice, discontinuation process and treatment of valid accrued benefits.] No indefinite access or migration period is promised. Stopping the preview does not automatically remove access to separately contracted Tessen services.

9. Support and related documents

The program carries no SLA or support response commitment unless separately agreed. Report failures with request identifiers and redacted diagnostics, avoiding tokens and credential files. For billing questions, distinguish preview allowances from paid usage in the request.

Read the Developer Terms, Node Terms, Acceptable Use Policy and Privacy Notice. Draft comments may be sent to hello@tessen.ai. Underlying liability and dispute decisions remain open for legal review in the Terms.

TessenUseful intelligence for people,
developers and organizations.

Products

HEROCodeBrowser ExtensionOrbitNodeKERNIn development

Models & research

Model familiesZ1Z1 CodeH1Research

Platform

PlatformConsoleDevelopersProject ZERODownloads

Enterprise

Tessen BusinessSolutionsPartnershipsContact Sales

Company

AboutAcademyIn developmentContactUpdatesCareersResources

Support & legal

SecurityLegal CenterPrivacyTermsHelp CenterStatus
hello@tessen.ai
© 2026 Tessen, Inc.PrivacyTermsBack to top ↑
TESSEN

This page is part of the next chapter.
Explore Tessen or get in touch in the meantime.

Open Tessen ↗hello@tessen.ai