# Terms of Use
General terms for individuals using Tessen and its connected intelligence experiences.

## 1. Draft status and contracting entity
This is a proposed V1 agreement for legal review. It is not an operative contract, does not establish an effective date, and has not been represented as attorney-reviewed. It must be approved, completed and presented through a valid acceptance process before reliance on it as binding terms.

In this draft, “Tessen,” “we” and “us” mean the entity that provides the relevant service. [COMPANY DETAIL REQUIRED: legal name of the contracting entity, registration details where legally required, service address and official legal-notice contact.] References to the Tessen brand or a website copyright notice do not determine the contracting entity.

## 2. Services and scope
“Services” means the Tessen websites, HERO intelligence experiences on Web, Mobile and Desktop, Code, Browser Extension, Orbit, Node, APIs, developer services and associated capabilities, including Connect, Memory, Work, Self, Files and Research. Platform is the developer-facing experience; console services support its administration and operation. Availability may vary by product, region, account, release stage and enabled permissions.

These Terms govern personal use when no separate agreement applies. Business customers should consult the Business Terms. API and integration use is also subject to the Developer Terms. The Acceptable Use Policy applies across the ecosystem. Product-specific Service Terms, Connect Terms, Node Terms and Project Zero Terms apply to their stated subject matter. The Privacy Notice explains personal-data handling and does not replace consent or a required processing agreement.

An expressly agreed order or signed agreement governs a conflict within its specific scope. Product-specific terms govern the relevant feature over these general Terms where expressly stated. No document may override rights that applicable law does not allow the parties to exclude.

## 3. Eligibility and authority
You must have legal capacity to enter the applicable agreement and comply with age and territorial restrictions displayed at registration. [LEGAL REVIEW REQUIRED: minimum user age, parental-consent approach, restricted territories and regional consumer disclosures.] If you act for another person or an organization, you must have authority to give the instructions and permissions you provide.

Do not create an account for someone without authority, misrepresent your identity, or use another person’s credentials. If an organization administers your account, its administrators may control access and content within the organization’s environment; the organization must provide appropriate notices and authority for those controls.

## 4. Accounts and access security
Provide accurate registration and contact information and keep it reasonably current. Protect passwords, device approvals, session tokens and other access credentials. Notify Tessen through the available support channel when you reasonably suspect unauthorized access. We may require identity verification proportionate to the request, without asking for unnecessary information.

You are responsible for instructions submitted by you and people you authorize, subject to applicable law and any separately agreed security obligations. Do not share individual accounts in ways that bypass limits or enable untraceable access. Signing out of one interface may not revoke every session, API key or connected-service permission; use the relevant controls where available.

## 5. Inputs, outputs and rights
“Input” is material you provide or authorize the Services to access. “Output” is material generated in response. You retain whatever rights you hold in Input. These Terms do not transfer ownership of your files or accounts to Tessen. You must have the permissions necessary to submit Input, process third-party information and instruct actions affecting others.

You grant Tessen a limited authorization to access, reproduce, transform, transmit and otherwise process Input and Output as necessary to carry out your requested service, maintain its operation and comply with applicable legal obligations, subject to the Privacy Notice and any applicable DPA. This is not a blanket authorization to train models. The treatment of content for model development, evaluation or improvement must be described separately and agreed where required.

[LEGAL REVIEW REQUIRED: final Output rights allocation, assignment language where legally possible, third-party model restrictions and treatment of feedback.] No term can create exclusive rights in material that is not protectable under applicable law. Other users may receive similar outputs. Third-party content, open-source components and externally sourced material remain subject to their own rights and licenses.

## 6. AI limitations and responsible reliance
Outputs may be inaccurate, incomplete, outdated, biased or inappropriate. A citation, confidence indicator or fluent answer is not a guarantee of accuracy. Review source material and independently verify information before using it in a consequential setting. Code may contain defects or security issues; research may miss sources; generated files may require checking.

The Services do not substitute for a qualified medical, legal, financial or other regulated professional. Do not rely on the Services alone for decisions involving safety, legal rights, employment, credit, housing, health or similarly significant interests. You remain responsible for selecting appropriate human review and for how you use or distribute Output. These provisions do not excuse Tessen from obligations imposed by law.

## 7. Instructions, tools and actions
Some features can communicate with external services, execute code, modify files, schedule work or initiate other digital actions. Permissions and approvals are scoped to the action or connected feature. Before authorizing an action, review the intended destination, account, affected data and consequences. Supplying content for analysis is not automatically permission to send it to another person or publish it.

Automated work may continue according to previously authorized instructions until completed, cancelled or otherwise interrupted. Changing an instruction may not undo completed actions. External systems can fail or respond unpredictably. Tessen should not be used as the sole control for safety-critical systems, and you must not bypass permission or confirmation mechanisms.

## 8. Connected services and local applications
Third-party accounts, browsers, model providers, stores and tools have their own terms and privacy practices. Connecting an account authorizes the specified access; it does not transfer ownership of that account. Review scopes and revoke unnecessary access. Revocation may prevent future access while leaving previously imported content subject to the applicable retention and deletion process.

Orbit, Browser Extension, Code and Node may operate on your device or interact with local resources. “Local” does not by itself mean that all telemetry, account data or processing stays on that device. Product notices and controls must explain the actual data flows. Node participation and Project Zero access are governed by their specific terms and do not promise earnings, capacity or permanent free access.

## 9. Charges and commercial conditions
Any paid plan, purchase or metered use must display its price, billing unit, currency, taxes where required and applicable commercial conditions before you commit. We do not establish fictional prices, renewal periods or credit economics in these Terms. [LEGAL REVIEW REQUIRED: billing, renewal, cancellation, statutory withdrawal, refunds and credit-expiry rules matched to actual checkout behavior.]

An advertised allowance or preview benefit is not an unlimited entitlement. Do not circumvent quotas or usage accounting. Payment disputes and cancellation requests should be raised through the available billing support process. Applicable consumer rights remain unaffected.

## 10. Acceptable use and platform integrity
Follow the Acceptable Use Policy, applicable laws and the rights of others. Do not use the Services to compromise systems, distribute malware, conduct fraud, exploit children, enable serious harm, evade safeguards or unlawfully process sensitive personal data. A feature’s technical ability to perform an action does not authorize that action.

We may investigate suspected abuse using proportionate measures consistent with the Privacy Notice and applicable law. We may restrict a specific feature, credential or account when reasonably necessary to address a security risk, material breach or legal requirement. Where appropriate and legally permitted, provide notice of the restriction and a route to challenge an error. Restrictions should not be represented as determinations of criminal liability.

## 11. Changes, previews and availability
Services may evolve and previews may be changed or discontinued. Release notes and feature descriptions should distinguish available functions from planned capabilities. We do not promise continuous operation, a specific model, fixed capacity or a service level unless expressly agreed in an applicable written commitment.

Material contractual changes should be notified with the legally required notice and acceptance process. A revised page alone is not a substitute for consent where consent is required. Changes should not retroactively remove accrued rights. [LEGAL REVIEW REQUIRED: change-notice procedure, applicable notice periods and termination rights for affected users.]

## 12. Ending use and consequences
You may stop using the Services and request account closure through the available process. Closing an account does not automatically cancel a purchase made through a third-party store or organization; follow the relevant purchase terms. We may end access for material breach or where required by law, applying any required notice and cure process.

On termination, access rights cease within the affected scope. Content export, deletion, backups and legally required retention are addressed in the Privacy Notice and any applicable business agreement. Do not assume immediate destruction of every copy or guaranteed indefinite access. Clauses intended to operate after termination, including outstanding payment obligations, rights provisions and dispute terms, survive only to the extent lawful and relevant.

## 13. Warranties, liability and disputes
The final agreement must distinguish consumer and business users and preserve mandatory warranties, remedies and liabilities. AI limitations are relevant to appropriate use but are not a blanket waiver of responsibility. [LEGAL REVIEW REQUIRED: permitted warranty exclusions, liability allocation, any monetary cap, exceptions and indemnity obligations.] No liability exclusion or cap is proposed as an operative condition by this draft.

