What PrivCaptcha actually does
Seven capabilities, and one of them is the reason most people move: your visitors' IP addresses are never stored.
Why most people switch
Privacy and GDPR
A captcha you can defend to your DPO.
Risk scoring
A challenge sized to the request.
Proof-of-work
Priced against volume, not against people.
Accessible challenge
An accessible path, not an apology.
Drop-in migration
Your existing integration already fits.
No Google dependency
It works wherever your visitors are.
Per-site dashboard
The whole telemetry surface, per site and per day.
Common questions about the PrivCaptcha feature set
Straight answers on how the challenge works, what we keep, and what actually changes on your side when you switch.
Privacy, almost every time. Teams arrive because a review flagged the captcha that was already on the page, and they stay because the rest of the list turned out not to be a compromise.
The ones that are choices, yes - the accessible path can be configured per site. Risk scoring and proof-of-work are not switches; they are how a challenge is built, and they are enforced server-side so nothing on the page can opt out of them.
No. There is no privacy tier or accessibility add-on - every feature here is in every plan, including the free one.