The whole telemetry surface, per site and per day.
Served, solved, failed and verified. That is everything we record, because there is nothing about the visitor to show you.
How it works
Counts you can reconcile
Per site and per day, so you can hold the numbers against your own funnel or a campaign report and see whether a route is still being worked.
Several sites, one account
Each site has its own sitekey, its own secret and its own domain allowlist, so a key leaking from one does not open another.
Nothing personal in it
There is no visitor list, no session replay and no per-person history - not withheld, simply never collected.
What that means concretely
Each of these is a statement about how the product behaves, not a description of how we feel about it.
Four counters per site per day: served, solved, failed, verified.
Secrets are stored encrypted and can be re-displayed, not just rotated.
A site's secret can never be derived from its public sitekey.
Per-site dashboard in PrivCaptcha: common questions
What per-site dashboard actually does, and where it stops.
No, and that is deliberate. The dashboard shows counts and rates; there is no visitor list underneath it, because the data that would build one is never collected.
Served counts challenges the widget handed out. Verified counts tokens your backend successfully checked. A wide gap between them usually means people are abandoning the form, or that your verify call is not being made.
So the numbers mean something and the blast radius stays small. Each site carries its own domain allowlist, so a leaked sitekey cannot be pointed at someone else's pages.
Every request is challenged - there is no invisible pass to aim a script at, and no allowlist that skips the check. What changes is the form the challenge takes and what it costs. The server scores each request and picks one of five difficulty levels, so an ordinary visitor gets a couple of seconds and a client that looks automated gets tight tolerances and a heavier proof-of-work. On the non-visual path, taken by screen-reader and keyboard visitors, there is no puzzle to solve at all: the proof-of-work is the whole challenge, at a fixed 22 bits.
Change two lines. Keep the rest.
10,000 verifications a month are free, and the integration is the one you already have.