> For the complete documentation index, see [llms.txt](https://uzume-bot.gitbook.io/uzume/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uzume-bot.gitbook.io/uzume/privacy-policy.md).

# Privacy Policy

Operator: **Lemonical**. Effective date: **27 September 2026**.

## Scope

This policy covers data handled by the Uzume Discord bot. These documentation pages are hosted by GitBook, which processes website usage data under its [privacy policy](https://gitbook.com/docs/policies/privacy-and-security/statement).

## Data the bot handles

Uzume receives Discord events needed to respond to commands and chat. The bot stores feature data in PostgreSQL hosted on Railway:

| Feature      | Stored data                                                                                                                                                                                    |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Chat         | Prompt text, generated replies, Discord user IDs, usernames, display names, message IDs, channel IDs, conversation links and model response data used to continue a conversation.              |
| Quotes       | Quote text, the saving user's ID, timestamps, tags and available source details such as author, server, channel, message ID and source link. Votes and favorites are associated with user IDs. |
| Share energy | Server ID, giver and recipient IDs, the reason and timestamps.                                                                                                                                 |
| Dreams       | Server ID, submitting user's ID, submission text, visibility setting and timestamp.                                                                                                            |

Operational logs may also contain identifiers, error details and diagnostic information used to investigate faults.

## When chat content is processed

Outside threads, a message beginning with a mention of Uzume and containing text starts a conversation. Replying to a bot reply from that conversation continues it.

In a thread Uzume has joined, new nonempty human messages can be processed without a mention. Multiple people can participate. Replies use conversation context from the same channel.

The bot does not collect general channel history for AI chat. This does not mean ordinary messages are unavailable to Discord or to the bot's enabled message-content access.

## OpenAI processing

Uzume sends chat prompts and recent conversation context to OpenAI to generate replies. This includes each speaker's Discord user ID, username and display name, message IDs and the server name where applicable. Each request can include the latest 20 completed turns from that conversation. That context limit is not a deletion schedule.

The bot disables storage of the Response object in its OpenAI API requests. This does not guarantee zero retention by OpenAI. Its abuse-monitoring logs may retain content for up to 30 days or longer where legally required. See [OpenAI's API data controls](https://developers.openai.com/api/docs/guides/your-data).

The bot has no training or fine-tuning feature. OpenAI states that API data is not used for model training unless the customer opts in. OpenAI's processing is also subject to the API account's data-sharing settings and its published policies.

## Why data is used and who receives it

Data is used to answer chat prompts, keep conversations connected, save requested content, operate community features and investigate service problems.

Discord carries messages and interactions. Railway hosts the bot and its database. OpenAI receives the chat data described above. These providers process data to deliver their services. Authorized maintenance access may be needed to investigate faults or handle data requests.

Saved quotes are available to community quote commands across servers. Dream submissions are private by default; choosing to publish makes them available on the submitting server's board. Messages and replies remain visible to people who can access the Discord channel or thread.

The bot has no feature that sells data or builds advertising profiles.

## Retention and deletion

Stored chat history has no automatic expiry. Bot data is kept until removed through a supported feature, deleted by the operator or no longer needed to provide the service. Deleting a Discord message or removing Uzume from a server does not automatically delete its database records.

Quote removal and clearing hide records from active quote features. Undo is available for 24 hours, but the hidden records are not automatically purged when that window ends.

Each use of `/dream forget` deletes your latest dream submission in that server from the active database. Removing a favorite or vote deletes that association. `/prune bot` removes Discord messages only.

You can request access, correction or deletion by sending a Discord direct message to **@lemonical**. Include your Discord user ID and the data or feature involved. Requests are handled manually. Lemonical may ask you to verify that you control the account before providing or changing data.

Provider logs and backups may remain subject to the provider's retention settings. A database deletion does not erase messages already posted on Discord or copies other people have saved. Any limits affecting your request will be explained when it is handled.

## Security and contact

The current deployment uses an encrypted database connection. Railway documents encryption at rest for its storage. These measures do not eliminate every security risk.

For privacy questions or data requests, send a Discord direct message to **@lemonical**. For general support, use the [support server](https://discord.com/invite/S75qwND). Do not post private account details or sensitive content in public channels.

This page will be updated when data handling changes. The effective date identifies the current version.
