> For the full page index, fetch https://echonova.ai/llms.txt # Data retention What an agent stores, which region it is stored in, how long it is kept, and exactly what each delete removes. Your content is kept until you delete it. Developer API request logs are kept for 12 months. In-app notifications and webhook delivery records are kept for 30 days. This page lists what is stored, which region it is stored in, and exactly what each delete takes with it, so you can answer a security questionnaire from it. ## What is stored | Thing | What is kept | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Agent configuration | Name, description, status, system prompt, first message, the voice list, the model and its reasoning setting, retrieval settings, database tool settings, the knowledge and tool selections, working hours and time zone, and who created and last changed it | | Knowledge files | The uploaded file itself, with its display name, original filename, media type, size in bytes and status | | Website sources | The address you crawled, the crawl status, and the text extracted from the page for retrieval | | Conversations | The agent, the channel, the customer name and contact id when the channel supplies one, start and end times, how it closed, turn counts, prompt and completion tokens, characters sent to text to speech, seconds of audio sent to speech to text, credits charged, the model that served it, which tools it called, the tags you set, and the summary when the agent writes one | | Transcripts | One message per side of each turn: direction, sender, message type, the words, the delivery status, and the per-turn measurements | | Analytics | Hourly counts and sums only. No words, no names, no contact ids | | Tools | The tool's definition. Credential values are not held on the tool | | Secrets and auth connections | The name and the metadata in clear, the value encrypted | | Database connections | The connection string, encrypted. See [Database tool security](/docs/agents/database-tools-security) | | Developer API request logs | Method, path, status code and response time per call. No body, no headers, kept for 12 months | | In-app notifications | The notification text, kept for 30 days | There is no audio. A voice conversation records how many seconds of audio went to speech to text, as a number, and the transcript records the words. No recording of a call is kept. [Transcripts and summaries](/docs/agents/transcripts-and-summaries) covers what each turn records in detail. ## Where data lives There is one region. Everything above is stored in `eu-north-1`, and a workspace cannot choose a different one. | Data | Detail | | --------------------------------------------------------- | ---------------------------------------------------------------------------- | | Uploaded files | Kept as files in `eu-north-1` | | Secrets, auth connections and database connection strings | Encrypted with a key held in the same region, with automatic key rotation on | | Everything else | Kept as records in `eu-north-1` | Uploads and downloads go through a link that works for a short time only. The name you see in the portal is the name you uploaded. ## How long it is kept Agents, conversations, transcripts, analytics, knowledge, tools, secrets and database connections are kept until you delete them. Developer API request logs are kept for 12 months. In-app notifications and webhook delivery records are kept for 30 days. Storage therefore grows until you prune it. Knowledge files count against the workspace storage allowance, so deleting a file you no longer need is what gives the allowance back. ## Automatic timeouts Some records are closed or moved on after a timeout. None of this is a retention policy: it moves a stuck item on, and in one case removes a source whose file never arrived. | What | After | What happens | | ------------------------------- | ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | A source stuck at **Uploading** | 10 minutes, checked every 5 | If the file arrived, the source moves to **Uploaded**. If it did not, the source is removed and its reserved storage is released | | A source still indexing | 1 hour, checked every 10 minutes | The source fails with `Indexing timed out. Try again.` The source and its file stay | | The workspace storage figure | Every hour | It is re-checked against the real sum of your file sizes and corrected. No file is touched | | An idle text conversation | 15 minutes with no activity, checked every 5 | A playground chat closes. A channel conversation stays open for the next inbound message | | An idle voice call | 30 minutes with no charged turn, checked every 5 | The call ends and closes with a timeout reason | | A stalled build or speech job | Checked every 5 minutes | A build with AI that got no answer fails with `Agent design timed out. Try again.` A text to speech or speech to text job that timed out fails and is refunded | The stuck-upload check is the only one that removes anything, and only when the upload never completed, so there is no file to keep. ## What each delete removes ### Archiving an agent Archiving does not delete, and there is no delete. The portal's control is **Pause Agent**. The agent, its conversations, its transcripts, its analytics and its knowledge and tool selections all stay, and the agent can be restored. [Agent status](/docs/agents/agent-status) covers what archiving stops. ### Deleting a knowledge source This is a real delete. The stored file is removed, the workspace storage allowance is credited back, the source is unselected from every agent that used it, the agent's indexed copy is dropped, and the source is removed from the library. The portal's confirmation says so: **This removes the source and frees its storage. This can’t be undone.** The indexed copy is removed within 30 days. [Add documents to the library](/docs/agents/knowledge-documents) covers the upload side. ### Deleting a knowledge folder The same steps run for every source inside it, then the folder is unlinked from every agent and removed. The confirmation counts the sources it is about to take with it, and warns that the folder and those sources are permanently deleted, removed from any agents using them, and cannot be brought back. ### Deleting a tool The tool goes, along with the operations of an imported OpenAPI tool and the agent's index of them, and the tool is unselected from every agent. An auth connection the tool used is reusable and is left alone. ### Deleting a database connection The agent's copy of the curated questions is dropped, then the connection and its questions are removed. Nothing is deleted on your database. [Database tool security](/docs/agents/database-tools-security) has the detail. ### Deleting a secret or an auth connection The record and its encrypted value go, and the delete is refused while a tool still references it. See [Workspace secrets](/docs/agents/secrets) and [Auth connections](/docs/agents/auth-connections). ### Deleting a conversation tag The tag is removed from every conversation that carried it, then the tag itself is removed. The conversations are untouched. ### Deleting a conversation Open the conversation and press **Delete**, then **Delete** again where it asks **Delete for good?**. The conversation and its transcript leave the workspace at once, our live systems within 30 days and our backups within a further 35 days. Analytics counts do not change. Deletion is final. A conversation that is still open, or ended less than 15 minutes ago, cannot be deleted yet; try again later. ## Deleting a workspace Only the workspace owner can delete a workspace, and the workspace created at sign-up cannot be deleted. To have one deleted, write to privacy@echonova.ai from the owner's account with the workspace name; see [Workspaces](/docs/account/workspaces). Closing your account deletes every workspace you own the same way, 30 days after closing. > [!WARNING] > Deleting a workspace deletes everything in it, and it cannot be undone: > agents, conversations, transcripts, knowledge, uploaded files, tools, secrets > and analytics. They leave our live systems within 30 days and our backups > within a further 35 days. Invoices and payment records are kept as long as UAE > law requires (5 years). ## Get it right Storage and retrieval both follow the library, not the agent. Remove content from the library when it is obsolete. **Recommended** - Delete an outdated policy from **Knowledge base**. Every agent stops using it, the file is removed and the storage comes back. - Archive an agent you no longer run, and delete the sources only it used. **Less effective** - Unselecting the source from one agent and leaving it in the library, where it keeps its storage and stays available to every other agent. ## What you can ask for The portal gives you back one thing directly: the original of a knowledge file, through **Download** in the source row, as a short-lived link. For a copy of your data or early deletion, write to privacy@echonova.ai with the workspace name and the ids involved. **Copy ID** on a conversation gives you its id. ## FAQ ### Is call audio recorded? No. A voice conversation keeps the number of seconds transcribed and the words. There is no recording. ### Which region is my data in? `eu-north-1`, for every workspace. ### Are secrets and database connection strings encrypted? Yes. The value is encrypted with a key held in the same region, with automatic rotation on, and the portal never shows the value again after you save it. ### Does archiving an agent delete anything? No. Archiving keeps the agent, its conversations, its transcripts and its analytics, and the agent can be restored. ### Can I delete a conversation myself? Yes. Open it and press **Delete**; see [Deleting a conversation](#deleting-a-conversation). ### How long are conversations kept? Until you delete them or close the account that owns the workspace. There is no expiry. ## Related - [Database tool security](/docs/agents/database-tools-security): how a connection string is protected - [Workspace secrets](/docs/agents/secrets): what a secret keeps and what deleting one does - [Auth connections](/docs/agents/auth-connections): the same for credentials - [Transcripts and summaries](/docs/agents/transcripts-and-summaries): what each turn records - [Find and read a conversation](/docs/agents/conversations): where **Copy ID** is - [Add documents to the library](/docs/agents/knowledge-documents): the upload side of a knowledge file - [Agent status](/docs/agents/agent-status): what archiving keeps and stops - [Request logs](/docs/developers/request-logs): what a developer API call records