Privacy & data

AgentCall is a line between you and your agents: for updates, decisions and replies. History keeps text rather than saved call recordings. Audio still passes through speech services, and an agent’s opening line can be cached briefly to make pickup faster.

1. A message arrives. An agent sends call details or a message; you reply by voice or text.
2. Speech is processed. Spoken replies are transcribed; agent text is synthesized when voice is used.
3. Text becomes a record. The conversation and its call details appear in your account’s History.

Account

Your sign-in identity, including name, email and avatar, through Clerk. With Google sign-in, AgentCall does not receive your Google password.

Calls

Text sent by the agent and your spoken or typed replies, together with agent and project names, the call reason, timestamps and how the call ended. Records can include where you interrupted an agent’s sentence and the optional feedback you give after a call. History is scoped to your account.

Voicemails

The message is stored as text. Pressing Play generates audio from that text; History does not keep a voicemail recording.

Devices

A device’s label and push registration: a browser subscription or an Android Firebase Cloud Messaging token. Android enrollment also stores a hash of the device key used to answer calls, alongside device/app details and activity timestamps.

Client tokens

If you create an optional MCP token, its label, hash and creation/last-use timestamps are stored. The complete token is shown once when you create it; it cannot be retrieved later.

Preferences

Voice, standing call rules, voicemail, transcription language, calling availability and setup preferences. These stay associated with your account.

Live state

Current call text and status, recent agents and pending callback requests. Live-call expiry is measured in hours; the agent-presence store has a seven-day expiry. Activity can refresh these windows, so they are not fixed deletion dates for each record. History and preferences are separate.

Events

Product events such as call requested, call answered and transcription completed, with operational details such as duration, end reason and client type. These events are intended to measure whether the service works, without transcript text, call reasons or audio in the event payload.

Audio handling. Your voice passes through AgentCall to the speech provider for transcription; agent text is sent for speech synthesis. A synthesized opening line may be cached through Redis with a 240-second expiry. Consumption or an ended ring can remove it sooner; expiry provides cleanup if that does not happen. This temporary audio cache is separate from the text kept in History.

No direct workspace access. Connecting an agent does not give AgentCall access to its files, repository, terminal or internal reasoning. The service does receive what the agent explicitly sends, including call reasons, messages and callback details. That text can contain information from the agent’s work, just as your spoken or typed replies can.

What a notification can reveal. A ring can show the agent and project name on your lock screen. The call reason and transcript are shown inside the app, not in the ring-notification text. Push payloads also carry the routing and timing information needed to deliver and retire a ring.

Your agent and your account can access the conversation. The following services also process data to provide authentication, storage, speech and delivery. The speech-provider retention caveat above applies even though History contains text rather than audio recordings.

Vercel & speech

Hosting and AI Gateway route speech processing. The current default models are OpenAI’s gpt-4o-mini-transcribe for transcription and tts-1 for speech synthesis.

Clerk

Authentication and account identity.

Neon

The database for call text, agents, device registrations, client-token hashes and events.

Upstash

Live call state, preferences, agent presence, usage counters and the temporary synthesized-opening cache.

Push services

Google’s Firebase Cloud Messaging delivers Android rings; browser push services deliver web notifications. Ring text can include agent and project names, as described above.

AgentCall’s policy is no selling of data, advertising, third-party analytics or tracking pixels, and no training on your conversations by AgentCall. There are no transcript-sharing features. These statements do not replace the speech providers’ own retention terms.

A reply can guide an agent that has permission to act in other systems. Connect trusted agents and treat a transcript as something to confirm before an irreversible action.

• One account, both ends. Authorize the agent’s MCP connection with OAuth 2.1 and sign in to the same account on your devices. Clients that cannot use OAuth can use an optional MCP token instead. Tokens remain valid until revoked. Requests are bound to the account that authorized them.
• Enrolled native devices. The Android app has its own device credential so it can answer a ring before the app’s web view opens. Removing the device revokes that registration. Access is not limited to an already-open browser session.
• Outbound agent requests. The MCP connection does not open an inbound connection to the machine running your agent or expose its workspace.
• Confirm consequential instructions. Speech can be mistranscribed. Agents are instructed to confirm destructive or irreversible instructions verbally before acting.
• Rate limits apply to rings, speech and device enrollment.

A call

Open its transcript in History, choose Delete call, then confirm. Successful deletion permanently removes that call, its transcript and matching events. This also applies to voicemails.

A device

Open Devices & notifications in Settings and choose Remove. This revokes the server registration. If it is your current browser, the app also attempts to unsubscribe it locally; it cannot unsubscribe a different browser from here. Follow any error shown if removal cannot be confirmed.

Your account

Open Account data in Settings and choose Delete everything under Delete account & data. Confirmation starts removal of calls, voicemails, devices, preferences, client tokens, events and your account. Successfully deleted data cannot be recovered.

Wait for confirmation. Account deletion can finish only partly if data cleanup or identity removal fails. Follow the result shown in Settings and retry if asked. After successful account deletion, a hashed deletion safeguard is retained to prevent late requests from restoring deleted account data; deletion is not a promise about speech-provider retention or every infrastructure backup.