Snag Capture · Privacy Policy

Nothing you record leaves your browser.

Snag Capture is a Chrome extension that records a tab, its console output and what you did, and turns that into a single report. It can also clone a page — its markup, its stylesheets and its animations — into a prompt you can hand to an AI assistant yourself. All of it happens on your own machine. The extension has no server, no account system and no analytics, and nothing it captures is ever uploaded. It reaches the network in exactly one situation, described under Cloning a page, and never to us.

What the extension records

Recording only happens while you have explicitly started a run, and only for the tab you started it on. During a run, Snag Capture may capture:

• Video of the tab you chose to record.
• Console output produced by that page — log, warn, error and anything else the page printed.
• Uncaught exceptions and rejected promises, including the exception name.
• Your interactions with the page during the run: clicks, navigation, form actions and window resizes, recorded so the steps can be replayed.
• Screenshots you take during the run, of the area you choose, kept with the recording.
• Network requests the page makes with fetch or XMLHttpRequest: method, URL, status, timing, content types and sizes. The body of a request is kept only when the request failed, capped at 8 KB and passed through the secret filter. Request headers are never captured.
• The environment at the moment recording started: browser and version, platform, window and screen size, pixel ratio, language, time zone, colour scheme, reduced-motion preference and the browser's estimate of the connection type. This is read from the browser itself and is used only to describe the conditions of the recording.

When a run is not active, the extension records nothing.

Cloning a page

Cloning is a separate action from recording, and it starts only when you click it. It reloads the page you are on, scrolls it from top to bottom, and collects the material an AI assistant would need to rebuild it: the rendered markup, the stylesheets, the fonts in use, and the animations — including the ones written by scripts, which are read as they run rather than from a file. The result is a prompt you copy or download. Nothing is sent anywhere on your behalf; where the prompt goes afterwards is your decision alone.

This is the one place the extension makes network requests. A stylesheet served from another origin cannot be read from the page for security reasons, so the extension fetches it from the same address the page itself already loaded it from, without cookies or credentials. If you also ask for images and fonts to be packaged, those are fetched the same way. These requests go to the servers the page already uses — never to a server of ours, because there is none — and nothing about you or your capture is sent with them.

A clone is a copy of the page as it stood, so treat it as such: text that was on screen is in the markup, and the value typed into a form field is captured exactly as it was. The secret filter described below does not run over a clone, because it would corrupt the markup and the selectors it is made of. The clone report says so plainly, and the prompt it produces repeats the warning.

Where it is stored

Everything stays inside your own Chrome profile, on your own computer:

• IndexedDB — the recording and the report, because video is too large for other extension storage.
• Local extension storage — small preferences, such as where you dragged the on-page overlay.
• Session extension storage — temporary state for a run in progress, discarded when the browser session ends.

This is storage, not cache: a recording is still there tomorrow, and after a restart, until you delete it. None of it is synced — the extension never writes to Chrome's synced storage, so a run made on one computer does not appear on another, and nothing travels through your Google account.

What is never collected

The developer of Snag Capture receives nothing. There is no upload, no sync, no backup, no telemetry, no crash reporting, no advertising and no third-party service of any kind. Your recordings are not sold, shared or transferred to anyone, because they never leave your device in the first place. Sharing a report is a manual act: you export the file and decide yourself where it goes.

Redaction of secrets

Console output and the bodies of failed requests frequently contain credentials. Before text reaches the report, Snag Capture filters values that match well-known secret formats — JSON Web Tokens, API keys, GitHub and AWS credentials, bearer tokens — along with fields and headers whose name marks them as sensitive, such as password, token, authorization or cookie, whether they appear as plain text or as JSON keys. It also filters common personal-data patterns, including e-mail addresses, payment card numbers and Brazilian CPF and CNPJ numbers.

The filter matches patterns, so it is a safety net and not a guarantee. A password that looks like an ordinary word matches no pattern, and will be recorded like any other text. In bug mode this filter runs over what you type; in test mode it deliberately does not, because a recorded step cannot replay a value it does not have. That is why test mode shows a notice before recording starts, marks the run as containing secrets, hides those values in the report and strips them from anything you export.

Video is the one thing the filter cannot reach. Redaction works on text, and a recording is pixels: if a token, a customer record or anything else sensitive is visible on the screen while you record, it is in the video, whatever the filter did to the text beside it. Review a report before you send it to anyone — while it stays on your machine it is yours alone, and sharing it is the moment that stops being true.

Your control over the data

Runs stay on your machine until you delete them. You can remove them individually from the extension, and removing the extension from Chrome removes the recordings and reports it stored with it. Because there is no copy anywhere else, deletion is final.

Permissions and why they exist

tabCapture — records the video of the tab you selected. This is the core function of the extension.

offscreen — encodes that video in the background, since a service worker cannot do it on its own.

storage — keeps the run and your preferences on your machine.

scripting and activeTab — place the recording overlay and the collector on the tab you are recording, and the collectors that read a page you asked to clone.

host permissions for all sites — a bug can happen on any page, and a page worth cloning can be any page, so the extension cannot know in advance which site you will need. The access is used only on the tab you acted on, during a run or a clone you started, and it is what allows a clone to fetch the stylesheets and images the page had already loaded. It is not used to browse, read or index your history, and nothing it observes is transmitted anywhere.

Remote code

The extension executes no remote code. Everything it runs ships inside the package reviewed and published on the Chrome Web Store.

Changes to this policy

If the extension ever starts handling data differently, this page will be updated before that version is published, and the date below will change.

Contact

Questions about this policy can go to netinho0588@outlook.com. You do not have to take the claim on trust either: open your browser's Network panel while you record, and watch nothing leave.

Last updated 16 August 2026