News for hackers. Stuff that matters.
Re:Big brother is here, and his name is Facebook by Deimorz on Saturday August 12, 2017 @01:02PM (#14998741)
It gets even more frightening if you realize that you're probably not even considering all of the "deeper" levels. Almost everything I listed in my comment was pretty surface-level stuff, where it's at least somewhat obvious that you're giving the data to them (some things like the analytics not so much, but still not really "hidden").

But now start thinking about some other things:

- Are any of the sites you're using hosted on GCP (or other Google-owned hosting)?

- Even if they're not, do they include any scripts/images/fonts/etc. from other sites that are?

- How much network infrastructure does Google own now? How much of your traffic is passing through it?

Re:Big brother is here, and his name is Facebook by jfktrey on Saturday August 12, 2017 @02:27PM (#14999176)
It almost seems impossible to use the internet for even a day without having some usage information leaked to Google.
Re:Big brother is here, and his name is Facebook by utbabya on Saturday August 12, 2017 @05:07PM (#14999968)
Even if you don't install any GApps, Android would still ping Google servers. I can't remember exactly since it was a while ago, but IIRC it was some hardcoded NTP server.

Not much but still a heartbeat per GeoIP.

Re:Big brother is here, and his name is Facebook by greedy_buffer on Saturday August 12, 2017 @10:57PM (#15001248)
Not to mention the captive portal redirect URL
Re:Big brother is here, and his name is Facebook by greedy_buffer on Saturday August 12, 2017 @10:56PM (#15001243)
For Google to collect data on their platform customers' layer 7 traffic would be a pretty big breach of trust (i .e. hacking if they were using HTTPS) If they are just collecting TCP data and selling it to third party marketers or building analytics profiles it would be a lot of work to reliably connect that to humans for little benefit, along with risk to their reputation.