- Store and/or access information on a device
- Personalised ads and content, ad and content measurement, audience insights and product development
- Use precise geolocation data
- Actively scan device characteristics for identification
- Store and/or access information on a device
- Personalised ads and content, ad and content measurement, audience insights and product development
- Use precise geolocation data
- Actively scan device characteristics for identification
Whether you click on the "Accept" or "Refuse" button of a webpage's Javascript-powered cookie banner has 0 technical incidence on whether you can be tracked or not. It's like going into a store and telling the clerk "please don't look at me, and when I leave please forget I ever came here".
Or saying "Please don't record me, I don't give my consent". But you are already in there archives. Facial recognise so they know what you like to buy.
I feel these cute analogies make the mistake of equating a human seeing and remembering you (maybe even writing your name down in a notebook) with a machine doing the same thing.
There's significant qualitative differences, mainly that the machine has perfect memory and can effortlessly share and collect your information with other machines.
That only makes the point for which the analogy is used stronger though.
* Store information on a device.
Cookies cannot:
* Personalize ads (they can store identifying information that can be used to personalize an ad, but something else has to actually ask your browser for the data) * Actively scan device characteristics * "Access information" Cookies don't do that. Code (Javascript in the browser usually or something on a web server) that might use data from a cookie does.