Subscription App Terms: Cancellation and Refunds
Last updated: November 17, 2026
Write subscription terms that match App Store, Google Play, and web billing. Separate renewal, cancellation, refunds, and account deletion.
A subscription agreement should answer four separate questions: what is purchased, when billing renews, how to stop renewal, and how to request a refund. Account deletion adds a fifth question. Treating all of them as one cancellation clause creates avoidable support problems.
Start with the billing channels you actually support. Do not copy the same instructions into an iOS store purchase, a Google Play purchase, and a direct website subscription without checking who manages each transaction.
Build a billing-channel worksheet
| Channel | Confirm before drafting | Link or process to test |
|---|---|---|
| Apple In-App Purchase | Product, duration, trial eligibility, renewal price, and entitlement behavior | Apple's subscription-management route and the applicable refund request process |
| Google Play billing | Base plan, offer, renewal behavior, access after cancellation, and any supported exceptions | Google Play's Subscription Center or the appropriate in-app management route |
| Direct website billing | Merchant identity, billing provider, contract duration, cancellation timing, and refunds | Your actual customer portal or cancellation process |
Document whether a paid feature is available across platforms and how the user restores access. A shared app account does not mean the billing relationship moves automatically between channels.
Match the purchase screen and terms
Keep plan names, billing periods, feature limits, trial duration, and renewal prices consistent across checkout, receipts, support copy, and the terms. Do not show an annual plan as if its monthly equivalent were the amount charged today.
Apple's subscription guidance sets out purchase-screen disclosures and requires Terms of Use and privacy-policy links in the app and metadata. Google Play's subscription policy addresses clear offers and accessible management and cancellation. Check both against the products configured in their consoles, rather than relying on terms text alone.
For a trial, explain what happens when it ends and where the user can cancel. Do not invent a universal deadline such as “cancel 24 hours before renewal” for every channel, plan, and jurisdiction. Verify the applicable store instructions and direct-billing contract separately.
Separate cancellation from refunds
Cancellation usually concerns future renewal. A refund concerns money already charged. Explain both without implying that the first necessarily produces the second.
For example, Google Play describes a general model in which cancellation stops future renewal while access continues through the current paid period, but also identifies jurisdiction-dependent exceptions and allows more flexible developer policies. This is why a blanket “no refunds under any circumstances” statement is unsuitable. Read the current management, cancellation, and refund rules and identify the route that applies to your purchase channel.
For direct billing, decide when a cancellation takes effect, whether any unused access remains, and how you handle mistakes or service failures. Have local consumer-rights requirements reviewed before publishing a discretionary refund policy. Avoid presenting a developer preference as if it overrides mandatory rights or a store's decision.
Keep account deletion as its own operation
Do not assume that deleting your app account stops a store-managed subscription. Check the actual billing integration and explain the consequences in the deletion flow. Apple's account-deletion guidance discusses users with auto-renewable subscriptions and the need to help them manage cancellation while still providing account deletion.
Likewise, cancelling a subscription does not necessarily delete the user's stored content. Describe data removal and any justified retention in the privacy policy. Keep those statements consistent with the account controls and support procedure.
Test the difficult account states
Use test accounts and sandbox transactions to verify the behavior before writing definitive promises:
- A trial user cancels before the first payment.
- A paid user cancels renewal but still has time remaining.
- A user requests a refund through the applicable channel.
- A user deletes an account with an active subscription.
- A user restores a purchase on another supported device.
- A payment fails or an entitlement is revoked.
Record what access remains and which message the user sees. Preserve enough operational evidence to help support resolve a complaint, while keeping that evidence subject to your retention rules.
Use the mobile app terms checklist for the rest of the agreement, then draft privacy policy and terms from verified facts. This guide is general product guidance, not legal advice or a substitute for the current rules of your billing channels.
Prepare your plans, billing channels, trial behavior, cancellation routes, and refund process before drafting. Review the subscription provisions for each market you serve.
Draft subscription app terms