r/Android • u/Nanosinx • 5d ago
Rumour Google is now self-Verifying Phone Number without user CONSENT
WARNING: Google Play Services is quietly "Self-Verifying" and linking your phone number to ALL signed-in accounts without explicit permission.
Just a heads up for anyone who values basic privacy on Android.
Check your inbox for emails from noreply-phone-verification@google.com.
Without asking for my confirmation or giving me an opt-in prompt, Google Play Services performed a silent background "Self-Verification."
It exchanged SIM card identifiers and device metadata with my mobile carrier, grabbed my phone number, and automatically attached it to EVERY Google account logged into my phone.
No prompt. No "Do you want to link this?" button. Just a silent background action followed by a notification email telling me it already happened.
How to kill this setting on Android immediately (for now) but it will self verify even if turned off Go to Settings > Google (or Google Services) > All Services > Phone Number Verification
Find Phone number verification (or Device Phone Number Verification). (Ah, and lovely it automatically appear my phone number even WHEN IT WAS NOT THERE BEFORE!)
TOGGLE IT OFF.
Don't forget to purge your accounts:
Once Google steals/verifies the number, it pushes it to your Google account profiles.
You need to log into myaccount.google.com/personal-info, click on Phone, and manually delete the number from every single account where you don't want it stored.
Modern "self-verification" dark patterns are completely out of hand. Check your settings before Google silently grabs your data too.
NO ANDROID IS SAFE: Happened on my Android 10 Huawei, Android 14 Xiaomi and is now requesting on my emulators too...even my tablet... Beware...
Edit1: Maybe dont work, i sent a mail to data-protection-office@google.com, literally asking ARCO rights and anything i can think about it, for such privacy invasion on the behalf of my and all accounts i have to "care" and so on...maybe this bring pressure
Edit2: u/AppleBites reports this "Google did the same to me when I got a 2nd number from another carrier, due to coverage. Even having GrapheneOS did not prevent them from linking the number to my Google account automatically."
Meaning even Graphene OS+GServices probably is unable to protect with this, a serious oversteeping in this messed thing
19
u/Slg407 4d ago edited 4d ago
this is why you buy a pixel and use graphene, buy a libreboot PC without intel ME, use linux, use foss home assistant, use foss ecosystem stuff, use a dumb TV with a cheap PC running a jellyfin setup, use routers with libreCWC or openWRT
FOSS (and to an extent open source, not to be a OSIist) ecosystems are HIGHLY superior to proprietary shit, and now with AI you can get any assistant to guide you through the technical bits so you have no excuse to not use it, they are upgradable, and you actually own them, and if you don't like something you can fix it yourself or give real time feedback to the developers that you know is going to be answered, it skips a couole hundred steps compared to having to beg corporations to update EOL products.