Fax service privacy

Updated October 11, 2026.

Local preparation and scanning process documents in your browser. Nothing is uploaded during those steps. Downloaded PDFs remain on your device until you delete them. Closing or refreshing the page clears files held in memory. When you choose to continue between PDF tools and fax preparation, the PDF and recipient/cover settings are saved in this browser for a one-time transfer lasting up to 15 minutes, without uploading it. The transfer is removed when opened; expired transfers are cleaned up the next time you transfer a document.

When you create an account, the service stores your email and a salted password hash. Web sessions use an HttpOnly cookie; native sessions use the device secure store. Sessions last seven days unless you sign out. Contacts are stored under your account to support device sync.

When you save a prepared fax or continue to checkout from a verified account, its PDF, recipient, fax number and page quote are uploaded. PDFs are encrypted on the service, and unsent drafts expire after 24 hours. Completed or refunded PDFs are removed from local storage. Completed fax files are queued for deletion at the fax provider after service-mode and ownership checks. Minimal cleanup job records remain until removal is confirmed; confirmed cleanup records expire after seven days. You can delete eligible drafts and terminal order records. Contacts and order metadata remain in the account until removed; backups may retain copies. You can export account metadata and delete your account after confirming your password and resolving active orders. Verification and password reset use one-time, 15-minute codes; a successful reset revokes existing sessions. SMTP delivery shares your email address and code with the configured mail provider. Queued codes are encrypted and removed after dispatch or expiration. Local previews may explicitly show a development code without sending email.

When you continue to checkout, Stripe receives your email and order reference and collects your payment and billing details, including the address used to calculate applicable tax. RichFax stores payment references, tax and total amounts; it does not store card numbers. After confirmed payment, your prepared PDF and destination fax number are transmitted to Sinch Fax for delivery. Ambiguous provider jobs require operator review. Their local documents are removed after at most seven days, while unresolved order metadata may remain for reconciliation. Provider cleanup failures are retained for operator attention.

For receiving numbers linked to your verified email, the Inbox reads incoming fax metadata and PDF files from Sinch over authenticated connections. Access is restricted to those linked numbers. Received documents remain subject to the provider retention period; download a copy for your records. Sinch Fax-to-Email also forwards received documents to the configured receiving email address. RichFax does not cache inbox API responses or received PDFs. RichFax also sends received-fax notifications from [email protected] with the received PDF attachment, using our configured SMTP provider. Outgoing delivery, confirmed failure and refund notifications include a transmission report with order metadata, not the original fax document. Notification records prevent automatic duplicate sending; uncertain email sends require review.

Application assets may be cached for offline use. The service worker does not cache documents, contacts or account API responses. The host may keep access logs. See the RichScripts site privacy policy for general site information.

The service does not claim HIPAA or PHIPA compliance. Do not use RichFax where a certified compliant service is required. For privacy questions contact [email protected].

Security and data flow · Receiving and email