Changelog

1. 9 September 2026 Policy and limits

   You can now read exactly how long each thing is kept

   The privacy policy answers the retention question in one schedule instead of in prose, which is the answer a client or a compliance reviewer asks you for first.

   • Every category of data now has a stated retention period in a single schedule, each sub-processor is described by category with its country and safeguards, and the provider is named on request.
   • Storage wording is now precise: your file exists only while the conversion runs and is deleted right after, in every case within one hour. The hour is the outer ceiling, not the usual case.
   • Terms cover accounts and monthly plans, and the refund policy now extends to plans as well as packs.
   • Photo uploads are capped at 10 per statement, so a long paper statement is split across two conversions.
   • Site content is in English. Turkish statements are read as before.
2. 8 September 2026 First release

   Convert a statement, and see the arithmetic tie

   The first release does one job end to end: it reads a statement and shows you, row by row, that what came out matches the balances the bank printed.

   • PDF, scanned PDF and phone-photo bank statements convert to XLSX, CSV, QBO, OFX, QFX, QIF and JSON.
   • Every conversion is balance-checked. The running balance is rebuilt from the extracted rows, compared line by line and then against the closing balance, and rows that break the chain are flagged with the difference.
   • Statements printed newest first are detected by running the check both ways, and exported in date order.
   • Credit-card statements flip the sign convention and exclude subtotal rows. Where the statement prints no running balance on each line, the check reports what it could tie rather than passing.
   • A native PDF that fails the check is read again with a stronger pass, automatically.
   • Three pages a day are free with no account. Page packs are $9 for 60, $29 for 300 and $79 for 1,000, and credits never expire.
   • Every release is validated against a fixed test corpus. How we test.

These entries describe work that has shipped. Planned work is on the roadmap, and how particular statements and export formats behave is documented in the help center.