Nabshot Privacy Policy

Nabshot · Last updated: August 4, 2026

Short version: Nabshot handles the screen content you choose to capture, and it does all of that on your own device. The developer receives none of it. Nothing is uploaded, stored remotely, sold, or shared.

Data Nabshot handles on your device

Nabshot is a screenshot and screen-recording tool, so by design it handles the content you point it at. It is worth being precise about what that means, even though none of it is transmitted anywhere:

Website and screen content. The pixels of whatever you choose to capture: the visible tab, a region you drag, the full scrolling page, or a screen, window, or tab you pick in the browser's own share dialog. Anything visible in that area is in the image or video, including any personal information shown on screen at the time.
Audio. System or tab audio, and your microphone, but only when you switch those options on for a recording.
Mouse position and clicks. Only during a "Record tab + cursor" recording, and only for the tab being recorded, so the cursor highlight and click ripples can be drawn into the video. They are used for that frame and nothing else.
Your settings. Save format, video format and quality, frame rate, countdown, retention limit, and audio preferences.

What the developer receives

None of it. There is no server, no account, no analytics, and no network request of any kind in this extension. The developer does not receive, remotely store, sell, or share your captures, audio, cursor activity, settings, browsing history, or anything else. The data above never leaves your computer.

How capture and recording work

Nabshot only does anything when you ask it to. Screenshots (the visible tab, a region you drag, or the full scrolling page) are built in your browser using the Canvas API. Screen recordings use the browser's own screen-picker, where you choose the screen, window, or tab to share; the video is encoded on your device and never leaves it. You can annotate screenshots in an editor and save or copy them, and play, download, or delete recordings yourself.

What is stored, and for how long

Recordings are written to the browser's local database (IndexedDB) on this device and stay there until you delete them, clear them all from the recordings library, or they are dropped automatically by the "keep the last N recordings" limit if you set one.
Screenshots are held briefly in local extension storage while they are handed to the annotation editor, and are cleared as soon as the editor has loaded the image. A still of your chosen source is likewise held while the region-recording picker is open, and is removed once you confirm or cancel. Screenshots are not kept after that unless you save or copy them yourself.
Settings live in chrome.storage.local, and your theme choice in the browser's localStorage.

All of this is on your own computer. There is no account and nothing is synced to the cloud.

Microphone and audio

A recording includes microphone or system audio only if you turn that on. Microphone access is requested by the browser and is used only to mix your audio into the recording on your device; it is never sent anywhere.

Permissions and why they are needed

Active tab and scripting: to capture the tab you are on when you trigger a screenshot, to draw the drag-to-select overlay for a region, and to scroll and measure the page for a full-page capture.
Offscreen: to run the small background document that records and encodes video and mixes audio on your device.
Downloads: to save a finished recording to your Downloads folder when you choose to.
Storage / unlimited storage: to keep your settings and to store recordings locally on your device without a size cap.
Clipboard: to copy a screenshot to your clipboard when you click Copy.
Tab capture (optional): requested only if you turn on "Record tab + cursor," so Nabshot can record a single tab. It is not part of the default install.

Nabshot declares no host permissions, so it has no standing access to any site. activeTab grants access to a single tab only after you explicitly invoke the extension there, and that access lapses when you navigate away or close the tab. None of these permissions is used to send your data anywhere.

Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Nabshot contains no analytics and makes no network requests of any kind, so none of the data described above is transmitted anywhere.

Third parties

Nabshot shares nothing with any third party, because nothing is transmitted off your device at all. The optional "Donate" link opens an external page (Ko-fi) only if you click it; any payment there is handled by that service under its own privacy policy.

Children

Nabshot is a general-purpose utility. Nothing it handles is transmitted to the developer, from anyone, including children.

Changes

If this policy changes, the updated version will be posted on this page with a new "last updated" date.

Contact

Questions? Contact the developer at contact@mcguigansoftware.com.