Why server-side checking is a trade-off
A cloud detector has to receive your content to analyse it, which means whatever you paste or upload is now on someone else's infrastructure, possibly logged, and tied to an account you created. For casual public content that's no big deal; for anything sensitive it's a real cost.
On-device checking avoids the trade entirely. The analysis happens locally when you scan, so there's no upload step and nothing to retain server-side. Privacy comes from the architecture, not from a policy you have to trust.
Calm verification, no setup
Because there's no account and no sign-in, there's also nothing to set up and no history to clean out later. You install verifai, scan when you want a read, and get a 0–100 confidence score on the images and text in front of you.
It's a deliberately quiet tool: on demand rather than always-on, local rather than cloud, built for a web that's filling up with synthetic images and writing.
frequently asked
- Does verifai send what I scan to a server?
- No. It runs on-device in your browser and keeps no server-side history of what you check.
- Do I need an account?
- No account and no sign-in. You install the extension and scan on demand.
- Can I use it on private or unpublished content?
- Because checking happens locally, you can scan content without uploading it. As always, follow any rules that apply to the material itself.
- Is it always running in the background?
- No. verifai only checks a page when you hit scan, so it isn't monitoring your browsing.
Last updated June 7, 2026