Trust & help
Privacy & where data lives
Local storage, connected-app credentials, cloud AI sharing, and controls for your data.
Synergoi is a desktop app with a local engine. Working records are stored locally, while cloud providers receive the prompts and content you use with them. Optional connected apps and the iPhone companion add the data flows described below.
How it's built
- The engine — the process that drives the CLIs, brokers approvals and stores transcripts — runs on your machine and listens only on
127.0.0.1, with a fresh bearer token every launch. Nothing on your network can reach it. - Provider CLIs (Claude Code, Codex, Grok, Cursor Agent, Antigravity) talk to their vendors exactly as they do in a terminal. Synergoi does not proxy, log or rewrite that traffic.
- Local models run through the bundled OpenCode harness against a server on your machine; no request leaves it.
Network connections and their purposes
| Destination | Why | What is sent |
|---|---|---|
| Lemon Squeezy (license API) | Activate and periodically validate your license key | The key, an instance name (your computer's hostname + "Synergoi"), the instance id |
| updates.tracewyn.com | Check for and download app updates | Version-manifest and download requests, including standard network metadata such as IP address |
| models.dev | Public model price list for the usage ledger's cost estimate | A public-list request and standard network metadata such as IP address |
| Your forge (GitHub, GitLab, Azure DevOps) | Only when you push, open a PR, clone or pull a PR in | Standard git and API traffic with your own credentials |
| Google Drive, Microsoft, Linear | Sign in, refresh access, and perform connected-app actions | Authentication tokens and the parameters or content needed for the requested action, sent directly to that service |
| Your selected AI provider | Process your conversation through its CLI | Prompts, selected files, requested tool results, and conversation context |
| relay.tracewyn.com and Apple push services | Optional paired iPhone companion | Encrypted application frames and routing metadata; see the Privacy Policy |
| Custom MCP services you configure | Run their tools | Tool arguments and credentials required by that service; review its own data practices |
There is no telemetry. Settings › Advanced has a telemetry opt-in switch for a future build; today it reads "No telemetry collector or transmission path is installed in this build", and that is literally true — there is no code path that would send anything.
Credentials
- AI subscription logins remain in the official provider CLI’s credential store. It adopts the login each vendor's CLI already holds and asks that CLI to do the work.
- Forge tokens you paste are encrypted at rest in the app's data folder; logins adopted from
gh,glab,azor a git credential helper are held in memory only. - Credential safeguards. Connected-app tokens are encrypted locally and excluded from chat/tool results. Agent launch environments are scrubbed; forge tokens are passed to git through an askpass helper for the duration of a single push.
The data folder
Everything Synergoi keeps — transcripts, Context Packs, rules, attachments, the usage ledger, settings, the license record, managed worktrees and the adapters it installs on first launch — lives in the app's own folder under ~/Library/Application Support/Synergoi on a Mac and %APPDATA%\Synergoi on Windows. Agent file edits and git operations can also write to repositories or working folders within the access you grant.
open "$HOME/Library/Application Support/Synergoi"explorer %APPDATA%\SynergoiExport and delete
Threads can be exported from their menu and from Settings › Archive. Deleting a project removes Synergoi's records and managed worktrees for it. Deleting the data folder while the app is quit removes everything, including the license record (deactivate the machine first so the slot is freed).
Disconnecting a connected app removes its local credentials but does not erase past chats, context packs, backups, provider history, or paired-phone copies. Google revocation is attempted on disconnect; you can also revoke it in your Google Account. Microsoft consent must be removed separately. Capability switches do not revoke OAuth grants.
For Google Drive’s selected-file access, AI sharing, and retention details, read the Google Drive connection guide and connected-app privacy disclosure.
Something wrong or missing on this page? Email [email protected].