Reply #7: Hash is great for dealing with sessions. But again, you first need to generate the data [View All]

if it is in a cookie then ok, but you are already tracking the user by setting a cookie. The cookie is only accessible to the domain which created it. So I really don't see any practical use websites would have to store this type of data nor do I see how it is any different from what they already do. If google ads wants to track you to fetch you specific ads they already do that using cookies. I guess this could be useful if cookies are not enabled but that's a tiny fraction of the internet user base.

So to pretend this is some kind of threat that will identify you is a bit on the paranoid scale in my opinion since no website will actually be performing these tests then storing them on the servers. If they store it in a cookie that is no different from what they can already do. Maybe if you can give me some specific things they can do with this to put your privacy in jeopardy.