CaptureSite works entirely on your machine. There are no servers, no accounts, and no analytics. Screenshots stay where you took them.
Effective June 27, 2026Nothing about you personally. CaptureSite does not collect, transmit, or store any personally identifiable information on any external system. There are no user accounts, no sign-ins, no analytics pipelines, and no third-party SDKs embedded in the extension.
The only data created during a capture is the screenshot image itself, along with the page title, URL, and timestamp of the tab you captured. All of this is stored exclusively inside chrome.storage.local — your browser's own sandboxed on-device storage. We have no mechanism to access it.
Captures are stored in chrome.storage.local — a sandboxed storage area that lives entirely on your device and is only accessible to the CaptureSite extension. They are never uploaded, synced to a cloud service, or visible to anyone else.
You are in full control. Open the CaptureSite dashboard to view, export as PNG, or permanently delete individual captures.
CaptureSite makes zero outbound network requests. Screenshot stitching happens inside an OffscreenCanvas in the browser's own background service worker — entirely local, no server involved. There is nothing to send data to.
There is no telemetry, no crash reporting service, and no remote logging. If something goes wrong, errors appear only in the browser's DevTools console on your machine.
Chrome extensions must declare permissions upfront in their manifest. Here is what each one is actually used for — nothing more, nothing less.