Google Play policy changes 2026: what every app publisher needs to know

1. Target API level: you must target Android 15 (API 35)

Every year, Google raises the minimum target API level Android apps must declare to be published or updated on the Play Store. In 2026, the bar is API level 35 (Android 15).

What this means practically:

• New apps submitted to Google Play must target API 35
• Existing app updates must also target API 35 — you cannot push an update to an older targetSdkVersion and expect it to go live
• Apps that fall below the floor are hidden from new users on newer Android versions

For apps built with SaasToStore, this is handled automatically. The Android App Bundle we generate targets the current required API level — no configuration needed on your end.

2. SafetyNet is gone — Play Integrity API is the standard

Google retired the SafetyNet Attestation API in June 2024. Any app that still calls SafetyNet will receive no response. The replacement is the Play Integrity API, which provides more granular device integrity signals:

• Device integrity — whether the device is certified and running a genuine Android OS
• App integrity — whether the APK was downloaded from Google Play or sideloaded
• Account details — whether the user has a valid Google account on the device

For most no-code apps and SaaS wrappers, this change is invisible — you typically don't call SafetyNet or Play Integrity directly. It matters most if your app involves payments, sensitive data, or anti-fraud logic. Still worth knowing if you're building a fintech or identity product.

3. Identity verification is now mandatory — and stricter

Google began requiring government-issued ID verification for all new individual developer accounts in 2023. In 2025, they extended this requirement and added tighter enforcement:

• New accounts: Government-issued ID upload is mandatory before you can publish any app
• Existing accounts: Google can require re-verification at any time; unverified accounts may be suspended
• Organization accounts: D-U-N-S number or equivalent business registration is required for business developer accounts
• Time to verify: 24–48 hours for individuals; up to 5 business days for organizations

The practical impact: plan your account setup before your build is ready. Getting locked on verification when you're eager to ship is avoidable with a one-day head start.

4. Policy 4.3 enforcement is tighter on webview apps

Policy 4.3 (Minimum Functionality) has been Google Play's biggest source of rejections for website-wrapped apps. In 2026, the automated enforcement is sharper:

5. Data Safety form: complete it accurately or face suspension

Google Play's Data Safety section (in the Play Console, under your app's Store listing) requires you to declare:

• What data your app collects (location, contacts, email address, usage data…)
• Whether data is shared with third parties and who
• Whether data is encrypted in transit and at rest
• Whether users can request data deletion

This form must be consistent with your privacy policy. If you use analytics (Google Analytics, Mixpanel, etc.) or push notifications (Firebase), those data flows must be declared. Google cross-checks declarations and has been suspending apps with significant discrepancies since 2024.

For SaasToStore-built apps: your app itself only collects what your website collects. Declare based on your website's privacy policy. If you use SaasToStore push notifications (Firebase-backed), that means declaring device identifiers and notification interaction data.

6. Billing compliance: what's new in 2026

Following the antitrust settlements in multiple jurisdictions, Google updated its billing policies:

• Play Billing mandatory — for digital goods and in-app purchases, Google Play Billing must be offered as a payment option, regardless of region (with some exceptions)
• User Choice Billing — in certain regions, apps may offer an alternative payment method alongside Play Billing
• No restrictions on external links — since 2024, apps may include links to external websites for purchases without risking removal (ending a years-long restriction)

For SaaS products wrapped with SaasToStore: if your web app already handles payments via Stripe or another gateway, you're in a gray zone — technically, digital goods sold via in-app flows require Play Billing. The practical enforcement is mostly against high-revenue consumer apps. For B2B SaaS with web-based checkout, most publishers operate without issue.

7. New listing requirements you may have missed

Several Play Console listing requirements were added or tightened:

What to do before your next submission

Whether you're submitting for the first time or pushing an update, run through this checklist: