Your banking password stays yours.
We process the files you choose. We never ask for bank credentials, connect to an account, or move your money.
Source files are not retained
Uploads are read on the server and discarded after the request completes. Raw bank statements are not stored in a public bucket or made available through file URLs. If a statement cannot be parsed, no partial transaction data from that file is saved.
Reports belong to your session
A randomly generated, HttpOnly session cookie controls access to your normalized transactions and reports. Server-side checks apply to reading, editing, and exporting. Knowing a report URL is not enough to access another browser’s report.
Private transport and storage
The hosted service uses HTTPS. Normalized report data is stored in the service’s database and is returned only after an ownership check. Uploads are limited by size, type, row count, and request rate. Spreadsheet archives are checked for excessive expansion and unsupported active content.
Categorization with limited context
Deterministic merchant rules are applied first. When AI categorization is enabled, selected descriptions, amounts, directions, and business type are sent to OpenAI to suggest categories. Long number sequences are redacted. AI does not receive source files or calculate your totals.
Paddle handles payment details
Card details are entered in Paddle Checkout. A verified, signed payment webhook is required before exports unlock. A browser redirect or a payment-success URL cannot grant access.
Delete your report data
Use “Delete my data” from a report or review page to remove the reports and transactions in your session. Payment records are kept separately. See the Privacy Policy for retention details.