Try to resolve a concern by contacting Tessen with the account context, relevant dates and remedy sought. Do not send passwords or complete secrets. [LEGAL REVIEW REQUIRED: governing law, court jurisdiction, regional consumer protections and whether any alternative dispute-resolution provision is appropriate.] This draft selects no jurisdiction, mandatory arbitration mechanism or class-action waiver.

## 14. General provisions and contacts
An invalid provision should be severed only to the extent the applicable law permits without rewriting the commercial bargain. Failure to enforce a provision immediately does not necessarily waive later enforcement. Assignment, notices and entire-agreement provisions must be finalized for the actual contracting entity and regional audiences. No implied partnership, agency or employment relationship is created merely by use of Tessen.

For this draft package, questions and review comments may be sent to hello@tessen.ai. This general contact is not a confirmed registered office, representative address or contractual service-of-process destination. Related documents: [Acceptable Use](/legal/acceptable-use), [Privacy](/legal/privacy), [Service Terms](/legal/service-terms), [Business Terms](/legal/business-terms) and [Developer Terms](/legal/developer-terms).


---

# Privacy Notice
A proposed ecosystem-wide notice covering personal data, AI context and connected services.

## 1. Status, scope and accountable entity
This V1 notice is a legal and operational review draft, not a representation that every described workflow has been deployed or legally approved. It is not effective as a final privacy notice. Statements of proposed practice must be checked against real processing before publication as operative policy.

The notice covers Tessen websites, Web, Mobile, Desktop, Code, Browser Extension, Orbit, Node, Platform, developer services and capabilities including Connect, Memory, Work, Self, Files, Research and Project Zero. Business processing carried out on a customer’s instructions may instead be governed by the customer’s notice and an executed DPA. Tessen can have different legal roles for account administration and customer-controlled content.

[COMPANY DETAIL REQUIRED: controller legal name, business address, privacy contact, and any required data-protection officer or regional representative details.] hello@tessen.ai is the available general contact for draft questions; it is not asserted to be a statutory representative’s address.

## 2. Data you provide
Depending on the feature used, data may include account identifiers, contact details, authentication information, profile preferences, organization membership, billing-related details, support messages, feedback and communications. Conversations and uploaded content may include text, documents, images, audio, video, source code and information about third parties.

Memory and Self may contain your preferences, goals, relationships, routines, work context and other personal information you choose to supply or authorize the system to derive. Do not upload secrets or sensitive information merely because a feature can accept it. Use appropriate controls and verify that the selected service is suitable for the information.

Payment-related processing must be described according to the actual payment flow. This draft does not assert that Tessen stores card numbers or that a specific payment processor handles them. [COMPANY DETAIL REQUIRED: actual account, payment and support data inventories, including required versus optional fields.]

## 3. Data from connected sources and other people
Connect may obtain information from accounts or services you authorize, within granted scopes. Browser tools may process page content, URLs and selected context. Code tools may access repository content, commands, files and execution results within the configured environment. Organization administrators may provide information about authorized users and their access.

Data can also arrive through another user’s instructions, shared files, public sources or communications. Such access still requires a lawful basis and appropriate notices. Public availability does not remove privacy rights. The production notice must identify relevant source categories and explain indirect collection where applicable; it must not suggest unrestricted access to all browsing or account activity.

## 4. Technical, usage and security information
Technical data can include device and application characteristics, session information, network identifiers, request timestamps, feature usage, error reports and security events. API usage can generate request identifiers, token or resource accounting, project attribution, model routing metadata and logs. Content can be present in diagnostic records if the implementation captures it.

Node may generate resource, configuration and task-execution information. Browser and mobile permissions can expose additional device information only according to the platform permissions and feature implementation. This notice does not claim a complete telemetry inventory. [COMPANY DETAIL REQUIRED: verified telemetry, logs, cookie/storage inventory, content logging and collection controls for each surface.]

## 5. Purposes and lawful grounds
The proposed processing purposes are to establish and manage access, deliver requested intelligence and files, execute authorized work, maintain relevant context, administer connected tools, measure and bill usage, support users, prevent abuse, maintain security and satisfy legal obligations. Each purpose must be matched to the actual data used and an appropriate lawful ground in each applicable jurisdiction.

Potential grounds may include performance of a contract, steps requested before a contract, legal obligations, legitimate interests subject to an appropriate assessment, and consent where necessary. They are not interchangeable. Optional analytics, sensitive-data processing or particular marketing activity may require additional consent or conditions. Withdrawing consent does not invalidate prior lawful processing but should stop processing that depends solely on that consent.

[LEGAL REVIEW REQUIRED: purpose-by-purpose legal-basis mapping, sensitive-data conditions, legitimate-interest descriptions and region-specific disclosures.] No broad “service improvement” purpose should be used to conceal distinct processing or repurpose content without the required notice and legal basis.

## 6. AI processing, models and training
Providing AI responses may involve routing Input, relevant context and instructions to one or more model or execution services. A provider may receive only the data required for a request or a broader context depending on the implementation. Its role, retention and permitted uses must be verified and reflected in the applicable contractual and privacy disclosures.

[COMPANY DETAIL REQUIRED: product-specific Input/Output routing, model-provider roles, provider retention, human-review access, evaluation and training practices, and available opt-out or contractual controls.] This draft makes neither a blanket “never used for training” promise nor a blanket authorization to train on user content. Those choices must be explicitly established before the final notice is adopted.

Generated Output may contain personal data or inaccurate inferences. Users should verify it, avoid unnecessary distribution and seek correction or removal through the available process. Similarity to public or third-party information does not determine whether a lawful processing basis exists.

## 7. Memory, Self and personalization
Memory and Self are intended to support continuity and personalization. Their data can include user-provided facts, selected conversation context and system-generated inferences. An inference is not an established fact about a person. Users should be able to understand the relevant context and request correction or deletion through implemented controls or support.

Deleting a conversation, editing Memory, disabling personalization and closing an account may have different technical effects. The final notice must explain these differences, including retained copies, shared context, previously generated Output and completed actions. It must not claim that a single toggle erases all downstream material.

[COMPANY DETAIL REQUIRED: actual Memory/Self collection rules, user controls, correction/deletion behavior, organization access and cross-surface synchronization.] Do not use personalization to make undisclosed sensitive judgments about users.

## 8. Work, automation and consequential decisions
Work and scheduled actions may process information over time, transmit data to a destination you authorize or produce execution records. Instructions, approvals and action results can be recorded to explain what happened and troubleshoot problems. Revoking a permission can interrupt future activity without undoing completed actions.

Personalization and automated assistance are distinct from solely automated decisions with legal or similarly significant effects. This draft does not claim that such consequential decision-making is either present or absent in every service. [LEGAL REVIEW REQUIRED: assessment of automated decision-making/profiling, relevant rights, safeguards and meaningful explanations where required.] Do not deploy the Services for such decisions without appropriate legal and human-review controls.

## 9. Disclosures and recipients
Recipients may include authorized colleagues or administrators, connected services instructed by you, infrastructure and operational providers, model/execution providers and professional advisers where needed. Disclosure to a provider must be limited to its authorized purpose and governed by the appropriate terms. An independent third party’s privacy practices may differ from Tessen’s.

Information may be disclosed where legally required, to protect rights or safety using a lawful and proportionate process, or in a proposed corporate transaction subject to applicable confidentiality and privacy protections. A business transfer is not an unrestricted license to change privacy commitments.

The [Subprocessor Register](/legal/subprocessors) distinguishes business subprocessors from user-selected independent services. No provider is asserted to be approved simply because it is technically integrated. [COMPANY DETAIL REQUIRED: verified recipient categories, disclosure practices and any applicable sale/sharing or targeted-advertising determinations.]

