Google Auto-Links Your Phone Number Across All Signed-In Android Accounts: What Changed and How to Opt Out

Google now automatically verifies your phone number and attaches it to every Google account signed in on the same Android device, without an explicit confirmation prompt. The behavior is documented in Google's own support page, which was updated between August and October 2025 to describe phone number verification as on by default and as applying to all Google accounts signed in on the device.

The change matters because it collapses account separation that many users rely on for security, work/life boundaries, and privacy. A phone number that was previously tied to one primary Google account can now appear as a verified contact method on secondary profiles, work accounts, and throwaway handles on the same phone.

What Google changed, according to Android Authority

Android Authority reported that Google's support documentation for phone number verification was updated between August and October 2025 to add two behaviors: turning phone number verification on by default, and adding all phone numbers to all Google accounts signed in on the device.

The support page (support.google.com/android/answer/7521240) has long stated that Google periodically re-verifies a device's phone number to keep communication and recovery features current. The newer documentation describes the automatic, cross-account behavior as an opt-out feature rather than something users enable themselves.

Android Authority said its own team had not seen the specific notification emails land in their inboxes, but that several colleagues checked their device settings and found the auto-verification toggle quietly enabled on their active devices.

How the automatic verification surfaces to users

The change was surfaced publicly through a Reddit thread in r/Android, where users reported receiving unexpected confirmation emails from noreply-phone-verification@google.com stating that their phone number had been verified.

In Google settings the feature is named "Phone number verification." It links the active phone number across all Google accounts signed in on the same phone, including secondary profiles, work accounts, and alternate handles.

How to disable phone number verification on Android

Disabling the feature stops future automatic linking. Android Authority documented these steps:

1. Open the phone's Settings app.
2. Tap Google (or Google services and preferences).
3. Switch to the All Services tab.
4. Under Privacy & Security, locate Phone number verification.
5. Toggle off Verify phone numbers automatically.

Turning the toggle off does not remove numbers that Google has already attached. To unlink an existing number, open the Google Account Personal Info page at myaccount.google.com/personal-info, go to Contact info > Phone, and manually remove the number from each profile where it does not belong.

Some users report the opt-out does not persist

Android Authority noted that some Reddit users, in a thread on r/degoogle, complained that disabling phone number verification does not stick and that the option re-enables itself when they return to the settings screen. Android Authority said it was unable to replicate that behavior and that disabling the feature stuck for its team "for now."

Android Authority also stated it had reached out to Google for a statement on the opt-out behavior and would update the story when it learned more.

"Silently" is disputed: Google sends confirmation emails

The most common pushback in the Hacker News discussion was about the word "silently." Multiple commenters said they received notification emails or on-device notifications before or when their numbers were linked.

"I think it's creepy and bad, but 'silently' is not accurate, at least in my case: Google sent each of my accounts an email telling me about it." — hoppyhoppy2

"'Silently' has been redefined to mean 'we know this because of the emails it sends'." — jeffbee

Another commenter framed the objection as a sequencing problem rather than a disclosure problem: the notice arrived after the number had already been attached, with no chance to opt out first.

"It did not leave a good taste that I had to do this after the fact, I would have appreciated a notice with a chance to opt out first, because they may have already permanently stored those numbers in some internal history." — anygivnthursday

Not every user observes the same behavior

At least one commenter reported a different result on their own device, which suggests the rollout or the linking logic is not uniform.

"This isn't the behavior I observe on my phone. All my SIMs I've used in my phone seem to have been added as verified phone numbers to my primary account, but my secondary accounts don't have any phone numbers still. It's still somewhat obnoxious since it means random travel sims that could get reused after they expire are 'verified' for my account." — barrkel

Another commenter described a login-verification flow that appeared to link accounts as a side effect: Google asked them to verify a login using the account tied to the backup email address, and after completing verification the phone number appeared attached to the secondary account.

Why account compartmentalization is the core concern

The practical harm described by users is not that a phone number is stored, but that it becomes a join key across identities that were deliberately kept apart. Commenters cited work/life separation, per-client isolation for contractors, and protection against a single account compromise cascading into others.

"The modern trend of trying to tie everything you ever do to a specific phone number and in some cases not even allowing multiple accounts to be created using the same phone number undermines that compartmentalisation." — Silhouette

"Very unexpected behavior, esp for those with several accounts and phone numbers, intending to keep them separate for security or other reasons." — jamiesonbecker

One commenter argued the linkage is not new in kind, only in scope, pointing to Google's history of correlating identities across products when enforcing bans.

"They don't ban accounts, they ban people." — jabroni_salad

Corporate and enterprise implications

The change creates friction for organizations whose policies forbid linking personal devices or personal phone numbers to corporate accounts.

"Our corporate policy doesn't allow personal phones to be linked to corp accounts, for obvious reasons. We have no idea what kind of security your personal phone number has setup, nor do we compensate employees for their personal phones, nor do we want corporate communications happening on your personal device (work/life separation). If the vendor is unable to comply, all we're using them for is email. Time to look elsewhere." — exabrial

The counterargument: convenience by default, few users affected

Not every commenter treated the change as a serious problem. One argued that the default should favor convenience and that the opt-out is sufficient.

"Probably only 0.0001% of people care about this. It makes sense that the more convenient option is default. There's an option to turn it off if you want." — kats

Others questioned whether the behavior was ever in doubt, with several commenters saying they had always assumed Google linked accounts signed in on the same device, and one suggesting the documentation update is a legal cover rather than a new capability.

"'Now'? I assumed they always did that. And I'd also assume the documentation change is CYA in case someone tried to sue them over it." — InsidiousWombat

The broader pattern commenters describe

Much of the discussion treated the phone-number change as one data point in a longer trend of Google requiring stronger identity signals to use its services. Commenters cited QR-code device verification during signup, reverse SMS verification where the user sends rather than receives a code, country-matching requirements for phone numbers used with VPNs, YouTube restrictions for signed-out VPN users, and Gemini failures when accessed over a VPN.

"Google is probably the most aggressive anti-privacy big tech company currently operating." — maxo133

"At this point your phone number has become your social security number of the internet." — declan_roberts

Several commenters described downstream consequences of phone-number-based identity: difficulty reusing a number as a second factor after it has been "used too many times," the risk of a single account action cascading to every linked account, and the possibility that a phone number becomes a durable root identifier for bans and access decisions.

"The problem this can cause is that it could become the root identity for the effective social credit system." — jhallenworld

One commenter reported that Google deleted their Gmail account for not supplying a phone number, and another noted that new accounts receive 5 GB instead of 15 GB of storage without a phone number.

What users are doing instead

Commenters described mitigations ranging from never signing secondary accounts into an Android device, to using third-party mail clients over IMAP to avoid connecting accounts, to migrating to GrapheneOS.

"Its taking me awhile (about a month so far) but Im migrating my Google Pixel 5A to Google Pixel 10 Pro and GraphenOS." — PerilousD

One GrapheneOS user reported a separate but related pressure: a financial institution required age attestation through Google Play, which they were unwilling to install. Another commenter said they had always kept their email account separate from their Android account specifically to avoid linkage, at the cost of not being able to use Google apps like Meet on their phone.

What remains unresolved

Google had not issued a statement on the opt-out behavior at the time Android Authority published its report. The two open questions are whether the automatic linking applies uniformly across devices and account types, and whether the settings toggle reliably persists after being disabled — a claim Android Authority could not reproduce but that multiple Reddit users reported.