SECURITY

Your Bank Statement Is Processed in Your Browser, Not Uploaded

This page describes how the converter works today. Claims such as SOC 2, bank-grade encryption, or guaranteed accuracy are not made here because they are not supportable.

What is loaded on the page

The selected PDF is read in the browser. Inspection, OCR, reconstruction, and export run on the device that opened the page. The PDF worker and the English OCR model are served from this origin. The in-browser converter does not send statement photographs to a third-party OCR API.

Third-party analytics and chat scripts are disabled on this origin so they cannot read financial pages or saved browser history.

Training and logs

Cloud processing is gated separately for redacted text and original file uploads. These paths remain unavailable until provider disclosures are approved. The file OCR path sends the file to Cloudflare Workers AI before text masking. Application usage records contain page counts and request metadata, not statement text. Saved browser history can include financial fields and persists until deleted; closing the tab does not delete that history.

Export safety

Descriptions that look like spreadsheet formulas are neutralized in CSV and XLSX so a payee name cannot execute as a formula. Money values are written as numbers, not as text that Excel might misread.

Cloud processing controls

Enabling cloud processing requires documented provider retention, region, training use and subprocessors. Cloud requests have input limits, server-side usage reservations and attempt budgets. Failed inference can return the customer's page allowance while still counting against the service's attempt budget. Do not email unredacted statements to support.

Questions: support@bankexcelconverter.com · Privacy