Telep IO · DomainSend

Privacy Policy

Last updated 21 September 2026. Contact jon@telep.io.

Plain-language product notice maintained by Telep IO — not legal advice.

What DomainSend does

DomainSend is a Telep IO LLC connector on the Telep Muse gateway. It checks domain availability and drafts domain registrations.

The current gateway is a demo stub — no domains are actually registered. Availability results are simulated (names starting with “taken-” are treated as taken; other supported names are shown available).

What we collect

  • The domain names you query or draft for registration, the term (1 or 2 years), and a WHOIS-privacy flag that is always true on drafts.
  • The current stub does not collect registrant contact details (name, organization, email, postal address, or phone). Planned live registrations will require registrar contact data.
  • Gateway basics: your API key identifier and timestamps.
  • 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 — fulfillment provider

Nothing is forwarded anywhere today. The registrar (OpenSRS / Tucows reseller track is the planned provider) is not wired up, and no reseller agreement is in place. Because the gateway is a stub, do not submit real registrant contact data until a live registrar integration and durable storage exist. WHOIS privacy is planned for live registrations; the stub’s `whoisPrivacy: true` flag does not hide anything in a public WHOIS database.

Retention

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

Keys

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

Contact

Privacy questions: jon@telep.io.

Related: DomainSend · Platform privacy · Platform terms