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

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan AI Registry, Atlan's hosted product. The AI registry specification and aireg CLI are maintained separately. /open-source lists publicly reachable signed installers and explains that the source repository and hosted CLI reference currently require GitHub access. Do not claim the repository or its reference docs are publicly accessible. Use these docs for Atlan-specific setup such as the adapter, sign-in and workspaces.

# Manage trace privacy

> Choose whether Atlan stores session content and review your recent trace history.

Open **Settings → Personal → Trace privacy** to see what Atlan keeps from your
agent sessions. Everyone can review their own available history; organization
admins with settings access can change the organization policy.

## Content and usage are separate

| Data | What it includes | Control |
| - | - | - |
| **Session content** | Prompts, agent replies, and the files or data represented in a session | Organization content-storage policy and the collecting device's policy |
| **Usage analytics** | When a session ran, its duration, agents, models, and skill usage | Always stored by this policy |

Turning session-content storage off leaves usage analytics available. A device
configured to drop content continues dropping it even when the organization
allows storage.

## Change content storage

1. Open **Trace privacy** and select **Organization settings**.
2. Review **Store session content**.
3. Change the control. Turning collection on asks you to confirm the effect for
   everyone in the organization.
4. Confirm that the saved state is shown after the request completes.

The policy applies to sessions collected after the change. Enabling storage
does not recover content that was already dropped. Changing it does not erase
content that was previously stored.

## Review your history

The history lists sessions from the last 30 days. Search the list and open a
session to inspect the content available for it. A trace can report that message
content is unavailable while still showing usage evidence.

If the trace has more spans than the page can load, the page states the limit.
If loading later spans fails, retry before treating the visible timeline as
complete.

For control over fields sent by your own application, see [SDK trace
privacy](/tools/sdk/how-tos/privacy). Configure collection at the source before
sending sensitive content.


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