Contents
1. Status, scope and accountable entity
This Privacy Notice forms part of Tessen Legal Center V1 and explains the personal-data handling described below. The version and effective date displayed with the published document identify the applicable notice. Descriptions of a feature apply only where that feature is actually available; this notice does not announce unreleased functionality or claim independent legal counsel certification.
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.
Tessen, Inc., a Delaware corporation, acts as controller where it determines the purposes and means of processing for its own account administration and service operations. Business processing performed on a customer's documented instructions is governed by the applicable executed processing agreement. Privacy inquiries may be sent to hello@tessen.ai or Tessen, Inc., 350 Sansome St, Suite 820, San Francisco, CA 94104, United States. This general contact does not designate a data-protection officer or statutory regional representative.
The incorporation record identifies Tessen, Inc., a Delaware corporation, file number 10801477, incorporated October 12, 2026. Incorporation alone does not determine a processing role or appoint a regional representative. The roles described in this notice and the applicable customer processing agreement depend on the actual processing activity.
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.
Account processing includes identity subject, email/name and authentication records; service processing can include conversations, files, memories and workspace permissions. Billing uses Stripe transaction references and wallet/ledger evidence. Stripe-hosted Checkout collects payment and, where enabled, invoice billing details; collection fields vary by flow. This notice does not assert that Tessen stores complete card numbers.
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. Public Web and Platform browser loads include Cloudflare Web Analytics and same-origin RUM submission. Web authentication uses a host-only Secure HttpOnly SameSite=Lax session cookie with an eight-hour lifetime; OAuth handshake cookies support state, PKCE and return navigation. Auth runs with cross-subdomain cookies disabled. These observations do not establish a complete inventory of authenticated or product-specific storage.
Production observations confirm Cloudflare Web Analytics on tessen.ai and platform.tessen.ai: a Cloudflare-hosted beacon loads and submits same-origin performance/usage telemetry to /cdn-cgi/rum. This replaces the legacy notice’s inaccurate categorical statement that no third-party analytics runs. Fresh anonymous observations of these public pages found no cookies or local/session-storage keys during that observation window; this is not a claim about all authenticated features, vendor data handling, legal classification or required choices.
The reviewed signed-out Web chat flow does not save the exchange into an account conversation history. Requests still pass through Tessen services and relevant model/infrastructure providers. Operational/security processing and provider-held copies can exist according to their actual configuration and terms. Closing a tab is not a promise that all recipients have deleted their records, and signed-out or incognito operation is not a blanket zero-retention guarantee.
5. Purposes and lawful grounds
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.
Personal information is processed to provide the requested service, secure accounts, meter and administer transactions, handle support and meet legal obligations. Each purpose uses the lawful basis applicable to that processing and jurisdiction; optional processing uses consent where required. 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.
Relevant prompts, authorized context and tool inputs are transmitted through Tessen’s Gateway to the services needed to produce the requested result. Provider roles, retention, safety review and training settings differ by service and contract. No blanket zero-retention or no-training representation is made without verified settings and agreements. This notice neither grants blanket authorization to train on user content nor represents that every provider follows a blanket no-training policy. Processing beyond the requested service requires the applicable notice, authority and controls.
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.
Web memory records are scoped to a user, organization or project, with authorization applied before retrieval. Records carry source and confidence information; supported controls allow viewing, correction and deletion. Optional memory expiry is recorded per item. Workspace behavioral learning records named interaction metadata and is enabled when no disabling preference exists; its disable control is distinct from model-training permissions. 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 notice does not claim that such consequential decision-making is either present or absent in every service. AI assistance and personalization must not be represented as an authoritative consequential decision about a person. Any solely automated decision with legal or similarly significant effects requires the applicable assessment, notice, safeguards and review process before use. 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 Provider and Subprocessor Disclosure identifies evidenced provider functions and expressly distinguishes unverified contractual roles from an authorized customer subprocessor list. Operational service providers evidenced for the reviewed service include Google Cloud infrastructure/authentication hosting, Cloudflare edge/storage/analytics, Stripe payment processing, Resend transactional communications and configured Modal inference hosting. Configuration alone does not establish whether a provider acts as a processor, subprocessor or independent controller, its contracting legal entity or every processing/access location. Customer-selected integrations require a separate role analysis. This public disclosure does not replace any completed list required under an executed customer DPA.
10. International processing
Remote access, provider routing and hosting may involve processing in more than one country. This notice provides no data-residency guarantee and names no unverified transfer destination. Questions about applicable transfer arrangements and safeguards may be sent to hello@tessen.ai; a cloud deployment region alone does not establish those arrangements.
Reviewed production Cloud Run services and production Cloud SQL are configured in us-east1. Cloudflare and other providers may process information in other locations. No all-data residency promise follows from a database region. The provider disclosure states which location facts are evidenced and which contractual/location particulars have not been verified. It does not execute transfer instruments or certify their sufficiency. Applicable transfer safeguards remain required for the affected processing. 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.
Web source provides expiry deletion for expiring memories and operational API-request rows and a thirty-day behavioral-learning window; expiry of credentials and entitlements instead stops their use and is not automatic audit-record deletion. Production Cloud SQL tessen-v1 has automated backups enabled, eight retained backups and seven-day point-in-time recovery logs. Financial records and vendor copies have separate requirements. 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.
The reviewed production Cloud SQL configuration retains eight automated backups and seven days of point-in-time-recovery logs; a backup count is not a promise of an eight-day deletion period. The file bucket’s observed seven-day lifecycle rule aborts incomplete multipart uploads and does not expire completed files. Source-level memory/request-log expiry and prepared enquiry-retention rules must not be described as a complete, actively enforced production deletion schedule without execution evidence. Financial records, legal evidence, backups and vendor copies need their own approved retention and exception rules.
The new agreement-onboarding implementation remains behind inactive production controls. When approved versions and the controlled release are enabled, it records canonical identity, agreement/version/hash, server UTC time, affirmative choices and organization representative attestations where applicable. Contract assent and privacy-notice acknowledgment are distinct records; neither is optional processing consent or authorization to train models. The approved legal-evidence retention rule must be specified before activation.
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.
Where applicable law provides them, individuals can request access, correction, export, deletion, restriction or objection and withdraw consent. The Web account export is session-only, owner-scoped JSON; account erasure requires signed-in confirmation. These technical controls do not replace applicable rights-request and appeal duties or legally required exceptions. A contact address or account control is not, by itself, evidence that every jurisdiction-specific procedure has 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. Use by children is governed by the approved eligibility policy and applicable law. Collection of children’s information requires any legally necessary authority, safeguards and response process. Do not submit information about children without the required authority and safeguards.
Material changes to this notice should be communicated in an appropriate manner and consent sought when required. Version history identifies published notices and their effective dates. Review Cookies, Connect, Node and the DPA for their specific subject matter.