Aller au contenu
MRRSignal
AccueilFilBlogLancementsClassementsStatistiquesSalonsRacheter
⌘K

MRRSignal

Le revenu des startups, vérifié par le prestataire de paiement.

Interroger l’IA sur MRRSignal

  • ChatGPT
  • Claude
  • Perplexity
  • Grok

Produit

  • Fonctionnement
  • Comment fonctionne la vérification
  • Classement
  • Statistiques
  • Prestataires
  • Nouveautés

Ressources

  • Calculateurs gratuits
  • Glossaire
  • Références MRR
  • Toutes les startups
  • Catégories
  • Comparer
  • TrustMRR alternative
  • Badge MRR vérifié

Entreprise

  • À propos
  • Comment nous utilisons l'IA
  • Tarifs
  • Annoncer
  • Featured on
  • Contact

Aide

  • Centre d’aide
  • Questions
  • État du service
  • Report a problem

Mentions légales

  • Confidentialité
  • Conditions
  • Cookies
  • Sécurité
  • Toutes les politiques

Follow MRRSignal

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

© 2026 MRRSignal

Legal

Politique de confidentialité

We read your revenue, keep one number, and show nothing until you say so. Here is everything else, in full.

Dernière mise à jour 18 novembre 2026Ce qui a changé

Cette politique est fournie en anglais, qui constitue la version faisant foi.

1 numberkept from your provider, per provider

No customer names, no emails, no payment details.

From your provider to one number

What Stripe sends for one subscription read 6 dropped 7
  1. {
  2. "id": "sub_••••••••", (not kept)
  3. "status": "active",only active ones count
  4. "customer": "cus_••••••••", (not kept)
  5. "default_payment_method": "pm_••••", (not kept)
  6. "latest_invoice": "in_••••••••", (not kept)
  7. "items": { "data": [ {
  8. "quantity": 1,seats
  9. "price": {
  10. "currency": "usd",
  11. "unit_amount": 9000,in cents
  12. "recurring": { "interval": "month",
  13. "interval_count": 3, "usage_type": "licensed" },
  14. "product": "prod_••••••" (not kept)
  15. } } ] },
  16. "metadata": { "plan": "Team" }, (not kept)
  17. "current_period_end": 1765843200 (not kept)
  18. }

Counted per month, in US dollars

9,000¢× 1 seat ÷ 3 months =$30.00a month

The one row we keep, per provider

provider
stripe
mrr_cents
3000
subscriptions
1
skipped
0
last_synced_at
2026-11-18 06:00

Who sees it

  1. Only you, until you list
  2. Listed as a band, such as $10K+
  3. Listed with the figure
A worked example with Stripe’s field names; every other provider sends the same facts under its own names. Identifiers are masked because we never read them. A plan billed by usage has no fixed price, so it is skipped and counted as skipped, never guessed.

La version courte

  • Votre clé en fait le moins possible. En lecture seule partout où le fournisseur le permet, et toute clé secrète Stripe est refusée. Elle est stockée chiffrée et n'est plus jamais affichée, même pour vous.
  • Nous ne gardons qu'un chiffre, pas vos clients. De vos abonnements, nous conservons votre revenu mensuel et un décompte. Aucun nom de client, aucune adresse e-mail ni aucune donnée de paiement.
  • Rien n'est public tant que vous ne vous référencez pas. Les salons affichent une tranche telle que $10K+, jamais le chiffre exact, et vous pouvez référencer votre startup avec la tranche seule.
  • Aucun suivi. Aucun cookie d'analyse ou de publicité. Les vues des sponsors sont comptées sous forme de total quotidien par réservation, jamais par personne.
  • Nous ne vendons pas vos données. Elles sont transmises uniquement aux prestataires qui assurent le fonctionnement du service pour nous, listés ci-dessous.
  • Vous pouvez les retirer. Déconnectez votre compte, retirez votre fiche ou supprimez vos messages vous-même, et écrivez-nous pour tout le reste.

Sur cette page

  1. 01Qui nous sommes
  2. 02Ce que nous collectons
  3. 03Pourquoi nous les utilisons, et notre base légale
  4. 04Ce que les autres peuvent voir
  5. 05Avec qui nous les partageons
  6. 06Cookies et stockage du navigateur
  7. 07Combien de temps nous les conservons
  8. 08Comment nous les protégeons
  9. 09Transferts internationaux
  10. 10Vos droits
  11. 11Enfants
  12. 12Modifications de cette politique
  13. Versions
Sur cette page
  1. 01Qui nous sommes
  2. 02Ce que nous collectons
  3. 03Pourquoi nous les utilisons, et notre base légale
  4. 04Ce que les autres peuvent voir
  5. 05Avec qui nous les partageons
  6. 06Cookies et stockage du navigateur
  7. 07Combien de temps nous les conservons
  8. 08Comment nous les protégeons
  9. 09Transferts internationaux
  10. 10Vos droits
  11. 11Enfants
  12. 12Modifications de cette politique
  13. Versions

