Privacy Policy
What Cohent needs to coordinate work, why it needs it, and what you can control.
Last updated August 12, 2026
What Cohent receives
Account details can include your name, email address, sign-in provider, project membership, and access role. If you connect GitHub, Cohent receives your GitHub profile, the repositories made available through the GitHub App, repository permissions, and encrypted connection credentials.
What a project contains
A Cohent project can contain its goal, definition of done, team members, invitations, agent plans, working paths, project decisions, messages, commands, coordination events, and project settings. These records let the Control Room explain what is happening and help agents avoid overlapping work.
How the information is used
Cohent uses this information to identify authorized people, connect approved repositories and agents, find related work, move relevant context between agents, keep a project history, protect account actions, and send invitations you request.
Prompts and secrets
Agent prompts reach Cohent as written. Projects can enable best-effort removal of likely secrets before storage, but no automatic filter is perfect. Do not intentionally place passwords, private keys, or other credentials in prompts.
Who handles the information
Cloudflare provides the application and database infrastructure. GitHub handles repository connections when you enable them. Resend handles the recipient address, invitation link, and optional message when an administrator sends an email invitation. An account provider such as Clerk may handle sign-in and connected identities when enabled.
Retention and project access
Project administrators choose who can see prompt content and can set prompt retention from 7 days to one year. Older prompt content can be replaced by an expiry marker while coordination history and other project records remain. Archiving a project makes it read-only; it does not delete it.
Your controls
You can disconnect GitHub, remove repository access, leave or archive projects where available, and request account deletion from Account settings. Account deletion revokes active Cohent credentials and removes personal account details while preserving anonymized project history that other team members still rely on.
Questions
Until Cohent opens publicly, privacy questions and deletion problems should be raised directly with the Cohent team through the private product channel used to grant access.