> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Protection

**We handle content submitted to the platform (prompts, files, agent configuration) and usage records with controls that cover the full lifecycle:** collection needed for the service, protection, limited use, and disposal.

<Info>
  This page describes Tess AI Platform data-protection practices. For privacy and data-subject rights, see [Privacy](/Privacy).
</Info>

## Protection controls

<CardGroup cols={2}>
  <Card title="In transit">
    Communications between the customer’s browser/API and the platform use modern encryption. This prevents content from being read or altered by third parties while it travels over the public network.
  </Card>

  <Card title="At rest">
    Persisted data — including databases and files — remains encrypted in storage services. Even if the underlying media were accessed at the physical layer (cloud provider responsibility), content remains logically protected.
  </Card>

  <Card title="Classification and handling">
    We distinguish categories such as identity, customer content, operational telemetry, and billing metadata. Each category has rules for who may access it, how long to retain it, and how to dispose of it.
  </Card>

  <Card title="Multi-tenant isolation">
    Every read and write validates the organization/workspace context. An agent, file, or history is only available to people with permission in that account — there is no cross-customer “global view.”
  </Card>

  <Card title="Payments">
    Sensitive card data is handled by specialized payment processors. Tess keeps the subscription and billing references needed to operate the service and does not store the full card number.
  </Card>

  <Card title="Retention and deletion">
    We retain data for as long as needed for the contract, operations, and legal obligations. Deletion requests and data-subject rights are handled through official channels, within the perimeter Tess controls.
  </Card>
</CardGroup>

<Tip>
  Your prompts and files do not train Tess’s models.
</Tip>

## Customer responsibility

The customer remains responsible for the lawful basis and appropriateness of content they submit to the platform (for example, third-party personal data in prompts or uploads).

## Next steps

* [Privacy](/Privacy)
* [Tess Commitments](/Tess-Commitments)
* [Responsibilities](/Responsibilities)