Privacy for statements

What happens when you review a statement

After you choose a PDF and select Review transactions, your browser reads the file and sends its file name and PDF contents, encoded as base64, in a POST request to /api/statement-review. The route validates the request, decodes the PDF, and uses the app’s server-side PDF parser to extract transaction rows before returning them to your browser. This flow does not call a third-party extraction provider.

App storage and infrastructure retention

While the review screen is open, the selected file and returned rows are held in browser-side page state. The API receives the PDF while processing the request. The current app code does not write statement PDFs or extracted rows to FolioCrumb’s database or object storage, and it does not define an app-level retention period for this flow.

The app code does not specify whether or how long hosting, network, or request-log systems retain request data. Infrastructure-level retention is therefore unspecified here; this notice cannot promise immediate or permanent deletion by those systems.

What “Start over” clears

Start over clears the selected file from the file input and the review’s on-screen file, transaction, and error state. There is no server-side delete endpoint for this flow. Start over is a user-interface reset: it does not securely erase browser memory, trigger an automatic deletion routine, or remove data that infrastructure systems may retain.

Downloaded CSV and Excel files

CSV and Excel exports are created in your browser and downloaded through the browser. Once downloaded, a copy is on your device, and FolioCrumb has no control in this flow to remove it. Manage downloaded copies using your device’s file tools.