privacy

privacy policy

verifai is built to answer one question — “is this ai-generated?” — without watching you do it. the free tier runs entirely on your device.

last updated: 7 june 2026

the short version

verifai's free tier processes everything locally in your browser. it has no accounts, no analytics, and no servers that see your browsing. it does not collect, store, sell, or share any personal data.

what we collect

nothing personal. verifai does not collect names, emails, browsing history, page content, or identifiers. there are no accounts and no analytics or tracking code in the extension.

the only thing verifai stores is a single on/off preference, kept in your browser's local storage (chrome.storage.local) on your own machine. you can clear it at any time by removing the extension.

how a scan works

when you click scan, verifai looks at the images and text on the tab you're viewing. for images, it reads the first portion of each image file to check for embedded provenance credentials (the c2pa / iptc “digital source type” standard that tools like dall·e, adobe firefly, and google gemini stamp into their output). for text, it applies a transparent on-device heuristic.

all of this happens locally. image data is read only to inspect its embedded credentials and is never uploaded to a verifai server, stored, or used for anything else. scans run only when you ask for them — nothing runs in the background.

permissions, and why

chrome requires verifai to declare the capabilities it uses. each one maps directly to a feature:

  • activeTab & scripting— to scan and highlight the page you're currently looking at, only when you click scan.
  • storage — to remember your on/off toggle, locally.
  • host access (all sites)— so you can run a scan on any page, and so verifai can read an image's embedded credentials regardless of which site hosts it. it is used solely for on-demand, on-device scanning.

third parties

the free tier sends nothing to third parties. verifai contains no advertising, no trackers, and no third-party analytics.

optional paid features (coming later)

we plan to add an optional “deep scan” that uses a hosted detection model to assess images with no embedded credentials (for example, screenshots). that feature will be opt-in: only images you explicitly choose to deep-scan would be sent to the detection service, and this policy will be updated to describe it before it launches. it is not part of the free tier.

changes

if this policy changes, we'll update the date above and, for material changes, note it in the extension or on this page.

contact

questions? reach out via ogbuilds, the studio behind verifai.