Moving from reCAPTCHA to hCaptcha

What this post added

This post details the migration from Google's reCAPTCHA to hCaptcha for CAPTCHA challenges. The rationale includes addressing customer privacy concerns related to Google's data usage, overcoming regional blocking issues (e.g., in China), and avoiding significant cost increases from Google's new charging model. The post highlights the benefits of hCaptcha, including its privacy-focused data handling, performance, accessibility features, support for Privacy Pass, and global availability. It also explains how Cloudflare leveraged its Workers platform to reduce hCaptcha's operational costs and negotiated a payment model. The post breaks down the usage of CAPTCHAs across various Cloudflare features like Firewall Rules, Bot Management, IP Firewall, Security Level, and DDoS protection, noting that free customers and paying customers utilize CAPTCHAs with roughly even distribution. Finally, it provides channels for users to report issues with the new implementation and reiterates the ongoing effort to minimize CAPTCHA usage.