• Hi at all,

    due to GDPR issues with our EU website, I’d like to link the ‘Reject button’ (which can be set up at ‘Notice Bar & GDPR’) to the ‘non amp version’ of the currently opened url. That makes sense and would be very userfriendly as well.

    Is there any option to do that?
    This would improve our GDPR safety a lot!

    I’m really looking forward to hearing from you.

    Best regards
    Mikey

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter mikey79

    (@mikey79)

    And by the way: Is there an option to change the position of the buttons – I mean reject first and agree second? I’m using the first GDPR design from AMP for WP …

    Plugin Contributor ampforwp

    (@ampforwp)

    Hi @mikey79,

    When a user clicks on the ‘Reject’ button, if it’s going to the ‘non-amp’ version of the currently opened URL, I guess you’re also configuring the GDPR compliance on the EU non-amp version site, am I right? Then the same compliance will also apply for the non-amp version so I guess it doesn’t make sense to render the non-amp version by clicking the ‘reject button’

    Please clarify me, If I’m wrong

    Thank you.

    Thread Starter mikey79

    (@mikey79)

    Hi ampforwp team,

    yes. Unfortunately, you are wrong.

    For sure, we’re forced by law to configure gdpr compliance for the non-amp version as well – but there’s one big difference between handling gdpr for amp and non-amp:

    The amp version is – by nature – hosted on Google (or generally spoken ‘external cache/cdn’) servers.

    That’s exactly, what gdpr forces us to inform about BEFORE a user visits the amp page. If a user clicks ‘reject’ or ‘close’, he’s still able to visit the amp website and that’s simply logically wrong.

    As we are forced by law to give users the choice if they want to visit a Google cache server or not, the only logical solution is to link the reject (as well as the close) button to the non-amp version.

    So the users free will decides. That’s exactly what gdpr is about!

    The key is to enable the choice for the users. This is exactly the problem, our lawyers informed us about and solving this would guide to the fact, that ampforwp will be really gdpr compliant – as the first plugin, as far as I know.

    I’d really appreciate, if you could find a solution or realize a hook or s.th. like that – then all your EU customers will be able to fulfill this ‘users choice’-part of gdpr.

    I’m really looking forward to hear from you!

    Best regards
    Mikey

    Thread Starter mikey79

    (@mikey79)

    @ampforwp

    I’d really appreciate receiving your response.
    Thanks a lot in advance!

    Best regards,
    Mikey

    Plugin Contributor ampforwp

    (@ampforwp)

    Hi @mikey79,

    Sorry for the delay in response.

    Your use-case scenario is right, but if a user clicks ‘reject’ or ‘close’ the GDPR on AMP, he’s still able to visit the amp website but Google will block all the AMP components like the analytics, Ads, videos, images etc. You can check an example here:
    * https://ampbyexample.com/user_consent/basic_user_consent_flow/
    * https://ampbyexample.com/user_consent/advanced_user_consent_flow/

    And when you say “users have the choice if they want to visit a Google cache server or not”, May I know where did you read this? as far as my knowledge and articles which I’ve shared above, they will serve the Google cache server but they block all the AMP components.

    However, I’ll discuss this feature to add the non-amp URL in reject/cancel button with lead developers team and if the use-case is valid, we’ll implement this feature in our plugin.

    Hope you understand.

    Thank you

    Thread Starter mikey79

    (@mikey79)

    Hi @ampforwp team,

    thanks a lot for your detailled reply. As written above, the fact about the ‘choice’ was mentioned by our lawyer – specialized on internet law.

    There are many sources concerning the fact, that users have to have a choice due to GDPR.

    See e.g.:

    ‘Consent must be freely given, specific, informed and unambiguous. In order to obtain freely given consent, it must be given on a voluntary basis. The element “free” implies a real choice by the data subject.’
    (https://gdpr-info.eu/issues/consent/)

    This is exactly the case, we are talking about. The user has to be able to chose, if he wants to visit a Google server or not. If not, it is forbidden to disadvantage him and not serve him with the requested information, because then the choice wouldn’t be voluntary – thus we have to forward him to the regular mobile Version without AMP technology – because it was his choice.

    This ‘if / when’ structure is exactly what makes GDPR so complicated.
    I’m really looking forward to seeing your update. We’ll then immediately switch to ampforwp with all pages, because this ‘choice thing’ is the key.

    Best regards,
    Mikey

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘how to change notice bar ‘reject button link’ target’ is closed to new replies.