What happens if RedChurn goes down?

Your app keeps working normally. Cancel flows, paywalls, and billing through your provider are unaffected. If our servers are unreachable, users simply won't see a retention message. Nothing breaks.

Can RedChurn break my app or billing?

No. RedChurn is read-only on your billing stack. We listen to webhooks from RevenueCat, Superwall, Polar, and other providers, then send retention emails and/or in-app messages at the right moment. We never modify your products, prices, subscriptions, or store configuration.

Which billing providers does RedChurn support?

RevenueCat (email + in-app), Superwall (email), and Polar (email) are live today. Connect via webhooks in a few minutes: paste your RedChurn webhook URL and secret into your provider dashboard. Stripe and more integrations are on the roadmap.

Do I need to change my paywall or pricing?

No. RedChurn sits on top of your existing setup. Keep your products, paywalls, and pricing as they are. We add recovery and retention flows on top of what you already ship.

How long does setup take?

Connect your billing provider in about 5 minutes. Email flows can go live the same day once Resend is connected, no app release required. The in-app SDK is one line and usually ships in your next store release.

Can I use email only, in-app only, or both?

Yes, per flow. Use email-only if you want recovery and win-back without touching the app yet. Use in-app-only for native cancel screens and dunning on the next open. Most teams enable both so email reaches users who do not open the app and in-app catches them inside the product.

What does the SDK weigh?

Less than 200 KB on iOS and Android. We obsess over bundle size because we know mobile teams do too.

How does pricing work?

Starter is free up to 50 active subscribers and includes analytics plus churn recovery on one app. As you grow, pricing scales with your active subscriber count — pick Starter or Growth on the slider. Every plan includes the Red Center, billing recovery, cancel saves, win-back, and in-app retention. Pay yearly and get 2 months free.

Is the beta open right now?

Yes. Sign up today, connect your billing provider, and start recovering MRR. You get the full dashboard, all three flows, and a direct line to the team while we polish for public launch.

Rétention à l’annulation vs win-back

La rétention à l’annulation capte l’intention avant la fin de l’abonnement. Le win-back cible les abonnés déjà partis. Les mélanger gaspille les offres et agace les utilisateurs.

Rétention à l’annulation (intercept)

Exécuté in-app quand l’utilisateur appuie sur annuler dans votre produit. Offres : pause, downgrade, remise — adaptées à la raison de churn via une enquête d’une question.

Relance e-mail sous 48 heures uniquement s’ils passent quand même à l’interface d’annulation store.

Win-back

Déclenché sur EXPIRATION ou après une période de refroidissement post-lapse. Les offres de réactivation doivent expirer automatiquement. L’e-mail rejoint les utilisateurs dormants ; l’in-app capte les retours.

RevenueCat rapporte que plus de 12 % des abonnés mensuels churnés se réabonnent sous 12 mois. Un win-back dans les 30 premiers jours avec une offre claire peut améliorer ces odds.

Comment les combiner

Configurez d’abord l’interception d’annulation — elle protège le MRR au pic d’intention. Ajoutez le win-back pour les abonnés qui ont filé entre les mailles. RedChurn exécute les deux depuis le même webhook RevenueCat avec des tableaux de bord séparés par flux.