Hacker News Reader

Comment by baybal2 | Hacker News Reader

Yep, they have GREASE TLS bytes, TLS resume ticket, RLZ value, X-Geo header, UA header, JS APIs with persistent random values (which they do indeed use on adsense! This is why you get surprise WebGL code seemingly doing nonsense once a while in adsense ads)

This cannot be a coincidence. They packed Chrome with fingerprints to work around GDPR by combining fingerprints on their side.

View on HN

Doesn't that risk massive fines if proven? Like a percentage of all revenue?

I believe they already did lawyerising, as written above.

They grabbed onto the wording of PII as "personally identifiable information" that information is identifiable, but not personally identifiable, so it is ok to use for ads.

So we knows it's you, but you are a integer.

“I am not a number! I am a free man!”

— The Prisoner

Reminds me of this:

"So here I was now, two years just to the day of being kicked and clanged into Staja 84F, dressed in the height of prison fashion, which was a one-piece suit of a very filthy like cal colour, and the number sewn on the groody part just above the old tick-tocker and on the back as well, so that going and coming I was 6655321 and not your little droog Alex not no longer."

Nothing like a little bit indirection to make it not true. It's blatantly obvious all the ways G can build a profile of someone by fingerprinting. Unfortunately it's not exactly an elevator pitch to make it a common knowledge thing.

I don't think this would stand up to scrutiny if the EU was willing to really enforce the GDPR (unfortunately they are not).

Thank you for the list, it could be useful.

Reply on news.ycombinator.com