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

Developer Terms

Proposed terms for APIs, SDKs, integrations, Code and applications built with Tessen.

Download draft
Not effective · Not represented as attorney-reviewed. Drafting markers identify decisions or facts required before adoption.
CONTENTS
1. Application and parties2. Developer accounts, projects and credentials3. Permitted integration and end-user disclosures4. Inputs, outputs and customer data5. Models, routing and external providers6. Tools, execution and connected actions7. Usage limits, accounting and payment8. Compatibility, changes and previews9. Safety and downstream responsibility10. Suspension, termination and portability11. Liability, support and related documents
All legal documents
Contents
1. Application and parties2. Developer accounts, projects and credentials3. Permitted integration and end-user disclosures4. Inputs, outputs and customer data5. Models, routing and external providers6. Tools, execution and connected actions7. Usage limits, accounting and payment8. Compatibility, changes and previews9. Safety and downstream responsibility10. Suspension, termination and portability11. Liability, support and related documents

1. Application and parties

These V1 draft terms apply to developer access through Platform, APIs, SDKs, Code and associated execution or integration tools. Platform is the developer-facing experience; console services are an administration/backend authority. They use the same legal center rather than a separate legal regime.

The contracting entity is identified in the Terms, subject to its outstanding company-detail marker. These terms supplement that agreement for individual developers or the Business Terms for organizations. A signed order or negotiated agreement controls an express conflict within its scope. The DPA controls customer personal-data processing where validly executed. This document has no operative effective date yet.

2. Developer accounts, projects and credentials

You must accurately identify the person or organization responsible for each project. Account permissions, project membership, API keys and device credentials should be assigned according to need. You are responsible for managing access by your personnel and application users and for revoking credentials that are exposed or no longer needed.

Do not embed secret keys in publicly distributed clients, source repositories, documentation or analytics. Use server-side secret handling and separate environments as appropriate. Tessen may revoke compromised credentials or apply limits to protect the service. Such action does not release either party from its own security obligations.

3. Permitted integration and end-user disclosures

You may integrate the Services into authorized applications within the documented capability, entitlement and usage limits. Do not imply that your application is operated, endorsed or professionally certified by Tessen unless expressly authorized. Use Tessen branding only according to an applicable permission or brand policy.

Give your users clear terms, privacy information and legally required AI disclosures. Explain the role of Tessen where relevant and identify the controller of personal data. Obtain necessary rights and permissions for content, connected accounts and actions. Your end-user agreement must not purport to bind Tessen to additional commitments.

4. Inputs, outputs and customer data

You are responsible for lawful submission of Input and appropriate use of Output. Code, context, repositories, files and tool results may include personal data, licensed material and confidential information. Minimize unnecessary sensitive data and confirm the suitability of the selected processing configuration.

Content rights and processing authorizations are governed by the underlying agreement and Service Terms. This document does not grant a model-training license by implication, guarantee exclusive Output ownership or override third-party licenses. Where you process personal data for another controller, ensure the required contractual chain and instructions are in place before access.

5. Models, routing and external providers

Model aliases, versions, context windows and availability may change according to the documented service and applicable notice process. An API-compatible interface does not guarantee identical behavior across providers. Outputs, tool calls, token counts and costs may vary. You should evaluate the models and versions appropriate for your use.

A routed provider may impose additional use restrictions and data-handling conditions that must be disclosed and contractually addressed. [COMPANY DETAIL REQUIRED: actual provider terms, routing disclosures and contractual responsibilities for model-specific restrictions.] Do not describe every provider as a subprocessor without assessing its role and agreement.

6. Tools, execution and connected actions

Code and tool features may run commands, modify files, call external APIs or interact with connected services. Give only the permissions needed for the task, use safe testing environments and verify destructive or externally consequential actions. Input from an untrusted repository, page or document must not be treated as authority to expand access.

Developers must not bypass approval checks, sandboxes, tenancy boundaries or connector permissions. You remain responsible for your application’s authorization model, secrets, end-user consent and execution policies. Logs and receipts can help explain actions but do not guarantee success or substitute for independent verification.

7. Usage limits, accounting and payment

Observe rate limits, quotas and permitted concurrency. Do not use multiple accounts or manipulated identifiers to evade restrictions. Metering may include tokens, requests, execution resources or other disclosed units; only the production pricing and applicable order establish charges.

[LEGAL REVIEW REQUIRED: metering definitions, reconciliation, dispute handling, prepaid credits, expiry, overages and billing rules matched to actual implementation.] This draft establishes no price, capacity reservation or refund entitlement beyond mandatory law. Free preview access is subject to Project Zero Terms where applicable, and must not be represented as guaranteed production capacity.

8. Compatibility, changes and previews

Design applications to handle timeouts, retries, rate limits, refusals and unavailable capacity without concealing failures from users. Idempotency and retry behavior depend on the specific endpoint. A repeated tool request may cause repeated external effects unless the relevant system prevents them.

Preview features may be unsuitable for production commitments. [LEGAL REVIEW REQUIRED: final versioning, deprecation, notice and migration commitments.] No SLA, backward-compatibility period or incident-response time is invented in this draft. An actual contracted SLA must identify covered services, measurement rules and exclusions separately.

9. Safety and downstream responsibility

Follow the Acceptable Use Policy and apply appropriate controls to downstream users. Evaluate Output, secure generated code and review uses with significant effects on people. Do not use an API to automate prohibited activity or to conceal responsibility for it.

Implement a reasonable route for users to report issues and stop harmful workflows. Human review should be proportionate to the stakes. Tessen’s safeguards supplement your application’s controls and do not eliminate your responsibilities as its operator, while preserving Tessen’s own obligations under law and contract.

10. Suspension, termination and portability

Tessen may limit developer access for security risks, material breach, legal requirements or expired entitlements, subject to applicable notice and cure obligations. Wherever appropriate, scope the restriction to the affected credential or project. You should retain copies of your application code and establish continuity plans independent of a preview.

On termination, stop using affected credentials and access rights. Data return, deletion and legally retained records follow the underlying agreement and DPA. Revoking an API key does not itself delete stored content. Any migration or export commitment requires express agreement.

11. Liability, support and related documents

Warranty exclusions, liability limits, indemnities and dispute procedures follow the final underlying agreement and require the review decisions identified there. This draft does not silently introduce a developer-specific cap or arbitration clause. No technical support level or response time is guaranteed without an applicable agreement.

Related documents: Terms, Business Terms, DPA, Acceptable Use, Service Terms and Project Zero. Send draft comments to hello@tessen.ai without credentials or confidential payloads.

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