PrivCaptcha.com

PrivCaptcha, the modern privacy-first captcha built for GDPR

A free captcha and reCAPTCHA alternative: fast, accessible and private, with no tracking, no Google and no ad-tech. Risky traffic simply gets a harder puzzle, and the first 10,000 verifications each month cost nothing.

5-minute setup Built for GDPR & CCPA 10,000 verifications/month free
PrivCaptcha the captcha everything else orbits
Credential stuffing Scraping Signup spam Spam comments Account takeover Click fraud Card testing Sweepstakes fraud Ticket scalping Inventory hoarding

How PrivCaptcha sizes every challenge to the risk

PrivCaptcha doesn't care who your visitors are, only whether the request looks automated. Risk scoring from request signals picks a difficulty from 1 to 5. Everyone solves a puzzle, and a suspicious client has to solve a much harder one, so there is no silent pass for a script to aim at. That is the difference from invisible reCAPTCHA or any other invisible captcha: human verification here is always a short task the visitor can see.

Example decision Scoring from request signals
Signals in

Only what the request itself reveals.

One score

A single risk number, computed on the server and never accepted from the client. There is no rule file to keep current.

Difficulty out

The score picks a level from 1 to 5. No request skips the are you human check, and a client that looks automated gets a much harder one.

Designed for privacy from day one

No tracking cookies, no fingerprint resale, no ad-tech. We never store your visitors' IP addresses, and we minimize everything else we touch. Built for GDPR and CCPA obligations rather than around them.

GDPR CCPA IP addresses Tracking cookies Fingerprinting

PrivCaptcha features that stop bots without profiling people

Event log EXAMPLE
verified slider · difficulty 1 siteverify ok
solved no-visual challenge · keyboard proof-of-work ok
failed rotate · difficulty 5 · off by 41° retry issued
served pick · difficulty 4 · 10 shapes awaiting solve

Every request scored from its own signals

Every request is scored from what the request itself reveals, and the score picks the puzzle difficulty. Headless browsers and automation frameworks land at the top of the range.

Difficulty that scales with the request

Tolerances tighten and the proof-of-work gets heavier as a request looks more automated, so there is nothing for you to configure and no threshold to keep current.

±20° rotate
±12px slider
5 shapes

Chosen per request from the risk score.

<!-- swap two lines, done -->
<script src="https://privcaptcha.com/1/api.js" async defer></script>
<div class="privcaptcha" data-sitekey="your-site-key"></div>

Keeps your reCAPTCHA markup

Swap the script tag and sitekey, keep your backend flow. Our endpoint speaks both the reCAPTCHA and the hCaptcha siteverify shape, so existing verification code keeps working unchanged.

reCAPTCHA siteverify hCaptcha siteverify
Server SDKs

A way through for screen-reader and keyboard visitors

Screen-reader and keyboard users get a non-visual challenge that is a first-class path, not a broken fallback.

No-visual challenge
Keyboard operable · no image, no audio CAPTCHA
screen readers keyboard only no color cues
One visitorone puzzle, one proof
Bot at 10k attempts10k proofs

Every attempt costs compute

Each challenge carries a small computation the client has to finish. A person pays it once and never notices. A farm hitting your signup form thousands of times a minute pays it every single time.

Privacy by design

We never store your visitors' IP addresses, and your users' data is never the product.

What is kept
A truncated HMAC of the IP, under a salt that rotates daily
Solve and failure counts, expiring after 24 hours
What is never touched
Raw IP addresses
Cookies of any kind
Device fingerprints
Anything sold or shared

Works on networks that block Google

Nothing loads from a Google domain, so the widget behaves the same wherever your visitors are and whatever browser they hardened.

Daily counts for every site you run

Served, solved, failed and verified, per site and per day. That is the whole telemetry surface; there is nothing about the visitor to show you.

served solved failed verified
Illustrative shape only, not real traffic.

Who uses PrivCaptcha?

One captcha service, whatever you are protecting. Whether you need a captcha for a website login, a checkout or a public form, it is the same widget, the same siteverify call and the same privacy guarantees.

Checkout, signup and gift-card forms

