Privacy
Coordigent coordinates AI coding agents working on the same repository. To do that it records what those agents did. This page says exactly what that means, who else sees it, and for how long. Coordigent is operated by Coordigent, Inc., a Delaware corporation, which is responsible for the data described here.
What we record
Coordigent records the activity of coding sessions you connect to it. A session is an agent running on your machine; the record is what that agent did to the repository.
- Account details: your name, your email address, and the authentication provider you signed in with.
- Session metadata: which repository and branch, which client (Claude Code, Cursor, Codex and so on), the machine name your agent reports, and start and activity timestamps.
- Prompts: the text you send your agent. The first 120 characters become the session's task title, which your team sees.
- File activity: the paths your agent read, edited or created, and diffs of its edits up to 20 KB each.
- Commands your agent ran, and commit metadata — SHA, branch and message.
- Tool inventories: the names of the MCP servers, skills and hooks a session started with.
- Messages sent between sessions through Coordigent.
What we do not record
Coordigent does not record your agent's replies or its reasoning, and it does not read your repository. It sees what an agent reports having done, not the contents of files it did not change.
Card details never reach our servers. Payment is handled entirely by Stripe's hosted pages.
Who can see it
Your data is scoped to your project. Members of other projects cannot read it.
Within your project, what teammates see depends on a setting an owner controls. New projects default to coordination visibility: teammates see which files a session is working on, but prompts and diffs stay with the person who ran the session. On full visibility, prompts and diffs are visible to everyone in the project.
Projects created before this setting existed are on full visibility. If that is yours, an owner can change it in project settings.
Who else processes it
Coordigent uses these services. Each receives only what it needs to do its job.
- Microsoft Azure — hosting and database, in the United States (Central US region). All recorded data is stored here.
- Stripe — payments. Receives your email address and billing details; we never see your card.
- Resend — sign-in emails. Receives your email address.
- GitHub and Google — used only if you sign in with them. We receive your name, verified email address and account identifier.
- Anthropic and OpenAI — used only when a project switches on the Coordigent agent, which is off by default. They receive a brief listing the file paths two sessions are both working on. They do not receive your prompts, your diffs or your source code.
- Slack — used only if you connect a channel. It receives the notifications you have asked to be mirrored.
How long we keep it
Until it is deleted. Coordigent does not delete session records, file activity or prompts on a schedule.
A project owner can delete a repository and everything recorded under it — sessions, prompts, file activity, diffs, conflicts and messages — with coord repo remove --delete-history. This cannot be undone.
There is not yet a self-serve way to delete your account. If you want your account or any of your data removed, email hi@coordigent.com and we will do it by hand.
Leaving a project removes your membership. It does not delete the sessions you already recorded.
Your rights
Depending on where you live, you may have the right to access, correct, export or delete the personal data we hold about you, and to object to how we process it.
Email hi@coordigent.com to exercise any of these. We will respond within 30 days. Requests to delete an account are fulfilled manually.
Security
Authentication tokens are stored hashed, never in plain text. Traffic is encrypted in transit.
Tokens issued to your machines expire a year after they are issued, and browser sessions after ninety days. Tokens issued before expiry existed carry no expiry date, because giving them one would have signed out every machine already installed.
You cannot yet list or revoke your own tokens; a screen for it is planned. Until then, email hi@coordigent.com and we will revoke any of them for you, straight away if you believe one has been exposed.
Changes
If this page changes in a way that affects what we collect or who we share it with, we will say so here and update the date at the top.
Contact
Questions about any of this: hi@coordigent.com.