Security & Trust
Your call is protected by TLS encryption. Your device is bound to your account, and you decide which AI agents may use your phone line.
How your call is protected
TLS encrypts your call audio and controls on the internet connection to Parrot Cloud. It helps prevent someone on the network from listening to or changing that traffic. Parrot also uses encrypted connections to your AI voice provider.
Your phone connects to Parrot App on Windows or an ESP32 board over Bluetooth. That local connection uses your phone's Bluetooth pairing. Your carrier or calling app provides the connection to the other person.
What WSS protects
WSS is a WebSocket connection protected by TLS. Parrot App and ParrotBridge use it to send call audio and controls to Parrot Cloud. For ESP32, ParrotBridge runs on your computer and connects the board to the cloud.
Encryption and AI processing
Parrot does not provide end-to-end encryption for the whole call. Parrot and your selected AI voice provider process the audio so the assistant can hear and speak. Parrot also saves the call recording, transcript and report. Using your own provider key changes which provider account handles the AI session; audio still passes through Parrot Cloud.
Your account and devices
Your device is bound to your account. Only you and agents you authorize can place or answer calls on it. Knowing a device's name or identifier does not give someone access to your phone line.
Control access to your device
An API key lets an agent use the device you choose. It can control that line and delete finished calls on that device. It can also read your whole account's call history (transcripts, results and recordings of calls on any of your devices) and list your account's saved assistants. It cannot manage your account, billing or AI provider credentials.
Give each trusted agent its own key. When it no longer needs access, remove its key on the API keys page. Keep keys private: someone with a valid key can use its permissions until you revoke it.
To replace a key, create a new one, update the agent or bridge, then remove the old key.
Connected apps with OAuth 2.1
OAuth 2.1 lets you approve an MCP client in your browser without giving it an API key. Review the requested permissions before selecting Allow. Calls can be bound to one line, while call-history reads or assistant management can apply across your account, depending on the permissions you select.
The client manages access-token renewal. You can stop its access and renewal by revoking the connection on API keys & connected apps. It must ask for your approval again to reconnect.
Protection against server impersonation
The ESP32 board verifies that it is talking to Parrot Cloud before allowing call audio or commands. This helps block an impostor server or a man-in-the-middle attack through the bridge, including attempts to replace the server's replies on a compromised computer. If verification fails, the board blocks audio, dialing and answering until it can verify the server again.
Windows uses TLS to verify Parrot Cloud. The ESP32 check adds protection at the board, but it does not make a compromised computer safe to use. Keep your computer and device under your control.
Only the owner can access a device
Signing in does not give someone access to another user's devices. Parrot checks that the device belongs to the account making the request, or to the account that authorized the agent. Requests for someone else's device are refused without revealing whether it exists.
Access to your call history
Your calls are available in History. Call history belongs to the account that made the call, even if the device is later transferred. Agents you authorize with a device key can also read your account's history, including recordings of calls on your other devices.
You can delete finished calls. Their replay and report links stop working immediately, and saved content is cleaned up in the background. Financial records remain; deletion cannot remove copies already downloaded or sent to an AI provider.
Provider keys you supply yourself are encrypted when stored. See AI providers to use your own provider account.
Keep control of your call
Turn off Bluetooth on your phone, or switch call audio to your phone or another headset, to take over from the AI. To end the call, hang up on your phone or use End call in Parrot.
See Take over or end a call for the controls.
Protect your account and computer
Keep your phone and paired computer or board under your control. Lock your computer when you leave it, sign out on shared computers, and keep API keys private. Encryption and server verification cannot prevent someone using an unlocked computer or a stolen key from acting with your permissions.