Privacy Policy

What SignSend does

SignSend prepares e-signature envelopes for Muse users: the agent drafts an envelope (document metadata, signers, signing order), a human reviews and pays, and a fulfillment provider is planned to send the signature requests.

The current gateway is a demo stub — no signature requests are sent to any provider yet.

What we collect

• Document metadata you send us: file names and page counts (up to 5 pages per envelope). The stub does not store PDF bytes.
• Signer details you send us: names and email addresses of the 1–5 sequential signers you designate.
• Gateway metadata: your API key identifier, timestamps, envelope 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: DocuSign (eSignature API). Status: partner-program application in progress; the integration is not wired. When it is live, signer names, emails, and documents will be transmitted to DocuSign to send and process signature requests, subject to DocuSign’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 durable storage, document copies held by the provider, and deletion on envelope completion.

Keys

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