Privacy

Privacy in plain English.

This page is a public summary of how Synapse Tools approaches website and product privacy. It is written to stay aligned with the real behavior of the products, not vague filler copy.

Website kept lightweight Synapse core data stays local where possible Connected features are optional
Website

What this site does

  • synapsetools.co describes products and provides support, privacy, and security information.
  • The public site is kept lightweight and currently avoids unnecessary tracking.
  • Any material change to that approach will be reflected here so the public summary stays current.
Synapse extension

How core product data is handled

  • Core Synapse data stays local to the browser wherever possible.
  • Settings, shortcuts, prompt library data, and workspace state are stored in browser extension storage.
  • Synapse does not rely on a Synapse-operated backend for its core workspace behavior.
  • Optional connected features communicate with the third-party providers the user chooses to configure.
Connected features

When external providers are involved

  • Provider-backed features are optional and matter only when a user explicitly enables them.
  • Permissions and connected flows map to real user-facing features rather than vague future plans.
  • This summary is kept aligned with the shipped build and current integrations.
Questions

Need clarification?

Email [email protected] if you want clarification about what a feature stores, when it calls a provider API, or how a permission maps to product behavior.

Public-facing principle

Privacy language stays tied to real product behavior.

If product behavior changes in a meaningful way, this summary changes with it so the public description still matches reality.