## 10. International processing
Remote access, provider routing and hosting may involve processing in more than one country. This draft provides no data-residency guarantee and names no unverified transfer destination. The final notice must identify applicable transfer arrangements and explain how a person can request information about safeguards.

[LEGAL REVIEW REQUIRED: verified data locations, transfer assessment, legally required safeguards, relevant transfer instruments and regional access risks.] Contractual clauses should not be described as executed or sufficient until the parties, modules, annexes and actual transfer context are confirmed. A selected local feature is not automatically a promise that all associated data remains in the user’s country.

## 11. Retention and deletion
Retention should be determined by the purpose of the record, service functionality, user or customer instructions, legal obligations, security needs and dispute resolution requirements. Different records may require different schedules. A meaningful schedule must cover content, Memory, files, connected data, logs, billing records, support records and backups separately.

[COMPANY DETAIL REQUIRED: verified retention/deletion criteria and schedules, backup treatment, legal holds, export windows and deletion propagation.] No exact period is invented here. Account closure or a deletion request may require verification and may be limited by lawful retention obligations; the final notice should explain the scope and reason rather than imply immediate complete deletion.

## 12. Rights, choices and requests
Depending on applicable law, you may have rights to access, correct, delete, restrict or object to processing, receive portable data, withdraw consent and complain to a competent authority. Some regions provide further rights concerning sensitive information, advertising, sale/sharing or automated decisions. These rights have legal conditions and exceptions; nationality alone does not determine the governing rules.

Send a request through the available account/support process or the general contact, identifying the relevant account and request without supplying passwords or unnecessary identity documents. Tessen should use proportionate verification, explain a lawful refusal where required, and respond within the applicable statutory timeline. An authorized agent may require evidence of authority. Requests about customer-controlled business content may need to be directed to the customer.

[LEGAL REVIEW REQUIRED: jurisdictional rights notices, complaint authority details, appeal process and designated privacy-request channel.] A draft contact workflow does not establish that statutory procedures have been implemented.

## 13. Security, children and updates
Appropriate security measures should be selected based on the processing risks, including access controls, credential handling, operational monitoring and incident response. This notice does not certify any particular control, encryption coverage or audit status. No system is immune from risk; actual measures and customer commitments must be verified.

The Services’ minimum age and handling of children’s data must be finalized consistently with eligibility, platform/store requirements and applicable law. [LEGAL REVIEW REQUIRED: children’s data and parental-consent rules, age assurance and response to unintended collection.] Do not submit information about children without the required authority and safeguards.

Material changes to the final notice should be communicated in an appropriate manner and consent sought when required. Version history should distinguish drafts from operative notices. Review [Cookies](/legal/cookies), [Connect](/legal/connect), [Node](/legal/node) and the [DPA](/legal/dpa) for their specific subject matter.


---

# Acceptable Use Policy
Proposed rules for responsible use across Tessen products, APIs and connected actions.

## 1. Scope and status
This V1 policy is a review draft and is not effective until adopted through the applicable agreement. It applies across HERO, Code, Browser Extension, Orbit, Node, developer services and capabilities, including content generation, connected accounts and automated work. It addresses conduct, not the technical availability of a feature.

Users, organizations and developers must obey applicable law, respect others’ rights and limit actions to their authority. Developers must apply appropriate controls to their own users and applications. Authorized research does not exempt a person from law or third-party access conditions.

## 2. Serious harm and exploitation
Do not use Tessen to facilitate violence, terrorism, human trafficking, exploitation, self-harm encouragement or the unlawful production or procurement of weapons or dangerous substances. Do not solicit operational assistance to carry out serious physical harm or evade controls designed to prevent it.

Do not create, obtain, promote or distribute sexual exploitation material involving children, assist grooming or exploit vulnerable people. Do not create non-consensual intimate imagery or sexual content involving a person without the required consent. Report suspected child exploitation or immediate threats through appropriate emergency or competent-authority channels rather than relying on an AI response alone.

## 3. Fraud, deception and identity abuse
Do not conduct scams, payment fraud, credential theft, identity theft, deceptive fundraising or impersonation intended to mislead about authority or origin. Do not generate forged documents, evidence or records for fraudulent use, or manipulate others through false representations about human involvement.

Synthetic media must not be used to unlawfully impersonate people or conceal information when disclosure is legally required. Legitimate creative fiction, education or satire still requires attention to context, labeling and applicable rights. Do not misrepresent AI output as an independently verified professional opinion or official decision.

## 4. Cybersecurity and system integrity
Do not distribute malware, ransomware, destructive code or credential-harvesting tools; gain unauthorized access; exfiltrate information; or conceal malicious activity. Do not attack Tessen infrastructure, other users, providers or connected services. Do not defeat authentication, quotas, approval gates, isolation or monitoring.

Security testing must be within written authorization and a defined scope. Stop when testing creates a risk of disruption or exposes third-party data beyond that scope. The existence of a security contact is not blanket testing permission, a promise of payment or a legal safe harbor. Share only the minimum evidence necessary to explain a vulnerability.

## 5. Privacy, surveillance and sensitive decisions
Do not unlawfully obtain, disclose, sell or infer personal information; doxx people; conduct stalking; or use connected context for unauthorized surveillance. Respect account scopes and organization access permissions. Access granted to a shared workspace does not imply permission to use its contents for unrelated purposes.

Do not use Tessen as the sole decision-maker for consequential medical, legal, financial, employment, credit, housing or similar decisions. Do not deploy discriminatory or unlawful automated decision-making. Sensitive uses require a suitable lawful basis, appropriate notices, evaluation and meaningful oversight. Do not infer sensitive traits for prohibited or unlawful targeting.

## 6. Content rights and communications
Only submit or retrieve content that you have the right to use for the intended purpose. Do not use Tessen to facilitate copyright infringement, unauthorized distribution, trade-secret theft or removal of rights-management information. A generated output may still implicate rights even if it is not a verbatim copy.

Do not send unlawful spam, harassing communications or deceptive bulk outreach. Honor consent, opt-out requests and third-party communication rules. Connected-service access is not permission to contact everyone in an address book or publish private correspondence. Review recipient identity and sensitive attachments before authorizing person-directed actions.

## 7. AI safeguards and model access
Do not bypass safety controls, entitlement checks, capacity restrictions or service limits through deceptive accounts, manipulated inputs or routing changes. Do not attempt to extract confidential system instructions, credentials, other users’ content or proprietary model material.

Evaluation of AI systems should use authorized methods and appropriate safeguards. Merely naming an activity “research,” “red teaming” or “simulation” does not authorize harmful behavior. Do not redistribute model access in violation of the applicable license, provider conditions or Tessen agreement.

## 8. Compute, Node and Project Zero
Do not use Node to run unauthorized workloads, conceal resource consumption, compromise local isolation or obtain access to another participant’s files or network. Participate only with equipment and network resources you are authorized to use. Do not claim credits for fabricated execution, exploit accounting defects or misrepresent hardware capability.

Do not abuse Project Zero through automated account multiplication, quota evasion, resale of preview access or routing manipulation intended to reach paid capacity without authorization. Respect shared resource availability. Participation is not an employment relationship or a guaranteed income opportunity.

## 9. Enforcement and review
Tessen may assess suspected misuse using a proportionate process, including limiting a particular action, credential, integration or account where necessary. Enforcement should consider severity, evidence, recurrence, safety, applicable law and the effect on legitimate users. Urgent protective measures may be appropriate before an investigation is complete.

Where lawful and practicable, provide a reason and a route to request review. A restriction does not necessarily mean a user committed a crime, and a mistake should be correctable. [LEGAL REVIEW REQUIRED: final enforcement, notice, appeal and legally mandated reporting procedures.] The policy does not authorize unrestricted inspection of private content.

## 10. Reporting and relationship to other terms
Report suspected misuse to the available support channel, including relevant request identifiers and a concise description. Do not include unnecessary personal data, secrets or harmful material. Immediate danger should be reported to the relevant emergency services. For suspected infringement, provide evidence of rights and the material concerned; the production process must be finalized for applicable notice-and-action rules.

