- Home
- Feature
Privacy: nothing leaves the browser
Short answer: the extension makes zero network requests; captures are made in your tab and stored in the browser on your device. No analytics, no ads, no account for the free version. The only things that ever leave are a bug report you press Send on and, with Pro, a capture you choose to save to your own Google Drive.
The extension makes no network requests. A capture is made in your tab, kept in the browser's own storage on your device, and goes nowhere unless you export it and send the file yourself. No analytics, no ads, no account for the free version. This page says what that means in practice and what each permission is for; the privacy policy is the binding text.
In practice
- Zero network requests. Not for capture, not for updates of anything, not for statistics. The only outbound actions are the ones you take: a bug report you press Send on, or a Pro upload to your own Google Drive.
- Captures stay on your device, in the browser's local database, listed under Files, deletable one by one or all at once.
- No account for the free extension. Nothing to sign up for, nothing to identify you.
- No analytics, no ads, no tracking. The store listing carries the declaration that the developer does not collect or use your data.
- Pages behind a login are captured in your own tab; no server ever sees them.
- Evidence mode keeps its facts inside the file; verifying a file at /verify/ uploads nothing either.
Each permission, and why
| Access to the page you are on | To scroll it, read its size and photograph it. Requested as site access at install, so embedded frames and PDF files can be captured without a prompt each time. |
| Scripting and web navigation | To reach inside embedded frames and to know when a page has finished loading during a capture. |
| Storage, unlimited | To keep your captures in the browser's own database on your device, however many there are. |
| Context menus | The right-click entries: capture, Files, Batch capture. |
| Identity | Used only if you sign in for Pro, or connect your Google Drive. Never used by the free extension on its own. |
| Downloads | Asked the first time you save a file, so the file can go to your Downloads folder or a folder you choose. |
What Pro adds to the picture
Pro needs an account, so that Pro follows you to another browser. The account holds your email, the identifiers and amounts Stripe gives it for the subscription, the country used to pick the price and the browsers you have signed in. Card details stay with Stripe. Captures are still yours and local; the optional Google Drive upload writes only to its own folder and can see only the files it created. The privacy policy lists retention periods and your rights.
Questions
Does the extension send my screenshots anywhere?
No. It makes zero network requests. A capture is made in your tab, stored in the browser's local database on your device, and leaves only when you export it and send the file yourself, or, with Pro, when you choose to save it to your own Google Drive.
Is there analytics or tracking?
No analytics, no ads, no tracking, no telemetry. The Chrome Web Store listing carries the store's declaration that the developer does not collect or use your data.
Then how do bug reports work?
Only when you press Send in the report form. That sends what you typed, the address of the page you were capturing, the extension version, browser and operating system, and a rough region, so the page can be fixed. Nothing is sent without that button.
Do I need an account?
Not for the free extension. Pro needs one, because that is how Pro follows you to another browser; it stores your email, the payment records Stripe gives it and the browsers you have signed in. Card details stay with Stripe. The privacy policy, in full
Where are my captures stored, and how do I delete them?
In the browser's own storage on your device, listed under Files. Delete any of them there, or all at once; uninstalling the extension removes them too.
Can it read pages I am not capturing?
It runs on a page only when you start a capture there, or when a batch opens the page. Site access is granted at install so that frames and PDF files can be captured without a prompt; nothing is read from pages you are not capturing.
What does Google Drive upload see?
With Pro, if you connect Drive, the extension asks Google for permission to see only the files it creates itself, in a "FullPage Capture" folder. It cannot see the rest of your Drive.
Try it and watch the network tab. Free, no account, nothing is uploaded.
Add to Chrome