Skip to content
MRRSignal
HomeFeedBlogLaunchesLeaderboardsStatsRoomsAcquire
⌘K

MRRSignal

Startup revenue, verified by the payment provider.

Ask AI about MRRSignal

  • ChatGPT
  • Claude
  • Perplexity
  • Grok

Product

  • How it works
  • How verification works
  • Leaderboard
  • Stats
  • Providers
  • Changelog

Resources

  • Free calculators
  • Glossary
  • MRR benchmarks
  • All startups
  • Categories
  • Compare
  • TrustMRR alternative
  • Verified MRR badge

Company

  • About
  • How we use AI
  • Pricing
  • Advertise
  • Featured on
  • Contact

Help

  • Help centre
  • Questions
  • Status
  • Report a problem

Legal

  • Privacy
  • Terms
  • Cookies
  • Security
  • All policies

Follow MRRSignal

  • LinkedIn
  • X
  • Instagram
  • Reddit
  • Discord
Preferred source on Google

© 2026 MRRSignal

Legal

Data processing addendum

When we read your subscriptions, your customers’ data passes through us for a moment. These are the processor terms for that moment.

Last updated 18 November 2026What changed

0customer records kept

Read in memory, reduced to a total, then gone.

The short version

  • Your customers’ data passes through, briefly. A provider’s subscription records can name your customers. We read them in memory to compute one figure.
  • We keep none of it. Only totals derived from prices are stored, never anything about a customer.
  • It applies automatically. It is part of the terms. Ask us if you need a signed copy.

On this page

  1. 01What this covers
  2. 02The processing
  3. 03Our commitments
  4. 04Sub-processors
  5. 05Transfers
  6. 06The parties
  7. Versions
On this page
  1. 01What this covers
  2. 02The processing
  3. 03Our commitments
  4. 04Sub-processors
  5. 05Transfers
  6. 06The parties
  7. Versions

01What this covers

When you connect a payment provider, we read your active subscriptions. The provider’s responses can include personal data about your customers, such as a customer identifier. For that data you are the controller and we process it on your behalf. This addendum is part of the terms of service and applies automatically; you do not need to sign anything.

It does not cover your own account data, which we control as described in the privacy policy.

In short

Your customers’ data passes through us for a moment. This is the contract for that moment.

02The processing

Subject matter
Computing your monthly recurring revenue from your payment provider.
Nature
Reading subscription records with your key, in memory, on a schedule and when you ask for a refresh.
Data subjects
Your customers.
Personal data
Whatever identifiers the provider includes in a subscription record. We do not request customer names, emails or payment details.
What is kept
None of it. Only the totals derived from prices, intervals, seats and currencies: one figure per provider and a count of subscriptions.
Duration
Each read lasts seconds. The authority to read ends when you disconnect the provider, which deletes the key.

Kept

Totals only: one figure per provider and a count. Never a customer record.

03Our commitments

For the data this addendum covers, we:

  • process it only to compute your figure, on your instructions as given by connecting the provider, and for no other purpose;
  • do not store it, sell it, or use it to train anything;
  • ensure everyone who can access our systems is bound by confidentiality;
  • protect it with the measures described on the security page, including encryption of your key and TLS in transit;
  • help you answer requests from your customers and meet your own obligations, as far as we can given that we keep none of their data;
  • tell you without undue delay, and within 72 hours, after becoming aware of a breach affecting it;
  • on request, give you the information you need to show this addendum is being followed.

In short

We use it only to compute your figure, protect it, and tell you within 72 hours if something goes wrong.

04Sub-processors

The reads run on our API, hosted by the providers listed in the privacy policy. You authorise those sub-processors, each under terms that protect the data at least as well as this addendum. We will update the list at least 14 days before adding one, and you may object by writing to us.

  • Amazon Web Services: database hosting (Amazon RDS) and key management (AWS KMS) for the API (United States)
  • Vercel: hosting for the website and sign-in (United States)
  • Amazon SES or Resend: sending account email: confirmation, password reset, welcome (United States)
  • Google, GitHub and X: sign-in, only if you choose to sign in with one of them (United States)

In short

The companies that host our API. We give 14 days’ notice before adding one.

05Transfers

Where the processing involves a transfer out of the UK or the European Economic Area, the European Commission’s Standard Contractual Clauses (module two, controller to processor) and the UK addendum to them are incorporated into this addendum by reference.

In short

The EU’s standard clauses cover any transfer abroad.

06The parties

The processor is:

MRRSignal
Registered address available on request from [email protected]

The controller is the founder, or the business they act for, that connected the provider. If you need a signed copy for your records, write to [email protected].

In short

It applies automatically. Ask if you need a signed copy.

Versions

  1. 18 November 2026
    First published.

Related

  • Terms of service
  • Privacy policy
  • Cookies and storage
  • Acceptable use
  • Refunds and cancellations