Sheet L-01 · Legal
Privacy
What we hold, why we hold it, and what happens to the content your agents read.
Your account
CodeBook has no sign-in of its own. Your account lives with the Bookbag account service, which holds your name, email address, profile picture and the organizations you belong to. CodeBook stores a reference to that account and the profile it needs to show you on a card.
Your workspace content
Factories, workflows, cards, comments, attachments, agents and the skills you have edited are stored for your organization and are readable only by members of the workspace they belong to. Authorization is checked on the server for every write, against the workspace the thing belongs to — not in the browser.
Conversations with a worker
A chat session belongs to the person who started it. Other members of the workspace cannot list your sessions and cannot open one by guessing its address.
Your own manager chats in a factory can read each other and keep notes in a shared memory, which outlives the chat that wrote it. That sharing stops at you: it does not reach another person, and agents working cards do not read it. You can read, edit and delete those notes, or turn the memory off.
Conversations we save from your own tools
When you use CodeBook from Claude Code, the CodeBook plugin saves that session to CodeBook: what was said, each tool call and its result, and the conversations of any sub-agents. It saves only sessions that call CodeBook. This is on by default, with a notice in the session and a switch to turn it off. What is said while it is off is never saved later.
ChatGPT and Claude’s chat tab do not show us your conversation. From those, something is saved only when you ask for it or import an export.
We remove anything shaped like a key or password before saving, on your computer and again on our server. This is best effort: it recognises formats and names, not meaning, so a password typed into an ordinary sentence would not be found. Avoid pasting secrets into a session.
Saved conversations can be read only by the person who saved them, with no admin view. If one is linked to a factory and you leave its organization, you stop being able to read it. They are kept for a year by default. You can choose 30, 90 or 180 days, or until you delete them, and you can delete one or all of them at any time. If you carry a saved conversation on in a new chat, that chat keeps its own digest of it after the original is deleted.
What reaches a model
When a worker runs, the card it is working on is sent to the model that serves it: its fields, checklists, discussion and attachments, together with the agent’s skill and the column’s instructions. Nothing else from your workspace is included.
A manager works across its factory, so what it reads for you reaches its model: the stations, the cards and their runs, your own conversations with that factory’s agents, your manager chats and memory, and any saved conversation you carry on with it.
An organization can run on our models or on its own provider and keys. With its own keys, the content goes to that provider under your agreement with them and is metered by them.
What we keep about a run
Every run leaves a job record: what triggered it, which worker ran, which attempt it was, what it decided and the events along the way. This is what makes the work auditable; it lives in your organization’s data and is removed with it.
We also keep the whole conversation of an agent’s run in our cloud, so you can read it from the card’s run history. Anyone who can read the factory can read it. We remove anything shaped like a key or password first, on a best-effort basis, and keep it for a year. A run governed by MadeBook keeps none.
Deletion
Deleting a card, a workflow, a factory or a workspace removes its content. Closing an organization removes the organization’s data from CodeBook. Your Bookbag account is closed with the account service, which removes the identity every product refers to.
Contact
Questions about any of this go to hello@codebook.work.