FullShot — Privacy Policy

Effective date: 2026-08-21  ·  Last updated: 2026-10-12  ·  Applies to: FullShot – Full Page Screen Capture, the browser extension for Google Chrome, Microsoft Edge, and Mozilla Firefox, version 1.10.1 and later.

FullShot is a screenshot tool that runs on your own computer. Capturing needs no account, sends nothing anywhere, and does not track you. This policy explains exactly what that means.

FullShot Pro is optional, and it is not available in this version: nothing in it needs or unlocks Pro. When it arrives it is planned to add watermark and logo images, brand kits, and annotation and redaction presets, and it is tied to a Nikatru account, which the Nikatru privacy policy covers. Capturing, annotating, redacting and exporting stay free and need no account, and nothing else this policy says about them changes.

1. Who we are

FullShot ("the extension", "we") is developed by Rajasekar Selvam. For any privacy question you can reach us at support@nikatru.com.

2. What FullShot does

FullShot captures screenshots of web pages you choose to capture — the full page, the visible area, a region you select, or an element you click — and lets you annotate, redact, beautify, and export them. Capturing, editing and exporting happen locally in your browser. The only exception is the "Report a problem" link (§3g), which opens a page on nikatru.com, and only when you click it.

3. What data FullShot handles

Google classifies taking a screenshot as "handling user data," so we disclose it plainly even though your screenshots never leave your device.

a. Screenshots (website content)

• What: When you start a capture, FullShot reads the content of the page in the active tab and produces an image of it. That image is website content.
• Where it goes: The screenshot is held in your browser's memory during capture and, if you keep it, saved to a local database (IndexedDB) on your device as your capture History. It is also saved to your Downloads folder or copied to your clipboard only when you choose to export or copy it.
• What we do not do: We do not upload, transmit, back up, share, or sell your screenshots. They never reach us or any third party. We cannot see them.

b. Settings

• Your preferences — image format, capture options, filename template, PDF options, and theme — are stored using your browser's extension settings storage (the storage.sync API). These are preference values only; no screenshots or page content are stored in settings.
• Because that API is the browser's own sync mechanism, if you are signed in with sync enabled these small preference values may sync across your own profiles of that browser — through Google in Chrome, Microsoft in Edge, or Mozilla in Firefox. It is the browser's mechanism, not ours; FullShot neither controls nor receives that sync, and it never includes your screenshots.

c. The last-failure note

• What: When a capture fails, FullShot keeps a one-line note so the popup can tell you why the next time you open it. The note holds a short fixed sentence chosen from a list built into the extension, the origin of the page (scheme and host only — never the path, query string or any credentials in the address), which capture mode you tried, the tab number, and the time.
• Where it goes: the browser's storage.session API — deliberately not storage.local and not storage.sync. It lives in memory for the current browser session, is erased when you quit the browser, never syncs to any other device, and never leaves this machine.
• What it never holds: no screenshot, no page content, and no text written by the browser or by a website. Only sentences FullShot itself wrote.

d. Automatic PII redaction (optional, off by default)

If you turn on "Redact PII," FullShot scans the captured page's text on your device for patterns that look like emails, phone numbers, credit-card numbers, Social Security numbers, and API keys, and paints a solid opaque block over each match it finds in the image (a permanent block, not a reversible blur). This detection runs entirely locally. FullShot does not collect, store separately, index, or transmit the detected values — the feature exists to cover what it matched, not to gather it.

What it cannot do. The scan reads text that the page exposes as text, and it does not read all of that. Anything the page draws as pixels — a canvas-rendered editor such as Google Docs or Figma, an embedded image, a scanned document, a video frame — holds no text for the scan to read, so nothing is blocked there even with the feature switched on. Nor does it read what you have typed into a form field, or text held in an attribute, or a number split across styled fragments of a sentence, or text inside a frame it did not enter. It matches five shapes and no others: not names, not postal addresses, not dates of birth, not account nicknames, not free-form secrets.

