Your browser
Settings, shortcuts, prompt-library data, workspace state, and local caches are stored in Chrome extension storage where possible.
Default boundaryPrivacy · Updated July 15, 2026
What stays local.
What leaves the browser.
No vague promises. This page explains what the website and extension handle, why each Chrome privacy label appears, and when a provider receives data because you chose a connected feature.
Data flow at a glance
Three boundaries. Three different responsibilities.
Provider you connect
Google, Microsoft, GitHub, Stripe, weather, or an AI website receives data only for the specific flow you start or configure.
User-directed boundarySynapse Tools
There is no Synapse-operated backend receiving the extension’s core workspace, browsing history, page content, location, communications, or OAuth tokens.
Not a recipientWhy Chrome shows six labels
“Handles” does not mean “sent to Synapse Tools.”
Chrome requires disclosure when an extension accesses or processes these data types—even when processing happens locally on the user’s device.
Read Chrome’s definition ↗Personally identifiable information
Google profile emailUsed to identify the connected Chrome profile for optional Google and Chrome Sync features.Authentication information
OAuth access tokensUsed to connect services such as Google or Microsoft only after the user starts that connection.Personal communications
AI chat contentRead only when the user explicitly chooses to export a supported AI conversation.Location
Device locationRequested only when the user enables live weather on the New Tab experience.Web history
Browser historyUsed locally for Synapse search, recent-search suggestions, and quick navigation.Website content
Current page or transcriptAccessed when the user invokes page context, chat export, or YouTube transcript features.Optional connected features
Providers are involved only when the feature needs them.
Synapse communicates directly with the service involved in the action. Those services process data under their own terms and privacy policies.
Google and Microsoft
OAuth is used for optional Drive, Calendar, Tasks, OneDrive, or Outlook features. Tokens are handled by the browser extension and the selected provider—not a Synapse Tools server.
AI websites and page tools
Page context, transcripts, prompts, or exported conversations are handled only when the user invokes those actions. Content may be handed to the AI site the user has open.
Weather
Location is requested only after the user enables weather. Coordinates are cached locally and used to request the weather experience.
Snappy checkout
Stripe handles checkout information. The Synapse Tools license endpoint verifies the checkout reference, rate-limits requests using a one-way hash of the IP address, and returns a signed license file without exposing Stripe account details.
synapsetools.co
The website is separate from extension data.
Cloudflare serves the site and may process standard request information such as IP address, browser details, requested URL, and security signals to deliver and protect the service.
The site does not currently load a third-party analytics or advertising tracker. If that changes, this page will be updated before the new tracking posture is represented as current.
If you email support@synapsetools.co, we receive the address, message, and attachments you choose to send. That information is used to respond to the request.
When paid checkout becomes active, Stripe will process payment and transaction information. Synapse Tools will receive the purchase information needed to deliver and support the license.
Your controls
You choose when optional data paths open.
Optional integrations
Do not connect a provider if you do not want Synapse to call that provider. Disconnect through Synapse and revoke access in the provider account when needed.
Local workspace data
Remove extension data through Synapse’s controls or Chrome’s extension storage/removal flow. Uninstalling can remove locally stored extension data.
Feature-specific questions
Email support@synapsetools.co with the feature name. Ask what it reads, where it stores data, and which provider receives the request.
A plain commitment
Privacy claims should stay as concrete as the product.
Material changes to website tracking, extension data flows, connected providers, or payment handling will be reflected here.