If you participated in the discussion about Libby and maybe-targeted ads and privacy policies, you might like to read The Register's deep dive on what they could determine about what actually happened from @thomasclaburn

https://www.theregister.com/2024/05/18/mystery_of_the_targeted_mobile_ads/

An attorney says she saw her library reading habits reflected in mobile ads. That's not supposed to happen

Follow us down this deep rabbit hole of privacy policy after privacy policy

The Register
@jessamyn It's horrifying that after all that hard work and expertise devoted to the problem, we still have no idea how this actually happened.
@jessamyn @thomasclaburn

so:

using a google account on IOS
+
using another google account on a device with Android to access the same things
=
you are identifiable, regardless of the data honesty of any apps you're using.

@jessamyn That's interesting. Plenty of people can say "that's not supposed to happen" or "this is how it possibly could have happened," but nobody can trace any way that such a thing definitely would have or did happen, and it seems like even if it isn't happening now, there the possibility that it could happen in the future.

That's not very reassuring. I'd rather we had ways of keeping data private and not crossing it that don't rely on the good will and pinky promise from a vendor.

@jessamyn @thomasclaburn I need to have a talk with the bibliocommons folks. People need to understand that if you “just” use google analytics to collect demographic statistics, it turns on the doubleclick advertising machine. And that machine can link all your devices, profile your interests in great detail , retarget you, survive cookie clearing, etc. All without a shred of “PII”.