by "improving their business metrics .." they are mostly using Google and co. Implicitly feeding the big cookie monster is not very harmless IMO.

Reply to this note

Please Login to reply.

Discussion

This is only a problem when you give google some user data. Most apps are only collecting data like app logs. Klick events and general statistics of how the app is used.

Saving this data isn’t a problem and it doesn’t matter where you store the data. Most backend systems are running on AWS, Azure or Google anyway.

I can fully understand when people using a app and then find out that there are some libraries in the app like google analytics for example, but it really isn’t that much of a deal.

What about fingerprinting?

Google does not necessarly need submitted user data for tracking. They are pretty good at working with your meta data.

Can be done with such libraries sure, but it can also be done from the backend server.

Just because some tracking libraries are onboard doesn’t mean that you are tracking as individual.

The other case is also possible. Just because there is no tracking library doesn’t man the app isn’t tracking you.

Most companies are using thirds party libraries because it’s much cheaper to use and much more convenient.

Are you really supporting the thesis, that a commonly shared cookie across multiple devices, apps and platforms distributed by a centralized entity has no substancial implications for a widespread attack surface on privacy?

That’s not what I said!