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

# Keeping what was said

> Saving, downloading, recaps and meeting transcripts.

## Nothing is kept unless you say so

Saving conversations is off to begin with. With it off, nothing is kept once you start a new
conversation, or leave for more than 30 minutes. Audio isn't recorded, except a meeting you record
for a transcript.

To keep them, turn on **Menu → Conversation → Save conversations on this device**. They stay on that
device, not in your account, and **Delete all saved conversations** clears them.

## Take the text with you

**Menu → Conversation** downloads, copies or shares the captions so far as text, whether or not
saving is on.

## Recap

**Recap**, on the captions so far, a saved conversation or a meeting transcript, has Claude write a
short summary: what was decided, who said they'd do what, and the details worth keeping, such as
dates, numbers, names and instructions. Say what it was, so the recap fits:

* **A conversation**: the main points and what was left open.
* **An appointment**: every instruction, medicine and next step, as given.
* **A class or talk**: its main points, in order.

A recap is written only when you ask, and kept with the conversation or transcript.

## A transcript of a meeting

**Menu → Conversation → Record a meeting** records the device's microphone until you stop, whether
or not captions are on. A timer at the top shows it's recording. Then it's sent to be transcribed,
and a few minutes later the transcript, with each speaker's turns and when they started, is under
**Meeting transcripts**.

* Only you and your account's owner see your transcripts.
* Readout doesn't keep the recording once it's sent. Before you send it, the app says which service
  will write the transcript, and whether that service keeps a copy.
* A recording can run up to about 3½ hours (about an hour in Safari).
* The recording is kept on the device until it's sent, so a reload doesn't lose it.


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