Data privacy
Data falls into four categories: what never leaves your enterprise, what leaves only in encrypted form, what leaves in plain form but is stored encrypted, and what leaves and is stored in plain form. For each, the tables below say who can read the data and how long the cloud keeps it. The 7-day periods are the free account's limits; the paid service has no such limits.
What never leaves your enterprise
Secrets read with sys.secret never leave the agent server, whichever source they come from: the environment, files, or your vault through the vault hook. Conversation state never leaves either when the account uses the conversation state hooks; the agent server then hands each conversation's state to your own code, in plain form, and reads it back from there. Agents run on the agent server, and every call to your APIs, databases, LLM providers and MCP servers leaves from there. What those calls return stays on the agent server, unless an agent writes it into its output or into a conversation variable. The log command writes to the agent server's own log, and nothing in that log is sent to the cloud.
What leaves only in encrypted form
The agent server encrypts these before sending them, and the cloud stores the ciphertext without ever decrypting it. See Encryption for who holds the key.
| Data | Who can read it | Kept for |
|---|---|---|
| An agent's const the fixed values the agent reads as const.name | Developers, in the UI; the account's agent servers decrypt it to run the agent | As long as the agent, or a draft of it, exists |
| Conversation state variables, prompt history, output, where an agent paused; not stored in the cloud at all when the conversation state hooks are set | Only the user whose conversation it is; the account's agent servers decrypt it to answer that user's next request | 7 days after the last use; pinned conversations indefinitely |
What leaves in plain form but is stored encrypted
| Data | What the cloud does with the plain text | Who can read it | Kept for |
|---|---|---|---|
| The user's query | Finds the matching agent. The shortened query is then stored encrypted as the conversation title, and the full query is stored encrypted on the execution record. | Only the user who typed it | Title: with the conversation. Execution record: 7 days |
| Agent descriptions | Indexes the agent for search. The plain text is held in memory for that and never stored. | Developers and above | Life of the agent |
| Long-term memories written by agents with the memory command | Embeds the memory text for semantic search. The label is stored in plain form. | Agents run by the user the memory belongs to | A year after the memory was last used in a query, or until the agent that stored it is deleted |
What leaves and is stored in plain form
Everything else. The cloud works with these directly: it checks definitions, serves configuration and profiles to your agent servers, and aggregates execution records into the reports. Passwords and license keys are stored as hashes.
| Data | Who can read it | Kept for |
|---|---|---|
| Agent definitions with titles, tags, prompts and past versions | Developers and above | Life of the agent; past versions 7 days |
| Drafts | The developer who owns the draft | Until published or deleted |
| Execution records agent name and version, result code, error message, command path, duration, LLM cost | Developers, in the agent reports; administrators, in the usage report | 7 days |
| Configuration agent servers, allowlist, limits, authentication | Developers or administrators, by part | Life of the account |
| Profiles LLMs, APIs, databases and MCP servers; a secret in a profile is a sys.secret reference, not the value | Developers and above | Life of the account |
| Users email address, name, role, UI preferences | Administrators and the owner | Until the user is deleted |
| Audit log what changed and who changed it, as field names, never values | Administrators in the UI; developers and above through the API | 7 days |
| Messages to Search2o sent from the UI | Search2o support | One year |
Who else can see it
Search2o Cloud runs on Google Cloud Platform. Search2o staff, and Google as the provider of the underlying infrastructure, can in principle see the data stored in plain form. With the default setting the account's key is managed by Search2o, so Search2o and Google can in principle read the encrypted data as well. With end-to-end encryption the key never leaves your enterprise, and neither Search2o nor Google can read what is stored encrypted. The privacy policy is authoritative.