Third parties may wish to store information on the equipment of a user, or gain access to information already stored, for a number of purposes, ranging from the legitimate (such as certain types of cookies) to those involving unwarranted intrusion into the private sphere (such as spyware or viruses). It is therefore of paramount importance that users be provided with clear and comprehensive information when engaging in any activity which could result in such storage or gaining of access. The methods of providing information and offering the right to refuse should be as user-friendly as possible. Exceptions to the obligation to provide information and offer the right to refuse should be limited to those situations where the technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user. Where it is technically possible and effective, in accordance with the relevant provisions of Directive 95/46/EC, the user’s consent to processing may be expressed by using the appropriate settings of a browser or other application. The enforcement of these requirements should be made more effective by way of enhanced powers granted to the relevant national authorities.
- ePrivacy Directive which is about local storage
- GDPR which is about information processing
Cookies aren't really mentioned in GDPR or other privacy laws, folks just latched onto cookies as one area that can track users. But really, all personal data is subject to most of the privacy laws, including outbound requests as well as stored data.
IANAL. But for context from lawyers, see: https://ico.org.uk/for-organisations/direct-marketing-and-el...
A web server’s logs may include the IP and http request they’ve made, but once you start attaching that to an identity instead it might count as data processing.
> ‘processing’ means any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction;
https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CEL...
One can use the “legitimate interest” basis (recital 49 may be relevant here) or “compliance with a legal obligation” for logging.
If I had to guess, based on what I know about you (what I mentioned in the previous paragraph), I would guess that you built your own computer. This almost guarantees a unique fingerprint.
With the deprecation of 3rd party cookies, we will definitely see an increase in fingerprint-based tracking. That being said, it’s going to look different than unique cookies (and it doesn’t explain OP’s situation.
(Or it might actually be that simple. Your fingerprint might be unique between IP re-addressing, and that’s all it is.)
Quite a lot of the specific details did surprise me though, to the point of wondering if there's a bug somewhere in their code determining percentages. "Audio context": "sampleRate : 44100, state : suspended" 0.05%? Gyroscope is a green check (I don't even 100% know what that means) and that's 0.13%? "Battery": "charging : true, chargingTime : 0, level : 1", 0.08%? (And is that even useful for fingerprinting over any significant period of time anyhow?)
So seems very skewed!
There are a few studies that used sites like that and got lots of traffic (by advertising on sites like HN) from non-normal users.
There was a landmark study done in France that measured fingerprints through a government website. The general population was much less unique.
Edit: found the AmIUnique paper: https://scholar.google.com/scholar_lookup?journal=Proceeding...
The other interesting thing is that it lists my plugins and "do not track" settings. They are both fairly unique. So, someone who attempts to anonimize themselves using plugins or browser features are just highlighting themselves.
I wonder how unique `wget` would be.
I would expect that any reasonably sophisticated fingerprinting system would not rely primarily on the useragent, and agree that anything that isn't stock only serves to distinguish you further.
Besides the fonts, only 3% of the people recorded in their database have their monitors configured for 30-bit color.
Therefore it appears that taking good care of my eyes makes me easily identifiable, but there is no workaround for this, except for running the browser in a VM, where the characteristics of the hardware and whatever else is installed could be well hidden.
It hides the fact that I have a 30-bit monitor by pretending that it is a 24-bit monitor, but the list of available fonts remains visible, so I can still be uniquely identified.
list of fonts list of plugins media devices (the combo of webcams and microphones my work computer uses)
Great site for understanding what your browser tells about who you are.
That still falls into the EU Cookie definition in the law. [0] If a website is doing this regardless of the user choosing not to allow cookies, it's committing a violation in the eyes of the law (in the EU at least).
GDPR absolutely does not rely on specific implementations. Even earlier things I'm pretty sure don't, but GDPR has a much more general coverage. It's extremely important people understand this when they're writing software.
So local storage is also covered by this law. For other fingerprinting techniques, if you can identify a user, GDPR applies. And for ad purposes, the only realistic legal basis is consent.
So basically what OP says is that most sites are just not following the European laws.
So the existence of that header actually makes tracking worse on the web
In the end, you've got two things to work with: Things you can convince the browser to actively identify itself with, and the things you can track regardless.
Cookies are in the first category, but they are not alone. You can get things as simple as presenting an entire site with customized URLs that track a user through querystrings being appended to everything with an identifier. You can track certain caching differences. You can program a website to use local storage and submit a token on every URL click with a fairly simple handler. This isn't even remotely a complete list.
In the second category, you've got IP address, browser versions, various settings... see something like https://www.amiunique.org/ .
In a nutshell, your rich browser experience leaks so much data along so many axes that it is essentially inconceivable that you could ever prevent yourself from being fingerprinted. What you can do is try to detach that fingerprint from a real person, to a certain extent rotate what you can, etc. But in reality you can't be shipping up kilobytes of header information on each web request and expect there isn't something in there that can track you.
https://www.amiunique.org/fingerprint says I'm 100% unique; with all the red lighting up I'm not surprised.