The short version: your statement is processed in memory to
extract the transactions, and then it's gone.
What happens to an uploaded statement
Files are parsed entirely in memory — the statement is never written
to disk, and the grid you see exists only in your browser.
When the response is sent, the raw file is discarded. Nothing is stored on
our side. There is no workspace and no library of client files on this server. If
you need the spreadsheet again, convert the PDF again; a re-download of a statement
that already tied, in the same month, does not count twice.
A page with no text layer is rendered to an image in memory and read by OCR
software (Tesseract) on this same server. The image goes to that program over a
pipe, never through a file, and no third-party AI or OCR service is in the path.
The OCR'd statement then has to tie like any other before it downloads.
Exports (Excel, CSV, .qbo, Xero CSV, OFX, QFX, QIF) are built from the grid you
send back and returned to you — also never written to disk.
We do not train on customer statements. Not models, not heuristics
fitted to your data.
PDF passwords are used for the one decryption call and exist in memory
only. They are never logged or stored.
If your bank statement doesn't parse
If your bank's layout isn't supported yet, we keep the
shape of the layout — column headings and where they sit, date and money
formats, fonts, page size — so we can add support. Never any amount, balance,
date, name or account number, and the failure message shows you the complete
list of words retained (usually about six, like "Date", "Description",
"Balance"). The statement itself is still never written to disk.
What we log
One anonymous metadata line per conversion: file
counts, sizes, whether the parse succeeded, which layout template read it, and
whether the balance proof tied. Never file contents, never filenames, never IP
addresses.
Infrastructure
The site runs on an isolated US server with TLS,
serving this product and nothing else. The parser and the OCR run on that one
server; the statement never leaves it. Questions, or want a data-processing
letter for a client? ville@pennyclose.com