Skip to content
← Back to RecoverMRR

Privacy Policy

Effective: 22 October 2026

1. Operator, scope and contact

RecoverMRR is a business-to-business (B2B) software service for subscription businesses that use Stripe, offered to business customers worldwide. This notice covers www.getrecovermrr.com, account registration, the RecoverMRR subscription, earlier waitlist requests and the integrations below.

Contact for privacy and account questions: billing@getrecovermrr.com. The founder is based in Italy.

Controller: RecoverMRR is operated by Mayboroda Anatoliy, a private individual (persona fisica) resident in Italy, not registered as a company and without an Italian VAT number (partita IVA). Address: Via Sanfrancesco 2, 84016 Pagani (SA), Italia.

2. Account information

Registration and login submit an email address and password to Supabase Auth. Passwords are handled by the authentication service and are not stored in RecoverMRR's own tables. A waitlist request submitted before launch stored your email address, submission source and creation time.

3. Free trial and RecoverMRR subscription data

A 30-day free trial starts when you confirm your email address. No payment card is required to start the trial. For the trial and the paid plan, RecoverMRR stores in Supabase: your account identifier, trial start and end times, the Stripe customer identifier, the Stripe subscription identifier, plan code, price ($24), currency (USD), billing interval (monthly), subscription status, current and paid period dates, the identifier of the paid invoice, payment verification time, cancel-at-period-end flag and cancellation date, Stripe Checkout session and request identifiers, Stripe event identifiers, types, times and a hash of each event payload (not the full payload), and trial-reminder delivery records.

The paid subscription is purchased through Stripe Checkout. Your card is entered on the Stripe-hosted Checkout page; RecoverMRR does not receive or store full card details. Subscriptions are managed and cancelled through the Stripe Customer Portal.

4. Stripe data access (Stripe Connect)

If you connect your Stripe account, RecoverMRR uses Stripe Connect OAuth (Standard accounts). Stripe grants this connection with read/write scope; RecoverMRR uses it only to read data and does not create charges, refunds or payouts, change invoices, customers or subscriptions, or move funds.

Connection records. RecoverMRR records the connected account identifier, connection status, mode (test or live), consent version and timestamps. Security records include hashed OAuth state and attempt information. In test mode, the OAuth access token is stored encrypted (AES-256-GCM) and used server-side only. In live mode, RecoverMRR does not store an access token for your account: it reads your data with its own restricted platform key on behalf of your connected account, and stores only an encrypted reference to the connection. Test and live use separate encryption keys.

What is read from Stripe. Only read requests are made: your account identifier and type (to verify the connection); the invoice.payment_failed and invoice.paid events of your account; the affected invoices; their invoice payments and the decline code of the related payment attempt; and the name of the product on the invoice.

What is stored. For failed and paid invoices of your customers, RecoverMRR stores selected fields: event, account, invoice, customer and subscription identifiers; event type and times; Stripe API version and request identifier; currency; amounts due, paid and remaining; invoice status; the failure classification derived from the decline code; and processing metadata. It does not store full webhook payloads or card details.

Recovery emails. To prepare a recovery email, the customer's email address and name, your Stripe account name, the plan (product) name and the Stripe-hosted invoice link are read from Stripe. The email draft (subject and text, which may include the customer's first name, your account name and the plan name) is stored for your review. An email is sent only after you approve it. For a sent email, RecoverMRR stores the delivery record: recipient and sender address, subject, text, payment link, the Resend message identifier and delivery status updates (stored as status, time and a hash of each provider event, not the full event). Delivery is handled by Resend, and the optional AI drafting by DeepSeek receives only the limited data described in section 6.

Purpose. Stripe data is read and used only to detect failed payments, classify the failure, prepare and send payment-recovery emails you approve, and detect when a payment is recovered.

