3 ms·
Why not do it like with cookies? People are already used to accept these cookie policies, so why not just widen it to GDPR related stuff? Also how much can be
by k__ 9y ago
Why not do it like with cookies?
People are already used to accept these cookie policies, so why not just widen it to GDPR related stuff?
Also how much can be caught with "security" reasons?
- molf 9y agoThere's a very clear distinction: GDPR requires that consent is not a precondition for offering a service. Most cookie policies in practice are all or nothing: you either accept and continue, or you decline and cannot use the service/website. That is not allowed under GDPR.
- reid 9y agoInteresting. Which part of GDPR disallows the “decline and you cannot use the service” case?
- molf 9y agoQuoting GDPR: "Consent should be given by a clear affirmative act establishing a freely given, specific, informed and unambiguous indication of the data subject’s agreement [...]" [1] "Consent is presumed not to be freely given [...] if the performance of a contract, including the provision of a service, is dependent on the consent despite such consent not being necessary for such performance." [2] [1] https://gdpr-info.eu/recitals/no-32/ https://gdpr-info.eu/recitals/no-32/ [2] https://gdpr-info.eu/recitals/no-43/ https://gdpr-info.eu/recitals/no-43/
- reid 9y agoThanks for replying! GDPR is complex. Indeed, declining these specific consents will still permit one to access a service. My understanding is that there can be other consents, such as consent to changes of Terms of Use, which are required to access a service.
- chii 9y ago> the provision of a service, is dependent on the consent despite such consent not being necessary for such performance. but to play the devil's advocate, if it costs money to provide a service, but that money is currently supplied by selling personal data to third-parties, then isn't it true that the service cannot be provided without the data?
- zaarn 9y agoWell then you'll have to hinge the performance of your service on actually asking the user for money.
- detaro 9y ago> Also how much can be caught with "security" reasons? Only things you only use for security purposes. You can't say "we need X for anti-fraud" and then use it for marketing purposes without consent.
- k__ 9y agoHow can anyone check this?
- detaro 9y agoThat's of course the rub with any regulation touching internal processes (just as it is with financial regulation, anti-discrimination laws, workers rights to some extend, ...). If you don't make a mistake revealing it, aren't forced into an audit and have no ex-employees holding a grudge, you can get far violating them. Part of GDPR effect is that if you get caught, you can't talk it away with some blanket claim in your EULA, you need to have a detailed justification, and there is potential for painful fines, so the risk increases.
- molf 9y agoWe cannot say for sure yet, but in general we can expect that these things will never be checked until there is a data breach of some kind; or if evidence is found in another way. If the details of the breach indicate you were using data for another purpose than what was allowed you will have a problem.