smry Browser Extension — Privacy Policy

In Chrome, the Extension displays a removable Get insights control on normal webpages. This control is local UI: it does not make a network request or read and transmit page content until you click it. You can hide it for the current visit, disable it for an exact site, disable it globally, or re-enable it from the Extension settings.

When you select text on a normal webpage in Chrome, the Extension can display a local Save highlight action beside the selection. It reads the active selection locally so it can offer that action, but does not transmit it until you click Save highlight. The selected quote and a short amount of surrounding context are held under a random save ID during the supervised handoff, never placed in the reader URL, and removed from extension-local storage after the save succeeds, fails, or times out. You can turn off the selection control or its locally generated success sound in Extension settings.

In Chrome, when you ask the Extension to process the current page (by clicking Get insights or by using its toolbar icon, page context-menu entry, or keyboard shortcut), the Extension shows a confirmation before its first page-content upload. That confirmation explains that the page URL, title, and sanitized rendered page content will be sent to smry. Nothing is uploaded if you cancel. If you continue, the Extension remembers that choice in extension-local storage until you reset it in settings. The separate Open this link in smry context-menu command sends only the link you explicitly selected; it does not capture the current page or grant page-content sharing.

For an approved request, the Extension makes a copy of the page and removes content marked hidden or non-rendered, form controls, editable fields, scripts, embedded frames, page metadata, and other non-article interactive elements. It removes arbitrary element attributes and strips credentials, queries, and fragments from links and image URLs inside the copied content. Only then does it send the page URL, title, and remaining rendered content to the smry backend (api.smry.ai). smry then opens a clean reader view. Get insights additionally searches the public web and builds an AI-generated, cited report with more sources.

Chrome loads the local Get insights and Save highlight content scripts on HTTP(S) webpages so they can render those controls. They do not track navigation or send page data in the background. Save highlight reads only the text you actively select before its explicit save click. Firefox and Safari do not currently ship these content scripts or the separate first-upload confirmation; their toolbar, context-menu, and keyboard actions still upload only after you explicitly invoke them.

• The page URL.
• The page title and sanitized rendered page content. smry extracts the clean article (body, author, publish date) from that content on its servers.
• For Save highlight, the selected quote and up to 160 characters of context on either side, when that context can be read from the page.

No account identifier or device identifier is attached to the Extension’s snapshot upload. If you are signed in after the reader opens, the normal smry site session may be used for rate limiting; generated report records do not store a user ID. When you ask for a summary, the extracted article body is sent to Groq or, if needed, OpenRouter so the provider can generate the summary text. When you ask for insights, a bounded research query derived from the article is sent to Keenable for public web search. Groq or OpenRouter then receives the resulting public-source titles and excerpts to generate the report; it does not receive the captured article as report evidence. Captured article text is not published as a report source.

Extension-captured URLs, titles, page content, and derived article data are not sent to smry’s contextual-advertising provider or used for advertising.

Reader and report tabs opened by the Extension are also excluded from client-side product analytics, advertising pixels, session replay, and client error telemetry.

If you choose to submit the uninstall feedback form, the private feedback record includes the Extension version and standard technical diagnostics such as browser and operating-system details, device type, screen and viewport size, hardware capability, locale, time zone, and network capability. This information is collected only when you send the form and is used to diagnose compatibility problems and improve the Extension.

• Your reader preferences (open behavior, save-recent toggle) live in extension-local browser storage.
• Your Get insights global setting and exact-site disable list live in extension-local browser storage.
• Your Save highlight visibility and success-sound preferences live in extension-local browser storage. A pending selected quote is also kept there only for the supervised save handoff and is removed on success, failure, or timeout.
• In Chrome, your first-upload confirmation lives in extension-local browser storage until you reset it from the Extension settings.
• A list of pages you’ve recently opened with the Extension (URL + title + timestamp) lives in extension-local browser storage. You can clear it from the Extension’s options page.
• On smry.ai, a tab-scoped session flag keeps the reader and generated report excluded from client-side tracking even after a refresh. The flag stores only the value 1, contains no URL or page content, and is cleared when that tab leaves the reader/report flow.

Extension-local browser storage is not synced across devices. Pending highlight content is transmitted to smry only after you explicitly click Save highlight.

• We do not attach your name, email, account identifier, or IP address to captured article content or generated reports. Like any web service, our infrastructure briefly processes network information such as an IP address for delivery, abuse prevention, and rate limiting; it is not used to build a browsing history.
• We do not transmit or keep a history of pages you visit when you do not invoke the Extension. The Chrome content script only checks the current hostname against your local visibility settings so it can decide whether to render the control.

• The article the Extension captures is held on the smry backend for a short handoff window (about an hour) so the reader can pick it up, then it expires. The handoff entry is keyed by a random token, not by user or account.
• We retain request logs (URL + timestamp + status) for up to 30 days for debugging and abuse prevention.

• Uninstall the Extension at any time from your browser’s extensions page. Uninstalling removes extension-local data automatically.
• Disable Get insights globally or for individual sites from the Extension settings without disabling the rest of the Extension.
• Disable the webpage Save highlight control or its success sound from the Extension settings.
• In Chrome, reset the saved upload confirmation from the Extension settings. The Extension will ask again before its next page upload.
• Clear local recent-links history from the Extension’s options page without uninstalling.