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

# Your data

> What Priors stores from your messages and files, who can read it, and what deletion does.

This page explains what happens to the data you send. After you read it, you know what Priors stores, who can read it, what deleting an agent or a thread does, and what you must not send.

You send Priors two kinds of data: what people say, and files.

## What Priors stores

The table below lists every kind of stored data.

| Data | What it is | Where it comes from |
| - | - | - |
| **Memories** | Short facts the agent wrote from observations. Each memory has the fact, the time it refers to, and a link to the observation it came from. | Every `observe`, `observe-file`, and answering call. |
| **Conversation** | The messages of each thread: what was sent and what the agent answered. | Answering calls and `observe`. You read it with `GET .../threads/{thread_id}`. |
| **Sources** | The original bytes of every uploaded document and image. | `observe-file` and image upload. |
| **Activity** | Which agent was used, in which thread, by which subject, and when. Never the text of a message. | Every completed message. You read it with `GET .../logs`. |
| **Usage** | One row per charged request: the call, the word counts, the cost. | Every charged request. You read it with `GET /v1/billing`. |
| **Your labels** | `metadata` on agents and threads, `tags` on observations. | You. Returned to you unchanged. |

Priors does not store your prompts or your model's output, unless you send them as observations.

## Where the data is kept

The data of one organization is kept separate from the data of every other organization. Inside an organization, the memory of one agent is kept separate from the memory of every other agent. Every read is limited to your organization first, so no request can reach the memories, conversations, or files of another organization. Data is encrypted when stored and when sent.

## Who can read what

Your organization owns everything its key creates. No other organization can read any of it, ever.

Inside one agent, `X-SP-End-User` narrows what one request reaches.

| Data | Your key, with no `X-SP-End-User` | Your key, acting for one person | Other organizations |
| - | - | - | - |
| Memories, through answers | yes | yes | never |
| The conversation of a thread | every thread on the agent | only the threads that person created | never |
| Sources | yes | yes | never |
| Activity | yes | yes | never |
| Usage | yes | yes | never |

Memories are never returned as a list. A memory is seen only inside an answer, and only when it relates to the question.

**The agent is the boundary between your customers, not the header.** Give each customer their own agent. The header separates one person's conversations from another's inside a single agent; it does not separate memory. Two people on the same agent can be answered from each other's facts.

## What deletion does

| Action | Effect |
| - | - |
| Delete a thread | The conversation cannot be read anymore. The memories the thread produced stay in the agent. Files uploaded in the thread stay with the agent. |
| Delete an agent | The agent, every thread, every memory, every file, and the activity history cannot be read anymore, by anyone. This cannot be undone. |

Agents do not expire on their own. Only a delete removes an agent.

There is no call that deletes one memory. To make the agent forget something, delete the agent that learned it and create a new one.

## What you must not send

* Secrets, keys, and passwords. An observation can become a memory that the agent repeats in an answer.
* Data that one of your users has not agreed to share with the other people on the same agent. Memory is shared across an agent, so an answer can repeat it to any of them.

## Retention and improvement

Stored data stays until you delete it. Your agreement with SapientPriors states how long data is kept after deletion and how records are used to improve the service.


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