What draften stores, where it lies and who sees it.
In draften's database
| What | Note |
|---|---|
| organisations, people, roles, access | members' e-mails and names |
| mailboxes and assistants | addresses, settings, instructions with all their versions |
| knowledge sources and attachments | uploaded documents including their extracted text, attachment files |
| messages | sender, subject, time, how the assistant sorted them and why, hidden texts found |
| drafts | the draft text, versions after revision, the difference against the sent version, the evaluation |
| learning | lessons and knowledge corrections with "before and after" examples |
| trial set | saved messages with their text and thread |
| new-assistant wizard | for each run, the description of the chosen threads (topic, kind, tone, verbatim quotes from your replies — greeting, sign-off, apology — and facts you state in them, such as prices, deadlines and contacts), an anonymised description of how you write, up to ten of your replies with a shortened query (addresses masked) and the texts of the trial: an excerpt of the query, your reply, the draft and its evaluation |
| records | mail checks, events, requests, change history |
So the database also holds customers' names and mail content. For the draften service the operator runs it; in an installation on your own server it is with you and reachable on the network only inside the installation.
What is encrypted
Secrets are encrypted in the database (AES-256-GCM) with MASTER_KEY, which is not in the database:
- model API keys,
- mailbox access (registration secrets, service account keys, tokens of connected accounts, IMAP passwords),
- access details for connected systems (CRMs),
- clients for signing in with Microsoft and Google,
- the password or API key of the mail sender.
A secret is never shown in the interface once stored, and it is not in the change history either. Users' passwords are stored only as a hash (argon2id).
On your own installation, MASTER_KEY can be replaced without an outage; everything stored is then encrypted again with the new key — see Backup and restore.
What is not stored
- Whole incoming messages are stored nowhere — a message keeps only its sender, subject and how the assistant sorted it, and the wizard keeps only the excerpts and your replies listed in the table above, which are deleted after the data retention period too.
- Data from connected systems is not stored — the assistant reads it while writing a draft; the log holds only the tool's name, not whom it asked about.
- Sent mail is not stored whole, only the text of the sent reply, for comparison with the draft.
What goes out
To the language model provider (Anthropic by default) go, during triage and writing, the content of the message and the thread, the instructions, the knowledge sources and data from connected systems. With OpenAI store: false is sent; still, with sensitive data check the provider's retention terms. With a local model on your own server, mail never leaves the server.
draften sends nothing else anywhere; e-mails go out only as invitations and notices through the configured mail sender.
How long the data is kept
The operator sets the data retention (Installation → Installation, the Data retention card): 90 days by default, 30 to 3,650 days, or "Never delete". Once a day, whatever is older is then deleted in every organisation:
- messages (sender, subject, headers),
- drafts with their first text, the sent reply and the difference against it, and their revisions by instruction,
- the records of mail checks (except the assistant's last good run), the worker's daily logs and the draft text inside old error events,
- the wizard's verbatim texts: your replies used to write the instructions, the texts of the trial and the quotes and facts in the thread descriptions,
- ended jobs (done and failed); a job that is waiting or running stays, however old.
What stays:
- lessons and knowledge corrections in full, with their "before and after" examples,
- the instructions, the wizard's findings and proposals and the description of how you write,
- the trial set with its results, until you delete it,
- events (for a revision the instruction, not the draft text) and costs.
Draft evaluations go with the drafts, so the overviews offer only periods the data still covers. Shortening the period asks for confirmation, because older data is deleted for good at the next clean-up. The database dumps in the backups/ folder of an installation of your own are not affected.
After the update that brings data retention, the first clean-up runs only 24 hours later: the operator has a day to set the period (or choose "Never delete") before anything is deleted.
Who sees what
- An organisation member sees only the mailboxes they have access to.
- The operator (superadmin) cannot see inside organisations — only their name, bindings, owners and size.
- The change record (who changed what) is read by the organisation's owners and managers.
Deletion
An organisation is deleted by the operator, and only a suspended one: it goes with everything in it (mailboxes, assistants, messages, drafts, keys, settings, change history). The accounts of people who were only in this organisation are deleted too; anyone who is a member elsewhere as well, or has access to a mailbox in another organisation, keeps their account.
A mailbox with no assistant on it is deleted by an owner or manager of the organisation: it goes with its access list, its mail access, the mailbox's API keys and its integrations. The mail in the mailbox at Microsoft, Google or on the IMAP server stays as it is.