This policy supplements the [Terms](/legal/terms), [Developer Terms](/legal/developer-terms), [Business Terms](/legal/business-terms) and product-specific terms. A signed agreement may provide additional controls but cannot authorize illegal conduct. The contracting entity and legal contacts remain subject to the review markers in the Terms.


---

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

## 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](/legal/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](/legal/terms), [Business Terms](/legal/business-terms), [DPA](/legal/dpa), [Acceptable Use](/legal/acceptable-use), [Service Terms](/legal/service-terms) and [Project Zero](/legal/project-zero). Send draft comments to hello@tessen.ai without credentials or confidential payloads.


---

# Business Terms
Proposed commercial terms for organizations using Tessen and developer services.

## 1. Status, customer and agreement structure
These V1 draft Business Terms govern an organization’s use where incorporated into an accepted order or signed agreement. They are not a completed agreement or a claim that enterprise offerings are generally available. “Customer” means the organization accepting the agreement through an authorized representative. Tessen’s contracting entity remains subject to the company-detail marker in the Terms.

The agreement consists of the executed order, these terms, incorporated product terms and, where applicable, an executed DPA. An order may describe products, authorized users, fees, term and specific commitments. A negotiated provision controls an express conflict within its scope; the DPA controls personal-data processing within its stated role. Consumer rights applicable to an individual are not removed merely by labeling an account “business.”

## 2. Access rights and organization administration
Subject to the agreement, Customer may permit authorized users to use the contracted Services for its lawful business purposes. Customer must manage users, roles, credentials and connector permissions and provide notices about administrative access. Administrator actions may affect organization data, integrations and accounts; delegated authority should be documented.

Contracted access does not convey ownership of the platform, models or another user’s information. Affiliates and external collaborators are included only to the extent the agreement permits. Customer must not resell access, bypass limits or allow unauthorized access under the guise of collaboration.

## 3. Customer content and operational instructions
Customer retains its rights in content supplied to the Services. It authorizes processing needed to perform its instructions and the agreement, subject to the DPA and applicable rights. Output rights and restrictions require the final allocation identified in the Terms; no exclusive title or third-party license clearance is guaranteed by this draft.

Customer determines what information it submits, who may access it and which actions it authorizes. It must have the necessary rights, legal basis and instructions. Tessen must not interpret a general access grant as permission to disclose confidential customer content for an unrelated purpose. Feedback must be distinguished from customer data and commercially sensitive information.

## 4. Confidentiality
Each party should protect non-public information disclosed by the other that is identified as confidential or reasonably understood to be confidential from its nature and circumstances. Use it only to perform the agreement and disclose it only to people who need it and are subject to appropriate obligations. Protect it with reasonable care appropriate to the information.

Information is not confidential to the extent lawfully known without restriction, independently developed, publicly available without breach or lawfully received from another source. Required legal disclosure should be limited to the legal requirement, with notice to the other party when lawful and reasonable assistance with protective measures. These exclusions do not override data-protection obligations.

## 5. Privacy, processing roles and security
The DPA must be completed where Tessen processes personal data on Customer’s behalf. Account administration, security and legal compliance may involve separate controller purposes that must be transparently described. Roles are determined by actual activity, not branding or a contractual label alone.

Security measures and any negotiated assurances belong in a verified security schedule. Customer must configure its environment, integrations and user controls appropriately. Tessen must meet the obligations actually agreed for its processing. This draft makes no claim of SOC 2, ISO certification, HIPAA suitability, data residency or other assurance. The presence of a security page is not a certification.

## 6. Fees, taxes and usage
The order or checkout must set the actual fees, currency, payment schedule and usage units. Each party must satisfy tax obligations assigned under the final agreement and applicable law. A commercial invoice or token counter should not be treated as proof of a charge unsupported by the agreed pricing.

[LEGAL REVIEW REQUIRED: final invoicing, payment due dates, disputed charges, taxes, late-payment consequences, subscription renewal, cancellation, refunds and credit terms.] No financial amount, refund policy or automatic renewal period is inserted here. Any right to suspend for non-payment must be proportionate and subject to applicable notice and dispute protections.

## 7. Services, support and changes
The Services are supplied within the scope identified in the order. Tessen may maintain and improve them, subject to agreed change controls and applicable law. A material reduction in contracted functionality must be assessed against the agreed scope and Customer’s rights.

Support coverage, response times, uptime, credits and maintenance rules exist only where an actual SLA or support schedule is expressly agreed. Preview and Project Zero capacity should not be used to promise production continuity. [LEGAL REVIEW REQUIRED: service-change remedies, support schedule and any separately negotiated SLA.]

## 8. Third-party products and integrations
Customer-selected third-party services remain subject to their own terms. Tessen’s responsibility for a provider engaged to perform contracted processing is distinct from responsibility for a service independently selected by Customer. The applicable roles should be identified in the DPA or relevant order.

Customer must authorize connections and respect scopes, licensing and access restrictions. Provider failures may affect workflows. No party may use that fact to disclaim obligations it expressly accepted. Changes in provider data practices must be assessed for disclosure, contractual and transfer implications before continued use.

## 9. AI output, professional use and human oversight
AI results may contain errors, omissions, bias, insecure code or inaccurate citations. Customer must select appropriate review, validation and supervision for its use case, including consequential decisions about individuals. Tessen is not a substitute for regulated professional services unless a separately authorized offering expressly says otherwise.

Customer must not operate illegal or prohibited workloads or remove required transparency. Tessen’s safeguards do not eliminate Customer’s responsibilities, and Customer’s review duties do not eliminate Tessen’s contractual or legal obligations. Regulated or sensitive workloads require separate suitability assessment and any necessary written terms.

## 10. Term, suspension and termination
The order should identify commencement, duration, renewal and termination rights. Material breach should be addressed through the agreed notice and cure process except where urgent suspension is justified by security, harm or legal requirements. Suspend the smallest necessary scope when practicable.

[LEGAL REVIEW REQUIRED: commercial term, renewal, termination for cause/convenience, cure periods and treatment of prepaid amounts.] No period is invented. On termination, Customer should stop use within the terminated scope and the parties should settle accrued obligations according to the agreement.

## 11. Data return, deletion and transition
Customer should specify authorized export contacts and formats before termination. Tessen should return or delete customer personal data according to the DPA and lawful instructions, while explaining any legally retained data and backup handling. Technical availability of a download button does not establish an unlimited export guarantee.

[COMPANY DETAIL REQUIRED: implemented export formats, post-termination access window, deletion process, backup schedule and legal-hold handling.] Continued transition support or custom migration is included only when expressly agreed. Confidentiality and lawful surviving obligations remain applicable to retained material.

## 12. Risk allocation, disputes and general terms
[LEGAL REVIEW REQUIRED: final warranties, liability cap and exclusions, non-excludable liabilities, intellectual-property and other indemnities, claim procedures, insurance requirements if any, governing law and forum.] This draft is intentionally neutral on unapproved economic and jurisdictional choices rather than imposing fictional limits.

Neither party may make commitments for the other without authority. Contract notices and assignment rules must be aligned with the real entity and transaction structure. Entire-agreement and severability clauses should preserve mandatory law and negotiated terms. Related documents are the [DPA](/legal/dpa), [Developer Terms](/legal/developer-terms), [Service Terms](/legal/service-terms) and [Acceptable Use Policy](/legal/acceptable-use).


---

# Data Processing Addendum
Proposed controller–processor terms and completion schedules for business processing.

## 1. Draft status and application
This V1 DPA is a proposed contractual addendum. It is not executed and does not certify compliance. It must be completed, approved and incorporated into an agreement between the actual parties before processor access to covered data. A completed DPA cannot cure processing that is unlawful in practice.

