Is it safe to connect my telecom account to an app?
- Your telecom credentials are encrypted with AES-256, never exposed to the browser or stored in clear.
- You stay in control: you can revoke or regenerate your keys from your provider anytime.
- A configurable spending cap prevents bad surprises on your telecom bill.
Yes, provided the app handles your credentials properly. At Relay, your telecom keys (Twilio, SignalWire or Telnyx) are encrypted with AES-256, never shown to the browser and never stored in clear on the server. And since it's your account, you can revoke those keys whenever you want.
It's a legitimate worry: handing your telecom account keys to third-party software deserves clear guarantees. Here's exactly what happens.
Where are my credentials stored?
Encrypted at rest, server-side, with a key that isn't in the database. When you paste your provider SID and key, they're immediately encrypted with AES-256-GCM. The browser never sees them again, and no one can read them in clear, even with storage access.
Telecom credentials connected to Relay are encrypted with AES-256-GCM, never returned to the browser and never stored in clear on the server. Encryption protects keys at rest, and each webhook call to your provider is validated, so an intercepted key doesn't grant access to your telecom account.
What if I want to remove access?
You take back control in seconds. Since the keys live on your provider account, you can regenerate or revoke them directly at Twilio, SignalWire or Telnyx. Relay then loses access, without you losing your number or your history.
It's the flip side of ownership: you're never locked in. The same principle that makes the multi-provider model lock-in-free applies to security: your account, your rules.
How do I avoid a runaway telecom bill?
By setting a spending cap. You define a monthly limit; Relay alerts you as you approach and can block beyond it. This protects against an unexpected usage spike or an abuse attempt on your number.
- Spending cap: a monthly $ limit, with an alert before blocking.
- Two-factor authentication (2FA): protects access to your Relay workspace, on top of the password.
- Anti-abuse: protection against repeated login attempts and inbound spam.
You can find the details of these protections on the security, and set the cap directly from your workspace.
Good habit: create a dedicated key at your provider for Relay, rather than reusing a master key. You can revoke it in isolation if needed, without touching your other integrations.