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.

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.

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.

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.