> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tawked.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Previews

> Keep a copy of every message an application sends for its 30 days: switching it on, who can read the copies, every view recorded, and reading a copy by API.

By default Tawked keeps no copy of a message's content once it is sent. An application can keep one: **Email → Settings**, **Keep a copy of each message**, by who manages the application's Email. Each message sent from then on keeps its subject, HTML and text (a template's rendered output), encrypted, for the message's 30 days. Attachments are never kept.

* **Who reads them:** the application's people who read the message log, in the message's window (HTML or text), and a key that manages Email, with `GET /v1/email/messages/{id}/content`. Tawked's team never reads them.
* **Every view is recorded** on the account's trail: by a person, and by a key with its prefix.
* **Turning it off** deletes every copy at once, and no message sent after that keeps one.
* **Backups:** the database's backups keep what was there for up to their own retention: 30 days, and 30 more for an older backup version.

A copy can hold what the message held: sign-in links, codes, personal data. Keep previews off on an application whose mail carries secrets, unless you need to see it.

## By API

`GET /v1/email/messages/{id}/content` answers `{ "id", "subject", "html", "text", "kept_until" }`, or `404 content_not_kept` when the message kept no copy. It needs a live key with `email:manage` (a test key with `email:send` reads its own test messages); a sending key limited to one domain never reads it. See [Sending email](https://docs.tawked.com/email/messages.md#read-what-was-sent).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.