Privacy policy

Last updated 18 October 2026

In one line: the files you drop into Statemint are parsed inside your own browser and never uploaded. There is no account, no server-side copy of your data, and no advertising tracker on this site.

Your files stay on your device

Statements, ledger exports and every number derived from them — including the difference report you generate — are read and processed by JavaScript running in your browser tab. They are written to a browser-local database on your own machine and are not transmitted to us or to anyone else. If you close the tab, nothing has left your computer.

This is why Statemint deliberately does not connect to Xero, QuickBooks or any other ledger API, and why it can keep working with no internet connection.

What we do collect

Anonymous usage statistics about this website, nothing more. We use Umami, a privacy-focused analytics tool, which records which page was viewed, the referring site, the country, and a rough device class. Umami sets no cookies, tracks no individual across sites, and does not build a profile of you. Compared with a supplier statement, this is roughly equivalent to counting how many people walked through the door.

License keys and settings

Your column mappings and, once purchased, your license key are stored in your browser's local storage on your own device so that you don't have to re-map the same export twice. You can clear them at any time from the app's settings.

Payments

Purchases are handled by our payment provider. We never see or store card numbers, and there is no recurring charge to cancel. We do not retain your payment details.

Contact

Questions about this policy, or anything else, are welcome at [email protected]. Because we hold no data about you, most questions can be answered in one email, and any request to remove data is usually unnecessary — there is nothing to remove.

Changes

If this policy ever changes in a way that would weaken a promise made here, we will say so plainly on this page and note the date at the top rather than burying it in a footer link.