Marion
2025-03-06 23:22:41 UTC
*How Google tracks Android device users before they've even opened an app*
<https://www.theregister.com/2025/03/04/google_android/>
"Leith said he wasn't able to ascertain the purpose of the identifier
but his paper notes a code comment, presumably made by a Google dev,
acknowledging that this identifier is considered personally identifiable
information (PII), likely bringing it into the scope of European privacy
law GDPR - still mostly intact in British law as UK GDPR."
Not the best of sources, and it doesn't even mention the most important
factor, which is nobody who cares about privacy sets up a Google Account
on the phone (they can have a google account - just not in the settings).
"Doug Leith, professor and chair of computer systems at Trinity College
Dublin, who carried out the research..."
"The DSID cookie is "almost certainly" the primary method Google
uses to link analytics and advertising events, such as ad clicks,
to individual users, Leith writes in his paper"
� <https://www.scss.tcd.ie/Doug.Leith/pubs/cookies_identifiers_and_other_data.pdf>
Leith specifically mentions these apps, one of which nobody ever needs:
1. Google Play Services
2. Google Play store
Note the existence of a 'DSID' cookie, which Google explains in its
documentation is used to identify a "signed in user on non-Google websites
so that the user's preference for personalized advertising is respected
accordingly. The 'DSID' cookie lasts for two weeks."
Note that this DSID cookie apparently only exist for those who sign into a
Google Account (which is usually as part of the Android startup process).
Likewise, "Another tracker which cannot be removed once created is the
Google Android ID, a device identifier that's linked to a user's Google
account and created after the first connection made to the device by Google
Play Services. It continues to send data about the device back to Google
even after the user logs out of their Google account and the only way to
remove it, and its data, is to factory-reset the device."
Notice none of this (likely) happens if you're smart enough to simply not
list a Google Account in the Android account settings, which, is so trivial
not to do, that it needs no explanation. The phone works better without it.
Note that the article concludes with "The findings come amid something of a
recent uproar about another process called Android System SafetyCore...
which scans a user's sent and received images.. for explicit images and
displays content warnings before the user views them.
<https://support.google.com/product-documentation/answer/16001929>
<https://www.theregister.com/2025/03/04/google_android/>
"Leith said he wasn't able to ascertain the purpose of the identifier
but his paper notes a code comment, presumably made by a Google dev,
acknowledging that this identifier is considered personally identifiable
information (PII), likely bringing it into the scope of European privacy
law GDPR - still mostly intact in British law as UK GDPR."
Not the best of sources, and it doesn't even mention the most important
factor, which is nobody who cares about privacy sets up a Google Account
on the phone (they can have a google account - just not in the settings).
"Doug Leith, professor and chair of computer systems at Trinity College
Dublin, who carried out the research..."
"The DSID cookie is "almost certainly" the primary method Google
uses to link analytics and advertising events, such as ad clicks,
to individual users, Leith writes in his paper"
� <https://www.scss.tcd.ie/Doug.Leith/pubs/cookies_identifiers_and_other_data.pdf>
Leith specifically mentions these apps, one of which nobody ever needs:
1. Google Play Services
2. Google Play store
Note the existence of a 'DSID' cookie, which Google explains in its
documentation is used to identify a "signed in user on non-Google websites
so that the user's preference for personalized advertising is respected
accordingly. The 'DSID' cookie lasts for two weeks."
Note that this DSID cookie apparently only exist for those who sign into a
Google Account (which is usually as part of the Android startup process).
Likewise, "Another tracker which cannot be removed once created is the
Google Android ID, a device identifier that's linked to a user's Google
account and created after the first connection made to the device by Google
Play Services. It continues to send data about the device back to Google
even after the user logs out of their Google account and the only way to
remove it, and its data, is to factory-reset the device."
Notice none of this (likely) happens if you're smart enough to simply not
list a Google Account in the Android account settings, which, is so trivial
not to do, that it needs no explanation. The phone works better without it.
Note that the article concludes with "The findings come amid something of a
recent uproar about another process called Android System SafetyCore...
which scans a user's sent and received images.. for explicit images and
displays content warnings before the user views them.
<https://support.google.com/product-documentation/answer/16001929>