> You acknowledge and understand that the reCAPTCHA API works by collecting hardware and software information, such as device and application data and the results of integrity checks, and sending that data to Google for analysis. Pursuant to Section 3(d) of the Google APIs Terms of Service, you agree that if you use the APIs that it is your responsibility to provide any necessary notices or consents for the collection and sharing of this data with Google. For users in the European Union, you and your API Client(s) must comply with the EU User Consent Policy [...]
The "EU consent policy" from Google is here:
https://www.google.com/about/company/user-consent-policy.htm...
You actually have to make a separate, opt-in checkbox, directly informing the user what will happen.
Why resort to flimsy legal methods when you can just use uMatrix and block those requests directly? It's your computer, after all.
Users need to be directly and visibly be informed, if and when data of theirs will be transmitted to third parties.
As Google's ReCaptcha is based on tracking what websites you visit, what search terms you enter, correlating this data, and comparing this tracking profile of yours, it's quite problematic that the user doesn't even see any captcha anymore. With the previous captchas, site owners could keep pushing the legal problems to Google, partially.
But this new solution doesn't fit with the EU Data Privacy Directive in neither intention nor letter of the law.
IANAL, this is not legal advice. You can not use this in court.