Data handling

What happens when you upload a Stripe CSV

Fee Auditor is intentionally not an OAuth app. You export a Stripe Balance CSV, upload it once, and get a report. The honest version: the CSV does leave your laptop for server-side analysis, but the raw file is not stored as a file, and the stored report is derived from the CSV.

Analyze my CSVRead Privacy Policy

The upload flow

1

You upload a Stripe Balance CSV

The CSV is sent to Fee Auditor over HTTPS so the server can analyze it. There is no Stripe OAuth connection, no API key, and no ongoing access to your Stripe account.

2

We parse it for fee analysis

The analyzer extracts the fields needed for totals, rates, dates, transaction types, and fee categories. It does not need live customer records or account-wide Stripe permissions.

3

We store a computed report, not the raw file

The raw CSV is not stored as a file. The report stores derived numbers and categorized rows so your private report link can reopen.

4

Reports expire automatically

Unpaid previews are short-lived outside beta, paid reports remain available for up to 30 days, and expired report rows are removed by cleanup jobs.

What is stored

  • +Processing rate and all-in Stripe cost rate
  • +Monthly totals, trends, and benchmark verdicts
  • +Grouped fee categories and high-fee charge flags
  • +Private report ID and access state
  • +Email only if you provide it for report access or checkout

What is not stored or requested

  • -Raw CSV as an uploaded file
  • -Stripe API keys or OAuth tokens
  • -Permanent access to your Stripe account
  • -Data for ads, profiling, or resale
  • -Free-text descriptions where they are not needed after analysis

Open core logic

You can inspect how the analysis works

The useful trust signal is transparency: you can see the parser, analyzer, and request flow. The repository is public, including the core CSV and fee logic.

CSV parser

Column mapping, amount normalization, and row parsing.

View on GitHub ->

Fee analyzer

Effective rate, high-fee charge detection, savings estimates, and storage redaction.

View on GitHub ->

Analyze API route

Server endpoint that receives the CSV, runs analysis, and saves the derived report.

View on GitHub ->

Plain-English privacy summary

Fee Auditor uses your CSV to produce the report you asked for. It does not sell financial data, does not use it for advertising profiles, and does not connect to your Stripe account.

Infrastructure providers still exist: Vercel hosts the app, Neon stores derived reports, Polar handles checkout, Resend may send transactional email, and Plausible measures aggregate traffic. The detailed version is in the Privacy Policy.

If your policy requires fully local processing, use the public code as a reference or wait for a browser-only preview mode. The current production app uses server-side analysis.

Need the CSV export first?

Use the Stripe Balance CSV guide, then come back and upload the Itemized export.

CSV export guideUpload CSV

FAQ

More security & pricing questions