Security and Compliance
BillingBench is designed to be PHI-free by architecture. The design principle is that tools which handle or process patient data must do so exclusively in the user's browser — data never traverses BillingBench's servers. This eliminates the need for end-to-end encryption of patient data in transit, reduces the HIPAA risk surface to workspace account data only, and means that a BillingBench infrastructure breach cannot expose patient records.
Public tools (Denial Risk Tool, Appeal Letter Builder, Denial Decoder, ERA Parser, Prompt Pay Interest Calculator, Timely Filing Calculator): fully stateless. No data entered into these tools is stored in the browser beyond the session or transmitted to any server. The ERA Parser processes 835 files entirely in browser memory using JavaScript — the file bytes never leave your machine. The Appeal Letter Builder generates letters locally from your inputs and the BillingBench regulatory library embedded in the application bundle.
Workspace accounts: denial queue entries, saved appeal letters, and ERA dashboard data are stored in Supabase with AES-256 encryption at rest and TLS in transit. Authentication requires email and TOTP (time-based one-time password) two-factor authentication — there is no SMS 2FA option due to SIM-swap risk. Sessions expire after inactivity. A Business Associate Agreement under 45 CFR §164.504(e) is executed at workspace signup. No BAA request form or separate compliance step is required.
Infrastructure: hosted on Vercel's edge network with SOC 2 Type II certification. Database on Supabase (SOC 2 Type II, HIPAA eligible). No third-party analytics pixels, no advertising trackers, no vendor pixels of any kind. Content Security Policy headers restrict script execution to first-party sources.