Security and data
Before your team starts, know that a synced session's chat, plans and code are stored on our server.
What leaves your computer
| Data | Where it goes |
|---|---|
| Session chat, plans and synced code | Stored on our server so teammates can receive them. |
| Text used by shared AI features, including team chat when the team agent is on | The AI provider, using the service's key. |
| Requests to your own AI | The AI provider you set up, using your key. |
| Files in solo mode | Not shared with a team. What your AI reads goes to its provider. |
| Usage data and crash reports | Not sent. Telemetry is off by default. |
Who can join a session
A person needs both the secret invite link and the owner's approval. See Invites and approvals.
Signing in
You sign in with GitHub or Google. Your sign-in token is sent in request headers rather than web addresses by current versions of the app.
Protecting secrets
- Agents and syncing skip files that usually hold credentials.
- Text that looks like an API key or token is masked in your AI's replies before they're shared.
- Your AI asks before running commands.
These checks catch common cases, not all of them, so keep secrets out of your source code.
Shared previews
A preview runs a teammate's code in your browser. It expires after 2 hours at most. Only open previews from people you trust.
Limits to know about
- Anyone in a session can read what's synced to it.
- I-IDE is in private development and hasn't had an independent security audit.