What Is reCAPTCHA?
reCAPTCHA is Google's service for telling human visitors apart from automated traffic on websites and in mobile apps. Google acquired it in 2009 and offers it in several versions, from a visible CAPTCHA checkbox to scoring that runs entirely in the background. In 2026 it changed in two ways that matter to anyone running it: it became part of a larger Google Cloud platform, and legal responsibility for the data it processes moved to the site operator.
Versions and How They Work
reCAPTCHA v2 comes in two forms. The checkbox asks visitors to confirm "I'm not a robot" and can follow up with an image challenge; the invisible variant drops the checkbox and by default prompts only the most suspicious traffic. reCAPTCHA v3 never interrupts anyone: it returns a score between 0.0 and 1.0, where 1.0 indicates a very likely legitimate interaction, and leaves the decision to the site. The enterprise line, sold through Google Cloud as reCAPTCHA Enterprise, adds reason codes, site-specific tuning and mobile SDKs. All versions follow the same pattern: a script loaded from Google's servers collects signals in the browser and issues a token, which the site's backend submits to Google for an assessment before accepting the login or checkout. Like any risk score, the result still has to be turned into a decision.
From Enterprise to Fraud Defense
Google moved reCAPTCHA into Google Cloud in stages. Between late 2025 and early 2026 it migrated the remaining classic site keys into Google Cloud projects. On 22 April 2026 it introduced Google Cloud Fraud Defense as "the next evolution of reCAPTCHA": reCAPTCHA remains the bot defense core, joined by account, password, SMS and transaction protection. Existing customers became Fraud Defense customers automatically, with site keys and integrations unchanged. One addition, still in preview, is a QR code challenge that has the visitor complete verification on a phone, an approach built on device attestation. Billing runs through three tiers: Essentials, free up to 10,000 assessments per month per organization; Premium, billed by usage beyond that; and Enterprise, a subscription with a twelve-month minimum.
Privacy Considerations for EU Site Owners
Since 2 April 2026, Google acts as a processor for reCAPTCHA data, and the site operator is the sole controller. The badge no longer points to Google's privacy policy, so the operator's own privacy notice has to describe the processing and its purpose, and the operator owns the legal basis. A GDPR assessment then faces several questions. Every protected page sends visitor data such as the IP address to Google, which raises the question of where it is processed and under which transfer mechanism. reCAPTCHA sets a cookie that Google classifies as necessary; whether that holds under the ePrivacy consent rules is for the operator to assess. And the processor terms let Google use the data to keep its detection effective against evolving threats, a scope worth reading closely. Operators who prefer fewer open questions can choose a service built differently: CaptchaFox runs on EU infrastructure without cookies and offers a reCAPTCHA-compatible API, so migrating mostly means renaming the script URL, field names and verification endpoint. Our guide to reCAPTCHA alternatives compares the options.
About CaptchaFox
CaptchaFox is a GDPR-compliant solution based in Germany that protects websites and applications from automated abuse, such as bots and spam. Its distinctive, multi-layered approach utilises risk signals and cryptographic challenges to facilitate a robust verification process. CaptchaFox enables customers to be onboarded in a matter of minutes, requires no ongoing management and provides enterprises with long-lasting protection.
To learn more about CaptchaFox, talk to us or start integrating our solution with a free trial.