CaptureProof Pro
Summary. CaptureProof Pro handles the contents of the pages you explicitly choose to capture. All of that handling happens on your own device. The extension makes no network requests of any kind, has no server, and transmits nothing to us or to anyone else. Nothing is sold, shared, or retained after you close the editor.
This policy applies to the CaptureProof Pro extension for Google Chrome and Chromium-based browsers, distributed through the Chrome Web Store. It does not cover any website you choose to capture with it, which remains governed by that site's own policy.
To do its job, the extension necessarily processes the contents of pages you explicitly ask it to capture. Here is everything it touches and what becomes of it.
| Data | Why | Where it goes |
|---|---|---|
| Pixels of the page you capture | To build the screenshot | Held in memory and in your browser's local storage only long enough to pass the capture from the background worker to the editor tab, then deleted immediately |
| Text of the page you capture | To find patterns that look sensitive, and their position on screen | Read in the page, matched against patterns locally, never copied out of your browser |
| Page URL, title and capture time | To record provenance on the exported proof report | Written into the file you export, and nowhere else |
| Your annotations, notes and report title | To build the export | Held in the editor tab only, discarded when you close it |
Because a captured page can contain anything, the extension may process personal, financial, or authentication details that happen to appear on it — that is precisely what the detection feature exists to find. None of it goes anywhere.
The extension contains no code that opens a network connection. It has no backend service, no API endpoint, and no third-party SDK, library, or tracker embedded in it. Nothing is uploaded, because there is nowhere for it to be uploaded to. You can confirm this by inspecting the extension's source, which is plain, unobfuscated JavaScript.
The extension uses chrome.storage.local as a one-shot handoff. The
background worker writes the capture there, the editor tab reads it, and the editor deletes
it in the same step, before you interact with anything. Nothing is retained between
sessions. Uninstalling the extension removes any remaining extension storage.
Files you export are saved to your device through your browser's normal download behaviour, and are yours to manage.
| Permission | Reason |
|---|---|
activeTab |
Access the page you are capturing, only for the tab you are on and only after you click the toolbar button. |
scripting |
Run the capture and detection helpers inside that page. |
storage |
The one-shot handoff described above. |
unlimitedStorage |
A full-page capture of a long page can exceed the default storage quota during that handoff. |
The extension requests no host permissions, so it cannot read or act on any page you have not explicitly asked it to capture.
There are none. No data is sold, rented, shared, or disclosed to anyone, for any purpose, including advertising. The extension bundles no third-party analytics or advertising code.
CaptureProof Pro's use of information received from its permissions adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically:
The extension is not directed at children and collects no data from anyone, regardless of age.
Sensitive-data detection is pattern-based. It reliably catches common formats, but it is an assistant rather than a guarantee: unusual formats can be missed, and ordinary text can occasionally be flagged. You remain responsible for reviewing any capture before you share it. A manual redaction tool is provided for anything the automatic scan does not catch.
Any change will be posted on this page with a revised "last updated" date. Material changes will also be noted in the extension's Chrome Web Store listing.
Questions about this policy, or about privacy in the extension, can be raised at the project's public issue tracker: github.com/generate-apps/captureproof/issues. Reports are read and answered there.
You can also reach the developer through the Support tab on the extension's Chrome Web Store listing, which routes messages privately rather than publicly.