PageShotter captures screenshots only when you explicitly start a capture. Screenshot images and webpage contents are processed locally on your device and are not sent to PageShotter servers or third parties.
Data handling
Everything the extension stores is kept in its own storage inside your browser, on your computer. None of it is sent to PageShotter or anyone else, because the extension makes no network requests at all.
While a capture is running, PageShotter stores the screenshot sections and the page title so a long capture survives Chrome restarting the extension mid-way. This temporary data is deleted after assembly, failure, or cancellation, and anything older than 24 hours is removed the next time PageShotter starts.
After a capture finishes, it is kept in your capture history so you can reopen and re-export it without capturing the page again. A kept capture includes the screenshot itself, the page title and URL, the words and link positions read from the page, and any edits you have made to it in the editor — the annotations you drew (rectangles, ellipses, arrows, lines, text, highlights, emoji and blur regions, with their colours, sizes and positions), any pictures you add to it from your own computer, how you grouped them, the crop, and the browser frame you presented it in. The words and links are what make an exported PDF searchable and its links clickable, and what let you search your history by what a screenshot says rather than only by the title its tab happened to carry; the edits are what let you reopen a marked-up capture and find it exactly as you left it. Your original screenshot is never overwritten by an edit.
You decide how long. History is kept for one week by default, and PageShotter’s options let you choose anything from one day to forever. You can delete any capture, or all of them, at any time. Uninstalling the extension removes the whole store with it.
Your settings (how long to keep history, how a capture behaves (how deep to go on a page that keeps loading, the pause between scrolls, and how long a section waits for its images), which colour theme to use, how you last chose to export — file format, image quality, export scale, and the PDF options — how you last chose to present a capture — the mock browser frame, its address text, background, margin, corners, shadow and date stamp — how the editor’s panels were last laid out, the emoji you placed most recently, the defaults you have saved in the editor — the appearance each tool’s new shapes start with, and the browser frame, background, margin and date stamp a new capture opens with — the download folder, which is the PageShotter folder inside Downloads by default, whether a finished capture saves itself instead of opening, and counters of your successful exports, the extension’s install date and whether a store review has already been asked for, kept only so the extension asks for a review only after real use) are stored the same way, on your computer. The folder setting includes when it last changed, used only so a delayed permission-revocation event cannot clear a folder chosen afterwards. The theme is also kept in the extension’s own browser storage so a page does not flash the wrong palette before it can read your choice; it is the same preference in a second place and it goes no further.
PageShotter also inspects layout-related webpage information locally to determine page dimensions, wait for images, and prevent fixed or sticky elements from repeating. That information is used during the capture and is not stored or transmitted.
PageShotter does not require an account for free capture. It does not read or export authentication cookies, credentials, or browsing history. The extension contains no advertising, telemetry, or remote executable code, and PageShotter does not sell or share browsing data.
Website and support
When you visit the PageShotter website, Cloudflare processes ordinary request metadata such as IP address, browser type, and requested page for security and delivery. Cloudflare Web Analytics measures aggregate website traffic. PageShotter records important Chrome Web Store CTA clicks in Cloudflare D1 so we can understand which pages generate interest. CTA event records do not include your email address. To limit request abuse, the API turns the connecting IP address and current hour into a shortened one-way fingerprint used only to count requests within that hour; the raw address is not stored in the launch database, fingerprints cannot be linked across hours, and rate-limit rows older than 24 hours are deleted during subsequent requests.
Before PageShotter launched, visitors could request one launch notification. For those existing requests, we stored the email address, submission time, source page, referrer without query parameters, and available UTM campaign fields in Cloudflare D1. The notification form is now closed. We use the retained information only to send the promised one-time launch notification and measure the launch funnel; it does not create an account or add anyone to a general newsletter.
Information you send to support is used only to answer and improve support. Do not send private URLs, credentials, or confidential screenshots.
Compliance
PageShotter uses information received from Chrome APIs only to provide the user-requested screenshot functionality, in compliance with the Chrome Web Store User Data Policy and its Limited Use requirements.