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

# Data handling: storage, retention and deletion

> MITHUNAI keeps your data in Germany until you delete it. What is stored, what you can delete, backups, and the incident response in place today.

MITHUNAI stores your organisation's data on its servers in Germany and keeps it until it is deleted: nothing is removed on a schedule, and no retention period has been set. You can delete sources and conversations yourself. Deleting or exporting a whole organisation needs a request to MITHUNAI, because there is no self-service path for either yet. Your content is not used to train models.

## What is stored

| Data | Kept | How it is removed |
| - | - | - |
| Your knowledge: sources, their documents, uploaded files, the index built from them | While the source exists | [Delete the source](https://docs.mithunai.com/knowledge/sources.md): everything it produced goes with it |
| Conversations, including your widget visitors' | Until deleted | [Delete a conversation](https://docs.mithunai.com/api-reference/conversations/delete-conversation.md) |
| Chat threads | Until deleted | The thread's menu in [Chat](https://docs.mithunai.com/chat/conversations.md) |
| Accounts: email address, display name, password hash | Kept | Removing a member ends their access to your organisation; the account itself stays |
| Your organisation, its members, roles and branding | Kept | On request to MITHUNAI |
| Saved connection tokens, encrypted | While the connection exists | [Delete the connection](https://docs.mithunai.com/knowledge/connections.md) |
| Usage records: counts and token totals, with no question, answer or person | Kept | Not removed |
| Audit records | Kept | Not removed |
| Invitation records | Kept after use, revocation or expiry | Not removed |
| Password-reset links | 30 minutes, as a digest | Expire |
| Support sessions | A week after they end, so you can review them | Expire |
| Server logs | A bounded amount per service, overwritten as they rotate | Rotation |

Deleted data remains in backups until those backups are replaced. See [Backups](#backups).

## What MITHUNAI does with it

* It is used to answer your organisation's questions, run its sources and show its analytics, and nothing else. No other organisation can retrieve it.
* **It is not used to train models.** The passages relevant to a question are sent to the model provider with the question, under that provider's terms. See [Subprocessors](https://docs.mithunai.com/trust/subprocessors.md).
* Credentials detected in your content are redacted before it is indexed. Detection cannot catch every format, so do not rely on it to make a secret safe to ingest.

## Export and deletion of an organisation

There is no self-service export of an organisation's data and no self-service deletion of an organisation. Your conversations, sources and analytics can be read through the [HTTP API](https://docs.mithunai.com/api-reference/introduction.md). For a full export or deletion, ask your MITHUNAI contact.

## Requests from individuals

A person can change their own password, and an Owner or Administrator can remove a member or delete a conversation. Other requests from individuals, such as access to or erasure of their data, are handled by MITHUNAI on request; there is no tooling for them in the product yet.

## Backups

The deployment includes a nightly database backup and a restore procedure that has been rehearsed. The 30 most recent backups are kept and older ones are replaced. Recovery is to the last completed backup: there is no point-in-time recovery, no second server, and no recovery-point or recovery-time commitment. Whether backups are encrypted and copied off the server is not yet settled; ask your MITHUNAI contact before relying on either.

## Incident response

MITHUNAI has written procedures for restoring the service when a component fails. It does not yet have a written security incident response plan, a breach notification procedure with a committed timeframe, or monitoring that alerts a person around the clock. To report a security issue, see [Security](https://docs.mithunai.com/security.md#report-a-security-issue).

## Related pages

* [Security](https://docs.mithunai.com/security.md): isolation, access control and untrusted content.
* [Shared responsibility](https://docs.mithunai.com/trust/shared-responsibility.md): who does what.
* [Compliance](https://docs.mithunai.com/resources/compliance.md): what MITHUNAI can and cannot claim.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.