Problem/Motivation
The module currently renders alternate branding text in the form when the hide_badge option is enabled. That text says:
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Google notified customers that starting on April 2, 2026, websites using reCAPTCHA should remove references to Google's Privacy Policy and Terms of Use shown in connection with reCAPTCHA.
That means the module's current hide-badge branding text appears to be outdated and potentially non-compliant with Google's updated guidance.
Relevant Google notice/background:
- Email notification from Google Cloud: [Legal Update] Google transitions to data processor for reCAPTCHA starting Apr 2, 2026
- Google community post about the April 2, 2026 reCAPTCHA data-processor change
Related existing issues:
Steps to reproduce
- Install and configure the
recaptcha_v3module. - Enable
hide_badge. - Render a form protected by reCAPTCHA v3.
- Observe that the form includes text linking to Google's Privacy Policy and Terms of Service.
Proposed resolution
Stop rendering the old Google Privacy Policy / Terms of Service branding text when hide_badge is enabled, and update documentation accordingly. At minimum, the module should no longer output the outdated notice text after April 2, 2026.
Optionally, since showing additional text on the form as a replacement for the badge is no longer necessary, consider making the hide_badge option default to true on new installations.
Remaining tasks
Confirm the exact Google guidance maintainers want to follow.Decide whether this is a bug fix only or a deprecation/removal of(bug fix)hide_badge.- Update the rendered output accordingly.
- Add or update test coverage.
- Update module documentation and release notes.
User interface changes
Forms using reCAPTCHA v3 with hide_badge enabled will no longer display the current Google Privacy Policy / Terms of Service notice text and links.
API changes
None.
Data model changes
None.
| Comment | File | Size | Author |
|---|---|---|---|
| [Legal Update] Google transitions to data processor for reCAPTCHA starting Apr 2, 2026.pdf | 238.64 KB | jwilson3 |
Issue fork recaptcha_v3-3580636
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
jwilson3Regarding the open question:
See https://docs.cloud.google.com/recaptcha/docs/faq#hiding-the-badge
The current reCAPTCHA FAQ still says you may hide the badge only if you show the old branding text with Google’s Privacy Policy and Terms of Service links.
But then there is a new note:
Comment #3
jwilson3Since hiding the badge is still allowed, but showing additional text on the form as a replacement for the badge is no longer necessary, I suggest also considering making the
hide_badgeoption default totrueon new installations.Summary updated accordingly.
Comment #5
jwilson3I reviewed the MR's CI Pipeline failures, and all are unrelated to this issue. I'll file a followup.
Comment #6
jwilson3I created #3580901: Pass GitLab CI pipeline.
Comment #7
jwilson3This needs manual review. The automated tests are failing due to unrelated issues that I just fixed in #3580901: Pass GitLab CI pipeline.
Comment #8
dench0Comment #10
dench0Comment #12
jwilson3I sincerely thank you, Denis!
Comment #13
dench0@jwilson3
Thank you for your work.