Data Retention & Deletion Policy
Updated November 15, 2026. Understand exactly what stays in your browser tab versus what is handled on the reconciliation server (reconcilebankstatement.online).
1. Browser Storage & Passwords
- Run IDs in
sessionStorage: Keyscleartie:last-reconciliation-idand optionalrec-token:<id>remain only while your browser tab is open and are removed automatically by your browser when the tab closes. - PDF Unlock Passwords: Kept only in transient React component memory during upload and never persisted in browser storage or web cookies.
- API Proxy Caching: Next.js API proxy routes (
/api/reconciliation/*) explicitly setCache-Control: no-storeto prevent shared edge/CDN retention.
2. Server-Side Reconciliation Runs & Exports
When you upload two documents, the upstream reconciliation service generates a unique reconciliation_id (and may attach an access_expires_at timestamp) so you can view the preview route (/reconcile-preview/<id>), paginate category tables, and download .xlsx or .csv files.
Backend TTL & Cleanup Schedule: Report snapshots remain retrievable via reconciliation_id until their server-side access_expires_at expiration or automated backend purge runs complete.
3. Requesting Removal & Support
If you need immediate verification or removal of a specific reconciliation_id, contact [email protected] with your reconciliation_id. Also review our Responsible Use guidelines.
Related Documentation & Trust Resources
Ready to compare your bank statement against your ledger?
Upload PDF, image, CSV, or XLSX files directly in the workbench or test immediately with our sample CSV pair.