Privacy and data

Privacy

Data and privacy controls per agent, from call recording and spoken consent to redaction, retention, and telemetry.

Every control in the agent editor's Privacy section decides what a call leaves behind.

Like every editor section, it is read-only while you view a published version, so open a draft to change it. Most of its settings reach live calls when the draft is published. Retention is the exception: it belongs to the agent rather than to a version, so a change applies as soon as it is saved.

Workspace defaults and per-agent values

Most controls here can follow a workspace default or be set on the agent. Workspace defaults live in Workspace and members.

  • Retention offers Workspace default, and Record call audio and Diagnostic sharing offer Inherit workspace default. Each follows the workspace setting, or takes a value fixed for this agent.
  • Data storage follows the workspace while the agent is on Full transcript. Any other level is fixed for this agent.
  • The two disclosure switches follow the workspace only until they are set on the agent. Flipping one either way fixes it for this agent. The disclosure lines themselves are always set on the agent.

A new agent follows the workspace's retention period, but is created with its own values for recording and disclosure: call recording on, both disclosures off. A workspace recording setting reaches a new agent only once you set the agent's recording to Inherit workspace default.

Call recording

Record call audio controls whether the platform stores the call audio.

SettingEffect
Inherit workspace defaultRecords only if the workspace default is on
On: record call audioRecords this agent's calls
Off: don't record call audioNever records this agent's calls

The workspace default for recording is on.

When you record audio, tell the caller. That is what the recording disclosure below is for.

Recording after a transfer

When the agent puts a caller through to someone on your team, the recording stops at the transfer. The caller's conversation with that person is not recorded.

To record it too, set Recording after a transfer to Keep recording until the call ends. On a call that kept recording, the call page marks the part after the transfer on the Carrier recording, and the Clean recording ends at the transfer.

The agent can speak two short consent lines at the start of a call: a recording disclosure and an AI disclosure. They sit ahead of the greeting and are the first thing the caller hears (see Voice and speech).

Turn the recording disclosure on whenever you record call audio. Consent and disclosure covers the preset lines, the spoken order, and why a switched-on but blank disclosure blocks publishing.

Data storage

The Data storage control decides how much of each call's transcript is kept. The levels, categories and matching rules are on PII redaction.

Redaction happens when transcripts are written to storage, and for some categories in a pass after the call. It never touches the live conversation, so it cannot break the agent mid-call.

What redaction does not reach

Redaction applies to the stored transcript only. The call recording is unredacted audio, so a number the redactor strips from the transcript is still audible. Turn call recording off if that matters.

Data retention

Retention sets how long this agent's calls are kept before automatic deletion.

SettingEffect
Workspace defaultFollows the workspace retention setting
A fixed periodDeletes calls older than that period (1 day to 2 years)
Keep foreverNever auto-deletes calls

A workspace keeps calls forever until someone sets a period, and a new agent follows the workspace. Use a shorter period for agents that handle sensitive calls.

What a period deletes

When a call passes its period, its transcript and recordings are deleted, and so is everything worked out from it: the summary and analysis notes, the reasoning behind each score, the details pulled out of the conversation, the record of the tools it used, and the caller's name and number and the agent's last reply. The call still counts in your dashboards by its outcome, duration and scores, with nothing of what was said.

Caller memory follows the same period. A remembered caller loses what calls older than the period added. A caller with no call inside the period is forgotten, unless someone on your team blocked them or set a routing rule for them: then the block or the rule stays, with the caller's number and the notes your team wrote.

Recordings follow the same period

A call's recordings are deleted with the rest of the call when its period passes, so an agent set to "Keep forever" keeps its recordings too. Permanently deleting an agent, or a workspace once its recovery window ends, deletes its recordings before anything else.

On a phone call, the phone-line provider makes the recording and we copy it to our storage. Once our copy is verified, we delete the provider's copy and check that none is left.

Transcripts and recordings both appear on Calls and analytics until the call's period passes.

The audit log is on a separate clock

The workspace audit log (who changed what, when, from which IP, and whether it was allowed) is kept for two years by default, set separately under Settings → Privacy and retention. It is deliberately longer than transcript retention: the record of who deleted a call has to outlive the call, or the trail expires with the thing it describes.

Refused attempts are recorded too. A permission check that says no is a security signal, and a log of successes alone cannot answer whether anyone tried.

Reading a call is recorded, not just changing one

When someone on your team opens a call's transcript, plays its recording, listens to a call in progress, or opens a caller's profile in the app, it writes its own entry, under Views beside Changes on the same page. So do listing calls with their summaries, exporting them, and reading a call through a connected AI tool. The entry records who, their role, which calls, where it was opened, when, from which IP, and whether audio was served. It never records the transcript, the recording, or anything the caller said. Those stay where they were.

Reads by Vertical AI staff are recorded the same way and marked as staff access. A staff member who is not in your workspace appears as Vertical AI support.

The two are kept apart because they answer different questions and arrive at very different rates: a workspace changes a setting occasionally and opens call detail all day. Mixing them would bury the change trail rather than enrich it.

Access entries follow the same retention as the rest of the audit log, and export with it.

Telemetry

Diagnostic sharing controls how much call content flows to third-party observability tools. Data storage governs what the platform keeps; diagnostic sharing governs what leaves to those services. The sub-processor list is available in writing on request. See Compliance.

LevelWhat is sent
Inherit workspace defaultFollows the workspace telemetry level
Off (metadata only)No conversation content, metadata only
Redacted contentContent sent after the PII redactor runs
Full contentVerbatim content

The workspace default is Off (metadata only). The inherit row shows the resolved level, so you can see what an agent on "inherit" actually sends.

On this page