Google Play's 2026 Anonymous and Random Chat App Rules: Age-Restriction, Child-Safety and Developer Verification Changes

What Google Play Changed in July 2026

On July 15, 2026, Google Play announced a set of policy changes that do two things at once: they bring anonymous chat and random chat apps under Google's core child-safety policies, and they tighten developer verification and Play Console registration requirements across the whole store. The changes were published on Google Play's Policy Deadlines page, with staggered effective dates running from August 2026 into early 2027. The August 26 and September 30, 2026 dates have now passed.

The anonymous-chat element is the headline. Google says apps covered by its Age-Restricted Content and Functionality policy must block minors "to help ensure the safety of children and prevent access to potentially harmful content", and the update applies its existing age-restriction, Families and child-endangerment frameworks directly to this app category. Alongside that, a separate but equally consequential thread — Play Console registration and developer verification — determines whether an app can remain distributable at all.

"We're expanding our Families Policy Requirements policy to prohibit developers of anonymous chat apps from targeting children.
— Play Console Help, Policy Deadlines (announced July 15, 2026)"

This guide sets out exactly which policies expanded, the deadlines that apply, how the Play Console registration and verification requirement works, and what the SMS and Call Log permission change means. For the broader Google advertising framework these apps also touch, see the Google Ads policy guide, and track how this and related changes evolve on the Policy Change Tracker.

The Three Child-Safety Policy Expansions

Three separate Google Play policies were expanded to apply to anonymous chat and random chat apps, all effective August 26, 2026. Each targets a different layer of the child-safety problem, and together they close the space in which this app category previously operated with lighter obligations.

What Is Expanding, and to What

The practical effect is layered. The Families Policy expansion means an anonymous chat app must not target children: Google's Families policy says social apps whose "main focus" is chatting with strangers or chatting anonymously "must not target children". The Age-Restricted Content and Functionality expansion is the most concrete: apps "whose core functionality is to facilitate randomly connecting users to spontaneously communicate with people they do not know" or "for users to communicate anonymously where the identity of one or more users is deliberately hidden" are "required to use the Play Console functionality and tools to block minors". And the Child Safety Standards expansion brings these apps under the child-endangerment framework that governs how platforms must prevent and respond to child sexual abuse and exploitation risks. Because all three land on the same date, developers of affected apps face a combined compliance workload rather than a single change. Screen store listings, feature descriptions and in-app copy for risk with the Keyword Risk Checker.

Key Compliance Deadlines

The July 15 announcement bundles several deadlines with different dates. Treating them as a single event is a mistake — each has its own timeline and its own consequence for missing it. The table below sets out the sequence as published.

The Deadline Timeline

The staggering matters for planning. The child-safety expansions took effect first and carry the most direct enforcement risk for the affected app category. The Play Console registration deadline is store-wide — Google says unregistered apps risk global removal from Google Play. The permission change is further out but requires engineering work to re-architect account verification, so it should not be left until January 2027. Map these dates into your own release calendar and track any further updates on the Policy Change Tracker.

Play Console Registration and Developer Verification

Separate from the child-safety changes, Google is enforcing a store-wide registration and verification requirement with a September 30, 2026 deadline. This is the change most likely to catch developers by surprise, because it applies to every app, not just a specific category.

What the Requirement Says

To meet Android developer verification requirements and Play Console requirements, developers must register their Play apps in Play Console. Google states that roughly 99% of apps on Play were registered automatically, so most developers are already compliant — but the responsibility to check remains. Developers should review their Play Console Home page and register any remaining apps they want to continue distributing, in order to avoid global removal from Google Play and ensure a smooth installation experience for users.

Why It Matters Beyond the Play Store

• Global removal is the stakes: Google says registering remaining apps is needed "to avoid global removal from Google Play".
• It extends to off-Play distribution: developers can also register apps distributed outside Google Play, so they remain installable on certified Android devices. Android developer verification protections began on September 30, 2026 for installs from participating stores in Brazil, Indonesia, Singapore and Thailand, with a global rollout in 2027. See our September 30 registration deadline explainer.
• The 99% figure is not a guarantee for you: automatic registration covers most apps, but any app in the remaining share must be handled manually before the deadline.