Card testing, gift-card draining and inventory hoarding all arrive at the same handful of endpoints, and all three are volume games: the attacker needs thousands of attempts for the numbers to work. A proof-of-work challenge on every attempt turns a free script into a metered one, while a real buyer solves a slider once and carries on to the payment step.

Where the widget goes
  • Checkout and payment
  • Gift-card balance check
  • Account registration

Login and onboarding

A captcha on a banking login sees every customer who ever signs in, which makes it the worst place on the site to hand a third party a profile of that person. PrivCaptcha never stores a visitor's IP address and loads nothing from an ad network, so adding friction for credential stuffing does not mean adding a data-sharing relationship you then have to disclose.

Where the widget goes
  • Login
  • KYC onboarding
  • Password reset and contact change

Teams moving off an older captcha

Our siteverify endpoint answers in both the reCAPTCHA and the hCaptcha response shapes, so the verification code already running on your backend keeps working unchanged. The migration is the script URL, the verify URL and the keys; server SDKs for Go, Node, PHP and Python cover the rest, and the free tier covers most trial and contact forms outright.

Where the widget goes
  • Trial signup
  • API key request
  • Contact and demo forms

Account creation, giveaways and in-game economies

Multi-accounting and giveaway abuse scale with how cheap an account is to make. A puzzle and a proof-of-work on every registration and every entry put a real price on each one, and because the level is picked per request, the players who are not farming still get the quick version rather than a blanket lockdown.

Where the widget goes
  • Registration
  • Giveaway and drop entry
  • Trade and market listing

Public services have to work for everyone who arrives

A public form cannot quietly exclude the people who most need it. The non-visual challenge is a first-class path for screen-reader and keyboard users rather than an audio clip bolted on at the end, and nothing loads from a Google domain, so the form still works on hardened networks, on privacy browsers, and in regions where those services are unreachable.

Where the widget goes
  • Benefit and permit applications
  • Appointment booking
  • Inquiry forms

Endpoints that cost you money on every call

SMS sends, prepaid top-ups and number lookups all bill per request, so automated abuse shows up on the invoice before it shows up anywhere else. Scoring each request from what it reveals about itself sizes the puzzle per attempt instead of blocking whole carriers or regions, which matters when one mobile NAT sits in front of thousands of real subscribers.

Where the widget goes
  • SMS verification send
  • Prepaid top-up
  • Number lookup

A captcha you can put in your own privacy policy

If the promise of your product is that you do not track people, a captcha that fingerprints them undoes it on your most sensitive page. We keep a daily-rotating HMAC of the IP rather than the address itself, expire the counters after 24 hours, set no tracking cookies and sell nothing, so the paragraph you write about us is short.

Where the widget goes
  • Signup
  • Contact form
  • Newsletter subscribe

Why switch to PrivCaptcha?

Every captcha provider on this list stops automated traffic, and all of them are run by people who know the problem well. If you are looking for the best captcha for privacy, the difference is what happens to your visitors on the way through: who their request is shared with, and what is kept afterwards.

Capability PrivCaptcha reCAPTCHA hCaptcha Turnstile
Run by RapidFoundry Google Intuition Machines Cloudflare
What visitors see A short puzzle sized by risk A checkbox, image grids, or nothing with v3 A checkbox and image challenges Usually nothing, sometimes a checkbox
Stops automated traffic
Drop-in reCAPTCHA and hCaptcha siteverify
Non-visual accessible challenge Built in, keyboard operable Audio challenge Accessibility program Not published
Never stores visitor IP addresses See their policySee their policySee their policy
Loads from a Google domain
Proof-of-work on every challenge Not published Not published One of several browser checks
Tuning required None, scales per request Score threshold Difficulty setting Widget mode
Free tier 10,000 verifications a month 10,000 assessments a month Free plan Free, no request cap
Personal data points sold 0See their termsSee their termsSee their terms

The privacy column is the reason to pick a captcha alternative at all. A captcha sits on your most sensitive forms, which makes it the last place you want a third party building a profile of the person filling them in. We never store your visitors' IP addresses, we sell nothing, and nothing loads from an ad network.

Compiled from publicly available documentation in November 2026. Where a behavior is not published we say so rather than guess, and each vendor's current terms are the authority on their own product.

PrivCaptcha implementation: migrate in a few minutes

