Zero-Upload Privacy Policy

1. Financial Statements Never Leave Your Browser

BankFilePro is engineered as a client-side browser application. When you open or drag-and-drop a CSV, Excel (.xlsx / .xls), Quicken (.qif), or Open Financial Exchange (.qfx, .ofx, .qbo) file onto BankFilePro, the file is read strictly inside your device's local RAM via standard Web File APIs.

Zero transaction rows, payees, balances, or account digits are ever uploaded, logged, cached, or transmitted to BankFilePro servers or any third party. You can verify this directly in your browser's Developer Tools Network tab while converting a file.

2. Local Browser Storage (localStorage)

If you activate a Pro License Key or save named Bank Presets, those settings are stored locally in your own browser's localStorage so you do not have to re-enter them on every visit. A pending checkout ID, random verification token, and expiry time are also saved locally so payment can be verified when you return. Statement rows stay in this tab's memory; clearing site data removes the saved settings.

3. Billing & License Key Verification

Paid subscriptions ($9/month) are processed by our Merchant of Record payment partner, Dodo Payments. We never see or store your credit card numbers. When you activate or validate a license key, your browser sends the license key and device activation ID over TLS to our verification endpoint (/api/license/*). Payment verification uses the checkout ID and its random browser token. These requests never include statement content, balances, account digits, or filenames.

4. Contact

Questions regarding security, CPA firm compliance, or privacy may be sent directly to support@bankfilepro.com.