Guide · 7 min read
App Subscription Cancellation Rules 2026: What Apple, Google, and the FTC Now Require
The rules around app subscription cancellations tightened in 2026 on three parallel tracks: Apple now requires explicit auto-renewal disclosure and an in-app cancellation path, Google Play enforces a 2-tap maximum with dark-pattern prohibitions, and roughly 30 US states have auto-renewal laws that remain in force regardless of federal rulemaking. Whether you sell on iOS, Android, or both, your cancellation flow is now a compliance surface — not just a conversion variable.
The FTC click-to-cancel rule: vacated, but ROSCA enforcement is still active
The FTC's click-to-cancel rule was vacated by a federal appeals court in 2025 — but the underlying federal law it was built on, ROSCA, and active FTC enforcement both remain fully in force. The FTC finalized its Negative Option Rule amendment in October 2024, requiring subscriptions to be cancellable as easily as they were started. An appeals court vacated it on procedural grounds before enforcement began, and in March 2026 the FTC launched an Advance Notice of Proposed Rulemaking to revive it with a corrected economic-impact analysis.
The practical consequence for app developers: the Restore Online Shoppers' Confidence Act (ROSCA) — the federal statute the rule derived from — was never affected by the court ruling. ROSCA requires online subscription sellers to obtain affirmative consent before charging and to clearly disclose cancellation terms. FTC enforcement under ROSCA has continued through 2025 and 2026, producing major settlements against subscription services with obstructed cancellation flows. The formal rule is on pause; the enforcement wave is not.
Any app already meeting Apple's and Google's platform requirements is effectively ROSCA-compliant by construction — both platforms independently mandate clearer disclosure and easier cancellation than ROSCA strictly requires. Compliance with both platform policies does the federal work as a byproduct, not as an added burden.
Apple App Store subscription requirements in 2026: disclosure at the button, not in the footer
Apple requires auto-renewal disclosure adjacent to the purchase CTA and a visible in-app cancellation path — both updated requirements in the 2026 App Review Guidelines. The disclosure must appear before purchase: price, billing period, and an explicit 'automatically renews until cancelled' statement placed immediately adjacent to or inside the subscription buy button. Terms buried in a scrollable modal below the paywall are not compliant.
Apple's in-app cancellation requirement is specific about discoverability: a Settings, Account, or Subscription Management section within the app must provide a path to cancel or manage the subscription. Routing the user to the OS-level Settings → [App Name] subscription screen is acceptable as the final destination — but a modal that only says 'to cancel, go to the App Store' is not. The path to cancellation must be findable within the app without requiring the user to exit it entirely.
Apple added a new subscription model in 2026: monthly billing with a 12-month commitment, where users pay monthly but commit to a year before the subscription reverts to standard auto-renewal. This model carries the same disclosure requirements as standard auto-renewable subscriptions — the commitment structure and total obligation must be explicit at purchase. For the broader intersection of paywall design and disclosure placement, the contextual paywall design guide covers where conversion motivation and compliance requirements reinforce each other.
Google Play 2-tap cancellation rule: exactly what compliance looks like
Google Play requires that users can cancel any subscription in at most 2 taps from your app's main subscription management screen — and the entire flow must stay inside the app. Google Play policy enforced in 2026 explicitly prohibits sending users to the Play Store, your website, or any external flow to complete the cancellation. In-app means in-app.
The 2-tap rule: Tap 1 reaches the subscription management screen (from Settings, Account, or a dedicated menu item). Tap 2 initiates cancellation or reaches a final confirmation. Any additional screen — a retention prompt that implies negative consequences, an informational step that adds a layer before the cancel button appears — counts against the 2-tap limit. Google's policy distinguishes providing information at the confirmation step (acceptable) from adding a procedural screen between the user's decision and the cancel button (not acceptable).
At Google I/O 2026, Google announced an update to the Subscription Management API that lets developers surface cheaper plan alternatives, pause options, or limited-time discounts inside the Google Play cancellation flow. An offer screen before the final cancel button is explicitly permitted — as long as the cancel button remains accessible in one more tap from the offer. This is the compliant retention mechanism: an opt-in at the moment of cancel intent, not a friction layer hiding the exit. For how this fits into your broader Android monetization model, see the comparison of in-app purchase vs subscription vs one-time pricing.
30+ state auto-renewal laws: the compliance floor that predates the FTC
Roughly 30 US states have their own auto-renewal laws, and the strictest — California, New York, and Virginia — require affirmative consent, clear disclosure, and online cancellation that go beyond what many apps currently provide. These laws were in force before the FTC rule was finalized and remain in force regardless of its vacatur.
California's Automatic Renewal Law applies to any subscription sold to a California resident, regardless of where the developer is incorporated or based. It requires clear disclosure of auto-renewal terms at the point of sale, affirmative consent before charging, and the ability to cancel online without calling or emailing support. The law carries a private right of action, meaning non-compliant subscriptions can face class-action suits rather than just regulatory penalties — a real risk for any consumer app with a US audience.
The practical compliance floor that satisfies ROSCA, Apple's guidelines, Google's policy, and most state laws simultaneously: (1) auto-renewal terms disclosed at the purchase screen, adjacent to the CTA; (2) cancellation accessible from within the app; (3) affirmative consent captured before charging. Any paywall meeting all three passes most current regulatory requirements without a jurisdiction-by-jurisdiction audit. See the subscription pricing display principles for how to make required disclosures readable without cluttering the conversion moment.
Dark patterns both platforms prohibit — and that invite class actions
Apple's 2026 App Review Guidelines and Google Play's 2026 policy both explicitly prohibit the same four subscription dark patterns: roach motels, cancellation shame screens, misdirected cancel paths, and out-of-app cancellation requirements. Every pattern on this list is also the basis of active FTC enforcement actions and state-law suits.
Roach motel: Subscribe in 2 clicks; cancel in 10 steps across 4 screens. This pattern violates Apple's HIG, Google Play policy, and ROSCA simultaneously — it's the most-regulated pattern in subscription commerce. Cancellation shame: Screens that list what the user 'will lose' in punishment framing — 'Your 247 saved workouts will be deleted. Your streak will reset.' Information about what changes is acceptable; language designed to produce anxiety rather than inform a decision is not. Misdirected cancel path: Hiding the cancel option in a non-standard location while placing 'Stay subscribed' as the prominent primary CTA — asymmetric discoverability by design. External cancellation requirement: Telling users to email support or call a phone number to cancel a subscription purchased digitally. Both platforms have explicitly prohibited this.
The common thread across all four patterns: they add friction to an action the user has already decided to take. Both platforms' 2026 policies treat deliberate friction as evidence of deceptive intent. Apps still running these patterns carry genuine compliance risk — not just a conversion optimization problem.
Easier cancellation increases trial conversion — the counter-intuitive revenue effect
Apps with frictionless cancellation language consistently convert more free trials to paid subscribers than apps with obstructed cancellation flows — because the primary blocker for starting a trial is fear of being trapped, not the risk of cancelling. A clearly disclosed 'cancel anytime in 2 taps' promise lowers the perceived risk of entering, and more trial starts means more paid conversions even if the cancellation rate on trials rises slightly.
The pattern observable in top-grossing subscription apps: transparent cancellation terms at the paywall — 'Try free for 7 days. Cancel anytime.' — outperform paywalls that emphasize value while obscuring the exit. Total subscription revenue is a product of trial volume, trial-to-paid rate, and retention. Friction that reduces trial volume is not offset by a marginally lower cancel rate — the math reliably favors lower friction at entry. The right retention move at cancel intent is a legitimate offer: a pause option, a cheaper tier, or a temporary discount. A user who pauses is worth more than a user who churns resentful.
If you're rebuilding your paywall for compliance, use the paywall conversion principles to keep required disclosure from reducing the conversion signal. Once the paywall and cancellation screens are updated, you'll likely need updated App Store screenshot dimensions for the new paywall assets — the AppsTemple screenshot editor covers every required size for iOS and Android.
5 compliance fixes most subscription apps can ship without a full paywall rebuild
Five targeted changes bring most apps into compliance with Apple, Google, and applicable US law. Fix 1 — Disclosure at the CTA: Add price, billing period, and 'renews automatically until cancelled' language immediately adjacent to the purchase button. Not in a footer. Not in a modal the user has to open. Fix 2 — In-app cancellation path: Add a Manage Subscription or Cancel Subscription item to your Settings, Account, or Profile screen that leads to the cancellation flow without requiring the user to exit the app.
Fix 3 — Remove punishment language from cancel confirmations: Review every screen in the cancellation flow for loss framing. Replace 'Your streak will be deleted' with 'Your streak is saved — it resumes when you return.' Information, not anxiety. Fix 4 — Test the 2-tap rule on Android: From your app's main menu, count taps to a final cancellation confirmation. Three or more taps is non-compliant with Google Play policy. Fix 5 — Add a pause or downgrade offer at the cancel screen: A Google Play Subscription Management API offer or an in-app pause button is the compliant retention mechanism — effective, permitted by both platforms, and positioned as a genuine alternative rather than a friction layer.
These five fixes address every prohibit on Apple's and Google's current policy lists and collectively satisfy the ROSCA affirmative-consent and easy-cancellation requirements. The compliance changes are also product improvements: a subscription experience that discloses clearly, cancels easily, and offers a legitimate alternative at cancel intent earns more trust and converts more trials than one that obscures exits.
Audit your paywall before a regulator does it for you
The compliance pass is straightforward: check disclosure placement at the purchase CTA, test the cancellation path on a fresh device install, audit every confirmation screen for punishment language, and count taps to cancel on Android.
If the compliance updates also require new paywall screenshots or updated listing assets — which they usually do — the AppsTemple editor covers every required device size so you can preview at real App Store dimensions before exporting.
Preview your paywall screenshots in the editor →
Frequently asked questions
click to cancel app subscription — is it required by law in 2026?
The FTC's formal click-to-cancel rule was vacated by a federal court in 2025 and is being revised — so there is no active federal mandate as of August 2026. However, the underlying law (ROSCA) still requires affirmative consent and clear disclosure for online subscriptions. Apple mandates an in-app cancellation path, Google Play enforces a 2-tap maximum, and roughly 30 US states have independent auto-renewal laws requiring easy cancellation. For any US-facing subscription app, in-app cancellation and pre-purchase auto-renewal disclosure are required regardless of the federal rule's status.
what are apple app store subscription disclosure requirements in 2026?
Apple requires auto-renewal terms — price, billing period, and 'renews until cancelled' — disclosed adjacent to the purchase CTA before the user taps buy. Disclosure buried in a modal or below the fold is not compliant. An in-app cancellation path visible from the app's Settings or Account screen is also required; the path can route to the OS subscription settings page, but the route must be discoverable from within the app.
what is the google play 2-tap cancellation rule?
Google Play policy requires that users can cancel any subscription in no more than 2 taps from your app's main subscription management screen, with the entire flow staying inside the app. Tap 1 reaches the subscription screen; Tap 2 initiates cancellation or a confirmation. Extra steps — additional retention prompts, informational interstitials that add a screen before the cancel button appears — make the flow non-compliant. The exception: a Google Play Subscription Management API offer screen (discount, pause, or downgrade) is permitted, but the cancel button must be reachable in one additional tap from it.
does making subscription cancellation easier hurt app revenue?
No — and the conversion direction is counter-intuitive. Apps with frictionless cancellation ('cancel anytime in 2 taps') consistently convert more free trials to paid subscribers because fear of being trapped is a larger barrier to starting a trial than the risk of cancelling. Total subscription revenue depends on trial volume × trial-to-paid rate × retention. Friction that reduces trial volume is not offset by a marginally lower cancel rate. The compliant retention strategy is to offer a pause, a cheaper tier, or a discount at the cancel screen — not procedural obstruction.
do state auto-renewal laws apply to my app if i'm not based in california?
Yes. California's Automatic Renewal Law applies to any subscription sold to a California resident, regardless of where the developer is incorporated or operating. The same principle applies to similar laws in New York, Virginia, and roughly 28 other states. For any consumer-facing app with a US audience, state-level requirements apply based on where users are located, not where you are. The practical compliance path — pre-purchase disclosure, in-app cancellation, affirmative consent — satisfies most state laws simultaneously.