Privacy Policy
Last updated 13 November 2026
The short version
KeptMRR reads billing and login data from the accounts you connect, to show you which paying customers may be about to cancel and to draft a check-in email for each. We never move money, change subscriptions, or email your customers ourselves. We don't sell personal data, we don't share it for advertising, and we don't run advertising trackers.
Who this covers, and our role
This policy covers people who visit keptmrr.com and people who create a KeptMRR account (“you”). It also explains how we handle the data about your customers that you connect to KeptMRR.
- Your account and usage: we decide why and how this is used, so for this data we are the controller.
- Your customers' data (the billing and login records you connect): you decide why it is used, and we process it on your behalf, only to provide KeptMRR. You are responsible for having a lawful basis to use your customers' data this way and for what you tell them. For this data we are the processor.
KeptMRR is run from India. Questions about this policy go to support@keptmrr.com.
What we collect
From you:
- Account details. When you sign in with Google we receive your name, email address and profile picture link from Google. We don't see your Google password.
- Workspaces and settings. The businesses you create, their names, your alert thresholds and your email templates.
- Provider keys. The read-only keys or connections you give us for billing and logins (see “Your provider keys” below).
- Messages to us. Anything you send to support.
From the providers you connect (Stripe or Dodo Payments for billing; Supabase or Clerk for logins):
- Billing data about your customers: customer IDs, names and email addresses, plan, amount, currency, subscription status, renewal and cancellation dates, card expiry month and year, and failed payments, refunds and disputes. We never see card numbers.
- Login data about your customers: their email and when they last signed in or were last active. We build a simple history of the days they were active. We don't read message contents or what customers do inside your product.
From your use of KeptMRR:
- Which customers were flagged and why, what you marked as handled, snoozed or saved, and the revenue you kept.
- The emails drafted for you, and a record (recipient, subject, time and method) of emails you sent or copied.
- Your plan, trial dates, billing status, and the customer and subscription IDs from our payment provider.
Automatically:
- Standard server logs from our host, such as IP address, browser type, pages requested and error details, used to run and secure the service.
- The cookies and local storage listed under “Cookies and storage” below.
How we use it
- To provide KeptMRR: sync your billing and logins, work out who is drifting and why, and build your Monday list.
- To draft a short check-in email for each flagged customer. You read and edit it, and nothing goes to your customer until you press Send (or you copy it into your own mail).
- To send you service emails: your Monday digest, plan-limit notices, and security or account messages.
- To bill you for your plan and to apply plan limits.
- To keep the service secure, prevent abuse, fix problems and improve how it works.
- To answer support requests and to meet legal obligations.
We don't use your customers' data for anything other than providing KeptMRR to you. We don't combine it across accounts, and we don't use it to train AI models.
If you are in the EEA or the UK, our legal bases are: performing our contract with you (running your account and the service), our legitimate interests (securing and improving the service), your consent where we ask for it, and legal obligation.
Your provider keys
We ask for the narrowest access each provider allows: a restricted read-only key for Stripe, a read-only key for Dodo Payments, and for Supabase either a one-click connection (OAuth) where we run a single fixed read query, or a read-only database role that you create.
Clerk is the exception. Clerk does not offer read-only keys, so you give us your Clerk secret key. We use it only to read last-active times and never create, change or delete users. Keys are stored encrypted and are never sent back to your browser. You can replace or revoke any key at any time from your provider or from KeptMRR. Our Security page has the details.
Who else handles data
We share data only with the service providers we need to run KeptMRR, and only for that purpose:
- Supabase: our database and sign-in. Holds account data and the data you connect.
- Cloudflare: hosts and runs the service, and sees request data such as IP addresses.
- Google: sign-in. Provides your name, email and profile picture link when you choose to sign in with Google.
- Dodo Payments: bills you for your plan. Receives your name and email and handles your payment details, which we never see. Their privacy policy applies to what they hold.
- Resend: delivers your Monday digest and our notices, and the emails you choose to send from KeptMRR (which means it handles your customer's email address and the message).
- A public exchange-rate service: we fetch currency rates to convert prices to US dollars. No personal data is sent.
We may also disclose information if the law requires it, to protect our rights or the safety of others, or as part of a merger, sale or reorganisation, in which case we will tell you. We do not sell personal data and we do not share it for cross-context advertising.
The providers you connect (Stripe, Dodo Payments, Supabase, Clerk) have their own terms and privacy policies, and your relationship with them is separate from ours.
How long we keep it
- We keep your data while your account is open, so your Monday list, history and signals keep working.
- Deleting a workspace removes its connections and stored keys, customers, login history, billing events, flags, email templates and sent-email records. Deleting your account does that for every workspace and removes your sign-in. Both take effect right away.
- Copies in database backups and server logs are kept for a limited time and then removed on their normal schedule.
- Payment and tax records for your KeptMRR plan are kept by us and by Dodo Payments for as long as the law or accounting rules require, even after your account is deleted.
- If a connection can't be used any more (for example a revoked key), we stop reading from it. Your stored data stays until you delete it.
How we protect it
- Provider keys and tokens are encrypted at rest (AES-256-GCM).
- Each workspace is isolated with row-level security: a signed-in account can read only its own rows.
- Background jobs use a server-side credential that is never sent to a browser, and the job endpoints require a secret.
- Traffic is encrypted in transit (HTTPS).
No system is perfectly secure. If a breach affects your data, we will tell you and the relevant authorities as the law requires.
Where data is processed
We are based in India, and our providers run servers in several countries, so your data may be processed outside the country where you live. Where the law requires it, we rely on safeguards such as standard contractual clauses or our providers' own transfer mechanisms.
Your rights and choices
- Export: in Settings you can download everything we hold for a workspace as a file.
- Delete: in Settings you can delete a workspace, and in Profile you can delete your whole account yourself (stop any paid plan first).
- Revoke: you can revoke any key or connection at any time in your provider.
- Access, correct, restrict or object: depending on where you live (for example under the GDPR, the UK GDPR, India's Digital Personal Data Protection Act or California law), you may have these rights too. Email support@keptmrr.com and we will reply within 30 days. We may need to confirm it is you first.
- Emails: you can't opt out of essential service emails while you have an account, but you can turn off the Monday digest in Settings.
If you are one of a founder's customers and want to see or remove your data, please contact that founder: they decide how it is used. If you write to us, we will pass your request on to them.
If you think we have handled your data unlawfully, you also have the right to complain to your local data protection authority.
Cookies and storage
We use only what is needed to run the service. We don't use advertising or analytics cookies.
- Sign-in session cookies (set by Supabase): keep you signed in.
- Active workspace cookie (
keptmrr_active_workspace): remembers which business you are looking at. - Theme setting (browser local storage): remembers light or dark mode.
Your profile picture is loaded straight from Google's servers, so Google can see that request.
Children
KeptMRR is for people running a business and is not meant for anyone under 18. We don't knowingly collect data from children.
Changes and contact
If this policy changes in a way that matters, we will update the date above and tell account holders by email. Questions or requests: support@keptmrr.com.