The verification push reflects a broader Android direction: tying app distribution and installability to verified developer identity. For agencies and studios managing multiple apps or client portfolios, the action is straightforward but must not be skipped — audit every app in every Play Console account and confirm registration status. Audit your wider compliance posture with the AI Compliance Audit.

The SMS and Call Log Permission Change

The third strand of the July 15 announcement is a change to the SMS and Call Log Permissions policy, effective January 27, 2027. It is narrower than the child-safety expansions but has real engineering implications for any app that verifies user accounts through the phone.

What Changes

Under the updated policy, the READ_CALL_LOG permission will no longer be permitted as a way to verify accounts via phone call. In other words, developers cannot lean on call-log access as a mechanism for confirming a user's identity or account. Google directs developers to more privacy-preserving alternatives: the Digital Credentials API — used directly or through a verification provider built on it — or the SMS Retriever API, which allows one-time-code verification without requiring broad SMS-reading permissions.

Why It Matters

• Reducing sensitive-permission use: call-log and broad SMS permissions are among the most sensitive an app can request, and Google has been steadily narrowing the use cases that justify them.
• Steering to purpose-built APIs: the Digital Credentials API and SMS Retriever API achieve verification with far less access to personal data, aligning with data-minimization expectations.
• Google's stated aim: the policy page tells developers to use these APIs "to securely verify accounts without requiring sensitive app permissions".
• Lead time: the January 2027 date leaves time to migrate, but re-architecting verification flows is non-trivial and should be scoped now.

For product and engineering teams, the takeaway is to inventory any account-verification flow that relies on call-log or broad SMS permissions and plan a migration to the recommended APIs well ahead of the deadline. This dovetails with broader data-minimization duties under privacy law; map cross-border obligations with the Legal Compliance Scan.

What Developers, Agencies and Brands Must Do

Although the child-safety expansions target a specific app category, the July 15 package touches a much wider set of developers, agencies and brands. The practical response depends on which apps you run and how you verify users.

Practical Actions by Situation

• If you build anonymous or random chat apps: since August 26, 2026 the app must comply with the Age-Restricted Content, Families and Child Safety Standards policies — including using Play Console tools to block minors where random or anonymous chat is the core functionality, not targeting children, and meeting child-endangerment obligations.
• If you run any Play app: the September 30, 2026 deadline has passed — check Play Console Home now and register any remaining app to avoid global removal, even if you expect automatic registration covered you.
• If your app verifies accounts by phone: plan migration away from READ_CALL_LOG-based verification to the Digital Credentials API or SMS Retriever API before January 27, 2027.
• If you are an agency or studio: run this as a portfolio audit across every client and every Play Console account, since a single unregistered app or non-compliant chat feature can remove access.

There is an advertising dimension too. Marketers running user-acquisition campaigns for affected apps should check that targeting and creative do not reach minors, consistent with the app's age restriction. Brands whose apps have random or anonymous chat as a core function are in scope; apps where chat is only an incidental feature should check the policy wording to confirm whether they fall in scope. Because policy wording and deadlines can shift, verify the current position against Google Play's official policy and deadline pages before finalizing changes, and see the child-and-teen dimension of platform rules in the compliance glossary.

Google Play Compliance Checklist

• Determined whether any of your apps qualify as an anonymous chat or random chat app under the expanded policies
• Brought affected apps into line with the Age-Restricted Content and Functionality policy by August 26, 2026
• Ensured anonymous chat apps do not target children under the expanded Families Policy Requirements
• Met the Child Safety Standards / Child Endangerment obligations for affected apps
• Reviewed Play Console Home and confirmed every app is registered (deadline was September 30, 2026)
• Registered any off-Play-distributed apps you want installable on certified Android devices
• Inventoried account-verification flows using READ_CALL_LOG or broad SMS permissions
• Scoped migration to the Digital Credentials API or SMS Retriever API ahead of January 27, 2027
• Reviewed user-acquisition targeting and creative for age-restriction compliance on affected apps
• Verified all requirements against Google Play's official policy and deadline pages