01Who we are

MRRSignal is operated by the company below, which decides how and why your personal data is used. Under the GDPR that makes us the controller of it; under the CCPA, the business.

MRRSignal
Registered address available on request from [email protected]

For anything in this policy, write to [email protected]. A person reads every message.

En bref

We decide what happens to your data, so we answer for it. Write to us and a person replies.

02What we collect

Your account

Your name, email address and password when you sign up. The password is stored only as a salted hash, so we cannot read it. If you sign in with Google, GitHub or X, we receive your name, email address and profile picture from them instead, and no password.

Your sign-in sessions

Each time you sign in we keep a session with the time it started, when it was last used, when it expires, and the IP address and browser it came from. This is how you stay signed in and how we spot a sign-in that is not yours.

Your provider key

To verify your revenue you give us a key from your payment provider (any of the supported providers). We ask for the narrowest key the provider offers. Where it has keys that can only read, we accept nothing else: for Stripe, a restricted key, never a secret key that could move money. Where a provider has no read-only keys, we use the key only to list your subscriptions, and the connect screen says so before you paste it. The key is tested against the provider, then encrypted before it is written (see how). It is never sent back to the site, to you or to anyone else. We also keep a one-way fingerprint of it, so the same key cannot be connected to two accounts.

Your revenue

With that key we read your active subscriptions: the price of each, how often it bills, how many seats and in which currency. From those we keep one figure per provider, your monthly recurring revenue in US dollars, with the number of subscriptions it came from, the number we skipped, and when it was last read. We keep a daily record of that figure, so growth can be measured. We do not keep your customers’ names, email addresses, payment details or anything else about them; the example below shows exactly what is read and what is kept.

Your startup listing

If you create a listing: what you enter (name, address on the site, tagline, description, website, category, country, founding date, logo address) and your choices about whether it is listed and whether it shows the exact figure or only a band.

What you write in rooms

Your messages, the room, and when each was sent, edited or deleted. Reports you file about a message, and reports others file about yours, with their reasons.

What you send us

Through the contact form: your name, email address, the topic and your message. We do not record your IP address with it. By email: whatever you choose to write.

Sponsors

If you book a sponsor slot: your contact name and billing email, the card you ask us to show (name, headline, text, link, image address), the booking dates, the price and the invoice.

Counting sponsor views and clicks

When a sponsor card has been on screen for a second, and when someone clicks it, we add one to that booking’s total for the day. That total is all we store. No cookie is set, and nothing about who viewed or clicked is recorded.

Technical records

Our servers log each request with its time, the address requested, the response, and the IP address it came from. To limit abuse, an IP address or account is also held in memory for the length of a rate limit, between one minute and one hour. When an admin changes something on your account, the change, the admin and the reason they gave are recorded in our audit log.

Never collected

  • Your customers’ names, emails or payment details
  • A Stripe secret key, or any key where a read-only one exists
  • Your IP address with a contact message
  • Anything about who saw a sponsor card

03Why we use it, and our legal basis

We use personal data only for the purposes below. Under the GDPR each rests on a legal basis.

PurposeLegal basis
Running your account, verifying your revenue, opening the rooms your figure reaches, and showing your listing if you listPerforming our contract with you
Keeping the service secure: sessions, rate limits, logs, the key fingerprint, moderating roomsOur legitimate interest in a service that is safe and cannot be gamed
Statistics across founders that never point at one of themOur legitimate interest in describing the community
Counting views and clicks per sponsor booking, in daily totalsOur legitimate interest in reporting to sponsors, with no personal data involved
Sign-in with Google, GitHub or XYour consent, given when you choose it
Sponsor invoices and booking recordsOur legal obligations, such as tax law
Answering what you send usOur legitimate interest in replying, or steps you ask for before a contract

We do not use your data for advertising, we do not build profiles of you, and we make no automated decisions that have legal or similar effects on you. Where a room opens because your verified figure reaches its threshold, that is the rule you sign up for, and an admin can review it on request.

04What other people can see

Your revenue is private until you decide otherwise.

  • In rooms, other founders see your display name, your picture if you have one, and your revenue band, such as $10K+. Never the figure.
  • On the public leaderboard, nothing appears unless you list a startup. If you list it with the exact figure, the figure, its daily history and its growth are public. If you list it as a band, only the band and your rank are public; the figure, history and growth are never sent to the site.
  • Which provider verified you is shown beside a listed figure, unless you mark the connection as anonymous. Then the public pages say only “a payment provider”. Admins still see which one it is.
  • In statistics, groups of fewer than three founders show a count and no money, and a total is withheld wherever subtracting the published figures could reveal one founder’s private figure.

Anything that is public can be read by anyone, including search engines and AI answer engines that cite the leaderboard. Unlisting removes it from our pages at once; copies others have already made are outside our control.

