Privacy

What this site, the audit and the key actually do with your data

Written from our code, not from a template. It says what the audit form stores, what the Stripe key you send us can read, where the audit output goes, and how to get all of it deleted — including the parts we have not automated. It is short because it is specific.

Last checked against the code on 2 October 2026. Where this page and the code disagree, the code is what actually happens and this page is wrong.

1. The audit request form on the main page

You type your work email and your company name, and optionally your website, your monthly revenue range and your billing processor. That is everything you type.

When you submit, our server adds three things from the request itself, none of which you type: the page you submitted from, the page that referred you here, and your browser's user-agent string. The row also carries the time it arrived.

It is stored in a Postgres database we run, so that we can reply to you. That is the only purpose we hold it for. We do not sell it and we do not share it with anyone else. There is no analytics, no advertising and no third-party script on this site (section 4), and we do not store your IP address — the lead table has no column for one.

One honest detail in the plumbing: if that database cannot be reached when you submit, the submission is written to our server's own log and to a fallback file on the same server instead of failing. A lead is never lost and you never see an error — but it does mean a copy can sit in a log file as well as in the database.

When our email notification is switched on, the only copy of your submission that leaves our server is a short message to our own inbox telling us a submission has arrived. It contains what you typed and nothing else — no IP address, no user-agent, no referrer.

To have it deleted: email the address in the footer of every page here and say so. Deletion is a manual act today — we remove the row, and any logged copy, by hand and tell you when it is done. There is no self-serve delete button, and this page will not pretend there is one.

2. The Stripe restricted key you send us for the audit

You create that key yourself in your own Stripe dashboard. What it can read is exactly what you grant it, and the steps ask for three permissions in total:

  • Invoices → Read — invoice status, amounts due and paid, currency, the attempt count, the next scheduled retry, the customer id and the customer email recorded on the invoice, and the decline code Stripe recorded.
  • Charges → Read — whether the charge behind an invoice failed, and its decline code.
  • Account → Read (optional, only so the page can print your account's name). Everything else — customers, subscriptions, products, prices, payment methods, balance, payouts, other keys — is left on None and stays unreadable to us.

Card numbers and CVCs are never returned by Stripe's API to any application at any permission level, so they are not something we could see even if we asked for it.

Every call the audit makes with that key is a GET. It refuses a live secret key or a publishable key rather than holding it, and it cannot create a charge, take a payment, refund, move money or change anything in your account.

The key itself is not stored by the audit: it is read from an environment variable or a command-line argument, held in memory for the run, and redacted out of everything the tool prints or writes. What we cannot control is the message you sent it in — that sits in our mailbox until it is deleted. That is why the next section matters more than this one.

3. The audit output, and how long we keep it

The audit writes its result to our own disk: `.run/audits/<your Stripe account id>/audit-<date>.md` and a matching JSON file, on the server that ran it. None of that is published. The only audit on this website is the sample page, and that one was produced from synthetic test data, not from anyone's account.

That file holds Stripe's data about your customers, because counting their failed invoices is the whole point of the audit: invoice ids, amounts and currencies, decline codes, attempt counts, the customer id, and the customer email address on each failing invoice. We read it to write your audit page, and we do not send it anywhere else.

How long we keep it: the code has no automatic expiry. In practice we keep the audit files until someone deletes them, and today deleting is a manual act. We have not written down a retention window, so we are not going to publish one we do not implement.

To have it deleted: ask us by email and we delete the audit files, the message holding the key and your form submission by hand, and tell you when it is done. If you go on to a pilot, the same promise has a command behind it: we run one job that deletes your rows from the database and your audit directory from disk, in a single transaction, and it refuses to report success if anything of yours survived.

4. Revoking the key — you never have to ask us

Our access ends the moment you end it. In your Stripe dashboard, open Developers → API keys (dashboard.stripe.com/apikeys), find the key you created for us, and Delete or Roll it. It stops working immediately. The key's Last used column and Developers → Logs show you exactly what was read before you did.

Revoking stops us reading any more, but it does not delete the audit we already produced. If you want that gone too, email the address in the footer and we will delete it.

5. Cookies, analytics and tracking: there are none

This site sets no cookies. It runs no analytics, no advertising or tracking pixels, no session recording and no third-party scripts. Nothing on any page is loaded from another company's server: the pages are rendered on our own server and sent to you as HTML, and the only JavaScript is our own code for the audit form. We do not build a profile of which pages you read, and with no analytics installed we have no way to.

6. If you go on to a pilot

The engine that chases failed invoices keeps its own records: which invoice failed, what we did about it, and the customer's email address as recorded on the invoice, because that is who a dunning message goes to. It lives in the same private database and is never published. Ending the engagement deletes those rows and your audit files in the one verified job described above. Your customers can stop the messages themselves at any time from the one-click link inside each one.

7. If something here is wrong

Email the address in the footer. When this page and our code disagree, the code is what happens — tell us and we will correct the page rather than the story. This page is a plain description of what our software does; it is not a certificate from anybody.

Ask us to delete something

One email is all it takes, and a person does it — nothing here is automated, and nothing is refused for a lack of a form. Write to [email protected] and say what you want removed: your submission, the audit output, or both. The key itself needs no email: revoke it in your Stripe dashboard and our access is over.