Clicking 'no' should still allow people to view the website, but without placing any tracking cookies.
Source (in Dutch): https://autoriteitpersoonsgegevens.nl/nl/nieuws/websites-moe...
I think the real problem here is that the technical feature of cookies providing browser state is a poor proxy for what EU/DPA _really_ wants to regulate, which is privacy-related tracking.
There are tons of sites I've written which use cookies, but have no ads and perform no user-tracking whatsoever, not even Google Analytics. It is true that cookies are the _easiest_ (if not the only) way to do the other; but making "cookies" the thing that gets effectively "regulated"... I realize this isn't necessarily the intent of the regulations, but I'm suggesting it's part of what results in the situation troy mentions. There are very few sites that don't use cookies; there are or at least could be more sites that don't track you in a privacy-compromising way, to train the user that this is the same thing is just too much noise for the user to actually make any discernments.
"This shall not prevent any technical storage or access for the sole purpose of carrying out the transmission of a communication over an electronic communications network, or as strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service."
Of course, no website will ever tell you "Hey, we're using cookies to track you"; it's in most companies' (both legal consulting companies' and website owners') best interest to keep people ignorant. Consulting companies want website owners to be scared and buy legal consulting services, and website owners want people to think that the pop-ups are a result of stupid EU legislation and not because they are actually being tracked.
If I need to get explicit opt-in for "So, remembering your shopping cart when you come back requires cookies, that okay with you?" I'm not sure how much better that would be. It's still gonna be information overload "false positives".
But I think that is what the regulations actually intend. "We need cookies to give you: Shopping cart; search history; login to your account; whatever -- opt in or out to each one, you can still use the site just without those features if you go out."
A) That is actually fairly expensive to implement. B) I think it _still_ wouldn't accomplish the goals, it's still _way too much information_. Nobody cares whether or not you use cookies to implement a shopping cart. They care about things related to "tracking", especially aggregated tracking, and profiling. C) But you are exactly right that no company is ever going to tell you what you _really_ care about. Unless regulations make them maybe. These regulations were trying. Not there yet.
I'm not entirely sure if a user account at an online store would require consent; in my view, cookies would be "strictly necessary" to provide the user experience a user expects which includes being able to create an account to save their shopping cart and view their order history, while using cookies to show tailored product suggestions wouldn't be. However, IANAL and I haven't even read through the text of the directive.
In any case, the vast majority of the times I see the cookie notice are times where there are exactly zero reason to use cookies (or other methods of persistent storage) other than tracking, such as blog posts and news articles. Every single one of those websites would be able to get rid of their annoying pop-ups if they just spied on their users a bit less.
You can 100% support a logged in account experience without cookies. Java, for example, supports jsession id in the URL for people with cookies disabled. This id belongs to a session that is managed by the app server, which you can use to store information such as the cart, logged in account id, etc. If Java can do it, other languages and web frameworks that currently only support cookies can do it too.
I think the better angle to look at it is: session cookies expire when someone closes their browser. They aren't that good at tracking people.
In that light I tend to agree with GP. If you're just using cookies to run sessions for your site, I just can't see regulators coming down on you.
There's some potent mix legal and technical pedantry combining with the profit motive of consultants everywhere that has led to a huge wave of overblown FUD around GDPR.
The fact is, ad-tech has been running amok for years and I don't think it's that hard to draw a line if we're intellectually honest. Of course it will take years for case law to catch up, but it's not as hand-wringingly difficult as some would have us believe.
You don't provided you have a reasonably short retention period, are not storing personal information that is not directly needed for remembering the shopping cart and are only using it for that and not simply using that as a justification for something else.
> Nobody cares whether or not you use cookies to implement a shopping cart.
Nor do the regulations. You have to meet the exactly the same requirements to store personal information using some other mechanism that you do using cookies.
The biggest lie in most cookie warning popups is that you need to accept them for the site to function. It is often not true. Those are session cookies and you don't need to warn users about them, they're just allowed.
I didn't know this, and neither do any of the cookie warnings mention this. So like many people I thought the cookie law was the stupidest thing ever because like you say, you gotta have state. But the session cookies used to make a site hold state, those aren't considered tracking. When I learned about this little fact, it changed my opinion about the cookie law considerably.
As far as I understand it, the GDPR does everything and more than the cookie law was supposed to, so IMO it's about time we put that disaster behind us.
On the web, your approximate unique ID is your browser fingerprint. That can be used to join your activity to other activity. Your session cookie is your activity for your browsing session (or for users who never quit their browser, your entire computer uptime).
Think about it -- a cookie is information the web server gives to you; it's essentially a bookmark to your current position in the app. The server already knows where you were -- it saw you there!; it just doesn't know that you want to go back there on your next HTTP request.
Tracking data is data you give to the web server. Cookies are only one primitive to enable tracking. Cookies can be replicated by URL query parameters, subject to size constraints.
There’s only a handful that need them for logging in.
Most sites I visit I don’t want to interact with, I just want to read.
Silent cookies aren't completely banned by the GDPR/cookie laws, only cookies that aren't necessary to provide the service requested by the user. That's sort of vague, but I think mostly obvious what is intended there. It's pretty easy to operate within the spirit and letter of the law: Shopping baskets, load balancer cookies and login tokens are fine (provided you only use them for those purposes!), third party advertising tracking cookies are absolutely not (without consent). More info here: https://ico.org.uk/for-organisations/guide-to-pecr/cookies-a...
Lawyers have told me that you do not even need consent for Google Analytics, unless you enable the data collection for advertising features.
It appears to me that there's intentional bad faith misunderstanding from some, regarding both the cookie law and GDPR, in order to try and paint it as unworkable.
So, yeah, it's a mess. These "extra" warnings are contributing to user fatigue, I agree with troy hunt that users are just gonna ignore them all. I also understand why a small organization can say "Well, I don't really understand if we need it or not, the lowest risk thing to do is just to supply it." And there's no law _preventing_ you from supplying an unnecessary pointless cookie warning banner...
It's 88 pages of legalese consisting of 99 articles distributed over 13 chapters. It also has dozens of footnotes which incorporate thousands of pages of other laws by reference.
> and if execs/managers aren’t smart enough
Clearly I am too stupid to operate a business and have reading comprehension problems. Thanks for letting me know.
Google analytics feeds tracking data to google for advertising purposes and tracks you across sites, it's exactly the sort of crap the cookie warning was meant to stop.
> These "extra" warnings are contributing to user fatigue
Your need for analytics is contributing to user fatigue.
> I agree with troy hunt that users are just gonna ignore them all
So do websites putting up these silly warnings, do you actually wait for people to accept before they get their tracking cookie?
That is why GP said "(no advertising features)." That is the name of the feature in GA that does that, and it can be disabled.
But I also understand the law, that anonymous user statistics are just fine and don't need consent as long as you retain the data yourself and of course mention it in your privacy policy. Though you might still be obligated to respect "do not track" and adding an opt-out setting.
Very much this. None of the cookie warning dialogs (I've seen) mention this, and a lot of them use the dialog to complain about the law.
Something seems to have changed when GDPR came around though. The cookie warning dialogs before just had angry or condescending warnings with only a big "I accept" button, and otherwise too bad. But recently I've begun to see more and more warning dialogs that both have more honest wording about what they're about, as well as providing a "Decline" button.
IIRC there is something in the GDPR about explaining the privacy choices in clear language to the user, as well as having to provide an alternative if possible. If that's the case then it really does smell like intentional bad faith.
Although to be fair in addition to bad faith, I think it's also a lot of webdevelopers just not doing research what is exactly required and just parroting the scary story off each other.
But there's certainly a large part that just want to scare their users into accepting Google Analytics tracking. I'm curious about what those lawyers told you, though. Analytics data flowing through a third party widget that is doing the same on almost every site anywhere, sure feels like tracking to me. But maybe if you disable the data collection for advertising option, Google really won't cross-correlate that data for their own purposes. Even then, doesn't Analytics track the path users take on a single site too? For measuring "conversions" and such, as well as just detect whether people get "lost" on the site, or something.
Now certainly that's useful information, but it is tracking. Also you can get a lot of that information (and more) by just doing basic usability testing on real users. No tracking required and if you ask 10 people to try your site, you get 90% of the usability issues, with diminishing returns (based on some usability research I once read somewhere). But the information is much higher quality because you can ask them questions, ask them to perform tasks, actually look over their shoulder, etc. Tracking website users through analytics is just numbers and doesn't tell the whole story in very many cases, anyway.
https://www.nngroup.com/articles/why-you-only-need-to-test-w...
Is there any legitimate and reasonably necessary purpose for third party cookies? And similarly is there any undesirably exploitative use of first party cookies? As I am not a web developer, these are not rhetorical questions.
"Legitimate reasons" is another. You can process personal data (use cookies) under that reason, and you don't need to ask for consent.
--- quote ---
Removed support for the expired Do Not Track standard to prevent potential use as a fingerprinting variable.
--- end quote ---
From the same website you link [1]: “Does anyone refuse tracking cookies? Then you still need to give this person access to your website or app, for example after payment.” (google translated)
[1]: https://autoriteitpersoonsgegevens.nl/nl/onderwerpen/interne...
If a site makes its money from ads, on the other hand, the location of the visitors is irrelevant when it comes to taxation. The payments from the ad network will just be ordinary business income at the place the site is located.
I don't think the charge a fee model has a chance, except for a few large sites, until some sort of intermediate service is developed that isolates the sites from having to deal with taxes in a bazillion jurisdictions. Something like a Spotify for site access, where users can pay the service a subscription fee, and the service pays sites after taking care of the appropriate taxes on the user's subscription fees so that the sites don't have to deal with it.
Shopping baskets, load balancer cookies and login tokens are fine (provided you only use them for those purposes!).
Third party advertising tracking cookies are absolutely not (without consent).
Edit: guess somebody never integrated a payment provider :-)
It's hilarious how everyone has just forgotten that used to be a thing. The people on this website are literally the problem, you can't even conceive of a website that doesn't track every click you make across the whole internet, and you guys are the people building the new web.
Do you think TV adverts are placed randomly? They aren't. Different times of day have different value to different advertisers. TV ads are targeted based on detailed knowledge of audience demographics.
Do you think billboard ads are placed randomly? They aren't. Their placement is optimised based on the beliefs of the ad firms about who will drive past them or see them.
Do you think internet ads were placed randomly before AdSense? No, they were targeted by rough demographic guessed from the sites content just like TV and billboard ads were.
All that's changed on the internet is that targeted has got more precise and more sophisticated. But there's no bright line separating "generic" from "targeted" ads, like you imagine. And the better targeting is hardly an optional feature like the DPAs seem to imagine. It increases revenues which enables firms to provide new content and new features. Roll back the web to 1990s era ad techniques and now all the ads on generic sites like news or search with no clearly defined audience will be barrel-scraping "punch the monkey" animations, for those of us who remember that stuff.
Facebook is a great example on keeping diluting these concepts. They ask for your information for function security purposes and then go back and use that same data for ads - that is unethical and has to stop.
If the user is not getting something out of it (besides the generic "access to my website") then presumptively don't do it. GDPR is literally as easy as that.
GDPR understands full well that you need session cookies to provide a shopping cart or user account. That's why there's specific exemptions for it.
Ads were always a thing, they're just going to be better targeted with more info.
There is no free lunch, so what this means is the 'no cookie' users may be exposed to more ads.
I understand the market dynamics are not working very well, but we have to remember that information provided is not free either.
Companies are not trying to 'do inherent evil' - they just want to show relevant ads. And by the way, consumers definitely appreciate the relevance.
There is another side to the equation, and there are economic consequences to all of this that will come home to root.
Personally, I loathe Facebook and don't use it for personal reasons, but I have a small business and it's the only advertising mechanism that works for us: we have a neat little product for a niche category.
There are entire economies that can only exist with the ability to effectively get the word out, there is tremendous social good in this.
We just have to figure out a way to do it that fits within reasonable privacy guidelines.
What is not allowed is to withdraw services to those that want to exercise their right to privacy.
This is like a government saying to a restaurant "You can't discriminate against people who don't want to pay you money for the food. You can ask them if they are willing to give you money for the sandwich, but if they say no, you still have to give them the sandwich"
It’s more like the government saying, you can’t discriminate against people who demand that their food is cooked in a kitchen that isn’t filled with cockroaches. It’s going to hurt the bottom line, and might kill some businesses, but it doesn’t reduce to a prohibition on making money.
What?! Are you seriously speaking of prohibiting cockroaches?
Cockroaches are everywhere! They are essential to survival of businesses! And it would be impossible to completely get rid of them anyway. Prohibiting cockroaches in public restaurants would push immense cost upon eaters. Without cockroaches how could we possibly get rid of the food waste, that routinely accumulates in kitchens? Do you expect us to spray our kitchens with toxic pesticides? To hire some specialized people of to lick food scraps off kitchen stoves with their bare tongues?? Insane!
Clearly, you are the enemy of the people.
To me it sounds very sensible to make such a business practice illegal.
You're right, it's the currency now. It would be great if it wasn't. If there was some way to force the industry to come up with new, non-privacy-invasive methods... Hey maybe if we made a law to ban the old, bad, way....
Advertisers will still pay for ads even without the tracking.
Are there other examples?
Disclaimer: I'm not saying I agree with any of this. Nor that any of this is truth in any way. I just view the governments involvement here, saying how ad companies can behave, to be similar. Whether that is good or bad is complicated, and out of the scope of this conversation.
In essence, GDPR states that you're not allowed to violate the privacy of people unless they really want to (freely given, informed, narrow/specific opt-in consent) - and this time, all the oft-used loopholes to "extract consent" don't really fulfil the criteria, as forced consent is not considered consent.
My stance is even more ridiculous: Deadbeats who can't afford hosting without begging, selling ads, or turning against their users, scale your site down to something that's cheap to host, or get the hell off the internet. Back to the amateur web of the 90s. It was fine.
Shouldn't people be able to choose what currency they want to pay for something in?
Thats a very libertarian position statement and I understand it. But the EU is much less capitalist/libertarian than you are. Their parliament made the call that they don't want people paying for services with their personal data.
There's valid arguments on both sides here. Some arguments supporting the EU's stance:
- If online newspapers get paid in proportion to views, they make more money by writing divisive clickbait
- Privacy is a fundamental right; not a currency. Treating it as currency means only wealthy people will be free from spying, and that is borderline dystopian.
- Advertising on the internet worked just fine before everyone was tracked and monitored through every click. Don't annoy me with cookie notices. Just don't use cookies for tracking and we'll get along fine.
The EU's document is "Charter of Fundamental Rights of the European_Union"[0], which does grant privacy as one. That pretty clearly does make it a "fundamental right".
Note the US Constitution's Bill of Rights does not offer right-to-privacy (but the 4th provides protection from searches-and-seizures without probable cause, which really doesn't deal with "privacy", especially from non-governmental actors).
Perhaps parent should have said "fundamental right granted by the EU", but in this context it's pretty clear.
[0] https://en.wikipedia.org/wiki/Charter_of_Fundamental_Rights_...
So 'choice' is already something that has failed in the free market. Bring on the privacy.
You only have to see the howling every time someone posts a subscription only newspaper link on HN to see how vehemently opposed people are to paying for stuff like news.
it's expensive and maybe non-viable for many websites. But it's not like all websites need to exist? There was a world wide web before cookies.
I like to think of that time as a great time too, but oh man so much we couldn't do.... I get what you're saying generally, but man I'd hate "before cookies" to be the standard.
I don't really see it as "what we couldn't do" but "what poor usability we have overcome". I'm glad we have cookies and other forms of local storage, especially for the latter there are many other benefits. Maybe one day we'll get Web SQL.
In the meantime people can still disable cookies entirely, or at least delete them when they close the browser, both with out of the box browser settings (and I have no idea what extensions are available to do even more) and return to that less-usable (if slightly more private) experience. The crucial idea of a "user agent" is I think the biggest mindset change the web brought, it's important to keep that even if on the dev side we constantly complain about being asked to support more than one configuration of anything.
Yeah I think that's accurate.
It's a little weird sometimes reading all these articles about cookies, JavaScript, etc and I always think "But I use those things to ... give people things, convenience, data, help them do things." But so many times it's not treated as a tool, it's almost implied to be a negative thing.
Most just do stuff nobody sees at any volume.
Have you ever reviewed how little you need in order to do all those things, outside of third-party dependencies? Any second guesses at all?
We didn't have e-commerce before cookies.
The same functionality of correlating multiple requests for a single request (building sessions upon packets) was just more difficult to use by encoding the session ID as a parameter in query string for each request. Many frameworks still support this mode.
SSL is largely irrelevant to banking security anyway. Actual security is built upon charge-back system. The underlying security model was designed when everyone trusted written checks.
The €0.00002 it took to serve that one page just because the user doesn't want to consent to cookie placement/tracking? Is it really that harmful?
NPR seems to do this just fine for GDPR reasons: Decline and Visit Plain Text Site
I mean, by your argument, all digital goods should be free, since it never costs much to transmit the bits.
The OC didn't consider the fact that you can have advertising without cookies/tracking/fingerprinting and just reduced it to absrudism by saying that the company would bear the brunt of the cost but even the cost of that single event is marginally insignificant, overall.
So, no, my argument was never about all digital goods being free. However, if we want to play the devil's advocate and utilise your reduction to absurdism: By your argument, shouldn't all digital goods be paid for...? For example, Ubuntu costs money to host and serve, yeah?
I do love NPRs approach though.
Aye, if they're only looking at it from a "cookie placement/tracking or nothing" hard-limit perspective, which is what the OC posited it as.
...but if other sites can absorb the costs, case in point: NPR, why is it such a dastardly evil thing to point out? Is there some foolhearted belief that if we cut tracking, tomorrow, the internet would cease to function? Is there absolutely no room for advertisements without cookies/pixels in the modern world...? Do we really believe that it's that expensive to serve webpages?
So what can these - now shady - companies do? They probe the limits of the law, and try to keep their business model alive as long as they can. We need to wait and see. In my opinion, the most probable development is that European data protection agencies will start to hand out fines. Of course, the shady companies will fight them in court, and of course, they will lose. Then they will retreat a step, and try again with a little bit less intrusion into the user's privacy. Over time, courts will rule, and fines will increase, until the shady companies will give up in EU.
Then EU will essentially become free of tracking networks. It might take a few years, but I think the intermediate annoyance is worth it.
I don't disagree with you but I think it is more likely that these companies will just not let EU peoples use their sites at all.
One BIG fine (and you know they're salivating at the prospect of getting multi-billions out of Google and/or FB) and doing business in the EU becomes too much of a gamble for a company to justify the risks.
It might even encourage some more ethical alternatives, or some real attempts to solve micropayments.
Everyone knows that FB and Google are expending serious resources to be in compliance yet they will more likely than not get some large fines anyway because politics. I doubt they will ever leave the EU but other, smaller, companies will not have the resources to throw at the problem so will be effectively locked out of the EU market.
It's probably in Google's best interest to pay a couple billion euro fine (to scare off the smaller fish) in order to lock in their de facto advertising monopoly.
And yes, I do consider it terrible that my nanny state government decided what is best for me, over some hysterical fears about tracking. I don’t give a damn. I don’t consider tracking of me in the way the browser can do actual personal information.
I’m OK with a strict regime for actual personal information, like name+address, heck, even spam data like phone and email, but extending that to tracking cookies, at the enormous cost in usability we’re already seeing, is ridiculous.
As it looks to me, they are responding back by trying to push through articles 11 and 13 so that they can then all switch to paywalls. A paywall for a news company is practically useless as the internet currently stands as any major story 1 makes gets linked to and paraphrased by dozens of other news agencies within minutes. Why would users pay for a news website when they can get practically the same thing at a free one that did not work to come up with the story. And article 13 is to prevent 1 user who does pay for a website from copying the entire article and pasting it in a comment (I see that and archive/outline links all the time here and on reddit).
Don't like cookies? No one is forcing you to visit a particular website.
I also feel like tech companies could adopt an open standard for cookie acceptance preferencesin web browsers, but they're afraid to lest they be forced to deal with even more regulation later.
to decide whether to track your users? through third parties? for advertising purposes?
Why? Why do you get to decide and not the users? I'd rather you didn't!
It really honestly does surprise me the amount of crap Americans are willing to swallow when it comes to advertising methods, or even just profit in general. Your whole society is rife with abuse. There's robo-calling, giant billboards, attack ads, pharma ads, ads or contests that are literally scams, just a few from the top of my head. Probably more I don't know about (ads to target children? there is NO good way to argue that children "should" be targeted by ads).
It's a small miracle you managed to push a mandatory "unsubscribe" link underneath mass email lists. I suppose it's mandatory because given the attitude to this kind of abuse I doubt they would put them there voluntarily.
Also, you've seen what happened to the online ad industry without this kind of regulation. If you don't make rules they're going to push it as far as they can. It's gotten to the point where people recommend adblockers for security not getting rid of annoyance. Or for saving about 95% of your mobile data plan surfing sites. Did you ever notice the most profitable ads pay for the shittiest content? The system isn't even working.
However I think websites should be able to block access to anyone they want. It doesn't seem fair to force websites to serve an audience if they do not wish to.
However, if they say "press here to forego your privacy or we'll block you", then that's not a freely given consent to forego your privacy, and in this case this "consent" doesn't count as consent. In this case they're not allowed to track people who "consented" because they didn't really consent (both in moral and in legal sense). Consent "counts" only if it's freely given, if people really want you to do that thing; in EU privacy rights are not something that can be sold or bartered away.
It's somewhat comparable to consent to sex - let's imagine that in a place where you can freely fire workers at will, you say "consent to have sex with me, or I'll fire you". You technically can fire them, but that "consent" isn't really consent, and even if they "agree", that's still nonconsensual. Privacy (in EU) is pretty much the same.
I'll take freedom any day over someone telling me that they know better.
Obviously you cannot do whatever you want to a person who physically enters your business. This is a facile point. The same is true of websites: simply because a person navigates to your website, you do not automatically have the right to place tracking cookies into their browser.
For a privacy advocating party it would suit them to not log anything and be very clear about that.
Source: https://autoriteitpersoonsgegevens.nl/nl/over-deze-site/cook...
No! It doesn't. Viewing a website isn't anyone's god-given right. The tracking cookies are part of the business model. If you don't agree with how a business makes money, stop patronizing them.
If this is serious, look for companies to just block all traffic from The Netherlands. Why even bother dealing with the hassle.
Some business models are predatory societal negatives and should be done away with at a government level of respecting individual rights. Behind-the-scenes tracking and data brokering are in that class.
Regarding options, in the current model it is generally unknown to the user what is happening with their seemingly private, personal, and "lock icon" encrypted activities on a site. While some here might consider it a "fair exchange" to give up PII in exchange for website services, the vast majority do not understand or even perceive that, and it is not an informed exchange at all. It violates the user, both in the nature of the exchange and in the privacy implications. It is a type of interaction that should rightly be barred in the absence of understanding and explicit, intentional consent.
GDPR seems like it could evolve quite quickly, and sort of fork a bit here...
Also makes me wonder, do they have to have access to the whole site?
This feels like a war on cookies, and there are bad things done with cookies, but I'm not sure if they're fighting on the right front long term here.
If people simply just say yes all the time / don't know, not sure we're making progress.
Problem is will-full misinformation. It's a war on tracking cookies, not session cookies for login state, etc. But all the cookie warning dialogs make it sound like it's a war on all cookies no matter what, so "just accept because otherwise this site won't work, also <insert clueless condescending remark about the cookie law>" (really, the amount of sites that use this dialog as a misinformation soapbox to vent against not being able to track their users...).