Security & Trust
What we store, how we isolate it, and how we prove it. Written for the people who screen vendors for a living.
Built to operate without PHI
BillOnly manages scheduling, product declarations, charge capture, and billing metadata. The platform is designed so that protected health information is not required for any workflow — cases are identified by scheduling metadata, not patient identity.
No payment processing
BillOnly tracks remittance status only. No money moves through the platform — there are no payment credentials to store and nothing to divert.
Tenant isolation, enforced in the database
Every network's data is isolated with row-level security enforced by the database engine itself, keyed to the authenticated session. Application-layer guards provide defense in depth, but isolation does not depend on application code behaving correctly.
Vendor reps see only their own cases
A rep's access is scoped to the cases they are explicitly assigned to and to data they authored. This boundary is enforced at both the database and application layers.
Encryption
All traffic is encrypted in transit with TLS. Data is encrypted at rest.
Complete audit history
Core records are system-versioned: every change is retained with when and by whom. Administrative and security-relevant actions land in a central audit trail.
Authentication
BillOnly runs its own identity stack with short-lived rotating tokens and step-up multi-factor authentication for sensitive operations.
Hosting
BillOnly runs on Microsoft Azure.
Responsible disclosure
Found something? Tell us at info@billonly.com. We read every report.