Tarseek Legal Center

Data Practices & Retention

Effective

September 2026

Last updated

September 2026

Version

1.0

This page is a plain-language companion to the Privacy Policy. It describes how Tarseek handles different classes of data.

1. API requests

API prompt and output content is not retained long-term by Tarseek by default. Usage metadata may be retained. Temporary content retention may be required for debugging, abuse, security, or delivery, and is time-bounded and access-controlled.

2. Chat

Hosted Chat history may persist because storage is an explicit user-facing feature. Users can request deletion of Conversations.

3. Memory

Memory, if offered, is separate from Chat history: persistent information, a stated purpose, user control, deletion, disablement, and its own retention period. Memory is not assumed to be enabled until it appears in the product.

4. Files

Uploads are processed to fulfill a request and may be transmitted to Model Providers. Files attached to Chat may be stored with the Conversation. Files used only for a single API call are not kept long-term by Tarseek by default.

5. Usage metadata

Tarseek may retain Models, providers, token counts, pricing, timestamps, latency, errors, routing, request IDs, and API-key identifiers for billing, history, support, and security.

6. Security logs

Security and fraud information may be retained where reasonably necessary, including IP addresses, authentication events, and abuse signals.

7. Backups

Deletion from primary systems may lag in backups until those backups expire or are rotated.

8. Account deletion

When an account is deleted, Tarseek deletes or de-identifies Customer Content that is no longer needed, while retaining billing, tax, and legal-hold records as required. Provider-side copies may remain under provider policies.

9. Zero Data Retention

Zero Data Retention (ZDR) means a Model Provider is represented as not retaining prompts/outputs beyond fulfilling the request. Tarseek will only label a deployment as ZDR when that representation has been verified. Unverified endpoints are not marked ZDR.