Talqing keeps call and conversation content forever by default. Setting retention_days on the workspace makes each call’s content delete itself after that many days; the call record and its billing survive. You can also erase a single call at any time.

​
The retention policy

The deadline is fixed when a call ends, from the policy at that moment: ended_at + retention_days. A chat’s deadline counts from when the chat ends; an open chat is never purged. Changing the policy never moves a deadline already set, so shortening it does not delete existing calls sooner and lengthening it does not save calls already scheduled. To remove older calls sooner, delete them yourself.

​
What a purge deletes

Once every call in a conversation is purged, the conversation is deleted, and once a contact has no conversations left the contact record goes too. That contact’s userdata is the agent’s cross-call memory, so the next call from that person starts as if they were new. See conversation memory.

​
Task runs

The same policy covers task runs: each run’s content is deleted retention_days after it ends. That is its inputs, its files and the page images rendered from them, its output, its trace, its stored config and its error message. The run record stays with its status, error type, metadata, timings, usage and cost. DELETE /v1/task-runs/{run_id}, or POST /v1/task-runs/delete by metadata, does the same at once.

​
Deleting a call now

DELETE /v1/calls/{session_id} runs the same purge immediately. EDITOR or ADMIN.
It answers 202 and normally completes within seconds. A call still in progress is refused with 409; retry once it has ended.
This cannot be undone and removes the transcript as well as the audio. To delete only the audio, use DELETE /v1/calls/{session_id}/recording. See recordings.

​
Deleting a conversation now

DELETE /v1/conversations/{conversation_id} erases a whole thread: it purges every call and chat in it, and deletes the items posted outside any session (templates, notes, instructions), which a call purge alone can’t reach when a thread has no sessions. The contact and its userdata go once it has no conversations left. To erase everything about a person, list their threads with GET /v1/conversations?contact_key=…&status=all and delete each. EDITOR or ADMIN; 202, and 409 while a call or chat in it is still open (end a chat with POST /v1/chats/{chat_id}/end first).

​
Recording and the recording notice

Voice and video agents record by default: one stereo file per call, caller and agent on separate channels. recording.enabled: false on the agent turns it off; there is no per-call or per-number switch. recording.notice makes the agent announce it, uninterruptibly, where the greeting places {{recording.notice}}. There is no tool for a caller to stop a recording mid-call; delete it afterwards if you need to. Whether recording is lawful where your callers are is yours to determine. Full detail is in call recording. An agent task entered mid-call cannot pause the recorder, so anything said during it is recorded. Do not build card capture on one.

​
Where data lives

A call’s region comes from its phone number, its stream connection, or the region on a web call token. +91 numbers are always in; WhatsApp calls are always us. An in call’s audio stays in India while it runs, but what is stored afterwards is in the United States.

​
Model providers and BYOK

Every model runs on your provider accounts, so the content those providers see is governed by your agreement and settings with them (data retention, training opt-outs). Talqing has no separate arrangement with them on your behalf. OpenRouter is a gateway that forwards each request to one of many independent hosts, possibly in different countries, chosen per request.
  • LLM requests carry OpenRouter’s strictest data policy (data_collection: "deny"), excluding hosts that may store or train on prompts. A model with no compliant host fails with a message saying so.
  • Speech-to-text requests cannot carry that policy, so audio goes to whichever host OpenRouter picks under your account settings. If that matters, turn off training in your OpenRouter privacy settings or use an STT provider you contract with directly.
If inference must stay in one jurisdiction, use a provider you hold the account with directly. Talqing’s own model keys are used only for the CoPilots and for browsing voice and avatar galleries before you add a key; see provider keys.

​
Certifications

Talqing holds no compliance certification or audit report, and nothing here is a legal assurance. For procurement or legal questions, email hello@talqing.com.

​
Next

Call recording

Defaults, the recording notice, and deleting audio on its own.

Workspaces and roles

Who can change the retention policy.