Trust & compliance
Built so PHI never leaves the building
Faxart is designed for the people who own the HIPAA risk assessment. Every page, recording, and message is read on hardware you control, the account of who saw what holds up beneath the app as well as inside it, and a person confirms the patient before anything reaches a chart. This page is the posture in full, including where the boundary is and what stays your responsibility.
The data never goes off-site to be read
Both the OCR that turns a page into text and the model that classifies it run on a GPU inside your building. Cloud LLM APIs are not in the path for fax content, and that holds even where a signed BAA would permit it: on-prem is the rule, not a setting. The same applies to migrating years of history, which is read on-premises rather than on rented cloud compute.
The practical effect for a risk assessment: there is no cloud processor to add to your BAA inventory for the content of a fax, voicemail, or scan. The controls that apply are the ones you already run on your own network.
Why PHI stays on-premThe controls around it
Reads are logged at the data, not just the click
Every PHI read is recorded at the database floor with pgAudit, beneath the app, so the account of who opened which record cannot be quietly stepped around by raw SQL, a reporting tool, or a future integration. An app-layer overlay adds the who and the why on top.
How reads are loggedAccess is your directory, with scoped roles
Sign-in is your Active Directory over SAML; admin, auto-approver, and printer-admin are separate group-gated roles. The directory read uses a read-only service account; the one place that writes a fax number to AD is a separate, narrowly-scoped account, and that write is audited.
The directory modelA person confirms before anything reaches a chart
The system suggests a patient and a destination; it never files to a record on its own. A human verifies the MRN against the name and date of birth and confirms, and only what they confirm is transmitted, never the candidate the model read.
The trust gateNothing is silently dropped
Held, quarantined, junk, and failed are states you can see and act on. A fax that cannot be delivered is surfaced to requeue, not a quiet loss no one finds until a patient asks about it.
Reviewable controlsWhere the boundary is Your call
A trust page is only useful if it says what the product does not do for you. Two things stay on your side of the line.
Encryption in transit is a separate decision
On-prem keeps PHI off the public internet, but media and signaling on your LAN are not encrypted unless you turn on SRTP and SIP-TLS. That is a deliberate, separate change in coordination with your voice gear, not something Faxart silently assumes.
The infrastructure stays yours to run
Faxart runs on your servers, behind your network controls and your backups. It removes the cloud processor from the picture; it does not replace the operating-system, network, and physical safeguards your environment already carries.
Walk through it on your own stack
Book a demo, or read how PHI stays on-prem and how reads are logged.