How BillProofs handles your data

Your invoices and your 3PL agreement are commercially sensitive. This page says exactly what happens to them.

What is stored, and how

• Invoice lines, approved rates, findings, credits and ShipBob tokens are encrypted with AES-256-GCM before they are written to the database. The key is held in the host's secret store, separately from the database and its backups.
• Passwords are hashed with scrypt. Sessions use random tokens that are stored only as hashes, in cookies that scripts cannot read.
• Each client workspace is separate. Every database query is limited to the workspace you are signed in to.

Where AI is used

Only when you upload a rate card. The document is sent to Anthropic's Claude API, which suggests rates together with the sentence it read each one from. BillProofs does not keep the file. Nothing is used until you check the rates and approve them. Anthropic does not train models on data sent through its API. The invoice checks themselves are fixed arithmetic and never use AI.

ShipBob connection

You create a Personal Access Token with read-only billing access in ShipBob and paste it into BillProofs. It is stored encrypted and used only to fetch the billing transactions you ask for. Disconnect it in BillProofs and revoke it in ShipBob at any time.

What BillProofs never does

• Contact your 3PL or send a dispute on your behalf.
• Share invoice contents, rates or workspace names with advertising or analytics tools. Marketing cookies run only on the public website, only after you accept them, and never see what is inside your account.
• Sell data.

Your controls

• Download everything, including every invoice line, as JSON at any time.
• Delete a single client workspace's data, or your whole account.

Reporting a security issue

Email support@billproofs.com. We'll reply and keep you updated until it's fixed.