Security

How RevReclaim Protects Your Data

RevReclaim is designed around one principle: we should never have more access than we need. Your API key is restricted, your data is encrypted, and your billing account is untouchable.

Read-Only Access

RevReclaim uses restricted API keys scoped to read operations only. It cannot modify your billing account, create charges, cancel subscriptions, or access credit card numbers. This is enforced by Stripe, Paddle, and Polar at the platform level — not just a promise.

Key Never Stored

For one-time scans, your API key is processed in memory and discarded immediately after. It is never written to a database, log file, or any persistent storage. The scan takes ~90 seconds. That's how long your key exists on our servers.

Encrypted Everything

For auto-scan users who choose to store a key, it is encrypted with AES-256-GCM before storage. The encryption key is stored separately from the database. All data in transit uses TLS 1.3.

What We Read vs. What We Can't Do

What we read
  • Subscriptions & their status
  • Invoices & payment history
  • Coupons & discount details
  • Product prices (current vs. old)
  • Card expiry dates (not numbers)
What we can't do
  • Create charges or modify billing
  • Cancel or change subscriptions
  • Access credit card numbers
  • Delete any data from your account
  • Store your API key after the scan
  • Access or store customer full names

Privacy Mode

NEW

For teams with strict data policies, Privacy Mode adds an extra layer of protection. When enabled from your dashboard settings:

  • Customer emails are hidden from all reports and leak cards
  • Customer IDs are anonymized in exports (CSV, JSON, PDF)
  • Recovery actions still work — customer data is encrypted and only decrypted server-side
  • Customer names are never fetched from billing APIs in any mode

Available for Pro and Team plans. Enable it in Dashboard → Settings → Privacy Mode.

Technical Security Details

Transport

All data in transit is encrypted via TLS 1.3.

Storage Encryption

API keys for auto-scan are encrypted at rest using AES-256-GCM with a derived key. The encryption key is stored separately from the database.

Database

Supabase (PostgreSQL) with Row Level Security — each user can only access their own data.

Hosting

Vercel with automatic HTTPS, DDoS protection, and edge network.

Authentication

Passwords are hashed. Only essential cookies are used — no advertising or third-party tracking cookies.

Data Minimization

RevReclaim only fetches the billing data needed for leak detection: subscriptions, invoices, customers. It does not access payment method details, bank accounts, or personal identity documents.

Customer Privacy

Customer names are never fetched from billing APIs. Emails are masked (j***@example.com) in the UI and encrypted with AES-256-GCM in the database. Privacy Mode hides all PII from the dashboard and exports.

Third Parties

Only Vercel (hosting) and Supabase (database), both under strict data processing agreements. RevReclaim does not sell, rent, or share your data.

What if my key is compromised?

Fair question. Here's why a read-only restricted key has minimal risk even in a worst-case scenario:

  • 1

    Read-only keys cannot create charges, modify subscriptions, or access card numbers. This is enforced at the platform level by Stripe, Paddle, and Polar. Even if someone had your key, they could only view the same data categories you granted permission for.

  • 2

    You can revoke any API key instantly. Go to your Stripe, Paddle, or Polar dashboard → API Keys → delete the key. Access is cut off immediately.

  • 3

    One-time scan keys exist for ~90 seconds only. They're processed in memory and never touch a database or log. After the scan completes, the key is gone.

  • 4

    Auto-scan keys are encrypted with AES-256-GCM. The encryption key is stored separately from the database. You can delete your stored key at any time from your dashboard settings.

Security FAQ

Why not use OAuth instead of API keys?

Stripe, Paddle, and Polar each handle authentication differently. Stripe Connect (OAuth) is designed for platforms that manage billing on behalf of others — not for read-only scanning tools. Restricted API keys are the recommended way to grant scoped, read-only access. They give you full control over exactly which permissions to grant and can be revoked instantly.

Do you have SOC 2 certification?

Not yet. RevReclaim is a bootstrapped product built by a small team. We follow security best practices (encryption at rest and in transit, data minimization, zero key storage for one-time scans), but we haven't undergone a formal SOC 2 audit. We're transparent about this because we believe honesty builds more trust than vague claims.

Can I revoke access at any time?

Yes. For one-time scans, there's nothing to revoke — the key is already gone. For auto-scan, you can delete the stored key from your RevReclaim dashboard settings, or revoke the key directly from your billing platform's API keys page. Access is cut off immediately.

Who can see my billing data?

Only you. Your scan reports and dashboard are protected by Row Level Security in the database — each user can only access their own data. The RevReclaim team does not access customer billing data.

Ready to scan?

Free forever. Read-only access. Key never stored.

Scan My Billing →