Privacy policy

ScrollSnapshot captures the page you choose on your own device. Nothing you capture is sent anywhere.

Last updated: 11 November 2026

In short: ScrollSnapshot captures screenshots of the page you tell it to, entirely on your own device. Nothing you capture, and no browsing data, is ever sent to us, to any server, or to any third party. There's no account, no sign-in, and no tracking or analytics of any kind. If you turn on the optional agent connection, what a coding agent asks for goes only to the agent server on your own computer; your agent may then send it to its AI provider, as it does with anything else you show it.

What ScrollSnapshot does

ScrollSnapshot is a Chrome extension that captures the tab you're viewing: the visible area, the whole scrollable page, the page split into numbered image slices, or a region you draw or specify. It can also save the frame a video on the page is showing. From Settings, you can also start a batch over the web tabs in your current window or a list of addresses you paste. It can extract the text and colours shown in what you capture, save a whole page as Markdown, and let you crop, redact or annotate the result before you save it. Its live blur tool covers private details on the page itself, before you capture or share your screen, and Clean up page leaves ads, cookie banners and chat bubbles out of a capture.

You have to trigger every one of these actions yourself, by clicking the extension's icon, using a keyboard shortcut, or clicking a button inside its popup, Settings, result page, or the optional Markdown bar over text you select, or the optional capture button over a video. ScrollSnapshot never captures, reads or acts on a page in the background, or without that action from you. The one exception is a coding agent you connect yourself: once you turn the agent connection on and pair it, that agent can ask ScrollSnapshot to read or capture pages, within the limits described below. Live blur, if you use it, also runs on the sites where you kept a blur and, while you have demo mode on, on every page, so it can cover what you asked it to; it reads a page only to find what to cover, and sends nothing anywhere.

What data ScrollSnapshot accesses, and why

Chrome requires an extension to declare the permissions it uses. Here's what each one is for, and nothing more:

PermissionWhat it's used for
activeTab Lets the extension act on the tab you're currently looking at, only after you click its icon or a shortcut. It's the standard, narrowest way Chrome lets an extension read a page on request. Keyboard shortcuts and batches use the host access explained below.
scripting Injects the small script that measures the page, scrolls it during a full-page capture, and reads the pixels, text or line positions you asked to capture. It runs only while fulfilling a capture you started, including each page in a batch you started. If you turn on the Markdown bar for selected text (off by default), a separate small script is added to the pages you visit so the bar can appear; it reads only the text you select, and only when you press one of its buttons. If you turn on the capture button for videos (off by default), another small script is added to the pages you visit so the button can appear over a video; it reads no page content, acts only when you press it, and is removed when you turn the button off. If you use live blur, its script is added to the sites where you kept a blur, and to every page while demo mode is on (except sites where you paused it); it reads the page's text, on your device, only to find what to cover, and transmits nothing.
storage Saves your settings and the current capture result inside your browser. If Capture history is on, it also keeps the number of past captures you choose. If you use the agent connection, it keeps its pairing secret and the screenshots you chose to send your agent. If you keep a live blur, it keeps the blur's rule, the sites you kept blurs on, the sites where you paused demo mode, and the words and patterns you entered. See "Where your data is stored" below.
downloads Lets you save a finished capture to disk when you click Download.
clipboardWrite Lets you copy a finished capture to your clipboard when you click Copy.
debugger Used only if you turn on the optional "Turbo" capture engine, which uses Chrome's own DevTools protocol to capture a page more precisely and, if you choose one, apply a responsive viewport width. Chrome shows a banner across your browser windows for as long as this engine is attached, and dismissing that banner cancels the capture in progress. That's a restriction Chrome itself imposes on any extension using this permission, not something ScrollSnapshot adds.
alarms Used only while the optional agent connection is on: every 30 seconds it wakes the extension, so the agent server on your own computer can reach it. The alarm is removed when you turn the connection off.
<all_urls> (host access) Needed for keyboard-shortcut captures and a batch of tabs or addresses, where clicking the extension's icon cannot grant one-off access to every target. ScrollSnapshot doesn't read, monitor or transmit a page except while fulfilling a capture you started.

