Privacy

Effective November 12, 2026

Your files stay on your device

The bank CSV and the QuickBooks report you open, their file names, rows, dates, amounts and descriptions, and the CSV files BankFeedGap generates are handled only in this browser. They are never uploaded to BankFeedGap and never sent to Intuit, your bank or anyone else; there is no endpoint that accepts them. They are not stored either: they exist only in the open tab, and you open them again to continue later.

What reaches our server

• Checkout: the payment method you chose, a random comparison ID (a UUID that says nothing about you or your files), a SHA-256 comparison fingerprint computed in your browser from the two files’ SHA-256 hashes and the normalized settings (period, near-date window, column numbers, date formats and sign choices), a random checkout attempt ID and a campaign label from a fixed list. The fingerprint is a one-way hash: no file, row, amount or description is sent, and none can be read back from it. The server creates the checkout with Square or PayPal and returns a signed ticket that your browser keeps (with no content) so the payment survives the redirect.
• Payment verification: the server keeps the provider order identifier, the comparison ID, the fingerprint, a random per-attempt value and the payment status in a private order ledger (the item is “BankFeedGap Comparison Export”, $29.00 USD). It checks with Square or PayPal until the provider confirms the payment or the order closes. The return link can restore the unlock in another browser; the server stores only a keyed hash of that return code.
• Unlock check: when you reopen a purchased comparison, its ID, fingerprint and purchase grant are sent so the server can confirm them.
• Rate limits use short-lived in-memory counters per IP address. They are not stored on disk. Like most websites, the hosting server’s access log records requests (IP address, time, page requested) for operations and traffic counts.

Payments are handled on Square’s or PayPal’s own pages under their privacy policies. BankFeedGap does not see or store card numbers or PayPal credentials, and never sends them your files.

Counters

The server counts comparisons that ran with every confirmation in place (“preview completed”, at most once per comparison per visit), free downloads (the free first-rows CSV, the sample files and the sample comparison’s exports), hosted-checkout starts and provider-confirmed live sales, with a coarse campaign label from a fixed list (for example bankfeedgap_launch, bankfeedgap_guide or bankfeedgap_bookkeeping), the language “en”, payment provider, mode and the integer price paid. Use of the fictional sample is counted separately as demo usage. No IP addresses, cookies, file names, file hashes, rows or amounts are stored with these counts. Order numbers are stored only as a keyed hash. Sandbox payments are never counted as sales.

Browser storage

IndexedDB in your browser holds purchase grants, open checkouts and, for a checkout you started, the two files’ SHA-256 hashes with the settings you confirmed (column numbers, date formats, sign choices, period), so reopening the same files restores them. None of these contain file contents, names, rows or amounts. Local storage holds a campaign label from the link you arrived by (kept 30 days). No advertising or third-party tracking scripts are used. “Erase everything BankFeedGap stored in this browser” removes all of it.

Contact

Questions: contact support.