mintfax offers two retention modes to support different compliance requirements.
Standard mode
PHI is kept for a configurable retention window, then deleted. The window is set per environment: default 90 days, any value from 7 to 365.
- Fax content, cover page body, sender name, recipient name, and recipient company are deleted when the window expires
- The destination number and operational metadata (status, error codes, timestamps, attempt history) are kept as operational data, so the fax record stays queryable
- Billing records are retained permanently
- You can purge a delivered or failed fax with
DELETE /v1/faxes/{id} without waiting for the window to expire. A purge also scrubs the destination number.
PHI is scrubbed as soon as the fax is delivered or fails (the fax.delivered or fax.failed events). Operational metadata (status, timestamps, error codes, attempt history, destination number) is kept. This supports HIPAA’s minimum-necessary principle.
Zero-footprint is a per-environment setting, off by default. Turn it on in the dashboard.
Once a fax has been scrubbed:
GET /v1/faxes/{id}/image returns 422 with error fax_data_purgedPOST /v1/faxes/{id}/resend returns 422 with error fax_data_purged (the original document is gone)GET /v1/faxes/{id} still returns the fax, with PHI fields nulled
What gets deleted vs. kept
Compliance boundary
mintfax compliance commitments (HIPAA, GDPR, zero-footprint) cover mintfax infrastructure only: the mintfax API infrastructure, content storage, operational databases, and application logs. They do not extend to:
- Upstream carrier systems (carriers retain their own logs per their own policies)
- Recipient-side fax infrastructure
- Your webhook endpoints receiving fax data
- Third-party payment processors
BAA
A Business Associate Agreement is free for every customer, not an add-on. No plan, tier, or sales call gates it. Last modified on October 19, 2026
