{"id":3680,"date":"2026-04-17T09:54:33","date_gmt":"2026-04-17T09:54:33","guid":{"rendered":"https:\/\/www.captcha.eu\/?p=3680"},"modified":"2026-04-17T09:54:34","modified_gmt":"2026-04-17T09:54:34","slug":"typo3-recaptcha-alternatief","status":"publish","type":"post","link":"https:\/\/www.captcha.eu\/nl\/typo3-recaptcha-alternatief\/","title":{"rendered":"TYPO3 reCAPTCHA Alternatief: Hoe reCAPTCHA vervangen op Europese websites"},"content":{"rendered":"\n
\"TYPO3
captcha.eu<\/figcaption><\/figure>\n\n\n\n

reCAPTCHA on TYPO3 means cookies, US data transfers and a growing compliance burden that most DACH teams no longer want to carry. This guide explains what changed in 2026, which GDPR-compliant alternatives work with EXT:form and PowerMail and how to replace reCAPTCHA without touching every form individually.<\/p>\n\n\n\n

<\/path><\/svg><\/span><\/span>Estimated reading time: <\/span>11<\/span> minutes<\/span><\/p>\n\n\n\n

\n
Try CAPTCHA.eu free – no credit card<\/a><\/div>\n\n\n\n
View all integrations<\/a><\/div>\n<\/div>\n\n\n\n

At a Glance<\/h2>\n\n\n\n
\n

The core problem<\/strong><\/strong><\/h3>

reCAPTCHA sets the\u00a0_grecaptcha cookie, routes data through US servers, and creates ePrivacy consent obligations on every TYPO3 form it protects<\/p><\/div><\/div><\/div><\/div><\/div>\n\n\n\n

What changed in April 2026<\/strong><\/strong><\/strong><\/strong><\/h3>

Google moved to a processor model but the cookie remains. TYPO3 operators still need a lawful basis, updated privacy notices, and an ongoing consent assessment<\/p><\/div><\/div><\/div><\/div><\/div>\n\n\n\n

The practical alternative<\/strong><\/strong><\/strong><\/h3>

A proof-of-work CAPTCHA installed via Composer: no cookies, no US transfers, no cookie-consent layer for the CAPTCHA itself, compatible with EXT:form and PowerMail<\/p><\/div><\/div><\/div><\/div><\/div>\n<\/div><\/div>\n\n\n\n

\n\n\n

What this guide covers<\/h2><\/div>