Google Silently Links Phone Numbers Across Secondary Android Profiles

When Apple introduced App Tracking Transparency in 2021, it forced developers to ask permission before linking user data across different services. Google has taken the opposite approach with Android's account management, silently binding the device's primary phone number to every secondary Google account signed into the hardware.[1][2]

The change, which users began noticing in mid-October 2026, bypasses the traditional opt-in prompts that usually accompany data sharing between profiles. If a user maintains a primary personal account and logs into a separate work or anonymous profile on the same Android phone, Google automatically registers the device's SIM number to the secondary account's security settings.[1][6]

The linkage occurs in the background through Google Play Services, the core system component that manages account authentication on Android devices. Users are not notified when the number is attached to the new profile, and the connection remains active even if the secondary account is later removed from the device.[1][4]

The Privacy Implications

For years, Android users have relied on multiple accounts to compartmentalize their digital lives, keeping professional emails, YouTube viewing histories, and cloud storage separate from their primary identity. The automatic phone number binding compromises this separation, creating a hard link between profiles that were intended to remain distinct.[2][3]

The practice has sparked immediate privacy concerns, particularly for users who manage accounts for sensitive reasons, such as whistleblowers, activists, or those separating personal lives from professional identities. By attaching a verifiable phone number to an otherwise anonymous account, Google creates a direct path to identify the user behind the profile.[2][4]

Security researchers note that while Google frames phone number verification as a security feature to aid in account recovery, applying it universally without consent fundamentally alters the privacy model of secondary accounts. The linkage means that a data request or breach affecting the secondary account would immediately expose the user's primary phone number.[4][6]

How to Disable the Linkage

While the automatic linking happens silently, users can manually sever the connection after the fact. The process requires navigating deep into the Google Account settings for each affected profile, locating the "Personal info" tab, and manually deleting the phone number from the "Contact info" section.[1][2]

However, removing the number from the account settings does not prevent Google from re-linking it the next time the device performs a background security check. To stop the automatic binding permanently, users must disable the "Auto-verify phone number" toggle hidden within the Google settings on the Android device itself.[1][5]

This setting is buried under "Google" in the main device settings, then "Manage your Google Account," followed by "Security," and finally "Advanced Security Settings." Disabling this toggle prevents Google Play Services from automatically sharing the device's phone number with newly added accounts, though it does not remove numbers that have already been linked.[1][2]

Google's Silence

Google has not publicly commented on the change or explained why the automatic linking was implemented without user notification. The company's support documentation states that phone numbers are used for account security and recovery, but it does not address the privacy implications of cross-linking profiles.[4][6]

The lack of transparency has drawn sharp criticism from privacy advocates, who argue that the practice violates the principle of data minimization and user consent. The silent rollout also raises questions about whether the change complies with data protection regulations in jurisdictions like the European Union, where explicit consent is required for data sharing.[2][4]

Until Google provides a formal explanation or alters the behavior, Android users who rely on multiple accounts must proactively audit their security settings to ensure their profiles remain separate. The burden of maintaining privacy has shifted entirely to the user, requiring constant vigilance against silent background changes.[3][6]