Faximus Fax Delivery Disclaimer
Version: 2026.10.27-r1
Fax is a legacy, real-time telecommunications process. A transmission may pass through Faximus, internet providers, one or more telephone carriers, the public switched telephone network, private branch exchanges, fax servers, multifunction devices, and human workflows. Many of those systems are outside Faximus's control. Ordinary fax transport is not represented as end-to-end encrypted between Faximus and the recipient's fax device.
This disclaimer explains what Faximus status information means and what it does not prove. It is part of the Faximus Terms of Service.
1. No guarantee of delivery or receipt
Faximus uses commercially reasonable efforts to submit and receive faxes, but does not guarantee that a fax will:
- reach the intended fax number or person;
- be accepted by a recipient system;
- arrive by a particular time;
- contain every page in a legible form;
- preserve the exact appearance of the source file;
- be routed internally by the recipient to the correct person;
- be read, reviewed, filed, acted on, or kept confidential by the recipient; or
- have legal effect in a court, agency, transaction, or professional workflow.
A successful protocol or carrier response is not the same as proof that the intended human recipient received or read the document.
2. Status meanings
The exact status names available in the portal, API, email, or webhook may vary by interface or version. In general:
| Status concept | What it generally means | What it does not mean |
|---|---|---|
| Submitted or accepted | Faximus received a request that passed initial validation. | The document was rendered, transmitted, or delivered. |
| Queued or processing | Faximus is preparing, rendering, routing, or waiting to attempt the fax. | A carrier or recipient has accepted it. |
| Dispatching, sending, or in progress | A transmission attempt has started or is being placed. | The recipient received all pages. |
| Awaiting retry | The latest attempt did not produce a final success and another attempt may occur. | Every prior attempt was definitely unseen by the recipient. |
| Delivered, succeeded, or completed | Faximus's media system or carrier reported a successful fax session or the completion criteria defined by the current platform. | The number was correct, the intended person saw it, every page was readable, or a legal deadline was met. |
| Failed | Faximus did not receive a success result after the attempts or time allowed for the job. | No page or partial document reached any device. |
| Canceled | The job was stopped before Faximus recorded a final success. | No attempt occurred or no partial transmission reached the recipient. |
| Received or inbound complete | Faximus received an inbound fax associated with a number and stored or made it available according to the account configuration. | The sender was authorized, the content is safe, or the intended internal user reviewed it. |
When a status matters, use the current record in the portal or API. Email and webhook notifications can be delayed, duplicated, filtered, or missed.
Delivery status and billable usage are separate. A fax can create billable transmission usage even when its final status is Failed or Canceled, as explained in Section 6 and the Terms of Sale.
3. False positives, false negatives, and partial delivery
Fax protocols and carrier signaling are imperfect. A recipient device may acknowledge a session even when pages are faint, clipped, misrouted, or later discarded. A sender may receive a failure even though a recipient received one or more pages. A transmission may connect to the wrong device if the number is wrong, reassigned, forwarded, or misconfigured.
For that reason:
- do not treat a success status as conclusive evidence of human receipt;
- do not treat a failure status as conclusive evidence that no information arrived;
- do not automatically resend sensitive material without considering duplicate or partial delivery; and
- independently confirm critical communications with the intended recipient.
4. Rendering and document quality
Faximus may convert a source file into a fax-compatible image. Conversion can change fonts, margins, page breaks, colors, contrast, scaling, orientation, image quality, or page count. Recipient equipment may further reduce quality.
Customer should review important documents before sending, use high-contrast originals, avoid very small text, and confirm that the rendered page count is reasonable. Color information may be converted to black and white or grayscale.
Faximus is not responsible for content that is already corrupted, password-protected, malformed, low-resolution, or incompatible with the documented file requirements.
5. Retries and duplicates
Faximus may retry an unsuccessful or uncertain attempt. Carrier failover or Customer retries can also create duplicates. A timeout or lost API response does not prove that the original request failed.
Use idempotency keys where supported, check status before resubmitting, and design receiving workflows to tolerate duplicates. For sensitive or time-critical content, contact the recipient through a separate channel before resending after an uncertain result.
6. Billing for transmission work
Unless the applicable pricing page, plan, or order form says otherwise, Faximus may charge for billable pages submitted for outbound transmission when Faximus or its carrier, media, or network providers incur transmission cost or materially perform transmission work. The charge may apply even when delivery fails because of an invalid or disconnected number, a non-fax destination, busy or no answer, incompatible or rejecting recipient equipment, a recipient-side rejection, or another recipient-side, carrier, routing, or network condition outside Faximus's control. A usage charge shows that billable transmission work occurred; it does not prove successful delivery.
Faximus does not separately charge for Faximus-initiated automatic internal retries of the same submitted job unless the applicable pricing page, plan, or order form expressly says otherwise. A job newly submitted or resubmitted by Customer, Customer's software, or a third-party integration may create new billable usage, even when Customer intended it as a retry. Cover sheets count as pages unless the applicable plan says otherwise.
7. Delay and scheduling
Transmission time depends on queue load, page count, document rendering, carrier capacity, recipient availability, line quality, retries, geographic routing, and other factors. A scheduled or accepted job may begin or finish later than requested.
Faximus does not promise a completion time unless a signed order form expressly creates that commitment. An uptime SLA measures availability of a covered Faximus service, not the time needed to complete an individual fax.
8. Critical, legal, and regulated communications
Do not rely on Faximus as the sole channel for an emergency, urgent clinical instruction, prescription, court filing, regulatory notice, bid, closing, funds transfer instruction, safety notice, or other deadline-sensitive communication.
For a critical transmission, Customer should:
- verify the fax number from a trusted source;
- use an appropriate cover sheet and minimal necessary content;
- review the final document and page count;
- monitor the current job status;
- confirm receipt and legibility with the intended recipient through a separate channel; and
- retain the source document, status record, and any independent confirmation required by Customer's policy or law.
Faximus does not provide legal, medical, records-management, or filing advice and does not determine whether fax is an acceptable method for a particular notice or transaction.
9. Inbound faxes
An inbound fax may contain malware, deceptive content, misdirected information, or material sent without authorization. Customer is responsible for access controls, internal routing, safe handling, and deciding whether to trust or act on the content.
Assignment of a fax number does not guarantee that the number has no prior history or that senders will immediately update their records. Customer should expect occasional wrong-recipient or legacy traffic and handle it under applicable privacy and confidentiality rules.
10. Notifications are a convenience
Email, SMS, portal alerts, and webhooks are convenience features. They may be delayed or filtered by third-party systems. Customer remains responsible for monitoring the authoritative account records and maintaining its own operational controls.
11. Remedies
A delivery failure does not automatically create a refund or credit because outbound usage may measure transmission work and network or carrier cost rather than successful delivery. Any refund, billing adjustment, or service credit is governed by the Terms of Sale, an applicable SLA, or a signed order form. Those remedies are subject to their eligibility rules and limits, without limiting a right that applicable law does not allow the parties to waive.
12. Contact
Report a suspected platform issue to support@faximus.io with the account identifier, fax or job identifier, date and time with time zone, destination or assigned number, and a description of the issue. Do not email an unredacted sensitive document unless Faximus requests it through an approved secure channel.