As a Google reCAPTCHA alternative, PrivCaptcha answers on reCAPTCHA's and hCaptcha's own script paths and returns their verify shapes, so the markup, the response field and the backend call you already have keep working. You change the script URL, the verify URL and the keys. That is the whole migration, and it is usually done inside one deploy. If you want a Cloudflare Turnstile alternative, the move takes one extra edit, and the guide below says exactly which.

Server SDKs for Go, Node, PHP and Python, or call the captcha API through its REST endpoint directly.

Frequently asked questions about PrivCaptcha

Straight answers on how the challenge works, what we keep, and what actually changes on your side when you switch.

Because at the moment the request arrives the server has no way to know that. It sees headers and an address, not a person, so most systems guess, and the guess is wrong often enough that real customers get blocked, especially on a VPN, a shared office connection or a privacy browser. PrivCaptcha does not guess at your identity. Everyone gets a puzzle, and the only thing the score changes is how hard it is. A bad guess costs you a few extra seconds instead of your account.
An invisible captcha decides in the background from signals about the visitor, which is why it needs tracking. PrivCaptcha takes the other route: every visitor gets a short, visible task, and the server sizes it from the request alone. Nothing is collected that an invisible check would need, and there is no silent pass for a script to aim at.
Not in the sense of making a route unreachable. No captcha does that. Solver farms and automation exist, and anything a person can solve can eventually be solved for money. What a captcha really does is put a price on each attempt, so abuse that only pays at volume stops paying. PrivCaptcha is built around that honestly rather than around a claim of being unbreakable: the puzzle prices the attempt, the proof-of-work prices the scale, and a client that keeps failing pays more each time.
Not today, and that is the quiet advantage. The solving services that make bot work cheap sell turnkey support for the big names: you pay per solve and their SDK handles reCAPTCHA or hCaptcha for you, because a captcha on millions of sites is worth building against once and selling forever. Nobody ships a package for us, so an attacker has to write a custom solver, keep it running, and redo that work whenever our challenges change. That is real engineering time before the first request goes out, and every solve still pays the proof-of-work on top. We would rather be straight about the shape of this: it is an economic advantage, not a mathematical one. If we became the default captcha, solvers would follow.
The one that sends the least about your visitors to anyone. Ask each captcha provider whether IP addresses are stored, whether cookies are set, whether a fingerprint is built and whether any of it reaches an ad business. PrivCaptcha's answer is no to all four: a daily-salted hash, kept for 24 hours, is the only trace a visit leaves.
Because the answers were worth something. Those grids doubled as free labeling for the provider's own datasets, so visitors were doing unpaid work on the way into a form. Rotating a disc or dragging a piece into a notch generates no dataset, trains nothing and is worth nothing to us beyond the seconds it takes; there is no second product being built out of your visitors' time.
Four things: what happens to your visitors' data, whether the challenge works for people who cannot see it or use a mouse, how much of your code has to change, and what it costs at your volume. PrivCaptcha's answers are no stored IP addresses and no cookies, a non-visual path that is on by default, two URL changes from reCAPTCHA or hCaptcha, and 10,000 free verifications a month, counted only when your backend verifies a token.
10,000 verifications a month are free, which covers most contact, signup and comment forms outright. Beyond that the account needs quota or credits; if both run out we stop issuing challenges and the widget shows a quiet unavailable state rather than breaking your page.
Yes. The widget and the REST verify endpoint at /api/v1/siteverify are free for 10,000 verifications a month, with server SDKs for Go, Node, PHP and Python. There is no separate API plan: the same keys work for the widget and the verify call.
No, and not because we filter that traffic out afterwards, but because the meter never counted it. A verification is charged only when your own backend successfully verifies a token, and each token can be redeemed exactly once. So spending a single unit of your quota means an attacker had to pass a real challenge: a puzzle plus its proof-of-work on the visual path, or a fixed 22 bits of work on the non-visual one. Then they had to get your backend to check the token, by which point it is a request you would have wanted verified anyway. The challenge endpoint is also rate limited to 10 requests a second per address, and once you have listed your domains, a request from any other origin is refused before a challenge is issued.

Add PrivCaptcha now, in two lines of code

Drop in the script tag and sitekey and point your existing siteverify call at us. 10,000 verifications a month are free.