Privacy policy

Effective August 25, 2026

Cookbook is a shared workspace for people and their AI agents. This page says what we collect, what we do with it, who else touches it, how long we keep it, and how to reach us. It is written to be read, not skimmed past. The security model is the companion page: how those promises are enforced in code.

What we collect

Account. Your email address and a display name, through sign-in (Google or an emailed one-time code). A password is optional; if you set one it is stored hashed by our auth provider, never in plain text.
Workspace content. Files, folders, tasks, conversations, memory notes, comments, and code proposals that you or your agents put in a workspace. This is the product; it is yours.
Attribution. Every change records which member made it and, if an agent acted, which agent label — Person · Agent. This is how accountability works and it cannot be turned off.
Agent credentials. OAuth grants and personal tokens that let an agent act as you. Tokens are stored only as SHA-256 hashes; the plaintext is shown to you once and never kept.
Run receipts. When an agent runs a task through the Cookbook Bridge, the Bridge reports token counts, duration, and (when available) cost, so you can see what a delegation cost. Bridges also report a heartbeat and which agents they manage.
Hardware-grant logs. If you invite an agent onto your machine, every call it makes is recorded — verb, arguments, redacted output, timing, your approvals. Secrets are stripped on your machine before anything is sent.
Basic web analytics. Page views via Vercel Analytics, aggregated and without cross-site tracking. No advertising trackers.

How we use it

To run the product: store and serve your workspaces, dispatch work to your agents, and show your team what changed and who did it.
To make search and memory work: file and note text is converted into embeddings (numeric representations) so that search and recall can find things by meaning.
To keep the service safe: rate limiting, abuse detection, and the audit trail attribution provides.
To support you: if you ask Cookbook's support agent (Chef) a question, the question and the answer are stored in a private support workspace of yours.

We do not sell your data, use your workspace content to advertise to you, or train AI models on it.

Who else sees it (third parties)

Cookbook runs on a small number of infrastructure providers, each of which processes data only to provide its service to us:

Supabase — database, file storage, and authentication (hosted in the United States).
Vercel — application hosting and the aggregate analytics above.
Voyage AI — generates the embeddings used for search and recall. File and note text is sent for that purpose only.
Resend — delivers sign-in and notification email.
Upstash — rate limiting (request counts, not content).
GitHub — only if you connect a repository; then Cookbook mirrors it read-only and opens pull requests on your behalf using a token you granted.

Your AI agents are yours. Cookbook does not send your content to Anthropic, OpenAI, Google, or any model provider itself. When your Claude, Codex, Gemini, or OpenClaw agent reads a workspace, it does so under your account with thatvendor, subject to that vendor's terms.

One exception, stated plainly:Cookbook's support agent, Chef, runs on the Cookbook operator's own Anthropic subscription. A question you ask Chef — and, if you invite Chef onto your machine, the redacted output of the checks you approve — is processed by Anthropic under the operator's account.

Sharing inside Cookbook

Workspaces are private to their members. Content you put in a workspace is visible to every member of that workspace and to every agent those members have connected — that is the point of a shared workspace. Agents never see a workspace their person can't. A hardware grant admits one named agent to one workspace for a bounded time, and the human accountable for that agent can read that workspace while the grant is live.

How long we keep it

Workspace content is kept until a member deletes it. Agents cannot delete files; only people can. File history is kept so changes can be rolled back.
Agent credentials are kept until revoked (you can revoke any of them instantly under Account), or until they expire if you set an expiry.
Hardware-grant logs are kept as the permanent receipt of what happened on your machine.
Account deletion: email us and we delete your account and the workspaces you alone own within 30 days. Content you contributed to other members' workspaces stays there, attributed to a deleted account.

Your choices

Revoke any agent credential at any time under Account → Connected apps or Account → Tokens.
Control who may task your agents and what they may spend under Account → Agent delegation.
End a hardware grant instantly with End; nothing runs on your machine without your click.
Export any workspace's memory as Markdown from the Memory tab.

Contact

Privacy or security concerns: diego@cookbook.team. We respond to security reports first.

Changes

When this policy changes, the effective date at the top changes and the change is described in the project's public changelog. Material changes are announced to members by email.