Platform
Your data
The short version#
This page is written for anyone, technical or not. It says what we keep about your calls, for how long, and how you remove it.
- We do not keep the sound of your calls. When you ask for a recording, your own phone company makes it and keeps it in your own account. We keep only the reference that points to it.
- We keep the words of a call only if you switch transcripts on, and then for 90 days at most. After that they are deleted automatically.
- Chat messages delete themselves: 24 hours after they arrive, or after your agent's transcript period when you keep transcripts.
- Zero retention keeps none of the conversation. Switch it on for a project and we keep no transcripts, summaries or recording references of its calls, and its chat messages only for the 24-hour reply window. The call record your bill needs stays.
- We keep a record of every call: when it happened, the phone numbers, how long it lasted, what it cost, and the short summary your own AI wrote. It is your bill and your call history.
- Your keys are locked away. AI and phone-company keys, and the headers of your MCP servers, are stored encrypted and never shown again. Project API keys are stored only as a one-way fingerprint, so nobody can read them back, us included.
- Your account stays until you ask us to close it. Write to dev@dvaarik.com.
What we keep, item by item#
| Item | What we keep | For how long |
|---|---|---|
| Call audio | Nothing. With record_calls on, your phone company records the call in your own account and we keep its reference with the call record | The audio: as long as your phone company keeps it |
| Browser calls | No recording at all: no phone company is involved | Nothing to keep |
| Transcript (the words said) | Only when store_transcript is on | 90 days at most, less if you set a lower retention_days; then deleted automatically |
| Call summary | The short notes your own AI model writes after a call, when you set up insight_config | Kept with the call record after the transcript is gone |
| Call record | Time, duration, the two phone numbers, cost, outcome, the agent and its version, the models used, and your own metadata (up to 2 KB) | For as long as your account exists, then as accounting law requires |
| Saved agent | Its settings and prompt, because you asked us to keep them | Until you delete the agent (see below) |
| Transfer list | The names, phone numbers and notes you gave an agent's transfer destinations, saved with the agent. Transfer events carry the name, never the number | Until you remove them or delete the agent (see below) |
| Hand-off list | The names, the agents they point to, when to hand over and the first words you gave an agent's hand-off destinations, saved with the agent | Until you remove them or delete the agent (see below) |
| Hand-off record | On a call that was handed between agents: which agent held it from which second to which, the reason the previous agent gave (at most 200 characters) and how each part ended | Kept with the call record |
| MCP servers | Each server's name, address, tool names and time limit, saved with the agent; its headers encrypted, never shown again (a read shows the last four characters only). Calls record the names and addresses, never a header | Until you remove the server or delete the agent; removing headers erases them |
| MCP tool lists | The tool names, descriptions and input schemas a server listed, so calls start at once. Never a header, never a tool's arguments or results | 15 minutes |
| A call's prompt while it runs | A working copy in short-lived memory | 15 minutes at most |
| Outbound call request | The prompt and greeting until the call is placed, then they are removed | A small receipt (numbers, agent, time) stays 120 days so a repeated request never rings the same person twice |
| Call list | The people you uploaded: phone number, the columns that fill your agent, your other columns, and how each call went | Until you delete the list; deleted automatically 90 days after it finishes or is cancelled, and a list you never started is deleted 90 days after you last changed it |
| Do-not-call list | The numbers you asked us never to call, with a note if you gave one | Until you remove them |
| Knowledge document | The text you uploaded or pasted, its name and its size. For a PDF, only the text read from it: the PDF file itself is never stored | Until you delete the document or its knowledge base |
| Knowledge passages | The pieces of each document that search reads and, with meaning search, the vectors your own Google or OpenAI account made from them | Replaced when the document changes; deleted with the document |
| A question asked of knowledge | Not kept. With meaning search, its vector is held in short-lived memory under a key that does not contain the words | 2 minutes at most |
| Chat messages | What a person wrote and the agent's replies, with each reply's status, cost, tokens, model and the actions it ran. Attachments are named, never stored | 24 hours after each message arrived; with store_transcript on, the agent's retention_days (90 days at most). Then deleted automatically |
| Chat conversation | Who it is with (the name and id Telegram, WhatsApp, Instagram or your app gave), the agent, your variables and metadata | Deleted with its last message |
| Telegram bot | Its name, the bot's id and @username, the agent and its limits; the token encrypted, never shown again | Until you disconnect it; disconnecting erases the token |
| WhatsApp number or Instagram account | Its name, the phone number ID with its number and verified name (or the Instagram account id and @username), the WhatsApp Business Account ID, whether your app is subscribed, the agent and its limits; the access token and app secrets encrypted, never shown again | Until you disconnect it; disconnecting erases the token and the secrets |
| What WhatsApp says about a reply | Sent, delivered, read or failed, with the time; never anything else from the phone | Kept with the reply, deleted with it |
| Delivery receipts | Ids only, never the words, so a message Telegram or Meta sends twice is answered once | 7 days |
| Agent test | The test you saved: its name, the caller you described, the values and action answers you gave, and its checks | Until you delete the test |
| Test result | The typed chat, how each check went, the tokens used and which model ran it | 30 days, then deleted automatically |
| Unsaved changes you test | The job, first words, variables or actions you tried without saving | Only with that run, until it finishes; never saved to the agent |
| AI and phone-company keys | Encrypted, never shown again after you save them | Until you disconnect the account; disconnecting erases the key |
| Project API keys | A one-way fingerprint, never the key | Until you revoke the key |
| Webhooks we delivered | The event we sent, without the words of the transcript or the signing secret | 7 days |
| Webhooks we could not deliver | The same, so you can see what was missed and why | 120 days |
| Your account | Name, email, company details, sign-in records | Until you ask us to close the account |
| Billing | Top-ups, charges and invoices | As long as accounting and tax law requires |
With zero retention on#
Zero retention is a switch on each project, off by default. While it is on, for the calls, chats and tests that start after you turned it on:
| Item | With zero retention on |
|---|---|
| Call record | Kept as above, because it is your bill and your call history: times, length, numbers, cost, status, end reason, counts and speed. The end reason is a code (agent_ended when the agent hung up), never the agent's own words |
| Transcript | Never stored, whatever the agent's store_transcript says |
| Call summary | Never written, whatever the agent's insight_config says |
| Call audio | Your phone company is not asked to record, so there is no recording and no reference |
| Tool arguments and results | Never stored |
| Hand-off record | Which agent held the call when, and how each part ended; never the reason |
| A question asked of knowledge | Not kept, not even in short-lived memory |
| Chat messages | 24 hours after each was written (the reply window), then deleted, whatever the agent's retention_days says. A reply keeps the names of the actions it ran, never what went in or came back |
| Test result | Each check's result, the counts and the tokens; never the chat or a judge's reason |
| Webhooks | Still sent, live. The copy we keep until it is delivered has no transcript, message text or reasons |
What was stored before you turned it on stays until it expires, or until you delete it (below). Who turned it on or off, and when, is kept on the project.
What other companies keep#
During a call, the audio and the text go to the AI providers you connected, on your own accounts, and the call itself runs through your own phone company. They keep what their own terms say, and they bill you directly. Check their data settings for your region and for the people you call. With meaning search on a knowledge base, its documents and the questions asked of it go to the Google or OpenAI account you chose for it. A Telegram chat also passes through Telegram, and a WhatsApp or Instagram chat through Meta, on your own Meta app; each keeps what its own terms say. An MCP server you connect receives what the agent sends its tools during a call, and keeps what you decide.
How to remove things#
- A transcript, before its 90 days are up: call
DELETE /v1/calls/{call_id}/transcriptwith a project API key. It is gone at once. - A recording: delete it in your phone company's account. We never held the audio, so there is nothing for us to delete.
- A saved agent: delete it in the console or with the API. If it never took a call, it is erased. If it did, it is switched off and kept, prompt included, so your past calls still show which agent and version answered. Write to us to erase it completely.
- An AI or phone-company key: disconnect the account. The stored key is erased; the provider's name and the dates stay, for your own audit trail.
- A project API key: revoke it. It stops working at once.
- A call list: delete it in the console or with
DELETE /v2/call-lists/{list_id}(pause or cancel it first). Everyone on it is erased at once. - A number on your do-not-call list: remove it there. Nothing else is kept.
- An agent test: delete it under Test it on the agent, or with
DELETE /v2/agents/{agent_id}/tests/{test_id}. Its results go with it. - A chat: its messages delete themselves after 24 hours, or after the agent's
retention_dayswhen it keeps transcripts. To erase them sooner, delete the project's stored conversations (next). - Everything a project stored of its conversations, at once: press Delete stored conversations on the Projects page, or call
POST /console/v2/projects/{project_id}/stored-conversations/deleteuntil it answersdone: true. It deletes transcripts, summaries and extracted fields, recording references, chat messages, test runs' chats, hand-off reasons and the stored bodies of webhooks already sent. Call records and billing stay. A reply still being sent, a webhook still being delivered or a test still running is left for a later try. - A Telegram bot, a WhatsApp number or an Instagram account: disconnect it on the Chats page or with
DELETE /v2/chat-channels/{channel_id}. Its token and secrets are erased at once. Your Meta app keeps sending to our callback URL until you change it there; those messages are refused and never stored. - A hand-off destination: remove it on the agent, or save
handoff_destinationswithout it. - An MCP server or its headers: remove it on the agent, or save
mcp_serverswithout it ("headers": {}removes only its headers). Its headers are erased at once. - A knowledge document or a whole knowledge base: delete it on the Knowledge page, or with
DELETE /v2/knowledge-bases/{base_id}/documents/{document_id}orDELETE /v2/knowledge-bases/{base_id}. Its text and passages are erased at once, and agents stop using it. - Your account, projects and call records: write to dev@dvaarik.com. We confirm it is you before deleting anything, and we tell you what the law makes us keep, such as invoices.
What our own logs contain#
Our servers log what happened and to which call or project: identifiers, timings and outcomes. They do not log your prompts, your keys, or what anybody said on a call.
The privacy policy is the legal version of this page.
Use one project per boundary
Provider secrets stay encrypted and project API keys stay on your server.