On Google Play, a fintech update targets API 35 and its Data safety form omits an analytics SDK's data; what does each rule require as of October 2026?
answer
- target, not minimum
- August 31, 2026 deadline
- every published track but internal
- SDK data is yours to declare
- encryption claim covers all data
basics
~20 sFrom August 31, 2026, phone app updates must target Android 16 (API 36) to be submitted. The Data safety form must declare all user data the app collects or shares, including data its third-party SDKs send off the device.
solid answer
~50 sTwo separate rules apply. The **target API level requirement**: from August 31, 2026, new apps and updates must target Android 16 (API 36) to be submitted, or API 35 for Wear OS and Automotive and API 34 for TV and XR; existing apps below API 35 stop reaching new users on newer Android versions, and an extension to November 1, 2026 can be requested. It is about `targetSdkVersion`, not `minSdk`. The **Data safety form** on the App content page is required for every app on closed, open or production tracks, even one that collects nothing; apps active only on internal testing, private apps and system services are exempt. It must include data that SDKs send off the device, may claim encryption in transit only if all transmitted user data is encrypted, and must stay accurate. You alone are responsible for its accuracy.
go deeper
Know that Google Play sets a minimum target API level for updates and that every published app fills in a Data safety form.
Explain targetSdkVersion versus minSdk, the API 36 rule from August 31, 2026, and which tracks make the Data safety form mandatory.
Untangle the stopped update into its two causes, account for every SDK's data in the form, and plan the behaviour-change testing the new target needs.
Make target API upgrades and SDK data reviews routine release work, so a yearly deadline or a new SDK never blocks an urgent fix.
## Two separate gates An update can be stopped by two different Google Play rules, owned by different parts of the app: - The **target API level requirement** reads the `targetSdkVersion` of the bundle you upload. It is enforced when you submit. - The **Data safety form** on the **App content** page in Play Console declares what user data the app collects and shares. Google Play reviews it as part of app review and shows it on the store listing. Fixing one does nothing for the other, so treat a stopped update as two checklists. ## The target API level requirement (from August 31, 2026) | App type | New apps and updates must target at least | |---|---| | Phone and tablet apps | Android 16 (**API level 36**) | | Wear OS and Android Automotive OS | Android 15 (API level 35) | | Android TV and Android XR | Android 14 (API level 34) | What else the rule says: - **Existing apps** that publish no update must target at least API 35 to stay available to **new users** on devices running a newer Android than their target. An app left at API 34 or lower is available to new users only on devices whose Android version is the same as its target or lower. - If you need more time, Play Console offers an **extension to November 1, 2026**. - Permanently private apps restricted to one organization are exempt. - The rule is about the **target** API, not `minSdk`; raising the minimum does not satisfy it. The requirement is checked on each bundle you submit, so a hotfix built from an old branch with an old target is stopped too. Raising the target is not a one-line change: each release's behaviour changes apply only once the app targets that level, so review the Android 16 behaviour changes and test before you bump it. ## The Data safety form Who must complete it: - **Every app published on Google Play**, including apps on closed, open or production tracks. - Even apps that collect **no** user data; they still need a privacy policy link and a form that says so. - Apps active **only** on the internal testing track are exempt, as are system services and private apps. What it must cover: - All user data the app **collects** (transmits off the device) or **shares** with a third party. - Data that **third-party libraries and SDKs** send off the device, whether to you or to the SDK's own servers. The SDK's data is your declaration. - Security practices: you may declare **encryption in transit** only if it applies to all user data the app and its SDKs transmit, and you state whether users can **request deletion** of their data. Before filling it in, review the app's declared permissions and the APIs it calls, as Play's guidance suggests; a permission that reads location or contacts usually points to a data type to declare. Data that is processed only **ephemerally**, held in memory just long enough to serve one request, still goes into the form response, but when it meets that standard it is not disclosed in the listing's Data safety section. Google's review is not designed to verify the form's accuracy; you alone are responsible for it, and when Google finds a mismatch it can require a fix and take enforcement action. The form must stay accurate whenever the app's data practices change. ## Fixing the stopped update 1. Raise `targetSdkVersion` to 36, work through the behaviour changes, and build a new bundle with a higher version code. 2. Inventory every SDK in the build and read its published data safety guidance. 3. Update the Data safety form for each data type the SDK collects or shares, and recheck the encryption-in-transit and deletion answers. 4. Send the changes for review from the **Publishing overview** page. ## Worked example A fintech app's 4.3 update still targets API 35 after August 31, 2026, so Play Console will not accept it for release. While fixing that, the team finds that a newly added analytics SDK sends device identifiers and app interactions off the device, which the Data safety form never declared. The team moves the target to API 36 and adds the SDK's data types to the form before sending the update for review.
- What happens to an existing app that stays at API 34 and publishes no update after August 31, 2026?It stays on Google Play, but it is available to new users only on devices whose Android version is the same as its target API level or lower. Users of newer Android versions who do not already have it can no longer get it. An extension to November 1, 2026 can be requested from Play Console.
- Does a build that only lives on the internal testing track need a Data safety form?No. Apps active only on internal testing are exempt from the Data safety section. As soon as the app has a release on a closed, open or production track, the form is required, even if the app collects no user data.
- Can you declare that data is encrypted in transit if one SDK still sends data over plain HTTP?No. The encryption-in-transit claim on Google Play's Data safety form applies only when all user data the app and every library or SDK in it transmits off the device is encrypted in transit.
- Apps that collect no user data can skip the Data safety form.
- Data an SDK sends straight to its vendor is the vendor's to declare, not yours.
- The target API requirement applies to brand-new apps only, never to updates.
- Google Play's review verifies that Data safety answers are accurate.
- Raising minSdk to 36 satisfies the target API level requirement.
Assumes Google Play's target API level requirement that took effect on August 31, 2026 (API 36 for new apps and updates) and Play Console as of 2026-10-10.