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

# Privacy and data handling

> Understand what the Recallium client sends to Recallium Cloud

Recallium Cloud is a managed service. Your agents reach it through MCP, and the client sends two kinds of data: memory content and client telemetry.

## Memory content

Memory content is sent to Recallium Cloud when your agent explicitly saves a memory on your behalf.

Choose the project that matches the sensitivity of the work you want Recallium to retain.

## Client telemetry

The client can send edit metadata that helps Recallium connect memories to the work performed in a session. The sensor sends metadata such as:

* File paths
* Hashes
* Edit and activity counts
* Git branch and commit provenance

The sensor does not send source file contents. It supports file-link suggestions and provenance for memories created through MCP.

<Info>
  Memory text is separate from sensor telemetry. Your agent sends memory text when it uses a Recallium memory tool.
</Info>

## Inspect your connection

Use the CLI to see which server your installed client is using:

```bash theme={null}
npx -y recallium status
```

Use the diagnostic report to inspect each connected agent:

```bash theme={null}
npx -y recallium doctor
```