“Customer” is the party instructing covered processing. “Tessen” is the provider identified in the completed agreement. “Customer Personal Data” means personal data processed by Tessen on Customer’s documented instructions to provide contracted Services. Data processed by Tessen for genuinely independent controller purposes must be separately identified and transparently governed.

## 2. Definitions and roles
“Applicable Data Protection Law” means the law actually applicable to the covered processing. “Controller,” “processor,” “personal data,” “processing,” “data subject,” “subprocessor” and “personal data breach” have their relevant statutory meanings. A security event is not automatically a confirmed personal data breach.

Customer may be a controller or a processor authorized by an upstream controller. If Customer is a processor, it warrants sufficient authority to appoint Tessen and issue the instructions in this DPA. Tessen acts as processor or subprocessor only within the documented scope. [LEGAL REVIEW REQUIRED: applicable laws, role allocation and upstream authorization for the actual processing.]

## 3. Subject matter, duration and instructions
The subject matter is providing the contracted intelligence, storage, connected-tool and execution functions selected in the order and Schedule A. Processing continues for the contractual service period and any agreed return/deletion period, subject to lawful retention. Nature and purposes include receiving, storing, organizing, retrieving, transforming and transmitting Customer Personal Data to carry out authorized tasks.

Documented instructions include the executed agreement, agreed configuration, authorized user actions and lawful written directions within scope. Tessen shall process covered data only on those instructions unless applicable law requires otherwise. Where legally permitted, Tessen shall inform Customer of that legal requirement before processing. If an instruction appears to infringe applicable data-protection law, Tessen shall inform Customer and address the issue before continuing the affected activity.

## 4. Customer responsibilities
Customer shall establish a lawful basis, give required notices, obtain necessary consents or authority and minimize submitted data. It shall configure user access, connected-service permissions and retention options within available controls. It shall not instruct prohibited processing or submit data outside the agreed scope without assessment and agreement.

Customer shall communicate relevant restrictions, rights requests and processing changes to Tessen. Customer remains responsible for its own systems and independent recipients. These responsibilities do not relieve Tessen of processor duties or obligations it accepts in this DPA.

## 5. Confidentiality and authorized personnel
Tessen shall limit access to personnel who require it to perform authorized processing and are subject to confidentiality obligations or appropriate statutory duties. It shall maintain access governance appropriate to the risk and remove unnecessary access. Personnel shall be instructed on the applicable confidentiality and handling requirements.

An authorization to process data is not permission to use it for an unrelated purpose or disclose it to another customer. Support and debugging access must be scoped and documented consistently with the agreed security measures. Confidentiality continues for retained covered data after termination.

## 6. Technical and organizational measures
Tessen shall implement appropriate measures identified in completed Schedule B, taking account of risks, data sensitivity, processing context and the requirements of applicable law. Measures should address identity, access control, credential handling, segregation, transmission/storage protections where applicable, resilience, change management, incident response and deletion.

[COMPANY DETAIL REQUIRED: verified technical and organizational measures, implementation scope, exceptions, testing evidence and responsibility matrix.] This draft does not claim that a listed category is already implemented, certified or sufficient. Material changes must not reduce agreed protection in breach of applicable law or the agreement and should be disclosed where required.

## 7. Subprocessors
Tessen may engage a subprocessor only under the agreed authorization mechanism. It shall conduct appropriate diligence and impose written obligations that provide the protection required by applicable law for the delegated processing. Tessen remains responsible for subprocessor obligations to the extent required by law and the executed agreement.

The verified register shall identify legal names, functions, processing locations and other legally required information. [LEGAL REVIEW REQUIRED: specific or general authorization, advance-notice process, objection period and resolution/termination mechanism.] No notice period is invented. A legitimate objection should be assessed in good faith, with a lawful solution agreed before disputed processing continues. User-selected independent services require separate role analysis.

## 8. Assistance with individual rights
Taking account of the nature of processing, Tessen shall assist Customer through appropriate technical and organizational measures in responding to requests to exercise data-subject rights. If Tessen receives a request concerning Customer Personal Data directly, it shall promptly route it to Customer or direct the person appropriately unless law requires otherwise.

Tessen shall not independently decide Customer’s response without authorization except where legally required. Customer must provide enough information for safe identification and scope. Verification should be proportionate and protect unrelated data. The assistance process and any reasonable separately agreed charges must not obstruct statutory rights.

## 9. Personal data breaches
Tessen shall notify Customer without undue delay after becoming aware of a personal data breach affecting covered data, as required by applicable law. Notice shall provide available information about the nature of the breach, affected categories and approximate scope, likely consequences, measures taken/proposed and a suitable contact. Information may be provided in stages where it is not immediately available.

Tessen shall take reasonable steps within its control to contain and address the breach and assist Customer with applicable notification duties. Customer determines its regulatory and individual notices as controller unless law or a separate allocation requires otherwise. [COMPANY DETAIL REQUIRED: operational incident contacts and notification method.] No shorter numerical SLA, reimbursement commitment or insurance coverage is assumed.

## 10. Assessments and regulator cooperation
Tessen shall provide reasonable assistance with legally required impact assessments and prior consultation, considering its processing role and available information. It shall cooperate with competent authorities to the extent required by applicable law and notify Customer of relevant requests where legally permitted.

Customer should identify the use case, risks and required evidence, and must not represent that Tessen has approved a regulated deployment merely by providing documentation. Assistance is limited to matters within Tessen’s knowledge and control without diminishing statutory processor duties.

## 11. Demonstration, information and audit
Tessen shall make available information necessary to demonstrate compliance with applicable processor obligations and allow/contribute to audits, including inspections, as legally required. The parties should agree practical arrangements to protect confidentiality, security and other customers while preserving effective verification.

Existing independent evidence may be used where suitable but cannot replace an audit right that law requires. [LEGAL REVIEW REQUIRED: practical audit procedure, costs, confidentiality, frequency and urgent/regulator exceptions.] No certification or report is asserted to exist, and no procedure may exclude legally mandated access.

## 12. Transfers and location restrictions
Covered international transfers shall occur only with a lawful mechanism and required safeguards. The applicable instrument must match the real parties, roles, data flows and countries. Onward transfers and remote access should be considered, not just the primary storage location.

[LEGAL REVIEW REQUIRED: verified destinations, transfer instrument/modules, completed annexes, UK or other regional additions where applicable, and supplementary measures.] This DPA does not purport to execute standard contractual clauses by reference to an incomplete schedule or guarantee data residency. A binding location restriction must be explicitly agreed and operationally supportable.

## 13. Return, deletion and end of processing
On termination of covered Services, Customer shall choose return or deletion as provided by applicable law and the agreed process. Tessen shall delete existing copies unless law requires retention, explaining the legal basis and protecting retained data against unrelated processing. Backup deletion must follow a completed, disclosed process consistent with the obligation.

[COMPANY DETAIL REQUIRED: export format, return/deletion timing, backup treatment and deletion confirmation process.] No invented retention period applies. A legal hold must be scoped and reassessed; it does not justify unrestricted retention of all customer data. Tessen shall continue required confidentiality and security duties for retained covered data.

## 14. Liability, precedence and completion
Liability follows the executed underlying agreement except to the extent mandatory law or a valid transfer instrument provides otherwise. Any contractual restriction must not impair rights of data subjects or regulators. The DPA controls conflicts concerning its processing subject matter; mandatory transfer clauses take precedence where required.

[LEGAL REVIEW REQUIRED: final governing law, disputes, liability allocation and DPA execution mechanism.] Completion requires the actual parties and contacts, Schedule A, Schedule B, authorized subprocessors and necessary transfer documentation. Until completed and executed, this document is a draft for negotiation.

## Schedule A. Processing particulars
Products: the contracted features identified in the order, rather than every planned Tessen capability. Data subjects: authorized users and individuals whose information Customer lawfully submits, which may include personnel, customers, contacts and collaborators. Data categories: account-linked content, conversations, documents, repository context, files, connected-source data and authorized task results, as actually enabled.

