Google is silently linking your phone number across all signed-in accounts
Google’s practice of automatically linking a user’s phone number across all Google accounts on the same Android device is raising alarm over privacy, security, and account compartmentalization. Commenters describe it as an invasive default that aids identity correlation, fuels ad targeting, and weakens protections against SIM-based attacks, while noting that opting out is possible but buried behind confusing settings and dark patterns. Many see this as part of a broader trend in which tech companies, under pressure to fight fraud and abuse, increasingly require phone numbers, government IDs, and other strong identifiers at the expense of user anonymity and control.
Scope of the New Phone Linking Behavior
- Many see Google’s cross-account phone linking as a major, unexpected privacy invasion, especially for users who deliberately keep multiple accounts or numbers separate (personal/work, different clients, “faux” vs “private” devices).
- Some report it was not “silent”: they received device notifications and emails describing the feature and how to disable it.
- Others say instructions were incomplete or misleading: settings sometimes missing on certain devices (e.g., watches), and key ad/phone-number options only visible on the web, not on the device.
- Concern that deleting the number later doesn’t undo whatever internal history or correlations Google already created.
Privacy vs Abuse/Fraud Control
- One camp: Google has shifted hard toward maximizing data collection, systematically deanonymizing users (phone verification, VPN-hostility, ID/face checks, tying numbers to recovery and ads).
- Another camp: stronger identity requirements are driven largely by regulators and abuse realities (scammers, bots, fake accounts, ad fraud, kids’ safety, state demands). Same mechanisms that fight fraud also erode privacy.
- Some say Google and Meta are similar or worse than each other; difference is Google’s ecosystem is harder to avoid (Android, search, email, banking apps depending on Play Store).
Security and Risk of Phone as Root Identity
- Worry that attaching numbers increases attack surface: SIM-based takeovers, forgotten recovery paths, and irreversible “linking” of accounts.
- Complaints that many services now treat phone numbers as de facto KYC and central identifier, often disallowing VoIP or virtual numbers.
- Corporate policies sometimes forbid tying personal numbers to work accounts; new auto-linking can violate such policies.
Workarounds, Resistance, and Lock-In
- Users describe strategies: using multiple phones, GrapheneOS, privacy-focused tools, burner/secondary numbers, unique emails, or refusing services that demand verified numbers or government IDs.
- Others note practical limits: Google accounts increasingly required for banking apps, mobile OS features, or OAuth-based services.
- Some suggest regulatory responses (e.g., complaints to Attorneys General, GDPR arguments), but overall sentiment is pessimistic: surveillance and identity linkage feel inevitable, with most users accepting it for convenience.