Every store policy deadline on one page

Google Play is expanding its Age-Restricted Content and Functionality policy to cover anonymous chat and random chat apps. Apps whose core function is to randomly connect users to strangers, or to let users communicate anonymously (identity deliberately hidden), must use Play Console's tools to block minors from accessing the app.

Google announced new Google Play policy changes on July 15, 2026, with a 30-day compliance window for developers. Anonymous and random chat apps now face stricter requirements under the Age-Restricted Content, Child Safety Standards, and Families Policy guidelines, including an explicit ban on targeting children. Separately, the SMS and Call Log Permissions policy no longer allows phone-call-based account verification through the READ_CALL_LOG permission — developers should migrate to the Digital Credentials API or SMS Retriever API instead. Google is also enforcing developer verification: apps must be registered in Play Console, and unregistered apps risk removal from the store, though most existing apps have already been auto-registered. Developers should check their Play Console Home page to confirm registration status and review the full announcement for additional clarifications and reminders that may apply to their apps.

Apple has updated the App Store Connect age rating questionnaire to include new questions about social media capabilities, supporting the new Time Allowances feature in iOS 27, iPadOS 27, and macOS 27. Any app that lets users redistribute, amplify, or interact with user-generated content through a feed or similar discovery method is affected, regardless of its listed app category. Such apps will show a new "Social Media" content descriptor on their product page. Developers can answer these questions now, but starting September 2026, responses become mandatory for all new app submissions, updates, and notarization for alternative distribution. No extension has been announced.

To comply with the European Union Digital Services Act (DSA), Apple now requires developers distributing apps in EU countries to declare and verify their Trader Status in App Store Connect. Developers must provide accurate trader information, including business or contact details, before submitting new apps or app updates for distribution in the European Union. Apps that do not provide the required trader status information may be removed from App Store availability in EU regions until compliance requirements are completed. Developers should review and verify their trader information to avoid submission delays or distribution restrictions. (Required for EU app distribution and updates)

Google Play is removing geofencing from the list of approved use cases for the foreground service location type. Apps currently declaring geofencing under a foreground service (TYPE_LOCATION) will need to migrate this functionality to the dedicated Geofence API instead. Developers should audit their foreground service declarations in Play Console before August 26, 2026 and update any geofencing implementation to use the Geofence API to stay compliant.

To improve developer account security and ownership transparency, Google Play introduced updated account transfer requirements. Developers must use the official “Transfer ownership” workflow within Play Console when transferring apps or developer accounts. Manual credential sharing or unofficial ownership changes may violate Google Play policies.

As per updated Google Play policy requirements, apps may only access location data protected by device location permissions, such as ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, and ACCESS_BACKGROUND_LOCATION, for as long as it is necessary to provide current app features or services. Apps must not request location permissions solely for advertising or analytics purposes, and any advertising-related use of location data must comply with applicable Ads policies.

As per updated Google Play requirements, apps and updates must target an Android API level within one year of the latest major Android version release, with compliance reviews conducted annually around August 31. Additionally, apps targeting Android 17 or later (API level 37+) may request the READ_CONTACTS permission only when the Android Contact Picker does not sufficiently support core app functionality. Apps requesting this permission must also submit a Play Console declaration explaining the need for Contacts access and why the Contact Picker is insufficient.

As per updated Apple requirements, apps that use third-party or social login services for account creation or authentication may also be required to support Sign in with Apple as an equivalent sign-in option, in accordance with App Store review guidelines.

As per updated policy requirements, apps that include matchmaking, dating, or real-money gambling, games, or contest features must use available Play Console safeguards and age-restriction tools to prevent access by minors.

As per updated Apple requirements, starting April 2026, apps and games submitted through App Store Connect must meet updated minimum SDK requirements. iOS and iPadOS apps must be built using the iOS 26 and iPadOS 26 SDKs or later, while tvOS apps must use the tvOS 26 SDK or later.

Google Play requires apps offering in-app purchases or subscriptions to use Google Play Billing Library 8.0.0 or later starting August 31, 2026. Developers should update their Billing Library dependency, ensure third-party billing SDKs are compatible, and verify all purchase and subscription flows before publishing an app update. Apps using unsupported Billing Library versions may be unable to publish new releases or updates. If additional migration time is needed, eligible developers can request a one-time extension through Google Play Console until November 1, 2026.

To meet Google Play's latest requirements, apps must target Android 16 (API level 36) for new submissions and updates starting August 31, 2026. Developers should update their SDK configuration, test app compatibility, and release a compliant version before the deadline. If additional migration time is needed, eligible developers can request a one-time extension until November 1, 2026.