Privacy Policy
Supashot is local-first by default: captures and your library stay on your device unless you choose to sign in, upgrade, or share to the cloud. This policy describes the Supashot Chrome extension and the supashot.app marketing website.
Effective date: June 12, 2026
Local-first by default
Screenshots, screen recordings, annotations, thumbnails, and library metadata are stored locally in your browser (IndexedDB and extension storage). Capture and editing run in the extension on your device. We do not upload your library or receive the pages you browse unless you explicitly use an optional cloud feature described below.
For each capture, the extension may store the page URL and title you captured from (sourceUrl, sourceTitle) in your local library so you can find it later. That is not a log of your general browsing history.
No account required for core features
You can capture regions and visible areas, annotate, copy to the clipboard, and use your local screenshot library without creating an account or signing in. Sign-in is optional and is used for Pro features, subscription management, and cloud sharing.
Accounts and sign-in (optional)
If you choose to sign in, you may use Google (via Chrome's identity API) or an email magic link. We receive your email address and a Firebase user identifier to authenticate you and manage your subscription tier.
Account-related data is processed through Firebase (Google): Authentication for sign-in, Cloud Firestore for subscription tier and usage limits tied to Pro features (for example free-tier video limits or cloud-sharing quotas), and session tokens stored locally in the extension so you stay signed in. We do not sell your account information.
A small display cache (such as tier and email) may be written to extension storage on your device for the UI. Entitlement checks for Pro features are validated against Firestore, not bypassable local flags alone.
Pro subscriptions and payments
Supashot Pro is billed through Dodo Payments. Payment card details are collected and processed by Dodo, not by Supashot. We receive subscription status (for example whether your account is on the Pro tier) so we can enable paid features. When you start checkout, your Firebase user ID may be passed to Dodo as metadata so your purchase can be linked to your account.
Cloud sharing (Pro, opt-in)
If you are signed in with a Pro subscription and choose Share on a screenshot or recording, Supashot uploads that file to Firebase Storage and creates a public link on supashot.app (for example supashot.app/i/… for images or supashot.app/v/… for videos). Metadata about the share (such as your user ID, storage location, and upload time) is stored in Firestore.
Sharing only happens when you trigger it. Anyone with the link can view the shared file. If you delete a shared item from your library, Supashot attempts to remove the corresponding cloud file and share record when you are signed in.
Screen recording and video
Screen recordings (including optional microphone or webcam audio when you enable them) are stored locally in your library like screenshots. They are not uploaded unless you explicitly use cloud sharing. Video processing (export, trim, share preparation) runs in the extension and its offscreen document on your device.
How capture works
To capture a page, the extension may inject a temporary overlay on the active tab so you can select a region or run a scrolling capture. Images are processed locally in an offscreen document bundled with the extension. The extension only accesses the tab you are on when you start a capture (toolbar button or keyboard shortcut). It does not read or modify pages in the background.
Exporting your library as a ZIP uses a normal browser download from Settings. Copying to the clipboard happens locally when you choose Copy in the editor.
Extension: usage analytics
The Chrome extension sends coarse product-usage events to Google Analytics 4 (Google) so we can understand which features are used—for example when the popup or editor opens, a capture or recording starts, or you copy or download an image. Events are feature names only. We do not send screenshot or recording content, page URLs you capture, keystrokes, or the text inside your captures.
The extension stores a pseudonymous client identifier in extension storage on your device and associates events with that identifier and a per-browser-session ID. We do not send your email, Firebase user ID, or capture content to Google Analytics.
A small local counter may also record how many successful captures you have made so the extension can optionally show a one-time prompt to rate Supashot on the Chrome Web Store; that counter stays on your device and is not sent to Google Analytics.
Marketing website (supashot.app)
The marketing website is separate from the Chrome extension and does not load inside it. On supashot.app only, we use Vercel Analytics to understand aggregate page views and similar visit data. It does not use third-party marketing trackers or advertising cookies. It does not access your extension library, screenshots, or recordings.
Third-party services summary
- Google / Firebase — sign-in, account tier, cloud share metadata and storage (when you use those features)
- Google Analytics — coarse product-usage events from the Chrome extension (not screenshot or page content)
- Dodo Payments — Pro subscription checkout and billing
- Vercel Analytics — aggregate page-view analytics on the marketing website only
We do not sell or transfer your personal data to third parties for their own advertising. Data shared with the services above is used only to operate the features you use.
Your choices
You can use Supashot without signing in. You can sign out from the extension auth page at any time. You can delete items from your local library in the extension. Uninstalling the extension removes locally stored library data and analytics identifiers (such as the pseudonymous Google Analytics client ID) from that browser profile. Cloud shares you created may remain accessible via their public links until you delete them while signed in or until we remove them as part of account cleanup.
Updates
This privacy policy may be updated from time to time. Material changes will be posted on this page with an updated effective date.
Contact
If you have any questions about this privacy policy, please contact us at privacy@supashot.app.