Contents
1. Scope, status and precedence
These V1 terms cover specific Tessen features where released 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.
Web memory and behavioral learning expose separate owner-scoped controls. Source/confidence distinguish a stored fact from an inference; supported memory edits/deletions and learning disable are separate from model-training permissions. 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. Web file uploads use server-generated owner-prefixed paths and deployed Cloudflare R2 storage. The reviewed Web limit is 25 MiB per ordinary file; the separately routed direct-media path declares a 512 MiB ceiling with the media service remaining authoritative. Supported formats and extraction failure states are reported by the service. Account export provides owner-scoped JSON, not a promise to export every raw file or preserve every version forever. 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. Work proposals and execution records distinguish proposed, approved and completed actions. Scheduled execution, cancellation and external effects follow the actual capability’s controls; a conversational plan alone is not proof of execution. These terms do not 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 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. Browser features apply only to the separately released product and its declared permissions. The effective disclosure identifies which pages, URLs, history or content can be captured, local storage and remote processing; a design or download link does not establish those capabilities. 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. Connect’s authority, scopes, external actions and revocation conditions are in the Connect Terms. Project Zero is a capacity-limited preview governed by its Preview Terms.
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. Published versions and effective dates identify changes to the applicable text. Related documents include Terms, Privacy, Business Terms and the DPA. No independent SLA, liability cap, training permission or governing-law clause is introduced here.