Privacy
Plainly: what we store, who it is sent to, and how to get rid of it.
Last updated 2 September 2026
What we store
- Account. Your name and an account identifier from our authentication provider, Clerk. Your password is handled by Clerk and never reaches us.
- Projects and files. The names and full contents of the files in your projects, stored in Convex so they are there when you come back.
Project and file operations check that you own the project before returning or changing anything.
What we do not store
- Voice and video calls are peer to peer. The audio and video go directly between the two browsers and are never recorded.
- Files sent through the chat panel transfer directly between browsers and are not uploaded to us.
- Peer chat messages are relayed in memory and are not written to a database. They are gone when the room empties.
- Anything installed or generated inside your browser container (
node_modules, build output) stays in the tab and disappears when you close it.
Who else sees your code
- The AI features. When you use the agent, inline suggestions or Ctrl+I, the relevant code is sent to Groq to generate a response. Do not put secrets in files you ask the AI about.
- Anyone you invite. A person with your room link can see and edit that project while they are in the room.
- GitHub, if you use the export. Your token is used for that request and is not stored.
Deleting your data
Deleting a project deletes its files immediately and permanently. There is no backup to restore from. To delete your account and everything in it, email support@cocursor.ai.
Being straight with you
Cocursor is a student project, not a company with a security team. It is a good place to build and share things; it is not the right place for production secrets, personal data belonging to other people, or anything you could not afford to lose.