Privacy Policy

What FaxSend does

FaxSend prepares outbound fax jobs for Muse users: the agent drafts a fax (document metadata, destination number, optional cover page), a human reviews and pays, and a fulfillment provider is planned to transmit it.

The current gateway is a demo stub — no faxes are transmitted yet.

What we collect

• Document metadata you send us: file names and page counts (up to 10 document pages plus an optional billable cover page). The stub does not store PDF bytes.
• Destination fax number you designate.
• Gateway metadata: your API key identifier, timestamps, job status.
• Standard web logs (IP, user agent, request path) from the host/CDN.
• We do not sell personal information or run advertising pixels.

Fulfillment provider

Planned provider: Sinch Fax API v3 (formerly Phaxio). Status: not wired yet. When live, the document and destination number will be transmitted to Sinch to place the fax call, subject to Sinch’s own terms and privacy policy. Until then, nothing leaves the gateway stub.

Retention

Gateway state is in-memory and ephemeral: it disappears when the serverless instance recycles. There is no durable database on the gateway.

Do not treat the stub as document storage. Once provider fulfillment is live, retention terms will be updated to describe transmission records, provider-side copies, and deletion policy.

Keys

Bearer API keys authenticate agents. Treat them as secrets. Telep IO can revoke a key by removing it from the gateway configuration.