# Privacy

> The MCP server reads and writes one person's memory inside one app, and nothing else.

## What a call reads and writes

Each call is scoped to the key it uses. A person's key (`fsk_`) reaches only that person's memory. An app key (`fsa_`) reaches the app's people and setup.

- `ingest_text` writes a note or durable fact into that person's memory.
- `assemble_context` reads ranked context from that person's memory and connected sources. It is read-only.
- `action_history` reads the app's recorded actions for that person, newest first.
- `provision_user` adds a person or returns the one that exists. It works with the app key.
- `get_setup_bundle` returns the setup bundle for the app's agent: key variable names, never key values. It works with the app key.

Each app's data is separate. Each person's memory is separate. Every request is checked against the key.

## What the server does not do

- It does not stream conversation transcripts into memory. `ingest_text` is for text notes and durable facts only.
- It does not let a sign-in token make an owner-only change. A token comes only from the app's owner signing in on the Harny console.
- It does not claim a certification. See [Security](/security) for the security basics.

## Connected sources

`assemble_context` reads connected sources for the person whose key you hold. `configure_oauth` starts connecting one source and returns the link the person opens to approve it. Harny reads only that person's connected account. Disconnecting ends access.

## Erase a person

To erase everything for one person, call the Memory API:

```
DELETE /v1/users/{user_id}/data
```

To delete specific data points sent through the Memory API, use:

```
DELETE /v1/memory/data-points/{sourceId}
```

This also deletes the memories built on that data point. You can send up to 1,000 ids in one bulk call. Deletes are free. The Memory API pages describe both routes in full.

## Check what is stored

`GET /v1/memory/usage` shows the month's count. Use `diagnose` through the MCP server to see where the app's Harny connection stands and how fresh each connected source is.

## Next

- [MCP keys and access](/docs/mcp/keys-and-access)
- [MCP security](/docs/mcp/security)
- [Memory API overview](/docs/memory-api/overview)