Your data, your call

Most data vendors are easy to join and hard to leave. That asymmetry isn't an accident; it's the business model. Your usage history, your billing record, the list of everything you've ever checked — it all lives on their side of a wall, visible only through a support ticket, if at all.

We think that's backwards, so we built the exits before we built the marketing. Three of them are live in the dashboard right now.

Export: one file, everything

There's a button that hands you a single JSON file with everything we hold on your account — your plan, your API keys' metadata, your full credit ledger, your usage, your bulk jobs. Not a redacted summary. The actual records.

One thing that file will never contain: your API key. We only ever store a hash of it, so we couldn't hand it back even if you asked — which is exactly the property you want from a company holding your credentials.

Delete: immediate, and it means it

There's another button that deletes your account. When you click it, your keys, usage, credit history, and bulk jobs are gone in the same breath — no thirty-day "cooling off" during which your data sits on a disk somewhere, no soft-delete flag that quietly keeps everything. Sign up again with the same email and you get a brand-new account with a fresh free grant, because there is nothing left to restore.

We tested this the only honest way: we deleted a real account and then went and counted the rows. Zero, across every table. If deletion didn't actually delete, the whole pitch falls apart.

The ledger: where every credit went

Between joining and leaving, there's the question every metered product should answer and most dodge: where did my credits go? Your dashboard now shows an itemized ledger — every grant, every verification, every bulk job, every refund — newest first, with a running balance beside each line.

This is where a specific promise stops being marketing and becomes something you can check. We say credits never expire and that refills top up your balance without ever clawing back credits you've bought. The ledger is where you watch that hold, line by line, instead of taking our word for it.

Same reason as everything else

None of this is generosity. It's the same instinct behind the checks.not_performed field in every API response — the one that tells you, on every single call, what we didn't verify. A company confident in its product doesn't need to trap you inside it, and doesn't need to hide what a result is based on. A company that isn't, does both.

We're building a validation API in a market whose incumbents have spent years teaching customers to expect lock-in and vague billing. The cheapest way to stand apart from that is to simply not do it — and to make the not-doing something you can click, not just something we claim.

It's all self-serve, in the dashboard, today. Take your data, or leave. Your call — which was always the point.