Skip to main content
Limits, Data Retention and Policies

Security, Privacy and Compliance

How VoiceAIWrapper stores your keys and connections, how to protect team and client logins, where call data goes, and answers to common compliance questions.

Written By voiceaiwrapper

Last updated 26 days ago

This article answers the questions agencies and their clients ask most during a security review: how your keys are stored, how to lock down team and client logins, where call data goes, and what we can say about compliance. Use it to fill in a client's questionnaire or to tighten your own setup.

How your keys and connections are stored

Provider API keys

When you connect a Vapi, Retell AI or ElevenLabs Pod (an engine or provider connection), VoiceAIWrapper stores your API key so it can manage agents, phone numbers and calls in your provider account for you. VAW Native Pods need no keys at all.

Some connections need a key with full access:

  • ElevenLabs: "Please ensure that you enter an unrestricted API key."

  • Stripe (for billing your clients): "Ensure your Stripe API key is not restricted."

To limit the risk from any one key:

  1. Create a key just for VoiceAIWrapper in your provider's dashboard, rather than reusing one that other tools share. You can then revoke it without breaking anything else.

  2. If you think a key has leaked, create a new one with your provider, update the Pod in VoiceAIWrapper, then delete the old key with your provider. See Manage Pods: Rename, Update Keys, Switch and Delete.

Twilio, tool connections and other secrets

These are encrypted in our database with a separate platform key:

  • Twilio credentials you connect for VAW Native phone numbers. Only a masked Account SID is shown in the webapp.

  • Tool connections: the Bearer token, Custom header and Cal.com API key connections your tools use. See Store API Keys with Tool Connections.

  • GoHighLevel connection tokens.

  • Each VAW Native Pod's Webhook signing secret.

Your VoiceAIWrapper API keys

API keys let other systems add leads, manage campaigns and more on your behalf. Treat each one like a password.

  • Create and delete keys in Settings β†’ API Keys (Generate API Key).

  • Use a separate key for each integration, and delete keys you no longer use.

  • Each key has its own rate limit, so one busy integration doesn't slow down the others.

See Create and Manage API Keys.

Webhooks you receive

Every webhook a VAW Native Pod sends is signed with the Pod's Webhook signing secret (Standard Webhooks format), so your server can check it really came from VoiceAIWrapper. Use Roll secret to replace it; the old secret keeps working for 24 hours so you can update your server without dropping events. See Verify Webhook Signatures.

Protect your team's logins

  • Turn on two-factor authentication (2FA). Open your avatar menu β†’ Profile, find Two-factor authentication and click Setup 2FA. Scan the QR code with an authenticator app such as Google Authenticator or Authy, enter the 6-digit code and click Verify & activate. Each team member turns it on for their own login. See Turn On Two-Factor Authentication.

  • Limit who can change organization settings. Only Owners and Admins can open Settings, which holds billing, API keys, integrations and team members.

  • Remove people who leave. Take them out of your organization from Settings β†’ Members as soon as they go.

Protect your clients' logins

The client portal doesn't offer 2FA for client users. To control where clients can sign in from, use IP access control.

Available on: plans that include Client IP access control. Without it, the Security tab doesn't appear on client accounts.

  1. Open Client Accounts, then the client.

  2. Open the Security tab.

  3. On the IP whitelist or IP blacklist card, click Add IP Rule and enter an IPv4 address, an IPv6 address or both. Add one rule per address; ranges aren't accepted.

  4. Turn on the switch for the list you want to use.

With the whitelist on, only the listed addresses can sign in to the client's portal. With the blacklist on, the listed addresses are blocked from signing in.

If you or your team sign in to this client's portal yourselves, click Add my IP to whitelist before you turn the whitelist on. With the whitelist on and your address missing, you'll be locked out, and the page warns you with Your IP isn't whitelisted yet.

See Restrict Client Access by IP Address.

Recordings and call data

  • VAW Native recordings and transcripts are kept for as long as you choose in the Pod settings (Keep recordings for and Keep transcripts for). By default, recordings are kept for 90 days and transcripts are kept forever. Recordings are stored privately and played through short-lived links. Recording links inside webhook payloads stop working after 7 days.

  • Vapi, Retell AI and ElevenLabs store recordings and transcripts in your own provider account, under that provider's retention settings.

See Data Retention: Recordings, Transcripts, Logs and Exports.

Where your data goes

VoiceAIWrapper runs on Amazon Web Services (AWS).

During a call, data also passes through the services that power it:

Pod type

Services involved

VAW Native

LiveKit for the live audio connection, Deepgram for transcription, ElevenLabs or OpenAI for the voice you pick, and the AI model you pick (OpenAI, Anthropic or Google). Phone calls and texts go through your own Twilio account.

Vapi, Retell AI, ElevenLabs

Your provider account handles the call, with whatever models and telephony you've set up there.

On VAW Native, data also leaves the call in these cases:

  • Post-call analysis and Call Data Extractions send the transcript to an AI model (OpenAI by default, or the model you choose).

  • Knowledge bases use OpenAI to index your documents and to search them during calls.

  • Tools you attach send the data you map to the systems you point them at, such as your own server, Cal.com or GoHighLevel.

  • Webhooks send call data to the URLs you set.

If your Vapi organization is in Vapi's EU region, turn on Use EU Domain when you connect the Pod ("Enable if your VAPI organization uses the EU region (dashboard.eu.vapi.ai)").

Compliance

For a security questionnaire or compliance documents, ask us in Need help? β†’ Help Chat.

Your responsibilities

You decide who your agents call, what they say and what they record, so you're responsible for the calling, recording and messaging rules that apply to you and your callers. For example:

  • Tell callers when calls are recorded, where the law requires it.

  • Get consent before calling or texting, where required. For web widget visitors, see Add Consent and Legal Notices.

  • In the US, register local numbers for A2P 10DLC in your Twilio account before your agent sends texts. VoiceAIWrapper doesn't check this, and Twilio refuses texts from unregistered numbers.

Frequently asked questions

The webapp has no self-hosted edition or install option. If you have a specific requirement, ask us in Help Chat.

VoiceAIWrapper offers a full EU-based architecture on its Enterprise tier, starting at $2,000 per month, billed annually. Contact support to discuss your deployment requirements; see current pricing. This is separate from your BYOK provider account's own region. For example, Vapi's EU region still requires an eligible Vapi organization with Use EU Domain turned on.

Not yet. Use IP access control on the client's Security tab to limit where they can sign in from.

Related articles