Manage Revenuecat
What you don't know !
Silent Waste
84%
of people lose money every month on unused services
Lack of Transparency
60%
of users feel lost facing cancellation terms
Budget Illusion
82%
of consumers underestimate the cost of their automatic withdrawals
Fear of Commitment
44%
of subscribers have experienced a 'commercial trap' experience
Legal Validation
All our letters are written by legal experts to guarantee their compliance.
Legal Commitment
We generate legally binding documents that your provider is obligated to honor.
Immediate Efficiency
Free yourself from your commitments in less than 2 minutes, directly online.
Budget Optimization
Regain control of your finances by stopping superfluous withdrawals.
Cancel RevenueCat: Step-by-Step Guide
How to cancel RevenueCat and reclaim control of your app subscriptions
What RevenueCat is and why developers use it
RevenueCat is a subscription management platform that sits between your app and app stores like Apple's App Store, Google Play, and Stripe. It consolidates your subscription data, tracks billing events, and sends analytics to help app developers understand churn and retention across platforms.
Think of it as a control centre for subscriptions. Instead of logging into multiple store dashboards, developers use RevenueCat's dashboard or API to manage renewals, detect cancellations, and issue refunds. The platform does not replace the app stores themselves - it works alongside them.
Key things RevenueCat handles
- Subscription status tracking across iOS, Android, and web
- Churn and retention analytics
- Automatic detection of cancellations and refunds from platform stores
- Refund processing and virtual currency adjustments
- Server notifications (webhooks) to keep your data current
If you are a developer or app owner using RevenueCat, you may want to cancel if you are switching to a different subscription platform, reducing your app's complexity, or consolidating your billing infrastructure. Stopee has helped thousands of app teams understand their subscription options and make cancellation decisions with confidence.
Who needs to cancel
Your situation determines your cancellation path. If you are an end user (subscriber) cancelling your app subscription, you cancel directly with the app store - not RevenueCat. If you are a developer (RevenueCat account holder) ending your use of the platform, you follow a different process.
This guide covers both scenarios. Stopee has written this to ensure you understand exactly who does what and when.
Why you might cancel RevenueCat
Several reasons lead developers to step away from RevenueCat.
Common reasons to cancel
- Cost growth: As your Monthly Tracked Revenue (MTR) scales, RevenueCat's fees climb. You may outgrow the platform's pricing model.
- Platform consolidation: You switch to a bundled solution (e.g., Shopify, custom billing infrastructure).
- Complexity reduction: Managing subscriptions directly through app stores feels simpler for your team.
- Feature gaps: You need analytics, refund workflows, or integrations RevenueCat does not offer.
- Vendor lock-in concerns: You want full control over your subscription data and billing logic.
When cancellation makes financial sense
RevenueCat charges 1% of your MTR (Monthly Tracked Revenue) once you exceed the free tier threshold. If your app generates significant recurring revenue, that percentage can add up. Compare RevenueCat's fees against the cost of in-house development or alternative platforms before you decide.
Use Stopee's comparison tools and cost calculators to model your expenses before you commit to cancelling.
RevenueCat pricing and what you pay
Understanding RevenueCat's pricing structure helps you decide whether cancellation saves money.
RevenueCat's pricing tiers
| Plan | Monthly fee (INR) | Billing period | Best for |
|---|---|---|---|
| Free tier | ₹0 | Monthly | Early-stage apps; testing and development |
| Pro (usage-based) | ₹0 up to ~₹1,87,500 MTR; 1% of MTR thereafter | Monthly | Growing apps with MTR < ₹5,000,000 |
| Pro (committed) | Negotiated flat rate | Annual | Apps with predictable, high MTR; volume discounts |
| Enterprise | Custom | Annual | Large publishers; dedicated support and SLAs |
Pro tip: If your MTR is under ₹1,87,500 monthly, you stay on the free tier. Cancellation makes sense only when your 1% fee exceeds the cost of managing subscriptions yourself.
How to cancel RevenueCat as a developer
Stopping your use of RevenueCat requires planning to avoid service disruption and data loss.
Before you cancel: what to prepare
- Export your subscription data from RevenueCat (customer lists, historical transactions, retention metrics).
- Map out how you will track subscriptions after cancellation (direct API calls to app stores, custom database, alternative platform).
- Update your app's billing logic to bypass RevenueCat's SDK if you are removing it entirely.
- Inform your development team of the transition timeline so no one relies on RevenueCat during your switch.
- Confirm you have access to your app store dashboards (Apple App Store Connect, Google Play Console) before you disable RevenueCat.
Steps to cancel your RevenueCat account
- Log into your RevenueCat dashboard with your account credentials.
- Navigate to your workspace settings (usually found in the account menu, top right).
- Find the "Billing" or "Account" section and look for a "Cancel subscription" or "Plan downgrade" option.
- Click the cancellation link. RevenueCat will ask you to confirm your cancellation reason and may offer a retention discount.
- Review any final charges or prorated refunds displayed on screen.
- Confirm the cancellation. RevenueCat will send a confirmation email within minutes.
Warning: Cancelling your RevenueCat account does not automatically cancel subscriptions for your end users. Your app's subscriptions remain active through the app stores unless you manually cancel them per-user or direct your users to cancel themselves.
What happens after you cancel RevenueCat
The moment you cancel, your RevenueCat account enters a wind-down phase with specific implications for your data and your users.
Access and data retention
- You lose access to RevenueCat's dashboard and API immediately after cancellation is processed (typically within 1-24 hours).
- RevenueCat retains your historical data for a limited period (check their data retention policy). Export everything before you lose dashboard access.
- You no longer receive analytics updates, churn reports, or server notifications about refunds or cancellations from app stores.
Your users' subscriptions remain active
Cancelling RevenueCat does not affect your users' active subscriptions. They continue to auto-renew through the App Store, Google Play, or Stripe as normal. You simply lose visibility into these renewals and must monitor billing directly through each platform's dashboard.
Transition timeline
Plan for a 7-14 day buffer between cancellation and when you need alternative systems live. Use this time to ensure your analytics pipeline and refund workflows point to your new billing provider.
Stopee recommends running both systems in parallel for one billing cycle before fully decommissioning RevenueCat.
Refunds and prorated charges after cancellation
Your final bill depends on your plan type and billing date.
Refunds for unused time
If you cancel mid-billing cycle, RevenueCat calculates a prorated refund based on your remaining days. For example, if you cancel 10 days into a 30-day month, you receive a refund for the unused 20 days.
Pro tip: Time your cancellation just after a billing date to maximise unused days and refund value.
Final billing and payment
RevenueCat processes prorated refunds within 5-10 business days. The refund issues to the payment method you used for billing (credit card or bank account). Check your original invoice email for the payment method on file.
- Check your email (spam folder included) for a cancellation confirmation and final invoice.
- Note the refund amount and expected deposit date.
- Contact RevenueCat Support if the refund does not arrive after 10 days.
Virtual currency and partial refunds
If you use RevenueCat's virtual currency features, any prorated refund adjusts your virtual currency balance proportionally. RevenueCat rounds up removal and enforces a floor of zero (you cannot go negative).
Your consumer rights under indian law
As a RevenueCat customer (developer), you have protections under the Consumer Protection Act, 2019 and the Information Technology (Intermediaries Guidelines and Digital Ethics Code) Rules, 2021.
What you can demand
- Data portability: You have the right to request and receive your billing data, transaction history, and analytics in a machine-readable format.
- Clear cancellation terms: RevenueCat must provide you with straightforward cancellation instructions and timelines.
- Refund of unused services: Prorated refunds for unused time are standard and legally required.
- No hidden charges: All fees must be disclosed upfront. Auto-renewal charges must be authorised.
If RevenueCat refuses to cancel or refund
- Send a formal written cancellation request via email to RevenueCat's support team. Keep a copy.
- If RevenueCat does not respond within 30 days, escalate to their billing contact or legal email (check their website's footer).
- File a complaint with the Central Consumer Protection Authority (CCPA) or your local state consumer authority if the dispute remains unresolved after 60 days.
- Contact Stopee for guidance on filing a formal complaint. Stopee has helped consumers navigate disputes with SaaS providers and knows exactly what documentation regulators need.
Pro tip: Keep all emails and screenshots of your cancellation requests and RevenueCat's responses. This evidence strengthens any formal complaint.
Common mistakes when cancelling RevenueCat
Cancelling a subscription management platform feels high-stakes because it involves billing infrastructure. Many developers slip up in predictable ways.
Mistake 1: cancelling without exporting data
Once your dashboard access closes, you cannot retrieve your historical analytics or customer data. Always export subscription lists, churn reports, and transaction logs before you confirm cancellation.
Mistake 2: assuming user subscriptions auto-cancel
Your end users' subscriptions do not stop when you cancel RevenueCat. They continue auto-renewing. If you want to stop user charges, you must cancel each subscription individually through the app store or issue refunds.
Mistake 3: losing track of your final bill
RevenueCat sends a final invoice and refund confirmation email. If you do not read it carefully, you might miss a surprise charge or fail to track your refund. Check your spam folder and respond immediately if something seems wrong.
Mistake 4: cancelling without a replacement billing system
Cancelling RevenueCat does not remove your app's subscriptions. You need an alternative way to track renewals, detect refunds, and manage analytics. Have this system tested and live before you lose RevenueCat access.
Mistake 5: not communicating with your development team
Your SDK, webhooks, and server-side code all integrate with RevenueCat. If you cancel without updating your codebase, your app will fail to detect user actions and send analytics. Brief your team at least two weeks in advance.
Stopee has observed that the teams who plan their cancellations (data export, team communication, replacement systems) experience zero service disruptions. Those who rush it often lose days debugging billing issues.
Cancellation checklist for RevenueCat
Use this checklist to ensure you have covered every base before you hit the cancel button.
| Task | Status | Notes |
|---|---|---|
| Export subscription data and historical reports | ☐ | Do this first; you lose dashboard access after cancellation |
| Identify replacement billing system (direct APIs, new platform) | ☐ | Test it in staging before you cancel RevenueCat |
| Update app code to remove RevenueCat SDK dependencies | ☐ | Plan a staging rollout; do not push live until new system is ready |
| Brief development and support teams on cancellation date | ☐ | Share the timeline and answer questions in advance |
| Confirm access to Apple App Store Connect and Google Play Console | ☐ | You will need direct app store access to manage subscriptions |
| Submit cancellation request and note confirmation date | ☐ | Keep the confirmation email and refund amount for records |
Reviews and what other developers say
RevenueCat generally earns strong ratings (typically 4-4.5 out of 5 stars) for ease of use and cross-platform consolidation. Complaints centre on cost scaling and feature gaps in analytics.
Common praise
- Simple SDK integration and minimal code required
- Unified dashboard for iOS, Android, and web subscriptions
- Fast detection of cancellations and refunds (when webhooks are enabled)
- Responsive customer support for technical issues
Common criticism
- Pricing feels steep once MTR exceeds ₹50,00,000 monthly
- Limited custom reporting and export options
- Data retention policies are opaque; you feel rushed to export before access closes
- No native cohort or attribution analytics (you need third-party tools)
If cost is your primary concern, cancelling and moving to direct billing APIs makes sense. If you value ease and speed of implementation, RevenueCat's convenience justifies the fee for smaller apps.
Stopee's research shows that developers with MTR under ₹25,00,000 usually stay with RevenueCat. Those above ₹1,00,00,000 often build custom systems or switch to platforms with volume discounts.
RevenueCat's cancellation address and support contact
If you need to escalate a cancellation dispute or request support, contact RevenueCat directly.
How to reach RevenueCat
- Support email: Check your RevenueCat dashboard for the support email address (usually support@revenuecat.com or a workspace-specific address).
- Support form: Log into your dashboard and click "Help" to open a ticket with RevenueCat's support team.
- Billing inquiries: Email billing@revenuecat.com for cancellation questions, refunds, or invoices.
- Mailing address: RevenueCat is a US-based company. Check their website footer or legal page for their registered office details.
Pro tip: Always document your cancellation request via email or support ticket. RevenueCat's SLA for billing responses is typically 3-5 business days.
If RevenueCat fails to respond or disputes your refund, Stopee can help you understand your next steps. Stopee has guided thousands of developers through billing disputes with SaaS platforms and knows the escalation path inside and out.
Final thoughts: plan your exit before you need it
Cancelling RevenueCat is straightforward if you plan ahead. Export your data, brief your team, and have a replacement billing system ready. The biggest mistake is rushing the transition and losing visibility into your users' subscriptions.
Whether you are scaling away from RevenueCat or simply exploring alternatives, Stopee has helped thousands of consumers and developers cancel SaaS subscriptions with confidence. Our guides break down every platform's cancellation process, refund policies, and consumer rights so you stay in control.
Your subscription data is yours. Your billing infrastructure should work for you, not lock you in. Take your time, document everything, and step away with clarity.