Privacy
See what smry collects, who receives it, and how the browser extension handles page data.
Who can see what
We do not sell your personal information. We do share data with the providers below to run smry, analyze it, prevent abuse, and fund the free service with contextual ads.
- smry
- We receive the URLs, article or file content, search terms, chat messages, and other inputs you ask us to process. If you sign in, we also receive account information from Clerk. Items you save, sync, publish, share, or send to another service are stored or transmitted as needed to complete that action.
- Analytics and reliability providers
- Google Analytics, PostHog, and Databuddy may receive the page or route you visit, feature events, referral information, browser and device details, performance data, and an IP-derived approximate location. PostHog receives your stable Clerk account ID when you are signed in, but not your account email. PostHog autocapture and session recording are disabled. Sentry may receive error details, request and device context, IP address, and a sampled or error-triggered session replay so we can diagnose failures.
- Advertising providers
- Free pages may use Gravity, Koah, or Velocity to select and measure ads. Depending on the page, they may receive the current article title and a bounded excerpt or content sample. Homepage ads may also use titles, URLs, and excerpts from recent articles stored in your browser. They may receive a pseudonymous browser or session ID, language, device information, IP address, and ad impression or click data. If you are signed in, Gravity may also receive your stable account ID and a SHA-256 hash of your normalized email. A hash is pseudonymous, not anonymous. Your raw email is not sent for ad selection. This means ads can be chosen based on what you are reading and, on the homepage, what you recently read.
- AI, search, and content providers
- Providers such as Groq, OpenRouter, Keenable, context.dev, and document parsers receive the article content, messages, files, or bounded search context needed for the feature you request. We do not ask them to use that content for advertising.
- Account, payment, and delivery providers
- Clerk handles authentication, Stripe handles payment details, and Resend or Amazon receives delivery information when you choose an email or Kindle action. These providers see the data required to perform that job.
Browser extension
The extension does not send us a continuous history of the pages you visit.
When you invoke it
Opening, saving, or requesting insights can send the active page's URL, title, and a sanitized copy of its rendered content to api.smry.ai. Sanitization removes scripts, embedded frames, form controls, editable fields, hidden content, page metadata, and credentials or query strings in copied links. Saving a highlight also sends the text you selected and up to 160 characters of surrounding context on each side.
What the extension reads locally
Chrome can load local controls on supported webpages and YouTube. Those controls can read the current selection, page URL, and page title so they can offer a save or insights action. They do not transmit page data until you choose an action. Extension settings and up to eight recently opened page URLs, titles, and timestamps stay in extension-local storage. A pending highlight is stored only during its save handoff.
What happens after upload
The snapshot upload does not include an account or device ID. Our infrastructure still processes your IP address for delivery, abuse prevention, and rate limiting. The captured page is kept for about an hour for the reader handoff, and request logs containing URL, timestamp, and status may be kept for up to 30 days. Extension-origin reader and report tabs are excluded from client-side analytics, ad pixels, session replay, and client error telemetry. Their captured content is not sent to ad providers.
Your choices
smry does not currently have one in-product switch that disables every analytics service. PostHog and Gravity honor your browser's Do Not Track setting, but other providers may not. You can use browser privacy controls or content blockers, clear local site and extension data, uninstall the extension, or contact us to request access or deletion. Pro removes ads, but it does not by itself disable product analytics or error reporting.