Last updated: 28 August 2026
Synapse stores conversation history from your AI tools so that a different tool can read it back later. That history is the product, so how it is handled matters more here than in most services. This page states plainly what is stored, who can read it, and what we will never do with it.
Synapse is operated by WENJUN ZHU, an individual sole trader based in the People's Republic of China, acting as data controller. Contact: customer@getsynapse.link.
Payments are handled by Paddle.com as Merchant of Record. Paddle is a separate controller for payment data and applies its own Privacy Policy.
| Data | Why |
|---|---|
| Email address | Account identity and sign-in |
| Conversation turns you or your agent write — the full text of each exchange | This is the service: another tool reads them back later |
| Topic titles and summaries | So an agent can find the right topic |
| OAuth client registrations and access tokens | Authorising the AI tools you connect |
| Which client wrote a turn, and when | Attribution across tools and machines |
| Server logs (request time, endpoint, status, coarse IP) | Debugging and abuse prevention; retained 30 days |
We do not store card numbers or billing addresses. Those go to Paddle and never reach our servers.
Your data is encrypted in transit (TLS) and at rest, and every row is isolated to your account by database-level row security, so one account cannot read another's data.
Synapse is not end-to-end encrypted, and we will not claim otherwise. Our servers decrypt your turns in order to serve them, and search across your topics requires reading their text server-side. That means a Synapse administrator is technically capable of reading your stored conversations.
What limits that is policy and access control, not mathematics: administrative access is used only to investigate a fault or a request you have raised. If a service tells you it is end-to-end encrypted while also offering keyword search over your content, one of those two claims is not true.
The practical consequence: do not store credentials in Synapse. Redact API keys, tokens, and passwords before they are written. Treat a stored conversation as readable by anyone who can reach the account.
| Processor | Role | Location |
|---|---|---|
| Supabase | Database and authentication | Data stored in Supabase's hosted infrastructure |
| Vercel | Application hosting and edge delivery | Global edge network |
| Paddle | Payments, invoicing, sales tax | Per Paddle's own policy |
Nobody else. There is no analytics vendor, no session recorder, no advertising pixel on the application.
When you authorise a tool such as Claude, ChatGPT, Cursor, or a CLI agent, it receives a scoped access token and can then read and write topics on your behalf. What that tool does with the data afterwards is governed by that tool's own privacy policy, not this one. A turn read out of Synapse into another AI tool enters that tool's context and its retention rules.
Tokens are short-lived and can be revoked. Revoking access in Synapse stops future reads; it cannot recall data a tool has already read.
Turns are kept until you delete them. They are not deleted when you cancel or downgrade — that is deliberate, so that ending a subscription never destroys your history, and reading your existing turns keeps working regardless of which plan you are on. If we ever introduce a retention limit for cancelled accounts, section 4 of the Terms of Service sets out the notice and export window we would give first.
You can ask for a copy of your data, correction of anything inaccurate, or deletion, and you can object to a particular use. Write to customer@getsynapse.link and we will respond within 30 days. Export is also available without asking: topics_get_with_turns returns any topic as a plain markdown transcript, so your history is portable by design and not locked in.
Depending on where you live, you may also have rights under the GDPR, the UK GDPR, or the CCPA. We apply the same handling to everyone regardless of jurisdiction.
Synapse is operated from the People's Republic of China, and data is stored with the processors named in section 5, whose infrastructure is outside China. Using the service involves an international transfer of the data you write.
If we discover unauthorised access to stored conversations, we will notify affected accounts by email with what we know and when, without waiting until the investigation is complete. Given section 3, a breach of our database is a breach of readable conversation content, and there is no cryptographic backstop that would make it otherwise — so we will say so directly rather than describe it as an incident affecting encrypted data.
Synapse is a developer tool and is not directed at children under 16. We do not knowingly collect their data.
Material changes will be announced by email to account holders before taking effect. The date at the top of this page always reflects the current version.