Your telecom credentials. Encrypted, never exposed.
We built Relay to never see your secrets in clear. Here’s exactly how.
AES-256-GCM encryption
Your Auth Token is encrypted at rest with a key only you trigger.
Never exposed to the browser
Telecom access tokens are generated server-side, short-lived. Your secret never leaves the backend.
You stay in control
It's YOUR telecom account (Twilio or Telnyx). Regenerate or revoke your keys anytime.
Signed webhooks
Every provider event is signature-validated. No injection possible.
Your personal information
A designated person in charge, your rights of access, correction and portability, and a full purge when you delete your account.
Payments via Stripe
We never store your card. Billing handled by Stripe.
Two-factor authentication
Turn on 2FA (TOTP) for your account. Login protected by captcha and brute-force limits.
Telecom spending cap
Set a monthly dollar limit. Relay alerts you at 80% and 100%, and refuses outbound at the cap if you pick blocking mode.
Your own limits
You set a number of messages per day and call minutes per month, per team. Beyond that, the app refuses to go further. Your limit can only tighten the automatic protection, never loosen it.
STOP actually works
A recipient who replies STOP or UNSUBSCRIBE stops receiving any text from your team, whether from the app, the API or an AI agent. Relay keeps its own list, per team, whatever your carrier is configured to do.
Automatic circuit breaker
If an integration or an AI agent runs away, outbound sending stops on its own. Receiving continues: no client call is lost. The same limits apply whether you send from the app, through the API or via an AI agent. You restart it from the app whenever you want.
Emergency calling (E911)
Register your emergency address so 911 routes correctly (Telnyx).
Your secret stays in the vault.
Your Auth Token is encrypted on receipt. Relay generates short-lived tokens to talk to your provider — your secret is never sent back to the browser nor stored in clear.