Sensitive or special-category data is not automatically within scope. [COMPANY DETAIL REQUIRED: agreed data subjects, categories, special-category restrictions, purposes, processing operations, frequency, term and competent controller contacts for each deployment.] Describe these particulars before processing, including customer-side restrictions and any shared-controller scenario requiring another arrangement.

## Schedule B. Security and service responsibility record
The completed record must identify measures, responsible party, evidence and limitations for access control, confidentiality, encryption where used, tenancy separation, logging, resilience, restoration, vulnerability handling, incident response, personnel safeguards, physical/provider protections and deletion. It should distinguish customer configuration from Tessen and provider duties.

[COMPANY DETAIL REQUIRED: deployment-specific security schedule and evidence approved by the technical owner.] Aspirational control names are not contractual evidence. Consult the [Subprocessor Register](/legal/subprocessors), [Privacy Notice](/legal/privacy) and [Business Terms](/legal/business-terms) when completing this schedule.


---

# Subprocessor Register & Change Notice
Draft framework for identifying business-data processors and reviewing changes.

## 1. Status and purpose
This V1 register is a draft disclosure framework. No provider entries have been verified for publication in this package. This does not mean that Tessen uses no providers or that no personal data is processed externally. The register must be populated from actual contracts and data flows before an organization relies on it for procurement or DPA approval.

A subprocessor is a provider engaged by Tessen to process covered Customer Personal Data on its behalf. A model provider, hosting vendor, analytics service or support tool may have different roles depending on its actual terms and activity. Technical integration alone does not establish that role.

## 2. Required register fields
Each approved entry should identify the provider’s exact legal name, processing function, applicable product(s), relevant data categories, storage and remote-access locations, role, contract status, transfer mechanism where required, and the date/version of approval. Trading names should not replace the contracting legal entity. Location information should address processing and access, not merely headquarters.

[COMPANY DETAIL REQUIRED: verified subprocessor inventory and completed entries, including model, execution, infrastructure, storage, authentication, support and other actual processing providers.] Do not populate this register with inferred vendors, suggested tooling or a vendor logo found in the interface.

## 3. Register completion workflow
The technical owner should map each external recipient to a real data flow and identify whether content, metadata, secrets or support records are transmitted. The procurement/legal owner should verify the provider contract, role, confidentiality, processing restrictions, security evidence and any onward-processing chain.

Entries should be approved only after the role and lawful access are established. The review record should explain product scope, limitations and any customer configuration that changes the recipient. A provider used only for Tessen’s independent controller activities should be described in the appropriate privacy disclosure rather than incorrectly listed as a customer subprocessor.

## 4. Customer authorization and notices
The executed DPA determines whether Customer provides specific or general subprocessor authorization. Proposed changes should be notified through the agreed channel with the information needed to assess them. [LEGAL REVIEW REQUIRED: authorization mechanism, advance-notice period, customer notification channel and objection/resolution terms.]

The final register should preserve previous versions and effective change dates. Updating a public page does not satisfy a promised direct notice by itself. Emergency replacement may require special handling, but that handling must be agreed and lawful rather than assumed.

## 5. Objections and alternatives
A Customer objection should identify a specific, legitimate data-protection concern and the affected processing. The parties should consider whether the risk can be addressed through additional safeguards, configuration, an alternative provider or suspension of the affected feature. An objection is not automatically a right to control unrelated Tessen suppliers.

If no lawful solution is available, the parties must follow the DPA’s agreed termination or restricted-use procedure for the affected service. No deadline, refund or substitute capacity is promised by this draft. Statutory obligations and required protection remain applicable while resolving the concern.

## 6. Independent connected services
A service selected and authorized directly by a user through Connect may be an independent recipient or customer-appointed provider rather than Tessen’s subprocessor. The distinction must be assessed, explained and reflected in the appropriate agreement. The user’s authorization does not excuse unnecessary access or permit unrelated data use.

Model-provider routing also requires role-specific analysis. Different modes, endpoints or contractual plans can carry different processing conditions. A broad statement that “all providers follow the same policy” should not be used without verification.

## 7. Due diligence and ongoing review
Review should be proportionate to data sensitivity, access scope and service criticality. It should cover provider security and incident processes, deletion/return, confidentiality, onward transfers, model-training uses where relevant and audit information. Certifications should be listed only with verified scope and current evidence.

Material changes in provider practices must be assessed against existing commitments. Remove obsolete entries with a documented record of cessation and data handling. Review the register when adding products or changing routing; do not assume an approval for one product applies to every future service.

## 8. Requests and related documents
Customers may ask for the current verified register, relevant change notices and the appropriate data-processing documentation through hello@tessen.ai. Do not transmit confidential customer datasets with the request. The final legal/privacy contact remains subject to entity confirmation.

This framework should be read with the [DPA](/legal/dpa), [Privacy Notice](/legal/privacy), [Connect Terms](/legal/connect) and [Developer Terms](/legal/developer-terms). It offers a substantive disclosure process while expressly leaving unverified vendor facts open for completion.


---

# Cookies & Similar Technologies Notice
Draft notice for browser storage, authentication and measurement technologies.

## 1. Scope and draft status
This V1 notice covers cookies and similar technologies on Tessen websites and browser-based services, including Web and Platform. Comparable application storage and device identifiers may also be used in mobile or desktop products and require appropriate product-specific disclosure. This is a draft, not a claim that a consent manager has been deployed or that a storage scan is complete.

Cookies are browser-stored values. Similar technologies can include local/session storage, pixels, SDK identifiers and device or request identifiers. They may serve different purposes and have different consent requirements. Calling a value “technical” does not automatically make it legally essential.

## 2. Essential service functions
Authentication/session continuity, security, permission state and request-routing functions may require storage or identifiers to provide a user-requested service. Their exemption from consent, if any, must be assessed against actual purpose and applicable law. They should not be reused for unrelated tracking without the required basis.

Users who block genuinely necessary storage may be unable to sign in or maintain certain preferences. The final notice should identify the actual storage items and consequences. [COMPANY DETAIL REQUIRED: verified essential cookies/storage, providers, purposes, duration and affected domains.]

## 3. Preferences and optional measurement
Preferences may remember language, display choices or user-requested settings. Analytics may measure visits, performance or feature use. Advertising, cross-service tracking and profiling raise separate issues; this draft does not assert that Tessen uses or does not use those technologies.

[COMPANY DETAIL REQUIRED: actual optional analytics, personalization, marketing and embedded-content technologies, including third-party recipients and data links.] Optional categories must not be pre-enabled where valid consent is required. A category label should not obscure several materially different purposes.

## 4. Consent and choice design
Where consent is required, explain the purposes clearly before optional technology runs and provide a genuine choice. Acceptance and rejection should be accessible, understandable and available without misleading design. Consent should be specific enough for the actual purposes, and withdrawal should be practical without implying loss of unrelated essential functionality.

[LEGAL REVIEW REQUIRED: region-specific consent, preference storage, consent renewal, proof of consent, Global Privacy Control or other recognized signals, and any sale/sharing opt-out requirements.] This draft defines the review criteria; it does not certify that a banner or signal-processing mechanism is already working.

## 5. Inventory and third-party content
The completed inventory should identify name or identifier, provider, domain, purpose, category, personal data involved, duration/expiry, first- or third-party status and the activation condition. Session and persistent storage should be distinguished. Do not invent a duration from a vendor’s default documentation without checking actual configuration.

Embedded media, sign-in tools and linked third-party sites may introduce their own storage and tracking. The final page should explain which technologies run on Tessen and which are encountered only after leaving it or intentionally loading third-party content. A hyperlink alone is not necessarily a tracking integration.

## 6. Managing browser and application storage
Browser settings can block or delete cookies and site data. Deletion can sign you out or reset preferences but may not stop future storage or erase server-side records. Private browsing does not guarantee that service providers cannot receive request information. Device settings may provide additional application permissions and identifier controls.

