TabSnap Studio is a Chrome extension thatcaptures visible areas or full pages from user-selected browser tabs, then lets
users organize, annotate, redact, and export those captures as images or PDF
documents. This policy explains what data the extension touches, why, and what
happens to it.
Summary
TabSnap does not operate any backend server. There is no analytics, tracking, or
network code in the extension. Everything it does happens locally in your
browser. The only data it handles is (1) your Google account email, obtained
through an optional-to-decline-but-required-to-use sign-in step, and (2) the page
content you explicitly choose to capture. Neither is sold, shared, or transmitted
to any server controlled by TabSnap.
What we collect
Account email address: TabSnap requires Google sign-in before any capture
feature becomes available. Signing in uses Chrome's built-in Identity API, which
returns your Google account's email address. This is used only to identify your
local session inside the extension's interface. It is stored in Chrome's local
extension storage on your device and is never uploaded to a TabSnap-controlled
server, because no such server exists.
Website content you capture: When you use TabSnap to capture a tab, the
resulting image data is website content. It is processed and stored locally in
the browser for the duration of your editing session (cropping, annotating,
redacting, reordering) and leaves the extension only when you explicitly export
or copy it — as a downloaded PDF/image file or to your clipboard. TabSnap does
not upload captures anywhere on its own.
What we do not collect
TabSnap does not collect or transmit: health information, financial or payment
information, passwords or other authentication credentials, personal
communications, location data, a log of your browsing/web history, or activity
data such as clicks, mouse movement, scrolling, or keystrokes. The extension
contains no `fetch`, `XMLHttpRequest`, or other network calls to any TabSnap or
third-party server.
How permissions are used
Permission: Why it's needed
Tabs: List open tabs so you can choose which ones to capture; read their titles/URLs for the selection UI; activate a tab during capture and return to your original tab afterward.
Scripting: Runs only on tabs you select, to measure page dimensions, scroll for full-page capture, pause animations, temporarily hide fixed/sticky elements, and restore the page afterward.
Storage: Saves your preferences (theme, capture settings) and required local sign-in state; session storage temporarily passes capture-job data between the popup, background worker, progress page, and studio page.
ClipboardWrite: Used only when you choose a Copy action, to copy a captured image or page URL to your clipboard. |
Identity/identity.email: Provides the required Google sign-in and reads the resulting account email, as described above.
Host access (<all_urls>): Needed because you may choose to capture a page on any website. Used only on pages you select, to measure/scroll/adjust the page for capture and restore it afterward. |
Data sharing
We do not sell user data. We do not share or transfer user data to third parties.
We do not use or transfer data for purposes unrelated to TabSnap's single
purpose (tab capture, organization, annotation, and export). We do not use data
to determine creditworthiness or for lending purposes.
Google API Services User Data Policy
TabSnap's use and transfer of information received from Google APIs to any other
app adheres to the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy),
including the Limited Use requirements. The OAuth token obtained through sign-in
is handled entirely by Chrome's built-in identity system and is never sent to a
TabSnap-controlled server.
Data retention and deletion
Your email and preferences remain in local Chrome storage until you sign out,
clear the extension's storage, or uninstall TabSnap — any of which removes this
data from your device. Captured images exist only for your active editing
session unless you export them yourself.
Children's privacy
TabSnap is not directed at children under 13, and we do not knowingly collect
data from children.
Changes to this policy
If this policy changes, the effective date above will be updated and the new
version posted at this same URL.
Contact
Questions about this policy: rcham@gmail.com