mintfax offers two retention modes to support different compliance requirements.Documentation Index
Fetch the complete documentation index at: https://mintfax.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
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:GET /fax/{id}/imagereturns410 Goneafter the fax completesPOST /fax/{id}/resendreturns410 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
| Category | Deleted per retention | Retained permanently |
|---|---|---|
| Fax documents | Yes | |
| Fax images | Yes | |
| Recipient/sender details | Yes | |
| Transaction metadata | Yes | |
| Billing records | Yes | |
| Credit transactions | Yes | |
| Account information | Yes |
Compliance Boundary
mintfax compliance commitments (HIPAA, GDPR, zero-footprint) cover mintfax infrastructure only: our API, S3 storage, DynamoDB, MySQL, 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