Privacy policy
Last updated November 15, 2026
ChurnLeak helps SaaS founders find and recover failed payments in their Stripe or Paddle account. This page explains what data we handle, why, where it lives, how long we keep it and how you control it. It is written to meet the EU and UK GDPR and US state privacy laws such as the CCPA. We keep it short and plain on purpose.
Who is responsible
For your own account data (your login, settings and billing status), ChurnLeak is the controller. For the data we read about your customers from your Stripe or Paddle account, you are the controller and ChurnLeak is your processor: we handle it only to run the audits and recovery emails you ask for, under the data processing terms in our terms of service.
What we collect from you
- Account details: your email address and a hashed password. If you sign in with Google, we receive only your email address and Google's ID for your account, never your name or profile picture.
- Sign-in security: if you set them up, the public keys of your passkeys (your fingerprint or face never leaves your device), the secret your authenticator app uses, and hashed recovery codes.
- Your Stripe or Paddle key: a read-only API key. We encrypt it before storing it and never show it again.
- Recovery settings: your product name, reply-to email, customer portal link and, if you add one, your Stripe or Paddle webhook signing secret (encrypted).
- Slack alerts: if you turn them on, your Slack incoming webhook address (encrypted) and the last few characters of it so you can recognise it.
- Billing: your plan and subscription status from Polar. We never see your card details.
- Website visits: we count visits with Umami, a privacy-focused analytics service that sets no cookies and doesn't identify you. It records the page address (without any query string), the referring site, your browser, device type, country and the funnel steps you reach, such as opening the sign-up page. Separately, our server logs those steps with your IP address shortened.
- Sending domain: if you add your own domain to send recovery emails from (Growth plan), the domain name, the sender address you choose, the DNS records it needs and whether it is verified.
What we read from your Stripe or Paddle account
Stripe: with your read-only key we read subscriptions, invoices, customers, prices and the expiry month and year of saved cards. For a failed payment we also read why the card was declined (the decline code, such as "insufficient funds" or "expired card") and when Stripe will retry it, so we can tell you which payments Stripe may still collect and which need your customer. We never see or store full card numbers, and the key cannot charge, refund or change anything.
Paddle: with a key that has read permissions only, we read customers, subscriptions and transactions. From a transaction we use its status, amount, why a payment failed and the expiry month and year of the card used. We never see or store full card numbers.
- Free audits store totals only: counts and amounts per issue type, with no customer names or emails.
- Paid plans also store, per affected customer: their email, the amount owed, the related invoice or subscription, for a failed payment the decline reason and next retry date, and which reminder emails we sent.
Why we use it (legal bases)
- To provide the service you signed up for: running audits, showing results and sending the recovery emails you turn on (contract).
- To keep the service secure and working, for example logging errors and preventing abuse (legitimate interests).
- To understand how visitors find and use the website, through anonymous visit counts (legitimate interests).
- To keep billing and tax records, through Polar (legal obligation).
We don't use your data or your customers' data for advertising, profiling or training models, and we make no automated decisions with legal effects.
Emails to your customers
When recovery is on, we email your customers in your product's name about failed payments and card problems, with replies going to you. Each email says it was sent on your behalf by ChurnLeak. We send at most four emails per issue, never more than one a day, and never send marketing.
If you connect Slack, we post a short message to the channel you chose when a payment fails or is recovered. It includes the customer's email address and the amount, and goes to your own Slack workspace.
Emails go from a ChurnLeak address unless you add your own sending domain. Then, once you have added its DNS records and we have verified them, they go from the address you chose at that domain. Your domain is used only for your own recovery emails.
Every email has an unsubscribe link, and mail apps show a one-click unsubscribe button. Once someone unsubscribes, or you remove them from Settings, they go on a do-not-contact list and we never email them about that account again. That list stores a one-way hash of the email address, not the address itself.
Where your data is stored
ChurnLeak's app and database run on servers operated by Hetzner Online GmbH in the European Union (Germany and Finland). Some of the providers below are based in, or may process data in, the United States. Where personal data leaves the EEA or the UK, we rely on an adequacy decision (such as the EU-US Data Privacy Framework, where the provider is certified) or the European Commission's Standard Contractual Clauses with the UK addendum.
Who we share data with
- Hetzner (EU), to host the app and database.
- Stripe or Paddle, to read your billing data with the key you give us. It is your own provider; we don't send it any new data.
- Slack, only if you connect it, to post alerts to your own workspace through the webhook you give us.
- Resend (US), to deliver recovery emails. It receives the recipient's email address and the email's content. If you add your own sending domain, we register that domain with Resend so it can sign and send your emails, and remove it again when you remove the domain or delete your account.
- Google, only if you choose "Continue with Google", to confirm your email address when you sign in.
- Polar, our merchant of record, to take payment for ChurnLeak. It receives your email address and plan.
- Umami, to count website visits. It receives the page address, referrer, browser and device details and your IP address, which it uses only to work out your country and doesn't store. It sets no cookies.
We don't sell personal data and we don't share it for cross-context behavioral advertising, as those terms are defined by US state privacy laws. We'll tell account holders by email before adding a new provider that handles customer data.
How long we keep it
- Audits, recovery cases and email logs: for the period you choose in Settings (30 days, 90 days or 1 year; 90 days by default), then deleted automatically. Your most recent audit is kept so your dashboard keeps working.
- Open recovery cases: while the payment problem is still open in Stripe or Paddle. They then close and follow the period above.
- Your Stripe or Paddle key, webhook secret and Slack webhook: until you disconnect them or delete your account. Disconnecting deletes them straight away.
- Your sending domain: until you remove it or delete your account. We remove it from Resend at the same time; if Resend can't be reached, we keep retrying automatically until it is gone. A domain that isn't verified within 7 days is removed the same way. The DNS records stay in your own DNS until you delete them.
- Do-not-contact list: until you delete your account, so unsubscribed customers stay unsubscribed.
- Your account: until you delete it.
- Waitlist sign-ups: until you ask us to remove them or delete your account.
- Server logs and backups: up to 30 days, after which deleted data is gone from them too.
- Billing records: kept by Polar as long as tax law requires.
Controls in your account
Under Settings, then Privacy and data, you can do all of this yourself, at any time, without asking us:
- Choose how long history is kept.
- Add, change or remove your own sending domain (under Sending domain).
- Download everything we store about your account as a JSON file.
- Forget one of your customers: delete their cases and emails, remove them from saved audits and stop all future emails to them.
- Erase all customer data: every audit, recovery case and email log.
- Delete your account and everything linked to it, immediately and permanently, including your sending domain at Resend.
Your rights
EU, EEA and UK: you have the right to access, correct, delete, restrict or object to the use of your data, and to receive it in a portable format. You can also complain to your local data protection authority.
US states (including California): you have the right to know what we collect, to get a copy, to correct it and to delete it, and to opt out of the sale or sharing of personal data (we do neither). We won't treat you differently for using these rights. You may use an authorized agent; we may need to verify the request.
Most of these you can do yourself in Settings. For anything else, email us and we'll answer within 30 days. If you're a customer of a business that uses ChurnLeak, use the unsubscribe link in our email or contact that business; we'll help them with your request.
Security
All traffic is encrypted in transit. Stripe and Paddle keys, webhook secrets and Slack webhooks are encrypted at rest, passwords are hashed, and access to production systems is limited to the people who run ChurnLeak. If a breach affects your data, we'll tell you without undue delay.
Cookies
We use one essential cookie to keep you logged in. No tracking or advertising cookies, and our visit counts (Umami) use none either, so there's no cookie banner.
Children
ChurnLeak is a business tool and isn't meant for anyone under 16.
Changes
If we change this policy in a way that matters, we'll email account holders before it takes effect.
Questions? Email [email protected].