Disconnecting. You can disconnect at any time from your Stripe Dashboard (see Stripe's guide Disconnect your Stripe account from a connected third-party platform) or by emailing billing@getrecovermrr.com. After that, RecoverMRR can no longer read data from your Stripe account and prepares or sends no further recovery emails for it. Data from a disconnected Stripe account (connection records, invoice and event records, recovery email drafts and delivery records) is deleted within 30 days of disconnection, or sooner on request to billing@getrecovermrr.com. If you reconnect the same Stripe account within those 30 days, the scheduled deletion is cancelled and your data is kept.

The RecoverMRR Dashboard does not have a "Disconnect Stripe" button yet. To disconnect, remove RecoverMRR in your Stripe Dashboard settings (Connected apps / authorized applications) or email billing@getrecovermrr.com.

Stripe processes your Stripe account data under its own terms and the Stripe Privacy Policy, which apply in addition to this notice.

5. Purposes and roles

We use information to provide accounts, run the free trial and paid subscription, process Stripe payment events, prepare and send payment-recovery emails, send trial reminders, prevent duplicates and keep the service secure. For its own accounts and billing, the operator acts as controller. For your customers' data, you (the business customer) act as controller and RecoverMRR acts as processor on your instructions.

Legal bases (Article 6 GDPR): performance of the contract with you for accounts, the trial, the subscription and the Stripe integration; legitimate interests for security, abuse prevention and aggregated analytics; legal obligations for records the law requires us to keep. A data processing agreement (DPA) for business customers is available on request at billing@getrecovermrr.com.

6. Service providers

  • Vercel — hosts the website and application; processes requests and operational logs (which may include IP addresses). Vercel Web Analytics provides aggregated page-view statistics (see section 7).
  • Supabase — authentication and database storage for accounts, platform billing and integration data.
  • Stripe — Checkout, Customer Portal, subscription billing and Stripe Connect.
  • Resend — sends payment-recovery emails to your customers and trial-reminder emails to you. It receives the sender and recipient address, subject and message text (including any payment-update link).
  • DeepSeek (optional, only when enabled) — may draft the wording of individual recovery emails. It receives only the decline reason in plain words, the merchant name, the plan name and the customer's first name. It does not receive email addresses, Stripe identifiers, amounts, links or card data.

Locations: the Supabase database is hosted in the EU (AWS region eu-west-1, Ireland). The application's server functions run on Vercel in the United States (region iad1, Washington, D.C.). Stripe, Resend and DeepSeek process data in the locations described in their own terms and privacy policies. Where data is transferred outside the EEA, the transfer relies on the safeguards offered by each provider under its standard terms, such as the EU Standard Contractual Clauses (SCCs) or an adequacy decision. Each provider's data processing terms apply.

7. Cookies, browser storage and logs

Supabase authentication uses session cookies. Stripe OAuth uses a secure, HTTP-only state cookie with a ten-minute maximum age. The website stores your language preference in local storage. The website uses Vercel Web Analytics to count page views. It does not use cookies; visitors are counted using a hash created from the incoming request, which Vercel discards after 24 hours. For each page view it may record the time, page URL and path, referrer, filtered query parameters, approximate location (country, region, city), operating system, browser and device type, and the analytics script version. RecoverMRR sees only aggregated statistics. No advertising SDK is included in the application code.

8. Retention and deletion

Trial expiry or cancellation does not delete your account or data. Data from a disconnected Stripe account is deleted within 30 days of disconnection, or sooner on request (see section 4). Backup copies held by our service providers may keep deleted data for a limited time after deletion, until those backups expire. Other than that, no automatic retention schedule or self-service account deletion is implemented yet; you can request deletion by email.

Accounts, trial and subscription records are kept while your account exists and deleted after you request deletion, except for billing records the law requires us to keep (in Italy, generally up to 10 years). Payment history from a connected Stripe account is kept while the account is connected and deleted within 30 days of disconnection; an automated job checks for this daily. Hosting and analytics logs are kept by Vercel for the limited periods set by its service. Backups held by our providers expire on the providers' own schedules.

9. Your rights

Under the GDPR you may have rights of access, correction, erasure, restriction, portability and objection, and may withdraw consent where processing relies on it. You may complain to a supervisory authority, including the Italian Garante. Requests: billing@getrecovermrr.com. If a business you subscribe to controls your data, please contact that business first.

10. Security and changes

The implementation includes authenticated access, webhook signature checks, OAuth state safeguards, encrypted OAuth tokens and tenant-scoped database controls. No system is absolutely secure. Material changes to this notice will be announced before they take effect.

Effective date: 22 October 2026.

Read the Terms of Service