Privacy Policy

What PaperSend does

PaperSend turns a PDF into a physical letter: printed, put in an envelope, and mailed First Class in the US.

The Muse gateway job endpoints are stubs: creating a job does not mail anything, charge anyone, or call a print provider. Live printing and mailing are handled by the separate PaperSend application, not the gateway.

What we collect

• Document metadata you send us: filename and page count (1–5 pages). The gateway stub does not store PDF bytes.
• Sender and recipient addresses: name, street address, city, state, ZIP — everything needed to address a letter.
• Job metadata: timestamps, status, quoted price, and your API key identifier.
• Standard web logs (IP, user agent, request path) from the host/CDN.
• We do not sell personal information or run advertising pixels.

What we do with it

Gateway stub jobs go nowhere: they are stored in-memory on the gateway and never forwarded to a print or mail provider. No provider is wired to the gateway stubs today. If you use the separate PaperSend application, its own privacy notice governs how documents and addresses are handled there — the gateway and the app are different services.

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 submit live customer documents or addresses to the gateway stubs until a durable store and a provider contract exist.

Keys

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