Direct answer: Google announced a new Play policy package on July 15, 2026. The nearest compliance date is August 26, 2026 for anonymous/random chat and child-safety changes. Developers should also meet the annual August 31 target API deadline, verify app package registration before September 30, 2026, and replace phone-call verification that depends on READ_CALL_LOG by January 27, 2027.
Do this first: open the Android developer verification section on your Play Console Home page, confirm every package name you still distribute is registered, and assign an owner to each policy item below. Google says 99% of Play apps were registered automatically, but it explicitly tells developers to check the remaining apps.
Google Play July 2026 deadline table
| Deadline | Who is affected | Required action |
|---|---|---|
| August 26, 2026 | Anonymous chat and random chat apps, especially apps involving minors | Review Age-Restricted Content and Functionality, Child Safety Standards, and Families requirements. Anonymous chat apps may not target children. |
| August 31, 2026 | Apps subject to Google Play’s annual target API requirement | Confirm the app meets the latest applicable target API level requirement shown in Play Console. |
| September 30, 2026 | Google Play developers and developers distributing on participating stores | Register all package names you intend to keep distributing and verify developer/account details. |
| January 27, 2027 | Apps using READ_CALL_LOG for phone-call account verification | Migrate account verification to the Digital Credentials API, SMS Retriever API, or an eligible provider-based alternative. |
Important: Google’s July announcement initially says developers have “at least 30 days,” but its official Policy Deadlines table gives the specific dates above. Treat the deadline table and the policy shown in your own Play Console as the operational source of truth.
10-step developer compliance checklist
- Inventory every package name. Include production, internal, legacy, transferred, and externally distributed apps that you still support.
- Check registration status in Play Console. Do not assume automatic registration covered every app merely because Google reports 99% overall coverage.
- Confirm the correct account type. Google says financial, health, VPN and government app providers must register as organizations.
- Verify account details. Check the legal name, address, contact email and phone, payment profile, and D-U-N-S details where an organization account requires them.
- Audit anonymous and random chat. If either feature exists, review age restrictions, child-safety controls, target-audience settings and Families eligibility before August 26.
- Check the target API requirement. Use the status and exact requirement displayed for each app in Play Console before August 31.
- Find
READ_CALL_LOGdependencies. Search manifests, permission declarations and verification flows; create a migration ticket if phone-call verification relies on this permission. - Review third-party AI data flows. Document what user data is sent to an AI provider, why it is sent, retention behavior, consent, disclosures and deletion handling.
- Validate ratings and location disclosures. Google clarified that unrated apps are not allowed and added guidance for precise versus approximate location declarations in the Data safety section.
- Save evidence. Keep screenshots or exports of registration status, policy declarations, test results and the date each compliance owner signed off.
What changed for anonymous and random chat apps?
Google expanded three policy areas. Its Age-Restricted Content and Functionality and Child Safety Standards policies now contain requirements and restrictions for anonymous and random chat apps. Its Families Policy Requirements also prohibit anonymous chat apps from targeting children. These changes are listed with an August 26, 2026 deadline.
A practical review should cover onboarding age gates, whether users can be paired randomly, whether identity is hidden, moderation and reporting controls, store-listing claims, target-audience declarations, and any child-directed acquisition campaigns. The full Google policy—not this summary—controls.
Package-name registration: what Play developers should check
Google’s preview of the Play Console Requirements says developers must register app package names through Play Console to meet Android developer verification requirements. It warns that remaining unregistered Play apps may face global removal from Google Play. The requirement is listed as effective September 30, 2026.
- Play-only distribution: review verification status in Play Console and register any app not handled automatically.
- Distribution outside Play: Google says Play Console can also register externally distributed apps. Developers who distribute only outside Google Play can use the Android Developer Console.
- Initial rollout: Google says verification protections begin September 30 across participating stores for users in Brazil, Indonesia, Singapore and Thailand, followed by broader global expansion in 2027.
Third-party AI integrations: the developer remains responsible
Google clarified that its User Data requirements apply to third-party AI integrations. Adding an external model API, agent SDK, chatbot service or AI analytics vendor does not transfer the app developer’s policy responsibility to that provider.
At minimum, map each AI data flow: the input collected, the vendor receiving it, the purpose, user disclosure, consent basis, retention, access controls and deletion route. Compare that map with the privacy policy and Play Data safety answers. This clarification does not create a new enforcement standard, according to Google, but it makes the existing responsibility explicit.
Replacing phone-call verification that uses READ_CALL_LOG
From January 27, 2027, account verification by phone call will no longer be a permitted use case for READ_CALL_LOG. Google points developers to the Digital Credentials API or the SMS Retriever API, including eligible verification providers built on the newer approach.
Do not simply remove the permission immediately from a production app without testing the replacement. Trace the existing verification path, implement the alternative in a test track, verify fallback and recovery behavior, then remove the obsolete permission and update policy declarations.
Optional: use Google’s open-source Play policy AI skill
Google also released an open-source Play Policy Insights skill intended to ground compatible AI assistants in Google Play policies for code review in an IDE or CLI. It can help identify issues earlier, but it is not a compliance guarantee and does not replace the policy text or Play Console review.
FAQ
When do the July 2026 Google Play policy changes take effect?
The anonymous/random chat protections take effect August 26, 2026. Package-name registration becomes a Play Console requirement September 30, 2026. The READ_CALL_LOG account-verification change takes effect January 27, 2027. Google separately reminds developers about the August 31, 2026 target API deadline.
Does every Play app need manual registration?
No. Google says 99% of Play apps were registered automatically. You should still check every package name and manually register anything remaining that you want to continue distributing.
Are third-party AI providers responsible for my Play compliance?
The provider may have contractual and legal duties, but Google’s clarification says the app developer remains responsible for Play User Data compliance, including limited use, disclosure and consent.
Official sources
- Google Play policy announcement — July 15, 2026
- Google Play Policy Deadlines
- Preview: Play Console Requirements
- Android developer verification rollout details
- Android Play Policy Insights skill
Last checked: July 19, 2026. This is a practical summary, not legal advice. Google’s current policy text and the notices in your Play Console take precedence.