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

# Privacy

> Understand what Anam retains during Zero Data Retention sessions, what ZDR excludes, and how Enterprise customers enable it for personas and sessions.

## Zero Data Retention

For the governing documents, see Anam's [Privacy Policy](https://anam.ai/privacy-policy), [AI Governance Practices](https://anam.ai/ai-governance), and [Data Processing Addendum](https://anam.ai/data-processing). Review these alongside your agreement and deployment configuration rather than treating an integration mode as a retention policy.

Enterprise customers can enable Zero Data Retention at a persona level or at the session level (for ephemeral sessions).

When enabled, Anam does not persist any customer content - including conversation transcripts, user audio, TTS text, LLM prompts/responses, or session recordings. Processing occurs in volatile memory only. Anam retains operational metadata necessary for billing, service delivery, and security, including: session timestamps and duration, usage metering, error codes, performance metrics, and infrastructure logs (retained for 30 days). Account-level data (organization info, API keys, subscription) is retained as standard. Support and troubleshooting capabilities may be limited for ZDR-enabled sessions.

Turning off the recording or transcript with [`dataRetention`](https://anam.ai/docs/personas/session/recordings#turn-recording-and-transcripts-on-or-off) is not Zero Data Retention. Anam still stores the rest of the session report.

Zero Data Retention does not apply to any images used in one shot persona creation and/or any files uploaded to a persona's knowledge base.

### Enabling Zero Data Retention

On Enterprise plans, Zero Data Retention can be enabled via the `Advanced` tab of the lab, or via persona configuration for either stateful or ephemeral personas. See the [API Reference](https://anam.ai/docs/api-reference/personas/create-persona.md) for more details.

```javascript theme={"system"}
const personaConfig = {
	name: "Cara",
	avatarId: "071b0286-4cce-4808-bee2-e642f1062de3",
	avatarModel: "cara-4",
	voiceId: "de23e340-1416-4dd8-977d-065a7ca11697",
	llmId: "a7cf662c-2ace-4de1-a21e-ef0fbf144bb7",
	systemPrompt: "You are Cara, a helpful customer service representative. You're friendly, knowledgeable, and always try to solve problems efficiently. Keep responses conversational and under 50 words unless explaining something complex.",
	zeroDataRetention: true,
};
```

> [!NOTE]
>
> Not all LLMs and voices support zero data retention mode, when enabling zero data retention you may have to switch LLM or voice before you are able to publish and use your persona.

## Confirm retention for your deployment

Under section 6 of Anam's [Privacy Policy](https://anam.ai/privacy-policy), non-ZDR session recordings are retained for **up to 30 days**. Session reports, including transcripts, analytics, summaries, and generated insights, remain until the customer deletes them. A recording may be unavailable sooner. A signed download URL can also expire before the recording is deleted. Check the policy and your agreement for the applicable terms.

For audio-passthrough and turnkey deployments, confirm which rules apply to each data category:

* Session audio and video, including conversation recordings.
* Session reports, transcripts, analytics, and summaries.
* Operational metadata and logs.
* Source images used to create avatars and uploaded knowledge files.
* Files produced by script-to-video jobs.
* Data sent to external LLM, TTS, and other integration providers.

Use the current policy and your agreement for the applicable handling, location, and duration. Do not apply a recording retention period to every category, and do not use a signed download URL's expiry as a data-deletion deadline.

For available session operations, see [get session recording](https://anam.ai/docs/api-reference/sessions/get-session-recording.md), [delete session recording](https://anam.ai/docs/api-reference/sessions/delete-session-recording.md), and [delete session](https://anam.ai/docs/api-reference/sessions/delete-session.md). Check each operation's availability and retention restrictions.

For engine-routing controls, see [session regions](https://anam.ai/docs/personas/session/regions.md). Confirm any contractual residency requirement separately from the routing configuration.

## Data Processing Addendum

Read the [DPA](https://anam.ai/data-processing) and [Terms of Service](https://anam.ai/terms-of-service) for the agreement that applies to your use of Anam. If you need confirmation or agreement paperwork for a self-serve or another plan, contact [Anam Support](mailto:support@anam.ai) with your plan and requirements.

DPA applicability depends on your agreement. The plan requirement for enabling ZDR does not determine whether a DPA applies.


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