We had some constructive suggestions on what could be done instead, although these are definitely up for debate. The gist would be using a rel element like so:
<a href='privacy.html' rel='privacypolicy'>Privacy</a>
and then using that as a means of consistently linking to a privacy policy. As a result, policies would have consistent language for users ('look for the "Privacy" link') but could also be detected automatically by browsers or testing tools.
That way you could actually test your site is properly linking to a policy, and users could have browser preferences like "disable cookies until I've seen a policy" or whatever.
It's just an idea but we've implemented it on our sites and will be interested to see what others think:
http://blog.silktide.com/2012/09/fixing-a-broken-cookie-law/
Having a 10 page complaint form is what is dumb. Why can't you just send a suspect URL, then have it scoured for dubious cookies?
I think this is an important distinction and is one of the reasons I was disgusted with Kissmetrics using etags to identify users