We’re tired of the cookie law and the ham-fisted attempts to comply with it. Today we announced we’re dropping cookie solutions from our sites as a stupefying waste of time.
The law still exists of course and users still have legitimate privacy concerns. So we’re proposing a new solution.
A modest proposal
<a href="privacy.html" rel="privacypolicy">Privacy</a>
(Note the use of the rel attribute)
This is simple but accomplishes a couple of things:
- Easily testable. Automated tools can check these links are in place where they should be (we just updated Sitebeam to do this for free).
Why this matters
Privacy is important, and it’s a great shame this farcical law does nothing for it.
You might say we’re proposing pretty much what people were already doing before the cookie law came into effect, except slightly better. That would be about right.
Most solutions to this law interrupt the user with a message to tell them that cookies are being used, and link to a long technical document listing those cookies in detail. How exactly does that help a normal web user?
What people need is an open and sincere dialogue about how their privacy is affected being used, together with controls to opt-out of tracking that might legitimately cause them concern.
We welcome your thoughts and suggestions.