> ## Documentation Index > Fetch the complete documentation index at: https://docs.emanate.ai/llms.txt > Use this file to discover all available pages before exploring further. # Data Retention > What Emanate reads, what it keeps, and how long it keeps it Emanate reads more than it keeps. This page separates the two, so you can see exactly what ends up stored and what was only ever looked at while a piece of work was being done. ## What is read Reading happens against the systems you connect, using the access you granted, and always as the user who approved the connection. Emanate sees what that user sees and nothing beyond it. | Source | What is read | | - | - | | Email | Messages in the mailboxes you connect, so threads can be ranked, filed and replied to | | CRM | The objects and fields chosen when the connection was set up. See [CRM integration](/integrations/crm) | | ERP | Order history, pricing and availability, when **Allow ERP lookups** is on | | Documents | Only the folders you explicitly shared through a [document storage connection](/integrations/csm) | | Attachments | The files on an email being replied to, when **Use attachments** is on. See [Attachments](/trust-security/attachments) | Anything you have not connected is not read. Any source switched off is not read. ## What is stored | Data | What is kept | How long | | - | - | - | | Email | A copy of the messages in your connected mailboxes, so pages load without calling your provider every time | While your agreement is active | | Companies and contacts | The records brought across from your CRM and ERP | While your agreement is active | | Deals, meetings and logged calls | The records brought across from your CRM | While your agreement is active | | Attachment text | A short extract, capped at roughly 8,000 characters per file, so the same file is not opened twice | While the email it belongs to is kept | | Attachment files | Nothing. The file stays in your mailbox and is never copied into Emanate | Not stored | | Images on an email | Nothing. An image is looked at while the draft is written and not retained | Not stored | | Unused AI drafts | The draft sitting in your Drafts folder | 3 days by default, then removed | | Voice call recordings | Nothing. Recordings stay with the voice provider and are fetched by link when you play one back | Not stored | | Connection event records | The technical record of a sync or webhook. The message contents inside it are cleared after 90 days | 90 days for contents | ## Unused drafts The one retention window you control directly is how long an AI draft you never used sits in your mailbox. The default is **3 days**, which covers a weekend and little else. Under **Tactics → Agent Inbox → Settings** you can set anything from 1 to 30 days, or switch the clean-up off entirely and keep every draft until you deal with it yourself. Two things are never removed: * **A draft you edited.** The moment you change a word it stops being an AI draft and is left alone permanently. * **Anything you sent.** Clean-up only ever touches drafts that were never used. If Emanate cannot tell whether you edited a draft, it leaves it alone and checks again the next day. The uncertain case always falls on the side of keeping it. ## Deletion Data is retained while your agreement is active. On request, or at termination, it is deleted. Disconnecting a source stops all further reading from it immediately. Records already brought across stay until they are deleted, so ask if you want a disconnect to remove them as well. Switching off a feature is not the same as deleting what it produced. A switch stops the work from happening again. It does not erase what was already done, which is deliberate, so that turning something off for a week does not destroy a month of history. ## Next steps Where data lives and how it is protected Controlling what an agent can see Turning attachment reading on and off Certifications and controls This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.