Privacy
What happens to the CSVs you open
Nothing you load into SettlePair is transmitted anywhere. The invoice CSV and the bank transactions CSV are read by JavaScript running in your browser tab, held in memory for the session, and discarded when you refresh or close the tab. There is no upload endpoint, no server-side copy, and no account to create.
In-browser processing
CSV parsing, column mapping, match scoring, allocation arithmetic and CSV export are all client-side code. Selecting a file uses the browser's file input; the file's contents never leave the page. The export you download is generated in the tab from the data already in memory.
No storage
SettlePair writes no financial data to localStorage, sessionStorage, IndexedDB or cookies, and there is no database behind it. Refreshing the page clears every invoice, transaction, decision and allocation — this is deliberate, and it means an interrupted session has to be started again.
No bank connection, no third-party analytics
SettlePair does not connect to banks or accounting systems, holds no credentials, and calls no external matching, AI or enrichment service. The public pages load a web font from Google Fonts; the reconciliation workbench makes no request carrying your data.
Clearing a session
Refresh the page, or close the tab. Both discard everything immediately. If you are working on a shared machine, also delete the exported settlepair-reconciliation.csv from your downloads folder when you are finished with it — that file is on your disk and is your responsibility from the moment it is saved.
Limitations you should know
- SettlePair is a review aid, not an accounting system, and makes no claim of accounting accuracy. Every suggestion needs human confirmation.
- Automatic matching is deterministic and strictly one payment to one invoice.
- Very large files are limited by your device's memory, since all work happens in the tab.
- The site is served over HTTPS, but the security of your own machine and browser extensions is outside our control.