Last updated: October 23, 2026
This policy describes Full Page & Scrolling Screenshot (the “Extension”) and the product website at fullpagescrollingscreenshot.extsite.tech (the “Site”). The Extension captures a web page as an image or PDF when you ask it to.
Summary
- Screenshots are built in your browser and saved on your device. They are not uploaded to us.
- Settings and a few counters stay in Chrome storage. The last three captures stay in a local database so the viewer can reopen them.
- We do not sell personal information. There is no account.
- Optional anonymous analytics and error reports go to servers we run. They do not include page content.
What stays on your device
In chrome.storage.local:
- Capture settings: mode, format, quality, PDF paper size, after-capture action, sticky-element mode, inner-panel toggle, frame delay, file-name template, save location, and the shrink-on-copy toggle.
- A random analytics id and a short cache token for that analytics service.
- A counter of completed captures, used only to decide when to show an in-product feedback prompt. The counter is removed after you respond or dismiss the flow that consumes it.
In chrome.storage.sync (so it can follow your Chrome profile): interface language, popup open count, whether the welcome note was dismissed, and how often the rating and feedback prompts have been shown or completed.
In chrome.storage.session (cleared when the browser session ends): the in-progress capture state, and a short-lived note while you drag a selected area.
In IndexedDB (ssp-captures): the last three finished captures so Preview and the viewer can open them. Older entries are deleted automatically. Uninstalling the Extension, or clearing extension data, removes this store.
What happens on a page you capture
When you press Capture, or use Alt+Shift+S, the Extension injects a script into the active tab. That script measures the page, can scroll it, can hide sticky headers for the shot, and can wait for images. For Select area, it draws the drag overlay. Those scripts run only for a capture you start. They do not stay behind to watch browsing.
Frames come from Chrome’s visible-tab capture. They are stitched on an offscreen canvas in the Extension. The file is then written through Chrome’s download manager, or placed on the clipboard if you chose Copy. Nothing in that pipeline is sent to our servers.
Permissions
- scripting — inject the capture script into the tab you chose.
- storage — keep the settings and counters above.
- offscreen — stitch images and build the file off the popup thread.
- downloads — save the file to Downloads or to a folder you pick.
- clipboardWrite — copy an image when you choose Copy.
- Host access to all sites — a capture has to run on whichever site you opened. It runs when you trigger it, not in the background on every page.
- glitchtip.extsite.tech and umami.extsite.tech — the telemetry hosts below.
Analytics and error reports
The Extension can send anonymous events to Umami on umami.extsite.tech: a random install id, browser language, screen size, and event names such as install, update, capture success or failure (with mode and format), and export (download or copy). Events do not include the page URL, page text, the screenshot, or the file name.
Unexpected errors can be sent to GlitchTip on glitchtip.extsite.tech: the error message, a stack trace, the extension version, and a short action tag such as “capture”. Screenshots and page content are not attached. Expected failures (a blocked Chrome page, a tab you left, a page that is too large) are not reported as crashes.
You can avoid both by removing the Extension. There is no separate analytics toggle in the current version.
Feedback and ratings
Uninstall can open an optional form at feedback.extsite.tech, identified only by the product slug in the link. After many captures, the popup may ask you to rate the Extension or to send ideas to features.extsite.tech. Both are optional. Do not include secrets in what you type.
The website
The Site is static. It loads Umami (a separate website id from the Extension) to count page views. It does not use cookies for accounts. It does not embed the Extension’s analytics id.
What we do not do
We do not sell browsing history, screenshots, or contact lists. We do not ask you to sign in. We do not read your downloads folder beyond the file the Extension itself just saved.
Contact
Questions about this policy: use the feedback form linked from the Extension after uninstall, or the ideas form at features.extsite.tech with this product selected. Please do not send screenshots of private pages unless you mean to share them.