# privacy

what data the service stores, why, for how long, and who else touches it.

updated 2026-11-15

> draft: not reviewed by a lawyer. do not rely on it before launch.

This describes what the service stores when you use the API, the dashboard, the CLI, the MCP server or the browser extension. The operator's legal name and contact address go here before launch.

## what we store

- **Account**: your Clerk user id and organization, your role, and the projects and API keys you create. Keys are stored as a SHA-256 hash; the secret is shown once and never stored.
- **Runs**: for each action you run, the domain, action id, status, risk class, the tier used, timings, a step trace (short, redacted notes), the typed output of the action, postcondition results, and a digest of the input. The input itself is kept only while a run can still execute and is cleared when it finishes.
- **Ledger**: a hash-chained record of finds, reads, runs, policy decisions and approvals. It holds ids and digests, never page content or credentials. Search queries are stored as digests.
- **Approvals**: the exact payload a person is asked to approve, with its hash and decision.
- **Search provider keys** you configure: sealed with AES-GCM and never returned.
- **Audit log**: who changed keys, policy, providers, webhooks and claims.

## what we do not store

Cookies, passwords and session tokens of the sites you act on. In client-side runs they stay in your browser; the extension reports only typed outputs and booleans about what it observed. Opt-in telemetry carries outcomes only.

## page content

`read` and action outputs are fetched on your request and returned to you. Pages may be cached to answer repeated requests; the cache key is the URL, not you.

## who else touches data

See the subprocessors page. Search providers you configure receive your search queries and nothing identifying your organization.

## your choices

You can revoke keys, delete projects and webhooks, and ask for export or deletion by contacting the operator. Deleting a project removes its runs and ledger.

## retention

Run records and ledger entries are kept for the life of the project unless deleted. Demo accounts and their data are deleted after 8 hours.
