TrustMRR stores only the Stripe data it needs

I hear the concerns, so I wanted to be 100% and share what I do with Stripe API keys shared on TrustMRR: 1. When you upload the key, it hits my API endpoint (NextJS /api on Vercel) and gets a few information from Stripe 2. The key needs to read Charges and Subscriptions data to reconstruct your revenue and MRR. It also needs read-only access to Connect and File so I can use your Stripe account name, icon, and description to build a nice page. 3. Once done, I compute this data and store it in my database. I only store what TrustMRR needs to display a page: revenue per day, current MRR, startup name etc. If you don't see it on the page, it's not stored in my database. 4. Your API is then encrypted in my database in MongoDB. That way, every 12 hours, my cron job queries Stripe again, fetches new payments, and updates your revenue data. I just hired a security expert to audit the codebase because I know how important security is. That's it!

  • 7 reposts
  • 464 likes
  1. @marclou · Nov 1, 2025

    For instance, this is everything I store for this startup of mine: trustmrr.com/startup/byedis…

    For instance, this is everything I store for this startup of mine: trustmrr.com/startup/byedis…
    • 1 reposts
    • 59 likes

Join 50,736 readers

How to find startup ideas, launch fast, and get profitable.

Free. Unsubscribe anytime.

More tweets

All tweets →