FullShot reports what it covered; it cannot tell you whether the image is clean, because it never sees the image as a picture. Look at it before you share it. Before a screenshot and its description are copied for an AI assistant, FullShot shows you the exact image that is about to leave, with the blocks it covered marked on it, and asks you to confirm you have looked.

What this stores. To mark those blocks for you, FullShot stores — locally, on your device, alongside the screenshot and nowhere else — the position and size of each block it confirmed to be solid in the finished image. It stores no coordinates for anything it did not cover, and it never stores the matched text itself. Those positions are deleted with the screenshot, and are dropped entirely if the image is edited, beautified or clipped, because they would no longer describe it.

e. The page address and title kept with each screenshot

• What: Each screenshot in your History is stored with the title of the page and its address — the scheme, host and path only. FullShot removes the query string and the fragment (everything after a ? or a #) before it stores the address, because that is where sign-in codes, reset links and access tokens travel; screenshots kept by earlier versions have it removed when they are read.
• Where it goes: into the same local History as the screenshot, on your device. It is shown in History, and it is included in the description FullShot copies for an AI assistant and on a PDF only when you copy or export. It is deleted with the screenshot.

f. Private windows

• In Chrome and Edge, if you allow FullShot in private windows, the browser runs a separate copy of FullShot there. Screenshots taken in a private window are kept in that private session's storage and are discarded when you close the last private window; they never appear in your normal History. Firefox does not allow FullShot in private windows.

g. Report a problem (only when you use it)

The Options page has a "Report a problem" button, and the Help panel has a "Still stuck? Ask us" link. Clicking either one opens the report form on nikatru.com (https://nikatru.com/support) in a new tab. Opening it is your browser's request, not one FullShot sends: the browser opens that page, and its web address carries these values, which nikatru.com therefore receives when the page opens:

• app — the extension's id, fullshot;
• v — the extension's version number;
• loc — your browser's interface language (for example en-GB);
• plat — your browser's engine and major version only (for example chromium 130 or firefox 131), never the full user-agent string;
• category — the kind of report: "bug" from the Options page, "question" from the Help panel;
• q — from the Help panel only: the words you typed into its search box, at most 200 characters, and left out entirely if they look like a web address, a host name or an email address.

What it never carries: no screenshot, no page content, and nothing about the pages you capture or visit: no web address, page title, host or tab.

What happens next: The form fills in the category and any search words, which you can change; the id, version, language and browser above go with it as hidden fields. Nothing is sent to our support system until you write your report and press "Send report". If you do, what that report stores and for how long is set out under "Problem reports" in the Nikatru privacy policy, which covers it. If you close the tab instead, nothing more is sent.

4. What FullShot does NOT collect

• No account is needed to capture, annotate, redact or export, and FullShot itself never asks for your name or email. An account exists only if you choose to sign in to FullShot Pro (§5).
• No analytics, telemetry, usage tracking, crash reporting, or advertising identifiers.
• No browsing history. FullShot does not record the sites you visit; it only reads a page when you explicitly capture it, and keeps that page's address and title with the screenshot (§3e).
• No cookies set by the extension. No fingerprinting.

5. Data sharing and transmission

Capturing transmits nothing. Capturing, annotating, redacting and exporting make no network request to any server, ours or a third party's, whether or not you use Pro.

If you sign in to FullShot Pro. Pro is optional, and signing in is not yet available in the extension; until you sign in, FullShot holds no account credential and makes no request at all. If you sign in with a Nikatru account, FullShot contacts Nikatru's server (platform.nikatru.com) when you sign in and from time to time afterwards, to confirm that your account has Pro. It sends a sign-in token and the product name, and nothing else: never your screenshots, the pages you capture or your browsing history. The token is kept on your device in the extension's own storage, which the web pages you visit cannot read; in Firefox it is sent only after you grant the browser's "authentication information" data-collection permission. Nikatru's server keeps your account, the link between your account and this browser, and your purchase records. If you use Pro's brand features, the watermark and logo images, brand kits and presets you create are stored with your account so they follow you to any browser you sign in on. Cloudflare (which hosts Nikatru's server) and Supabase (which runs account sign-in) process this data for us. You can sign out at any time; the free features keep working without an account.

If you report a problem. Opening the report form sends nikatru.com only the values listed in §3g, and a report reaches our support system only if you send it.

If you buy FullShot Pro, Paddle handles the payment, or Razorpay for buyers in India. We receive a record of the purchase, never your card details.

6. Permissions and why they are used

• activeTab — lets FullShot read the current tab only at the moment you start a capture. No standing access to any site.
• scripting — injects the capture engine into the active tab on demand to measure, scroll, and stitch the page.
• downloads — saves a finished screenshot or exported GIF/WebM to your Downloads folder when you choose to save.
• storage — stores your preferences (see §3b), the last-failure note (see §3c), and, for the current browser session only (cleared when the browser closes, never synced), the progress of a capture or Batch run in flight, including the web addresses you typed into Batch.
• identity — optional, in Chrome and Edge only: not granted at install. It is reserved for signing in to FullShot Pro with a Nikatru account (§5), and your browser asks you for it only when you choose Sign in. The Firefox add-on does not declare it. Sign-in is not available in this version, so FullShot never asks for it.
• unlimitedStorage — lets your local capture History hold large images without hitting the browser's small default storage quota. Local only.
• Optional broad site access (<all_urls>) — not requested at install. FullShot asks for it only if you switch on expanding scrollable cross-origin iframes or Batch URL capture, and your browser shows its own prompt. Decline and the rest of FullShot still works.

FullShot contains no remotely hosted code; all code ships inside the extension (Manifest V3).

7. Data retention and how to delete your data

• History: Screenshots you keep live in local IndexedDB until you remove them. Delete individual captures from the History page, or clear them all there. Removing the extension also removes its local storage.
• Settings: Stored until you change them or uninstall. If your browser's sync is on, clearing synced data is done through the browser.
• The last-failure note: Dismiss it from the popup, or quit the browser — storage.session does not survive a restart. A capture that succeeds also clears it.
• Downloaded / copied files: These are ordinary files under your control; delete them like any other file.
• A problem report you sent: kept and deleted as the Nikatru privacy policy sets out, which also says how to ask us to access, correct or delete it.

Apart from a problem report you sent, everything above is on your device and under your control, and we hold none of it. If you signed in to FullShot Pro, Nikatru holds your account, the link to this browser and your purchase records: to access, correct or delete them, or to unlink a browser, write to support@nikatru.com from the email address on your account. Signing out removes the token from this browser.

8. Security

Local data is protected by your operating system and the browser's per-extension storage isolation. We ship no remote code that could later change this behavior.

9. Age requirement

FullShot is for adults. You must be at least 18 years old to install or use it, and it is not designed for or directed to anyone younger. India's Digital Personal Data Protection Act, 2023 treats every person under 18 as a child, and 18 is the single floor Nikatru applies everywhere it operates. FullShot collects no personal information from anyone, at any age.

10. Limited Use disclosure

This section is required by the Chrome Web Store and is stated in the form it requires. The practices it describes are the same in every browser FullShot ships to.

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

FullShot's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically: FullShot uses on-device data only to provide its single, user-facing purpose — capturing and working with screenshots you choose to take; it does not transfer that data except as part of a user-initiated save/export you perform, or — only if you sign in to FullShot Pro — the sign-in token and product name it sends to Nikatru's server to confirm Pro (§5), or the extension's version, interface language and browser version carried by a problem report you choose to open (§3g); it does not use the data for advertising; and no human at FullShot reads your screenshots or the pages you capture (we have no access to them).

11. Changes to this policy

This policy is a notice: it tells you what FullShot does with data. It is not something you agree to by installing or using FullShot. If our data practices ever change, we will update this policy and revise the "Last updated" date before the change takes effect, and — as required by Chrome Web Store policy — disclose material changes to users. If a change affects something you consented to, such as signing in to FullShot Pro, we ask you again in the extension before the change applies to your data.

12. Contact

Questions about this policy or FullShot's privacy practices: support@nikatru.com.