Use the relevant implemented privacy controls or contact Tessen for information about the actual mechanisms. This site does not present a fake preference button that claims to update consent without a connected consent system. Consent controls must be implemented and verified before the final notice refers to them as available.

## 7. Retention, security and privacy relationship
Storage duration should be limited to the purpose and accurately disclosed. Associated server-side information follows the applicable data-retention process rather than a cookie expiry alone. Cookies and similar technologies should not contain exposed authentication secrets beyond the protection appropriate to their design.

The [Privacy Notice](/legal/privacy) addresses purposes, recipients, international processing, retention criteria and rights. This notice supplements it for device/browser technologies and does not supply a universal lawful basis for personal-data processing.

## 8. Changes and contact
Review this notice when introducing a new domain, SDK, embedded service or tracking purpose. Material changes may require renewed choice rather than a silent text update. Keep the inventory and consent implementation synchronized with the published version.

Questions about this draft may be sent to hello@tessen.ai. The contracting/controller entity and legally designated contacts remain subject to the company-detail markers in the Terms and Privacy Notice.


---

# Project Zero Preview Terms
Proposed rules for capacity-limited developer preview access and Node participation.

## 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](/legal/developer-terms), [Node Terms](/legal/node), [Acceptable Use Policy](/legal/acceptable-use) and [Privacy Notice](/legal/privacy). Draft comments may be sent to hello@tessen.ai. Underlying liability and dispute decisions remain open for legal review in the Terms.


---

# Node Terms
Proposed terms for local, private and distributed Tessen compute.

## 1. Scope and status
These V1 draft terms apply to Tessen Node and any authorized local or distributed workloads. They supplement the applicable personal, developer or business agreement. They are not a release announcement, an employment offer or a promise of revenue.

Node is intended to provide local/private/distributed compute participation with user controls. The meaning and operation of each mode must be documented for the released version. A setting label is not, by itself, a data-security or residency guarantee.

## 2. Device authority and prerequisites
Install and run Node only on equipment and network resources you own or are authorized to use. Comply with organization rules, network agreements, device licenses and applicable law. Do not install Node covertly or enroll another person’s resources without informed permission.

You are responsible for selecting suitable hardware, maintaining your operating environment and protecting credentials. [COMPANY DETAIL REQUIRED: actual supported platforms, hardware requirements, update/signing process and installed permission scope.] No supported operating system or public binary is established by this draft.

## 3. Local and private processing
Local execution can still require account services, downloads, telemetry or remote requests. Private mode must be defined by its actual workload and data-flow behavior. Do not assume that “private” means every record stays on-device or that no provider receives data.

[COMPANY DETAIL REQUIRED: verified Local/Private/Earn mode semantics, telemetry, routing, file/network access and isolation behavior.] Product disclosures should make the relevant limits understandable before mode activation. Authorization for one task should not expand into unrestricted access to local content.

## 4. Distributed workloads and access boundaries
Distributed participation must be opt-in according to implemented controls. Workloads should execute only within the granted resource and permission scope. Participants must not inspect, retain, disclose or tamper with another user’s workload data beyond what authorized execution requires.

Do not bypass isolation, use workload access to probe other systems or repurpose data for model training or unrelated analysis. Task assignment is not authorization to contact an external recipient or access additional files. Any handling of personal data requires an appropriate legal role and contractual arrangement before deployment.

## 5. Resources, costs and operational risks
Node may use CPU, GPU, memory, storage, network bandwidth and electricity. Resource use can affect performance, heat, battery life and network costs. Review settings and use available pause/limit controls. Software errors or provider conditions may interrupt work.

The final product must explain actual limits and cancellation behavior. This draft does not guarantee a resource cap, zero hardware wear or uninterrupted operation. Tessen remains responsible for obligations it accepts, and users’ awareness of resource use is not a waiver of non-excludable rights.

## 6. Credits and participation incentives
Any incentive must be described by verified program rules before participation. Credits, if issued, are not automatically cash, securities, transferable property or a wage. Do not claim work that was not performed, manipulate execution receipts or exploit metering defects.

[LEGAL REVIEW REQUIRED: incentive eligibility, calculation, verification, reversals, redemption, expiry, tax treatment and territorial restrictions.] No earnings rate or cash-out promise is inserted. Where a program is linked to Project Zero, its preview limitations and capacity conditions also apply.

## 7. Privacy, confidentiality and customer processing
Account and operational information may be processed under the Privacy Notice. Workload content may be governed by a customer agreement and DPA. Participants’ roles and access to personal data must be assessed rather than presumed to be covered by an ordinary consumer account.

[LEGAL REVIEW REQUIRED: distributed participant role, required confidentiality/processing agreement, transfer implications and eligible workload classes.] Do not send regulated or sensitive customer workloads to an unverified participation pool. A privacy setting cannot substitute for the legal and technical controls the workload requires.

## 8. Updates, pausing and withdrawal
Use supported updates and do not disable security checks in ways that compromise workloads or other participants. Changes to Node behavior must be disclosed consistently with the underlying agreement. The released product must explain whether a pause stops new assignments, active tasks or both.

You may stop participation through the available controls. Completed external effects and records lawfully required for accounting or security may remain. [COMPANY DETAIL REQUIRED: actual shutdown, uninstall, credential revocation, active-workload cancellation and local-data deletion behavior.]

## 9. Misuse, termination and liability
Tessen may suspend participation where resources are misrepresented, workloads are tampered with, security is at risk or law requires action. Provide notice and review where appropriate. Ending participation does not automatically terminate separately contracted services or authorize forfeiture of valid benefits contrary to agreed terms.

Warranty, liability and dispute provisions follow the final underlying agreement and mandatory law, subject to its open review decisions. Related documents are [Project Zero](/legal/project-zero), [Developer Terms](/legal/developer-terms), [Service Terms](/legal/service-terms) and [Acceptable Use](/legal/acceptable-use). Draft comments may be sent to hello@tessen.ai.


---

# Connect Terms
Proposed terms for linking tools, accounts, services and external data.

## 1. Application and draft status
These V1 draft terms supplement the applicable Tessen agreement for Connect and connected-tool actions across Web, Mobile, Code, Browser Extension, Orbit and developer services. They are not confirmation that every integration is available or that provider approval has been obtained.

A connection links a particular account, service or resource within specified permissions. It does not transfer ownership of that account to Tessen and does not grant access beyond the authority of the person approving it. The Privacy Notice and any executed DPA govern the corresponding personal-data processing.

## 2. Authority and consent
Before connecting an account, confirm that you may grant the requested scopes and use the data for the intended purpose. Organization policies or a third party’s rights may limit that authority. Authentication proves access to an account; it does not necessarily prove permission to disclose all its data.

Review the connected identity, read/write scopes and action destinations. A read permission is not a send permission. An organization administrator must not silently expand another user’s authority beyond the applicable agreement and notices.

## 3. Tokens, credentials and scope
Use the supported authorization flow and protect tokens, keys and sessions. Do not paste credentials into conversations or expose them in repositories. Tessen should process connection credentials only for authorized access and protect them according to verified security practices.

[COMPANY DETAIL REQUIRED: actual credential storage, revocation, refresh, scope display, administrative access and permission-checking behavior.] This draft does not promise a particular encryption scheme or universal per-action approval. Technical checks must match the service’s real risk and authority model.

## 4. Reading, importing and context
A connection may retrieve content, metadata, files, contacts or other information within the enabled scope. Retrieved context may be used to answer questions, generate material or support authorized work. Imported material can persist separately from the source service if the feature stores it; the user must be informed of this behavior.

Instructions embedded in retrieved content are untrusted material, not authorization to change permissions or disclose unrelated information. The final service should distinguish source content, user instructions and system controls. Source deletion does not necessarily delete every previously imported copy or generated result.

## 5. Writing, sending and consequential actions
An action may modify a record, send a message, publish content, create a file or affect another person. Review recipients, account identity, scope and important consequences before granting authority. A prior authorization can cover a bounded workflow but should not be interpreted as unlimited permission for unrelated actions.

