Shadowfetch News — AI news. Real coverage.

apps

Google Play’s July 2026 policy pack: chat safety, call-log verification, and registration deadlines

The durable developer problem is not reading the announcement—it is mapping three separate clocks (26 Aug chat rules, 30 Sep app registration, 31 Aug target API) onto real product and permission debt before enforcement.

logo, icon
Photo by Rubaitul Azad on Unsplash

Google Play’s Policy announcement for 15 July 2026 updates Age-Restricted Content and Functionality and Child Safety Standards with new requirements for anonymous chat and random chat apps, and states that Families Policy Requirements now prohibit anonymous chat apps from targeting children. Play’s Policy Deadlines table pegs those chat and families expansions to 2026-08-26.

The same announcement tightens SMS and Call Log Permissions: account verification via phone call will no longer be an accepted use of READ_CALL_LOG. The Help Center SMS/Call Log article and the deadlines table both mark that change effective 2027-01-27 and point teams at lower-permission verification paths instead of reading the call log.

Play also ties Android developer verification and Play Console requirements to app registration in Console. The deadlines table lists 2026-09-30 for remaining registration work, with Google stating that about 99% of Play apps were registered automatically and that unregistered apps risk global removal. A separate yearly reminder requires apps to meet the latest target API level rules by 31 August 2026; the Target API level requirements article specifies Android 16 (API 36) for new apps and updates on phone, with platform-specific floors for Wear, TV, Automotive, and XR, and an extension path to 1 November 2026 when offered in Console.

Clarifications in the July pack matter for product reviews even when they are not “new” enforcement: User Data requirements explicitly cover third-party AI integrations, and unrated apps are not allowed on Play. Google also published an open-source Play Policy Insights skill (metadata last-updated 2026-07-13) so IDE/CLI agents can ground pre-submission checks in Play policy domains such as permissions hygiene, data safety, and restricted permissions—including SMS and call log.

Limitation: this article cites Play Console Help primaries and the published skill text. It does not rely on developer.android.com HTML hubs that fail unattended fetch with HTTP 302/OAuth, and it does not inventory every regional edge case, webinar Q&A, or Console UI label that may appear only inside a signed-in developer account.

Shadowfetch fit is adjacent hygiene, not a Play Console substitute. Exportveil: Privacy Report helps people and support teams sanitize diagnostic privacy reports before share when User Data and AI-integration scrutiny rises. Toolwarrant: MCP Audit is the desk for mapping tool/permission impact when agent features touch sensitive device capabilities. Pipelineweft: CI Audit reviews workflow YAML on the path that builds and ships the binary you will later target-SDK-bump. None of these apps file Play declarations or change store policy status for you.

Sources

  1. Policy announcement: July 15, 2026 (Play Console Help)
  2. Policy Deadlines (Play Console Help)
  3. Preview: Age-Restricted Content and Functionality (Play Console Help)
  4. Use of SMS or Call Log permission groups (Play Console Help)
  5. Target API level requirements for Google Play apps (Play Console Help)
  6. Play Policy Insights skill (android/skills, SKILL.md)

From Shadowfetch