# 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.
