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

# Privacy

> Fleet's privacy model and what it means for your conversations.

## No accounts

Fleet requires no sign-up, no email, no password. You choose a username per session — it exists only in your browser's `sessionStorage` and is gone when you close the tab.

## No persistent storage

Fleet stores nothing on disk. All rooms and messages live in the server's memory. When the server restarts or a room expires, everything is gone.

There are no:

* Databases
* Log files containing message content
* Analytics on message content
* User accounts or profiles

## Ephemerality

Every room has a 30-minute TTL that begins when the last user leaves. This is enforced server-side — there is no way to extend a room's life beyond its TTL.

## What the server does see

While Fleet is privacy-focused, be aware that:

* The server processes all messages in-memory to relay them to other users in the room — it does not log them, but it does handle them
* IP addresses may appear in server logs depending on your hosting environment
* Room names are visible to anyone running the server process

## Self-hosting

For maximum privacy, [self-host Fleet](/self-hosting/docker) on infrastructure you control. This way you're the only one with access to the server process.