Skip to main content
mintfax offers two retention modes to support different compliance requirements.

​
Standard Mode

Fax data and metadata are retained for a configurable period, then automatically deleted. The default retention period is set at the account level and can be overridden.
  • Fax documents, images, recipient/sender details, and transaction metadata are deleted when the retention period expires
  • Billing records and credit transactions are retained permanently
  • You can actively delete fax data at any time via DELETE /fax/{id}, without waiting for the retention period

​
Zero-Footprint Mode

Fax data and metadata are deleted immediately after the fax reaches a terminal state (delivered or failed). This supports HIPAA’s minimum-necessary principle. Enable via account settings:
In zero-footprint mode:
  • GET /fax/{id}/image returns 410 Gone after the fax completes
  • POST /fax/{id}/resend returns 410 Gone (original document is deleted)
  • GET /fax/{id} returns only the fax ID, status, and timestamps (no content or PII)

​
What Gets Deleted vs Retained

​
Compliance Boundary

mintfax compliance commitments (HIPAA, GDPR, zero-footprint) cover mintfax infrastructure only: our API, S3 storage, DynamoDB, Postgres, 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
We configure sub-processors we control (carriers, infrastructure) to uphold our retention commitments. For example, carriers with a “no image retention” option are configured to use it.

​
BAA

A Business Associate Agreement is available at every paid tier, free of charge. No enterprise plan or sales call required.
Last modified on July 14, 2026