Users should understand whether work continues unattended and how to cancel it. External effects may be irreversible and a repeated request may create duplicates unless the relevant system prevents them. Tessen should communicate failed or partial actions accurately rather than imply success from a planned action.

## 6. Third-party conditions and interruptions
Connected services retain their own terms, limits, privacy practices and availability. A provider can change its API, revoke access or restrict a feature. Tessen’s obligations for an engaged processor differ from obligations concerning a user-selected independent recipient.

Do not use Connect to circumvent provider restrictions, abuse rate limits, scrape prohibited data or evade opt-outs. Connection availability does not imply legal permission for bulk outreach, surveillance or redistribution. The [Subprocessor Register](/legal/subprocessors) should distinguish the relevant roles.

## 7. Revocation and removal
You may revoke a connection using the controls actually available in Tessen or the provider’s account settings. Revocation should prevent future access according to the actual token lifecycle, but may not undo completed actions or erase previously imported content. Scheduled work depending on the connection may fail or stop.

[COMPANY DETAIL REQUIRED: revocation propagation, cached data, imported-content deletion, active-task handling and retained logs.] The final UI and notice must explain these differences. Uninstalling an application is not always equivalent to revoking an external authorization.

## 8. Organizations, developers and responsibility
Business customers must manage authorized users, service accounts and administrator permissions. Developers must provide their own users with clear notices and control flows. They may not treat Tessen’s connector permission as end-user consent to every downstream disclosure.

The parties remain responsible for the processing and security obligations each actually controls. Tessen’s tools do not replace a customer’s access policy or necessary processing agreements. Sensitive or regulated integrations require suitability assessment before use.

## 9. Incidents, suspension and related terms
Report unexpected access or actions promptly through support, identifying the connected account and request context without exposing credentials. Revoke access if necessary and investigate completed effects. Tessen may suspend a connection to address security, abuse or legal requirements within the underlying agreement.

Read the [Privacy Notice](/legal/privacy), [Service Terms](/legal/service-terms), [Acceptable Use](/legal/acceptable-use) and [Developer Terms](/legal/developer-terms). Governing law, liability and other open legal choices remain in the underlying agreement; this supplement creates no separate jurisdiction or unverified guarantees.


---

# Service-Specific Terms
Proposed rules for intelligence, context, creation, browsing and execution features.

## 1. Scope, status and precedence
These V1 draft terms cover specific Tessen features and supplement the applicable Terms or Business Terms. They are not an announcement of feature availability. Product descriptions, release states and permissions determine which capabilities a user can actually access.

HERO is the core intelligence, experienced through Web, Mobile and Desktop where released. Code, Browser Extension, Orbit and Node are distinct primary products. Memory, Connect, Work, Self, Files and Research are capabilities rather than additional standalone product contracts. A specific supplement governs its stated subject matter; an executed DPA governs customer personal-data processing.

## 2. HERO conversations and context
Conversations may combine current instructions with authorized context to produce answers and content. Context may be incomplete or stale. A conversation’s references to a user, project or source are not a guarantee that all relevant information was retrieved or verified.

Users should review important statements and identify the desired scope. AI outputs can be inaccurate and similar results can be produced for others. The Terms’ content rights and AI limitations apply. A conversational suggestion is not proof that an external task has been executed.

## 3. Memory and Self
Memory may support relevant continuity; Self may organize user-controlled identity, preferences and personal context. System-generated inferences should be distinguished from confirmed user facts. Personalization does not justify undisclosed sensitive judgments or unrelated data use.

[COMPANY DETAIL REQUIRED: actual Memory/Self controls, inference rules, source visibility, correction/deletion and cross-surface synchronization.] Users should be able to correct inaccurate context through the implemented process. No feature description promises a perfect digital twin, complete life record or psychological assessment.

## 4. Files, Library and generated artifacts
Files can contain confidential, copyrighted or personal information. Submit only material you are authorized to process and verify generated documents, calculations, formulas, media and code before relying on them. Preview rendering may differ from the original application or final export.

Storage, export, version history and deletion behavior depend on the actual service. [COMPANY DETAIL REQUIRED: supported file operations, limits, export behavior, version/deletion rules and retention.] A visible artifact link is not a promise of permanent storage. The service must not silently imply that a file was saved, transmitted or shared if that operation did not succeed.

## 5. Research and sources
Research may retrieve, summarize and compare sources. Sources can change, contradict one another or contain errors, and a citation does not establish that the whole answer is supported. Check primary sources for consequential claims and respect source licenses and access terms.

Retrieved pages may contain instructions or malicious content. They do not confer authority to execute actions or disclose information. Research outputs are informational, not a substitute for regulated advice or comprehensive due diligence. Restrictions on private sources and paywalled content remain applicable.

## 6. Work, tasks and scheduled activity
Work can interpret an objective, plan steps and perform actions within granted authority. A requested outcome must be distinguished from the operations authorized to pursue it. Users and administrators should understand the accounts, tools and data involved, especially for external communications or destructive actions.

Scheduled work may run without the user present according to a prior bounded instruction. Cancellation can prevent future steps without undoing completed ones. [COMPANY DETAIL REQUIRED: actual approval gates, cancellation, unattended execution, notifications and task retention.] The draft establishes no guarantee that every requested outcome will be achieved or a particular execution deadline met.

## 7. Code and execution environments
Code features can generate, analyze or execute software and interact with repositories, dependencies and terminals. Validate security, licensing, tests and deployment effects. Generated code may include vulnerabilities or unsuitable dependencies. Do not execute untrusted commands merely because they appear in an AI response.

Environment access must be limited to authorized resources. Protect secrets, isolate risky workloads and review irreversible changes. CLI, IDE and Code Desktop are surfaces under the Code product, not separate legal centers. The [Developer Terms](/legal/developer-terms) address integrations and downstream applications.

## 8. Browser Extension and Orbit
Browser Extension brings Tessen into an existing browser; Orbit is Tessen’s own intelligent browser. Both may use page context within granted permissions, but their access and data flows must be described separately. Neither label implies unrestricted collection of browsing history.

Web content can be misleading or malicious. Browsing assistance should not bypass site permissions, access restrictions or user approvals. [COMPANY DETAIL REQUIRED: released browser permission scopes, URL/page capture, history handling, local storage and remote processing.] Downloads and supported platforms must be verified rather than inferred from a design mockup.

## 9. Mobile and desktop applications
Device permissions, store conditions and operating-system controls affect available functions. Microphone, camera, notifications, local files and background processing require the appropriate authorization. Only real store/build destinations may be presented as available downloads.

App-store purchase terms may govern a transaction made through a store, subject to mandatory law. No refund period, platform support or offline guarantee is invented here. Tessen Web remains a separate access surface; uninstalling an app may not terminate the account, subscription or connected permissions.

## 10. Node, Connect and Project Zero
Node’s resource, workload and participation conditions are in the [Node Terms](/legal/node). Connect’s authority, scopes, external actions and revocation conditions are in the [Connect Terms](/legal/connect). Project Zero is a capacity-limited preview governed by its [Preview Terms](/legal/project-zero).

These supplements should not be interpreted as guarantees of earnings, unlimited free access, private-only processing or identical provider behavior. A mode or entitlement must be assessed against its actual implementation and disclosed constraints.

## 11. Safety, support and continuing review
Every feature is subject to Acceptable Use and applicable law. Use human oversight proportionate to the potential effects, and do not deploy unsupported sensitive workloads. Report errors with relevant identifiers and redacted context rather than secrets or unnecessary personal information.

These terms must be reviewed when adding capabilities or materially changing data flows. Draft status and outstanding markers remain visible until approved. Related documents include [Terms](/legal/terms), [Privacy](/legal/privacy), [Business Terms](/legal/business-terms) and the [DPA](/legal/dpa). No independent SLA, liability cap, training permission or governing-law clause is introduced here.
