Privacy

Effective November 11, 2026

Your invoices stay on your device

The rate cards and invoices you load, project names, file names, audit results and the history of earlier audits are read, audited and stored only in this browser (IndexedDB), together with the purchase record of a paid invoice. Invoice and rate card files are never uploaded to WarehouseBillCheck or anyone else, and WarehouseBillCheck has no endpoint that accepts them. CSV files and printable reports are created in your browser.

We cannot restore projects you remove from this browser or lose by clearing site data. Keep your files and, for paid invoices, download the purchase record.

What reaches our server

• Checkout: the payment method you chose, the project’s random ID (a UUID that says nothing about your business), the SHA-256 fingerprint of the invoice file (a one-way hash; the invoice cannot be read back from it) and a random checkout attempt ID. The server creates the checkout with Square or PayPal and returns a signed ticket that your browser keeps.
• Payment verification: the server keeps the provider order identifier, the project ID, the invoice fingerprint, a random per-attempt value and the payment status in a private order ledger (the item is “WarehouseBillCheck Full Invoice Audit”, $59.00 USD). It checks with Square or PayPal until the provider confirms the payment or the order closes. After a confirmed payment, 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 open a paid project, its ID, invoice fingerprint and purchase record 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.

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

Campaign counters

The server counts actual free CSV downloads, hosted-checkout starts and provider-confirmed live sales, with a coarse campaign label from a fixed list (for example warehousebillcheck_guide, warehousebillcheck_launch or warehousebillcheck_agency), the language “en”, payment provider, mode and the integer price paid. No IP addresses, cookies, file names, invoice data or results are stored with these counts. Order numbers are stored only as a keyed hash to avoid double-counting. Sandbox payments and the demo are never counted.

Local storage

Besides IndexedDB, the app uses local storage for the last project you opened and a campaign label from the link you arrived by (kept 30 days). No advertising or third-party tracking scripts are used.

Contact

Questions: contact support.