For Chrome Web Store disclosure purposes, the extension accesses website content (captured pixels, text and layout) and web browsing activity (the captured page's address and title). These are used only to create, label and reopen the capture you requested. They stay on your device and are never sent to us.

Where your data is stored

Everything ScrollSnapshot produces or remembers is stored locally, inside your own browser profile, using Chrome's built-in storage. It's the same mechanism any website uses to remember your preferences. Specifically:

  • Captures and their page address, title and capture details are kept in your browser's IndexedDB. With Capture history on, the limit and optional age cutoff are yours to choose in Settings, and you can delete individual captures or clear everything. With Capture history off, only the current result remains so its result page can open; the next capture replaces it. Video frames are captures like any other, kept the same way.
  • The agent connection's pairing secret, and screenshots you send your agent (the newest 20), are kept only on this device. The secret is never synced.
  • Live blur's kept blurs, the list of sites you kept them on, the sites where you paused demo mode, and your words and patterns are kept only on this device and are never synced. Whether demo mode is on lasts only until you close the browser. Your blur style, strength and detection choices are ordinary settings, and sync like the rest.
  • Settings (format, engine, quality, the sites where you hid the video button or chose your own burst and subtitle settings, and so on) are kept in Chrome's storage API, which may sync across your own signed-in Chrome browsers the same way Chrome syncs bookmarks. That sync is Chrome's, not ScrollSnapshot's, and no ScrollSnapshot server is ever involved.

ScrollSnapshot has no server. It sends nothing it captures to us or to any service, and has no way to see what you've captured, stored, or deleted. There's nothing for us to collect, because nothing leaves your device. Its only connection of its own is the optional agent connection, which talks to a server on your own computer and nowhere else.

Live blur

Live blur draws covers over parts of the page you are looking at, so a screenshot or a screen share shows the cover instead. Finding sensitive data, such as email addresses or card numbers, happens entirely in your browser; the text it reads never leaves your device and is not stored. While a page has covers, ScrollSnapshot withholds that page's text from its own text tools and from a connected agent. Detection can miss things, so check a capture before you share it.

The optional agent connection

Settings → Agent connection lets a coding agent you use, such as Claude Code, Codex or Cursor, work with ScrollSnapshot through a small open-source server, scrollsnapshot-mcp, that runs on your computer. It is off until you turn it on.

  • Where data goes. The extension connects only to 127.0.0.1, your own computer, and only after both sides prove they hold the pairing secret you pasted. It hands the agent only what the agent asks for: page text and outlines, captures, your capture history's details, screenshots you choose to send it, and any note or drawing you add when it asks you to choose an area. The server saves captures it receives in a folder in your home directory, readable only by your user account, and deletes them after 7 days.
  • What your agent does with it. Your agent may send what it receives to its AI provider, as it does with your code and everything else you show it. That is between you and your agent's provider; ScrollSnapshot sends nothing to them itself.
  • Which tabs. By default an agent can use only the tab in front of you. You can allow any tab.
  • Opening and reloading pages. Only if you also turn on “Let agents open and reload tabs”, an agent can reload a tab it may use, and — if you allow any tab — open a web page in a new tab. It can never click, type, or run anything on a page.
  • The toolbar icon shows AI whenever an agent is connected.

Pages ScrollSnapshot can open. If you choose “Leave a review”, Chrome opens ScrollSnapshot's Chrome Web Store page. “Send feedback” in Settings opens a feedback form on this site, and removing the extension opens a short, optional form here too; the address of either carries only the extension's version number. If you choose to send one of these forms, what you typed, ticked or picked (such as what it is about and which part of the extension), the version number, and an email address only if you gave one are emailed to the developer through a Cloudflare Worker. Nothing is stored there. Your IP address is used briefly to limit how often a form can be sent and is not kept, logged, or emailed. The extension itself sends none of this; the form on this site does, and only when you press Send.

Limited Use

ScrollSnapshot's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only to provide the screenshot and local organization features you request. It is not sold or transferred to third parties, used for advertising, used for creditworthiness or lending, or used for any purpose unrelated to ScrollSnapshot's single purpose. No human reads your captures; processing is automated and local to your device.

Accounts, analytics and third parties

ScrollSnapshot has no account system, no sign-in, and collects no analytics, telemetry, or usage statistics. It doesn't use any third-party service, SDK, or advertising network of any kind.

Children's privacy

ScrollSnapshot is a general-purpose developer and productivity tool. It isn't directed at children. The developer does not receive personal data or captured content from anyone, including children.

Changes to this policy

If ScrollSnapshot's data practices ever change, this page will be updated and the "Last updated" date above will change with it. Since the extension has no way to contact you directly, check back here if you want to confirm nothing has changed.

Contact & support

Questions, bug reports, or anything else about ScrollSnapshot: