ALTCHA
Self-hosted CAPTCHA that proves a visitor is human with a background proof-of-work puzzle. No cookies, no tracking, MIT licensed.
Private alternatives to reCAPTCHA, vetted against our public criteria.
Grouped by threat level
Self-hosted CAPTCHA that proves a visitor is human with a background proof-of-work puzzle. No cookies, no tracking, MIT licensed.
Invisible, managed CAPTCHA from Germany. Uses background proof-of-work and no cookies, so visitors never solve a puzzle.
Self-hosted, proof-of-work CAPTCHA written in Rust. Rate-limits abusive traffic without tracking or profiling your visitors.
No matches for those filters.
| Tool | Hosting | Based in | Cost |
|---|---|---|---|
| | Self-hosted | · | Free |
| | Self-hosted | · | Free |
| | Managed (EU) | Germany | Freemium |
Every CAPTCHA on your site is a request you make of a visitor, and the popular one answers to Google. It watches how people move and click and sets a tracking cookie to follow them, then turns their solving effort into labels that train Google’s own models. All of that is the price of blocking spam you could block another way. The tools here do the same job with a background puzzle that costs a spammer real compute, while asking nothing of your visitor’s privacy.
The data collection is not a setting, it is how reCAPTCHA decides who is human. It scores behavioral signals such as mouse movement and click timing, then ties them to an identifier through the _GRECAPTCHA cookie and sends that to Google’s servers in the US. There is no toggle that keeps the bot-blocking while dropping the surveillance, because the surveillance is the bot-blocking. The data also does double duty: solving its challenges helps train Google’s machine-learning systems. The only way to stop your form from profiling your visitors is to stop using a profiler, which is what every pick on this page lets you do.
Each tool here is held to our public listing criteria: it must block abuse without tracking the visitor, set no advertising cookie, send no visitor data to a third party for profiling, and state plainly how it works. We favor proof-of-work designs that run in the browser and verify on your server, and we list only what we would put on our own contact form. Where a tool compromises, such as being managed rather than self-hosted, we say so.
Start with where the check happens. A self-hosted CAPTCHA like ALTCHA or mCaptcha keeps every request on infrastructure you control, so no visitor data leaves your server. Next, look at the method: a background proof-of-work puzzle stops mass spam without asking your reader to label images. Then check the cookie behavior, because a tool that sets no cookie and stores nothing in the browser is one you can deploy without a consent prompt. Finally, weigh the effort you can spend. Self-hosting gives you the most control, while a managed option like Friendly Captcha trades some of that for a service someone else runs.
Both are a clear step up from reCAPTCHA on privacy, and you may already have heard them recommended. They avoid the advertising-profile problem and are easy to drop in. The honest distinction is that both are still a third party you hand your visitors’ signals to: the verification runs on someone else’s servers, and you are trusting that company’s data terms rather than removing the third party entirely. That is a different posture from a self-hosted CAPTCHA, where nothing about the visitor ever leaves your own server. Both are reasonable if a managed service suits you, but for that reason we point you at the EU-based managed option above instead, and reserve our top spots for tools you can run yourself.
Pick one tool and drop its widget into the form you want to protect, then verify the response on your server, which each project documents with copy-paste examples. Most people start with a single high-spam form, a contact box or a signup, confirm the puzzle is doing its job, then roll it out across the site. If you are moving off Google’s tool specifically, our reCAPTCHA alternatives page walks through the swap. CAPTCHA is rarely the only Google script on a site, so pairing this with privacy-friendly analytics and a comment system that does not phone home closes more of the same leak. To cut Google out across the board, the de-Google playbook covers the rest.