Privacy Policy

What CallSend does

CallSend is a planned scripted-call connector: it is meant to place phone calls that read a human-approved, verbatim text-to-speech script — a notification call, not an autonomous conversation.

The current gateway is a demo stub. No calls are placed. The agent may draft the exact script; a human is required to review every word and pay before any live call would be placed.

What we collect

• Destination phone number you designate for the call.
• The exact script you approve — the words a live call would speak.
• Call job fields: status (draft, paid, queued, completed, failed), timestamps, voice label, and an unused `record` boolean. The stub does not store call duration and does not capture audio.
• Gateway metadata: 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.

Fulfillment provider

Planned provider: Twilio (Voice API). Operator-reported status: a Twilio account is provisioned with a 216 (Cleveland) local voice number. The exact number is not published here. SHAKEN/STIR attestation, CNAM (“Telep IO LLC”) caller ID, and API wiring are in progress — not live. Until announced live, no calls are placed. When live, the destination number and script would be transmitted to Twilio to place the call, subject to Twilio’s own terms and privacy policy.

Retention

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

Once provider fulfillment is live, retention terms will be updated to describe durable call records (status, timestamps — never audio) 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.