• Resolved james4311

    (@james4311)


    I wonder if anyone could clarify:

    1. How to block MailPoet’s Google reCaptcha implementation from loading until a user has consented to running it.
    2. What is MailPoet’s default fallback form behaviour if a user doesn’t consent to running reCaptcha and how can this behaviour be configured?

    Obtaining a user’s consent before loading Google reCaptcha is required for MailPoet to be GDPR compliant, correct?

    I couldn’t find any info about this on the “Guide to Conform to GDPR” help page.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Saravanan S, a11n

    (@simplysaru)

    Hi @james4311 ,

    Thanks for reaching out with your questions about reCAPTCHA and GDPR compliance with MailPoet.

    If you want to be fully GDPR-compliant and avoid issues with Google, use the built-in CAPTCHA option instead of the Google reCAPTCHA options. The extension just uses Google’s integration for reCAPTCHA. So there is no built-in way to prevent the reCAPTCHA from loading until user consent.

    If you ned to be fully compliant, yes, you need user consent before loading the Google reCAPTCHA.

    I hope that helps. Please let us know if we can clarify anything further.

    Thread Starter james4311

    (@james4311)

    Thanks for clarifying, @simplysaru .

    Plugin Support Saravanan S, a11n

    (@simplysaru)

    You are very welcome and thanks for marking the issue resolved.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.