If your app is removed from Google Play or the App Store, the refunds can still come out of your payouts

Two sentences in Google's Play Console help settle what happens to subscribers when an app is removed from Google Play: their future subscriptions are canceled, and past subscriptions will not be refunded. That second sentence sounds like good news for the developer. It isn't the whole picture. The Google Play Developer Distribution Agreement and Apple's Developer Program License Agreement both keep you responsible for refunds after your app is gone, and both let the store hold your money while it works out what you owe. Renewal revenue stops on day one. The liabilities don't. Here's what each agreement actually says, how removal, suspension and termination differ, and what a takedown can cost.

What happens to subscriptions when your app is removed

The two stores publish very different amounts of detail here. Google documents the subscriber outcome in its help center. Apple's agreement is about money and rights, and it doesn't describe what happens to auto-renewals when Apple pulls an app.

Do subscribers keep using the app after it's removed?

On Android, yes, for a while. Google's user help says an installed app keeps working, but it can't be updated, and Google Play's billing system will not work while the app isn't available. Section 8.1 of the agreement says removal doesn't change your obligation to deliver or support products users already bought. So your servers keep running for people who are no longer paying you.

Will my subscribers be charged again?

On Google Play, not after removal. The Play Console help is direct about it, and Google's user page adds that a subscription may be canceled depending on the renewal date and whether the app is reinstated. Apple doesn't publish an equivalent rule for an app it removes. If your iOS app is pulled, don't assume either outcome. Watch your App Store Server Notifications for what actually happens to each subscription.

The refund clauses that survive removal

None of this is new language. It sits in the agreements you accepted when you opened your developer account, and most developers never read it until a takedown email arrives.

Google Play: refunds, Legal Takedowns and withheld payments

Section 3.8 authorizes Google to refund users under the Google Play refund policies and to deduct those refunds from your payments. Section 8.1 says that if you remove a product yourself, you still comply with the agreement, including refund requirements, for anything distributed before removal.

Section 8.2 is the expensive one. A Legal Takedown is a removal you make with written notice to Google because of alleged infringement, a violation of third-party rights, or a finding that the product doesn't comply with the law. After one, if a user bought the product within a year before the takedown, or longer where local consumer law says so, you agree to refund everything that user paid, at Google's request.

Section 8.3 covers removals Google makes. If Google decides a product violates the law, the agreement or its policies, or creates potential liability for Google, it may reject, remove or suspend it, and it may withhold payments due to you.

Apple: Schedule 2 refunds and the termination holdback

Apple's Schedule 2 is the paid apps agreement most developers know as the Paid Applications Agreement. Section 6.3 lets Apple refund the full price paid when a user wants to cancel within 90 days of download, or by the end of an auto-renewing subscription period shorter than 90 days, or when the app fails to conform to your specifications, your product warranty or applicable law. When Apple refunds, you reimburse it, or grant it a credit, in an amount equal to the price. The same applies when a payment provider tells Apple a user got their money back.

Section 3.8(c) adds a subscription rule: you must fulfill the offer for the entire subscription period, as marketed. If you don't, you authorize Apple to refund the user, fully or partly at Apple's discretion, and you reimburse that amount.

Section 7.1 is the termination clause. After the agreement ends, Apple remains entitled to its commissions on copies downloaded before termination, and to reimbursement of refunds it paid to users before or after termination. It may withhold all payments due to you for a period it determines is reasonable to calculate and offset those refunds. If Apple suspects fraud or dishonest conduct, it can withhold payments at any time.

What an app removed from Google Play or the App Store costs you

The real bill is the overlap. Revenue stops at once, while costs and refund liability keep running.

Costs that keep running without revenue

Under section 8.1, Google expects you to keep delivering and supporting products users already bought. That means your compute, database storage, third-party API calls and push infrastructure stay on for existing users. Every one of those is a monthly invoice, and none of it is offset by renewals, because the renewals were canceled.

A worked takedown example

Say you sold a $29.99 lifetime unlock on Google Play to 1,000 buyers in the past year, then made a Legal Takedown after an infringement claim. If Google asks you to refund those buyers under section 8.2, that's $29,990 owed to users. Google's own fee on those sales doesn't change what the clause says you refund: all amounts paid. If your Play payouts are also being withheld, the refunds come out of money you may not be able to reach.

Chargebacks from confused customers

A buyer who sees an app vanish often goes to their bank instead of the store. Chargebacks are bank-final, and you only get to argue in one place: Google Play's chargeback review, which gives you 24 hours to respond through orders.reviewrefund. For Google Play orders placed after August 3, 2026, a lost chargeback costs you the purchase price, less Play's service fee, plus the bank's chargeback fee. Section 10.3 says a terminated account no longer has Play Console access, so that review is one more thing to set up before trouble, not after.

On iOS, the only refund flow that asks for your input is Apple's CONSUMPTION_REQUEST, with a 12-hour window to answer through Send Consumption Information. It still depends on your server being up and your purchase records being intact.

How to protect yourself before a takedown

Most of this exposure can be reduced in advance, and none of it can be fixed once the account is gone.

Keep purchase records outside the store

• Store transaction IDs, order IDs, purchase dates, prices and refund events in your own database, not only in the store console.
• Keep usage counts per purchase, so a CONSUMPTION_REQUEST or chargeback review can be answered from your data.
• Export your earnings and refund reports on a schedule, because a terminated Google account loses console access.

Hold a reserve against refunds

Apple can withhold payouts for a period it decides is reasonable, and Google can withhold them after a removal. A cash reserve that covers a year of refundable sales on your largest products is the only thing that keeps a takedown from turning into a cash crisis.

Fix policy warnings before they become removals

Google's Play Console help says warnings don't affect your account's standing, but the app is removed after the number of days in the warning email. Removals don't immediately hurt your standing either, while suspensions count as strikes. Apple's guidelines say apps that stop working or offer a degraded experience may be removed at any time. Treat each warning as a deadline with a refund bill attached.

RefundHalt tracks every refund, chargeback and evidence request against your own purchase records, so the data you'd need after a removal already exists outside the store.