Privacy policy

Last updated 20 October 2026

Chief, at runchief.ai, lets you connect your accounts and give AI agents limited, revocable access to them without handing over your passwords. This policy says what Chief keeps, why, who else sees it, and how to have it removed. Questions go to whoever runs this Chief.

What Chief keeps

• The waitlist: if you join it, your email address, until you are invited or ask us to take it off, and, if you came from a link in a cap someone shared, which cap, so we know how people find Chief. We use your email only to send you your invite.
• How often your caps and keys ask Chief's AI: a count of the calls, and of the characters sent, for each org and day, for 90 days, to hold each org to its daily limit.
• Agents asking to connect: when an agent asks to connect to Chief for you by your email, the email it gave, the name it gave itself, when and from which network address it asked, and what you decided: allowed (with the keys you chose for it) or denied. We mail you a link to decide; nothing happens without the code the agent showed you, and the agent is never told whether you have an account. Once you allow it, it works for you as your other agents do, and you can disconnect it any time.
• Your account: your name, your email address, a hash of your password (never the password itself), and the orgs you belong to.
• Your keys: for each account you connect, its name, the service, the account's address, and its credentials (OAuth tokens, API keys or other secrets). Credentials are encrypted with a master key that is kept apart from the database, and are used only to make the requests you approved.
• What you make: proxies (the operations a cap offers, and the program behind them), caps, spaces and their members, your agents and the permissions you gave them, and your approvals. A proxy may keep a small memory between uses, such as the ID of an event it booked. That memory stays with its cap, encrypted.
• The audit trail: a record of each use. It shows which cap or agent was used, which operation, when, whether it was allowed and whether it worked, and how much was sent. When an agent connects to a cap, the record also keeps the agent's name, its network address and its user agent. The audit trail never keeps the content that services sent back. Its entries are deleted after 90 days.
• Server logs: one line per request, with the path (cap tokens cut short), the response status, how long it took, and the browser's or agent's name. They are kept briefly and overwritten as new ones arrive.
• One cookie, to keep you signed in. Chief uses no analytics, advertising or tracking cookies, and its pages load no outside scripts or fonts.

How Chief uses it

Only to run Chief for you: to sign you in, to make the requests your caps and agents are allowed to make, to show you what happened, and to keep the service secure. Chief does not sell your data, show you ads, or use your data to train AI models.

Google user data

When you connect a Google account as a key, Google shows you what Chief asks for, and you decide. Depending on the kind of key, that is:

• Google Workspace: your Google account's email address, so Chief can show which account a key is; sending mail as you; your free and busy times; and reading, adding and changing your calendar events. If you allow it, also Google Sheets, and the Drive files that Chief creates or that you open with it.
• Google's Workspace servers (Gmail, Calendar, Drive, Docs, Sheets, Slides, Chat and Contacts): the reading and writing that each server lists when you connect it.

How Chief uses Google user data:

• Only to run the operations you approved in a proxy, when you, your agent, or someone holding a cap you made asks for one. Chief does not look through your Google data on its own.
• Chief reads your mail only if you allowed mail reading for that key, and then only what the program of a cap you approved searches for, such as messages from one sender. The same holds for Outlook mail on a Microsoft 365 key, where Chief reads attachments' names and sizes, never their content.
• What an operation returns goes to whoever asked for it: you, or the person and agent holding your cap. Chief does not keep it, apart from anything the proxy keeps in its memory.
• Your Google tokens are encrypted at rest. Agents, AI models and the people you share caps with never see them.
• The content of your Google data (your mail, events, files, chats and contacts) goes to an AI model only when a cap or key you approved says it asks Chief's AI, or sends it to an AI provider account you connected yourself. Then only the text its program sends goes, to summarize it, turn it into data or classify it: to your own agent (your machine's Claude Code or Codex, or your Chief in the cloud when none of your machines is online), or to TypeSafe's Jev to classify it. It is never used to train AI models. The built-in authoring agent is told which keys you have, including each key's account address, so that it can pick the right one.
• Chief does not use Google user data to develop, improve or train AI or machine learning models, and does not transfer it to anyone else for that purpose.
• Chief does not sell Google user data, use it for advertising, or use it to decide anyone's creditworthiness.
• The people who run Chief do not read your Google data, with three exceptions: you ask them to, for example to help with a problem; it is needed for security, such as investigating abuse; or the law requires it.
• You can remove a key at any time. Chief then deletes the credentials it holds for it, and the caps that use it stop working. You can also revoke Chief's access at https://myaccount.google.com/permissions.

Chief's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The same rules apply to the other services you connect, such as Microsoft 365 and Dropbox.

Dropbox files

When you connect a Dropbox account, Dropbox shows you what Chief asks for: your account's email address and name, and finding and reading your files. If you allow it, also saving files into a Chief folder, and making links that let anyone who has them open a file. Chief reads a file only when the program of a cap you approved asks for it, such as one folder you named, and sends what it reads only where that program sends it. You can remove the key at any time, and revoke Chief's access in your Dropbox account's settings under Connected apps.

AI models

Some features use an AI model. Chief reaches models through OpenRouter (openrouter.ai), which passes each request to the model's provider:

• The built-in authoring agent, when you ask it in your own words to write a proxy. It gets your request, and the name, service and account address of each of your keys.
• The connection assistant, when you ask it to connect a service. It gets your conversation with it, the public documentation it reads, and what the service offers, with secrets removed.
• Questions about a cap. The model gets the question and the cap's public description, never your data or your credentials.
• Caps and keys that ask Chief's AI. A cap or a key can ask Chief's AI to summarize text, turn it into data, or classify it, and it says so before you approve or connect it. When it runs, the text its program sends, which can come from the accounts you connected to it, goes to your own agent to summarize it or turn it into data, whoever uses the cap: to your machine's Claude Code or Codex, under your own plan with its provider, or, when none of your machines is online, to your Chief in the cloud, through OpenRouter to providers that keep none of what they are sent. To classify it, the text goes to TypeSafe's decision model, Jev (typesafe.ai); without it, your own agent classifies instead. Chief keeps neither the text nor the answer, apart from what the program returns or remembers, as for any of its calls.

Chief never sends credentials to a model.

Who else sees your data

• The people and agents you share with. Whoever holds a cap can run the operations you approved and gets what they return. Members of a space can use the caps put in it, and members of a team org share its keys, proxies and caps.
• Service providers who run Chief for us: DigitalOcean (servers), OpenRouter and the model providers it uses (for the features above), TypeSafe (classifying, for caps that ask Chief's AI to), Cloudflare (DNS) and Proton (email: the invites we send, and support). Each gets only what it needs to provide its service.
• The services you connect, which receive the requests your caps make, under their own privacy policies.
• Others, when the law requires it, or when it is needed to protect people from harm.

Nobody else: Chief does not sell or rent your data to anyone.

Security

Traffic to Chief is encrypted with HTTPS. Credentials, caps' memory and your conversations with the connection assistant are encrypted with a master key that is not stored in the database, and the database itself is kept on encrypted storage. Each org's data is kept apart from every other's, every use is audited, and a cap can be revoked at once. No system is perfectly secure: if a breach affects your data, we will tell you.

Keeping and deleting

Your data is kept while your account is open. Removing a key deletes its credentials, and revoking a cap stops it at once. Audit entries are deleted after 90 days. To close your account and have your data deleted, write to whoever runs this Chief. We will delete it within 30 days.

Children

Chief is not meant for children under 16.

Changes

If this policy changes, the new version will appear here with a new date. If a change matters, we will email account holders before it applies.

Contact

whoever runs this Chief