Privacy Policy
Effective November 15, 2026. This Privacy Policy explains truthfully what data is collected when you use reconcilebankstatement.online, how financial files are transmitted to the reconciliation engine, and how to request deletion.
1. Information Processed When You Use the Tool
- Uploaded Financial Documents: The bank statement (
bank_statement) and business ledger (business_ledger) files you upload (PDF, image, CSV, TSV, TXT, XLSX, or XLSM) to generate a reconciliation report. - Reconciliation Options: Date tolerance setting (0–31 days), description-matching toggle, and transient PDF unlock passwords (if provided for encrypted PDFs).
- Optional API Metadata: Only if entered by you under Advanced API Options: an optional
user_emailtag, HTTPSwebhook_url, and optionalwebhook_secret. - Standard Web Request Logs: Infrastructure hosts typically receive standard HTTP metadata (IP address, user agent, timestamps, status codes) required for network routing and abuse prevention.
2. Information We Do Not Request
reconcilebankstatement does not ask for your bank portal username, bank login password, multi-factor codes, Open Banking credentials, payment card details (for the free utility), or third-party advertising cookies.
3. Purpose & Service Architecture
Uploaded files are forwarded strictly to perform document parsing, OCR extraction, transaction comparison, balance verification, and report export (JSON preview and XLSX/CSV downloads) via our server proxy route (/api/reconciliation/* configured with Cache-Control: no-store). We do not sell uploaded statement records or sell financial transaction histories to data brokers or advertisers.
4. Cookies, UX Diagnostics & Tab-Scoped Session Storage
This web application sets no behavioral advertising or retargeting pixels. We use Microsoft Clarity for aggregate UI diagnostics (with data-clarity-mask="true" applied around financial reconciliation output views and masked PDF password fields). To let you reopen a recent run ID in the same tab, the browser stores cleartie:last-reconciliation-id (and optionally rec-token:<id> if guest token mode is enabled) in browser sessionStorage, which is cleared automatically when the tab closes. See our Cookie Policy and Data Retention Policy for complete details.
5. Privacy Rights (US, UK & EU) & Contact
Depending on your jurisdiction (including GDPR/UK GDPR or applicable US state privacy laws), you may request access, correction, or early deletion of persisted reconciliation runs associated with your reconciliation_id or optional user_email tag. Contact [email protected] and include your reconciliation_id if applicable.
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.