Change it yourself

Listing, band or exact figure: all in your startup settings. Unlisting takes your startup off the public pages at once.

05Who we share it with

We do not sell your personal data, and we do not share it for cross-context behavioural advertising. We share it only with the service providers that run MRRSignal for us, under contracts that limit them to doing that:

ProcessorPurposeData they handleRegion
Amazon Web ServicesDatabase hosting (Amazon RDS) and key management (AWS KMS) for the APIEverything the API stores: accounts, sessions, encrypted keys, revenue, listings, messages. KMS sees only sealed data keysUnited States
VercelHosting for the website and sign-inRequests to the site, with IP addresses, and the sign-in sessionUnited States
Amazon SES or ResendSending account email: confirmation, password reset, welcomeYour name and email address, and the email itselfUnited States
Google, GitHub and XSign-in, only if you choose to sign in with one of themThat you signed in, and the name, email and picture they holdUnited States

Your payment provider receives requests made with your key, which it already holds. The exchange-rate services we use (Frankfurter, and ExchangeRate-API as a fallback) receive a currency code and nothing about you. Sponsors receive daily view and click totals for their own booking and nothing about any visitor.

We may disclose data if the law requires it, to protect people from harm, or as part of a sale or merger of the business, in which case this policy continues to apply to it.

06Cookies and browser storage

We set only what the site needs to work and to remember your choices: the sign-in cookies, and a few settings kept in your browser, such as the theme. There are no analytics, advertising or tracking cookies, so there is nothing to consent to. Every cookie and storage key, by name.

07How long we keep it

1 minute1 hour1 day1 month1 year10 years
  • Rate-limit counters1 minute to 1 hour
  • Session cache cookie5 minutes
  • Sign-in sessions30 days after last use
  • Server logs30 days
  • Contact messages24 months
  • Admin audit record3 years
  • Sponsor invoices7 years
  • Your provider keyUntil you disconnect, deleted the moment you disconnect
  • Your listingUntil you delete it, yours to remove
  • Account, revenue history, messagesUntil you delete the account, removed with the account
A logarithmic scale, so each step to the right is ten times longer. Dashed rows have no fixed end: they last until you act.

When your account is deleted, your sessions, provider connections, revenue, history, listing, messages and reports go with it. Invoices are kept for as long as tax law requires, and the audit record for the period above.

08How we protect it

Provider keys are encrypted with a key of their own, which is in turn locked by a key management service, and bound to your account and provider so a copied row cannot be read. Connections use TLS. Admin access is limited by role, checked on every request, and every admin change is recorded with a reason. The security page has the detail, and how to report a weakness.

09International transfers

Some of our providers process data in the United States. Where data leaves the UK or the European Economic Area, we rely on the safeguards the law provides for it, such as the European Commission’s Standard Contractual Clauses or an adequacy decision, and on the provider’s own commitments.

10Your rights

You have these rights under the GDPR and UK GDPR, and California residents under the CCPA. Where the product can do it, the card links to the place; otherwise it opens an email with the request already named.

  • See your data

    GDPR art. 15, CCPA right to know

    A copy of everything we hold about you, and what we do with it.

    • Ask for a copyby email
  • Correct it

    GDPR art. 16, CCPA right to correct

    Fix what is wrong. Your listing you can edit yourself; for anything else, tell us.

    • Edit your listing
    • Ask usby email
  • Delete it

    GDPR art. 17, CCPA right to delete

    Remove a key, a listing or a message now, or the whole account with everything in it.

    • Disconnect a provider
    • Unlist or delete your startup
    • Delete your accountby email
  • Take it with you

    GDPR art. 20

    Your data in a machine-readable file, to move to another service.

    • Ask for an exportby email
  • Object or restrict

    GDPR art. 18 and 21

    Stop or pause a use of your data that rests on our legitimate interest.

    • Tell us what to stopby email
  • No sale, no sharing

    CCPA opt-out

    We do not sell personal information or share it for advertising, so there is nothing to opt out of.

    • Who we share with

Write from the address on your account, so we know the request is yours. We answer within one month, or 45 days for a California request, and tell you if we need longer and why. An authorised agent may ask for you with your signed permission. Using a right never changes how we treat you. You may also complain to your data protection authority, though we would like the chance to put things right first.

11Children

MRRSignal is for people running a business. You must be at least 16 to create an account, and we do not knowingly collect data from anyone younger. If you think a child has signed up, tell us and we will delete the account.

12Changes to this policy

When we change this policy we update the date at the top. If a change affects how we use data you have already given us, we will tell you by email or in the product before it takes effect.

Versions

  1. 18 novembre 2026
    Première publication.

Questions about your data? Write to [email protected], or use the contact form.

Voir aussi

  • Terms of service
  • Cookies and storage
  • Acceptable use
  • Refunds and cancellations
  • Data processing addendum