1

I'm having a hard time finding a simple and short consent phrase for the GDPR. I'm also trying to bundle that with the terms and conditions consent, and maybe with the cookie consent (The app does not work without any of those).

Do you guys have any examples?

Seems weird I can't find any, since the regulation will be in effect in less than two months.

Improve this question
5
  • 1
    Maybe that's the reason you can't find any examples - it's not in effect for 2 months. And most places won't be immediately compliant either. That was also the case for the cookie law when that was introduced. – JonW♦ Mar 28 '18 at 12:32
  • 1
    yeah, but this one has numbers on it ($), i was expecting people to be a bit more preoccupied – Bobby Tables Mar 28 '18 at 12:33
  • Note that functional cookies do not need consent. No need to ask for those :) – Yates Jun 27 '18 at 15:06
  • So what happened? What wording did you end up using? – ralien Feb 28 '19 at 13:06
  • Seems like you need legal advice, before you need ux advice – qoba Mar 4 '19 at 8:46
2

I ended up using this format:

enter image description here

Not ideal, but it serves its purpose.

Improve this answer
1

A goal of GDPR is to reduce bundled consent. You should be splitting out Terms and Conditions and cookie consent.

See here:

Unbundled: consent requests must be separate from other terms and conditions. Consent should not be a precondition of signing up to a service unless necessary for that service.

View source

Improve this answer
2
  • in this case, all are mandatory and necessary, can't proceed without, so i don't see a problem with bundling them. What the regulation recommends is unbundling the consent if there are separate scopes for the data processing, so you can choose what you let the processor do with your data. thank you for your response. that would be the ideal setup if i'd have lots of space and the number of clicks wouldn't affect conversion. – Bobby Tables Mar 29 '18 at 11:41
  • GDPR wrecks usability as it's just a bigger and more complicated box which pops up in front of the page which the user is trying to read... Basic rule of UX: don't make the users think. – PhillipW Jul 27 '18 at 22:14
0

GDPR defines conditions for proper consent in Article 7 and recited in Recital 32, which could be helpful:

Consent should be given by a clear affirmative act establishing a freely given, specific, informed and unambiguous indication of the data subject’s agreement to the processing of personal data relating to him or her, such as by a written statement, including by electronic means, or an oral statement. This could include ticking a box when visiting an internet website, choosing technical settings for information society services or another statement or conduct which clearly indicates in this context the data subject’s acceptance of the proposed processing of his or her personal data. Silence, pre-ticked boxes or inactivity should not therefore constitute consent. Consent should cover all processing activities carried out for the same purpose or purposes. When the processing has multiple purposes, consent should be given for all of them. If the data subject’s consent is to be given following a request by electronic means, the request must be clear, concise and not unnecessarily disruptive to the use of the service for which it is provided.

Basically, whichever way you choose that lets users understand what they consent to, works. But you definitely should not bundle data processing with you terms and conditions.

@Bobby Tables's suggestion is what I usually go for, but you also should consider using "I consent to..." instead of "I agree to..." as agreeing could mean more like two sides agreeing on something, whereas consenting is one side giving explicit permission to the other side, which GDPR seems to enforce. But that might be a cultural/language thing, so think of whichever way best communicates what you want from the user in accordance to GDPR.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.