Browser Capture privacy

Browser Capture has one purpose: when you click its toolbar button, it saves the source in that active browser tab to your connected SixSentences Library. It does not run passive browsing collection and does not capture another tab or your browser history.

For the active public HTTPS page, Browser Capture may read and send its sanitized source and canonical URLs, title, site name, authors, publication date, DOI, description, bounded bibliographic metadata and text you explicitly selected. When the active scholarly source exposes an exact PDF that can be verified, the extension may also send that PDF, up to 50 MiB, for storage with the Library item. Extracted author fields contain person names, and text you explicitly select may contain names, email addresses or other identifiers. This information is used only as part of the Library save you requested and the related security and support operations described below.

Browser Capture never reads, stores or sends cookie or browser-session values to SixSentences. For an exact PDF request explicitly triggered on the active publisher page, Chrome may attach existing publisher credentials only to the same publisher origin. Redirects are rejected and credentials are never forwarded cross-origin. The extension does not collect browser history, read passwords, copy request headers, or transmit the page DOM or full page body. URL fragments, common tracking parameters and likely secret query parameters are removed before provenance is stored.

Account pairing uses an interactive PKCE S256 flow. SixSentences receives the one-time pairing values, the extension version and a coarse browser/platform device label so the connected browser can be identified and revoked. Your SixSentences password and Chrome or Google account do not enter the extension.

After pairing, a scoped and revocable API credential is stored in Chrome local extension storage with access restricted to trusted extension contexts. Content-free idempotency receipts—a payload-digest-derived key, random capture ID and timestamp—are kept in session storage while a retry may be needed. They are removed after a confirmed success or conflict. After an ambiguous network, 5xx or lost-response failure, they remain until a later confirmed outcome or the browser session ends. Choosing Disconnect revokes and removes the scoped credential.

Captured data is used to create, deduplicate and manage the Library item you requested, attach a verified PDF, keep the connection secure and provide support. Transmissions to SixSentences use HTTPS. For an exact PDF request explicitly triggered on the active publisher page, Chrome may attach existing publisher credentials only to that same origin. Browser Capture does not bypass a paywall; redirects are rejected and credentials are never forwarded cross-origin.

Captured data is processed by SixSentences and its necessary hosting provider as described in the general privacy policy. It is not sold, used for personalized advertising or cross-site tracking, or used to train SixSentences foundation models. Human access is limited to a support case you specifically authorize, security, legal obligations, or aggregated and anonymized internal operations.

Saved sources and PDFs remain in your Library until you delete them or delete your account. The general privacy policy describes server logs, backup handling and legal retention periods. You can edit or delete a saved item in the Library, disconnect the extension from its popup, and export or delete your account in SixSentences settings.

Privacy requests can be sent to legal@sixsentences.com. Product support is available at sixsentences.com/support.

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Browser Capture collects, uses and transmits data only where necessary for its disclosed Library-save purpose and related security and support operations.

If Browser Capture begins handling data differently, this notice and the Chrome Web Store disclosures will be updated before the changed collection begins, and users will receive any additional in-product notice or consent required by policy or law.