Privacy
The short version: we never receive your clients' statements, because there is nothing to receive them with. One network call exists in the whole product — licence verification — and it never carries file data.
What happens to a statement you open here
When you choose a file, your browser hands it to code running in this tab. That code reads the file from your computer's own memory, rebuilds the transaction table, and writes the export straight back to your Downloads folder. At no point is the file — or anything derived from it: rows, balances, filenames, page counts — sent over the network. Close the tab and it is gone from memory.
The one network call: licence verification
When you activate or revalidate a licence key, the app calls Polar's licence API. That request contains your licence key, an activation label and our organisation identifier — nothing else, and never anything from a statement. Your licence key is verified online. Your files never are. If you are offline, an activated licence keeps working for 14 days without revalidation.
Payment itself happens on Polar's checkout pages in a separate tab, under their privacy policy. We never see your card details.
How you can verify this
- The assurance bar on every page runs a live monitor that wraps this page's network APIs and counts every byte of outbound request data. It reads 0 KB because nothing is sent.
- Open your browser's developer tools (F12 → Network) and convert a statement: you will see no requests carrying file data — only the licence check, if and when you activate a key.
- Load the page, disconnect from the internet, and convert. It works, because everything needed is already in the tab.
What we collect
No accounts, no cookies, no analytics, no file contents. The site is static files on a CDN, which — like every web host — records ordinary request logs (IP address, user agent) for page loads themselves. Licence state is stored in your browser's local storage on your machine.
Changes
If the network behaviour of this product ever changes, this page, the in-app disclosure and the measured badge change first. That ordering is a hard rule in the project's engineering constraints, not a promise.