Privacy Policy for FullShot – Full Page Screen Capture
Privacy Policy for FullShot – Full Page Screen Capture
Last updated: 15 August 2026
FullShot does not collect, store, transmit, or sell any personal data. Everything the extension does happens locally, inside your browser, on your own device. There is no server, no account, no analytics, and no tracking of any kind.
FullShot captures the full content of the webpage you are viewing as a single image and saves it as a PNG or PDF file. When you click the toolbar icon and press Capture, the extension measures the page, scrolls it in viewport-sized steps, captures each visible portion, stitches the segments into one image, and hands the finished file to your browser's normal download mechanism.
None.
None.
FullShot contains no network requests. It does not contact any server operated by us or by anyone else. It has no analytics library, no error reporting service, no advertising SDK, and no third-party code that phones home. All libraries the extension uses, including the PDF generation library, are bundled inside the extension package and run entirely offline.
Because no data ever leaves your device, there is nothing for us to store, share, sell, or hand over.
To produce a screenshot, FullShot necessarily works with the visual content of the page you choose to capture. It is important to understand how that content is treated:
The captured image exists only in your browser's memory while the capture is running.
It is assembled on an HTML canvas within the extension's own popup window.
It is never uploaded, logged, cached to a server, or shared with any third party.
It is discarded when you close the popup, unless you explicitly save it.
If you press Save as PNG or Save as PDF, the file is written to your own Downloads folder by your browser. We never see it.
FullShot only ever captures the single tab you are actively viewing, and only after you click the toolbar icon and press Capture. It cannot capture other tabs, it cannot capture in the background, and it does nothing at all until you ask it to.
FullShot requests the minimum permissions required to function.
activeTab — Grants temporary access to the one tab you are currently viewing, and only after you click the extension's toolbar icon. This is required to read the rendered pixels of the visible page, to inject the measuring and scrolling scripts, to show you which page is about to be captured, and to suggest a filename based on the page title. Access expires when you navigate away. We deliberately chose this permission instead of a broad host permission so the extension has no standing access to any website.
scripting — Required to inject the packaged scripts that measure the page's full scrollable size, temporarily hide sticky headers and footers so they do not repeat in every segment, and scroll the page step by step during capture. These scripts are part of the extension package, run only in the tab being captured, run only for the duration of the capture, and restore the page to its original state afterwards.
downloads — Required to save the finished capture to your Downloads folder. The extension only ever downloads files it generated itself from the current capture. It does not read, search, modify, or interfere with any of your other downloads, and it never uses this permission to fetch anything from the internet.
FullShot stores nothing. It uses no browser storage, no cookies, no local storage, and no extension sync storage. It keeps no settings and no history of your captures. Closing the popup discards everything.
FullShot shares no data with third parties, because it has no data to share. We do not sell or transfer user data to third parties. We do not use or transfer user data for any purpose unrelated to the extension's single purpose of capturing screenshots. We do not use or transfer user data to determine creditworthiness or for lending purposes.
FullShot does not collect data from anyone, including children.
If this policy changes, the updated version will be published at this same address with a revised Last updated date. Any change that would introduce data collection would be announced before it took effect and would require a new extension version reviewed by the Chrome Web Store.
Questions about this policy can be sent to:
kharshanacz@gmail.com