Set up your bannerConfigure Your ToolsGoogle Services

reCAPTCHA

How to configure reCAPTCHA at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features

Overview

This guide explains how to implement different privacy configurations for Google reCAPTCHA and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. This guide covers reCAPTCHA on websites (score-based "v3" keys and challenge-based checkbox keys) as offered through Google Cloud. Google's current documentation also refers to the product as part of Google Cloud Fraud Defense.

Out of scope. reCAPTCHA in native mobile apps; SMS toll-fraud defence; payment-page transaction signals.

What the service does in this scope. reCAPTCHA runs a risk analysis to distinguish humans from bots. It sets a cookie named _GRECAPTCHA "when executed for the purpose of providing its risk analysis".

Change of legal role on 2 April 2026. Since 2 April 2026, Google acts as data processor; customers are the sole data controller of Customer Data, which Google processes under the Google Cloud Terms of Service and the Cloud Data Processing Addendum. Google has removed the references to its own Privacy Policy and Terms of Use from the badge, and customers should remove such references from their sites.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskreCAPTCHA loaded only on pages containing a protected form, from www.recaptcha.net, after consent.
Configuration B — Higher risk (default snippet)reCAPTCHA (score-based key) loaded on every page from www.google.com to score all site traffic, after consent.

⚠ Recommendation — no-consent use is legally uncertain. Google describes _GRECAPTCHA as a "necessary" cookie. Whether storing it qualifies for the strictly-necessary exemption (Art. 5(3) ePrivacy Directive / § 25(2) No. 2 TDDDG) has not been settled, and Google's documentation does not list the session data collected or a retention period. This guide therefore offers no configuration without prior consent. An operator who loads reCAPTCHA before consent on a form page should document the reasoning and have it reviewed by their DPO or independent legal counsel.

Prerequisites and limitations.

  • Google does not document the specific data collected, the retention period or the processing location for reCAPTCHA data on its FAQ page.
  • If consent is refused, the protected form needs a fallback (for example, a server-side spam check), because the form cannot be verified without reCAPTCHA.
ActionConfiguration A — Lower riskConfiguration B — Higher risk (default snippet)
Pages where reCAPTCHA loadsOnly pages with a protected formAll pages
Script domainwww.recaptcha.netwww.google.com
LoadingBlocked by Consenter until consentBlocked by Consenter until consent
BadgeShown, or hidden with the text "This site is protected by reCAPTCHA."Shown
Consenter Manager entriesOne entry (Google as Processor)One entry (Google as Processor)

Step 1 — Configure reCAPTCHA

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Higher risk (default snippet)
1Processing purposesOperator decisionUnlock additional website features (form protection)Unlock additional website features (form and site protection)
2Pages on which the script loadsWebsite codeOnly pages with the protected formEvery page (score-based key used to assess all traffic)
3Script domainReplace https://www.google.com/recaptcha/api.js with https://www.recaptcha.net/recaptcha/api.js and apply the same change wherever www.google.com/recaptcha/ is usedwww.recaptcha.netwww.google.com (default)
4LoadingConsenter script blocking for the reCAPTCHA entryBlocked until consentBlocked until consent
5Badge and disclosureCSS .grecaptcha-badge { visibility: hidden; } plus the text "This site is protected by reCAPTCHA." in the user flowOptionalBadge shown
6References to Google's Privacy Policy and TermsWebsite text and privacy policyRemove (Google is processor since 2 April 2026)Remove
7Contractual basisGoogle Cloud Terms of Service and Cloud Data Processing AddendumAppliesApplies
8Retention of reCAPTCHA dataNot configurable / not documented——

Configuration A — Lower risk

  1. Intended use. Bot protection for a specific form (contact, login, registration).
  2. Implementation steps.
    1. Load the reCAPTCHA script only on pages containing the protected form.
    2. Use www.recaptcha.net as the script and frame domain.
    3. Configure Consenter to block the script until consent and provide a fallback for visitors who refuse.
    4. If you hide the badge, add "This site is protected by reCAPTCHA." visibly in the user flow and remove references to Google's Privacy Policy and Terms.
  3. Resulting processing. On the form page, the script runs a risk analysis and sets _GRECAPTCHA. Using www.recaptcha.net avoids sending other cookies that may exist on the www.google.com domain.
  4. Why lower risk. Processing is limited to the pages where protection is needed, and the google.com domain is not contacted.

Configuration B — Higher risk (default snippet)

  1. Intended use. Site-wide bot and abuse detection with a score-based key.
  2. Implementation steps. Load the default snippet from www.google.com on all pages; block it until consent.
  3. Resulting processing. Risk analysis runs on every page view, so browsing and interaction signals from the whole visit are processed. Requests to www.google.com may carry other Google cookies present on that domain.
  4. Why higher risk. Processing covers the entire visit rather than one form, and requests go to the google.com domain.

Step 2 — Map the configuration in the Consenter Manager

Processing location (applies to all entries). Google does not document a processing location for reCAPTCHA data. Google LLC is a US company and can be required to disclose data in its possession, custody or control regardless of storage location. The United States is therefore listed as a potential processing and access location.

Configuration A — Lower risk

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesUnlock additional website featuresProtection of the form so that it can be used.
Tracking methodThird party tracking (crosssession, cross-website)_GRECAPTCHA is set on the reCAPTCHA domain, which is shared by all sites using reCAPTCHA. Its lifetime is not documented by Google. Reasoned mapping: the cookie can recognise the browser across sessions and sites; Google states the data is used only to provide and secure the service.
IdentifierDevice identifiers, IP address_GRECAPTCHA cookie; IP address with each request.
Data categoriesDevice identifiers, IP address, Device characteristics, Browsing and interaction dataRisk analysis on the form page. Google does not list the session data collected.
Legal role of data recipientProcessorSince 2 April 2026, under the Cloud Data Processing Addendum.
Personalisation modelNo personalisationData used only for the service and its security.
Maximum storage durationNot documentedNo retention period published.
Processing locationUnited States as potential processing and access locationSee note above.

Configuration B — Higher risk (default snippet)

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesUnlock additional website featuresAs in A.
Tracking methodThird party tracking (crosssession, cross-website)As in A.
IdentifierDevice identifiers, IP addressAs in A.
Data categoriesDevice identifiers, IP address, Device characteristics, Browsing and interaction dataSignals from every page of the visit.
Legal role of data recipientProcessorAs in A.
Personalisation modelNo personalisationAs in A.
Maximum storage durationNot documented—
Processing locationUnited States as potential processing and access locationSee note above.

Privacy-policy follow-up

  • Purpose and recipient: bot and abuse protection; Google as processor (no longer a reference to Google's Privacy Policy).
  • Data and storage on the device: _GRECAPTCHA cookie; IP address; device and interaction signals.
  • Legal bases: distinguish the ePrivacy / TDDDG consent for the cookie from the GDPR legal basis for the risk analysis.
  • Transfers: Google LLC in the US; potential access by US authorities.

Verification checklist

  • Before consent: no request to www.google.com/recaptcha, www.recaptcha.net or www.gstatic.com/recaptcha.
  • After consent (A): reCAPTCHA loads only on form pages and only from www.recaptcha.net.
  • Badge text: no remaining references to Google's Privacy Policy or Terms of Service.
  • Fallback: form remains usable or offers an alternative when consent is refused.
  • Open points: retention period and processing location of reCAPTCHA data.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page