SeerSign (“the Extension”) is a Chrome browser extension published by Seerror. This Privacy Policy applies only to the Extension — not the main Seerror website or other products, which are covered in our site Privacy Policy. By installing or using SeerSign, you acknowledge this policy.

TL;DR
  • We do not collect, transmit, sell, or share any data from you.
  • Your documents are analysed entirely in your browser, on your device.
  • No accounts, no sign-in, no analytics, no telemetry, no ads.
  • Scan history stays in your browser's local storage only. You can clear it anytime.
  • SeerSign makes zero network requests to our servers or any third party.

1. Who we are

SeerSign is a Chrome browser extension built by Seerror, an independent privacy-focused studio founded by Jay Tiwari in Bengaluru, India. SeerSign is part of the Seerror Privacy Suite, which also includes products such as Seerguard and Seerraze.

You can reach the publisher at seerrorworks@gmail.com or via seerror.com.

2. What SeerSign does

SeerSign is a document-forensics tool. When you open a document in your browser (PDF, image, or screenshot), SeerSign can analyse it to help you decide whether it looks genuine or fabricated. It runs a 16-layer analysis engine that checks things like:

  • Font, metadata, seal, and layout consistency
  • Error Level Analysis (ELA) to detect image tampering
  • Copy-move manipulation and AI-generated-text indicators
  • Checksum validation for Indian documents (Aadhaar, PAN, GSTIN, IFSC)
  • WhatsApp-forward detection and known fake template matching

All of this runs locally in your browser. The analysis engine, OCR library (Tesseract), PDF engine (pdf.js), and template databases are bundled inside the extension — no external service is ever contacted to perform analysis.

3. What data SeerSign handles

3.1 Documents you analyse

When you ask SeerSign to scan a document, the document is read into your browser's memory (RAM) only for the duration of the analysis. Once analysis finishes, the document itself is not retained. SeerSign never uploads, copies, or transmits your document to any server.

3.2 Scan history (optional, on-device)

SeerSign stores a short history of your recent scans — just the verdict, confidence score, document type, and a short summary — in chrome.storage.local on your own browser. This lets you review past results. Three facts about this history:

  • It never contains the document itself — only metadata and the verdict.
  • It stays on your device. No one else (not Seerror, not Google, not any third party) can see it.
  • You can clear it anytime from the extension popup's History tab.

3.3 Web page context

Because SeerSign can analyse documents you encounter on any web page, the extension requests the <all_urls> content-script permission. This lets the extension inject a small script into the page you're viewing, so you can right-click a document and choose “Analyse with SeerSign.” The extension does not read, transmit, or store the general content of the pages you visit. It only activates when you explicitly invoke it on a document.

4. Data we do NOT collect

SeerSign does not collect any of the following — not locally, and certainly not remotely:

  • Your name, email, phone number, or any account details
  • Your IP address, device ID, or browser fingerprint
  • Your browsing history, tabs, bookmarks, or cookies
  • The contents of web pages you visit
  • Analytics, telemetry, crash reports, or usage metrics
  • Advertising identifiers
  • Location data

5. Network activity

SeerSign makes zero outbound network requests. You can verify this yourself:

  1. Open Chrome DevTools → Network tab while using SeerSign.
  2. Scan any document.
  3. Observe that no requests leave the extension during or after analysis.

The extension's manifest.json does not declare any host_permissions for third-party servers. The content_security_policy explicitly allows only 'self' for scripts.

Honest caveat about fonts

This privacy policy page (not the extension itself) loads web fonts from Google Fonts for visual consistency across the Seerror site. The extension popup does not load any external fonts — it uses only bundled, local resources.

6. Permissions we request, and why

PermissionWhy SeerSign needs it
contextMenus To add the right-click “Analyse with SeerSign” option on documents and images.
storage To save your scan history locally in chrome.storage.local on your device.
activeTab To receive the document or image you explicitly chose to analyse from the current tab.
unlimitedStorage Because OCR language data and bundled template databases can exceed the default 5 MB storage quota. All of this stays on your device.
<all_urls> content script To enable right-click analysis on any web page. The script is lightweight and does not read general page content — it only responds when you explicitly invoke the extension.

7. Children's privacy

SeerSign is not directed at children under 13. Because we do not collect personal data from anyone, we do not collect it from children either. If you are a parent or guardian and are concerned about your child using SeerSign, you can uninstall it at any time via Chrome's extension settings.

8. Sale and sharing of data

We do not sell, rent, trade, or share data with anyone, for any purpose. There is no data to sell, because none is collected. This is not a marketing claim — it is a technical fact enforced by the extension's architecture.

9. Security

Because all analysis happens on your device and no data leaves it, SeerSign's attack surface for data leakage is effectively zero. The extension is built on Manifest V3, uses a strict Content Security Policy, and ships with no remote code execution.

If you discover a security issue in SeerSign, please report it privately to seerrorworks@gmail.com. We respond to security reports quickly and will acknowledge responsible disclosure.

10. Your rights

Because SeerSign holds no data about you, there is nothing for us to disclose, correct, or delete about you on our side. Your scan history is entirely under your control via the extension popup:

  • View history: Open SeerSign → History tab.
  • Clear history: Click the “Clear history” button in the History tab. All local records are erased from your device.
  • Uninstall: Remove the extension from chrome://extensions. All local storage associated with the extension is deleted by Chrome.

Because SeerSign does not collect, process, or transfer personal data outside of your own device, most data-protection regimes apply only in a limited sense. Specifically:

  • India DPDP Act 2023: No personal data is collected, so no consent, notice, or data-principal rights framework is triggered.
  • GDPR (EU): No data controller/processor relationship is created between Seerror and the user.
  • CCPA (California): No “sale” or “sharing” of personal information occurs.

This does not reduce your general privacy rights under these laws — it simply means SeerSign does not create obligations under them, because it does not collect data.

12. Changes to this policy

If we ever change what SeerSign does with data, we will update the version number of the extension, publish an updated policy here, and list the changes at the top of this page. We will never change the architecture in a way that silently introduces data collection — if the extension ever begins any form of telemetry, it will be visible in the source code, disclosed in this policy, and opt-in rather than default-on.

What this policy does NOT cover

This page covers only the SeerSign browser extension. Other Seerror products (Seerguard, Seerraze, Seerie) have their own privacy policies. The seerror.com website uses standard web hosting and minimal analytics to measure page views — see the site-level privacy policy for details.

13. Contact

Questions, bug reports, or privacy concerns:

Questions about this policy: SeerSign product page · Contact Us · Seerror Privacy Policy

Seerror — privacy-first security tools

SeerSign Chrome extension — Powered by Seerror