Good Night Music Bot Privacy Policy

Current prefix commands use message content to identify the command and resolve the music link or search text you provide. Processing a command does not mean that all conversation is archived, but message-derived values can appear in diagnostic logs when a request fails.

There is currently no per-user setting that opts you out of message-content processing. You can stop submitting requests and contact staff about stored data. Server administrators can restrict the bot's access through Discord channel permissions or remove it from the server. These choices do not automatically delete existing logs.

Automatic requests from music-sharing channels and role-based DJ updates are proposed features. They have not been implemented. This policy does not describe them as currently collecting data or performing actions.

• The proposed request feature would read supported music links in administrator-selected channels, associate a post with an unplayed queue entry and respond to edits or deletions. It would need the message, requester and channel identifiers and the music link.
• The proposed DJ feature would use configured role identifiers, member identifiers and hosting assignments to respond to role changes made in Discord or a member leaving the server. It would not require presence or activity tracking.

Before either feature is enabled, we will update this policy to describe its actual scope, storage, retention and user controls. Generated interface concepts are illustrations of these plans, not records of a working feature.

Queue and playback records are used to manage their listening sessions. Temporary panel routing records are eligible for cleanup after about one minute when the cleanup routine runs; this is not a guaranteed deletion deadline. Room ownership records are released as sessions end, but stale records can remain after interrupted operation.

A fixed maximum retention period for all music-bot files, diagnostic logs and backup copies has not been established and verified. Logs can remain after a listening session ends. We do not currently guarantee that all API data or message-derived data is deleted within 30 days. Proposed seven-day logging or backup limits are not current guarantees.

You can request access, correction or deletion through the contact process below. Staff will review the request and explain what can be removed and any relevant limitations, including records still needed to operate the service or address a legal or security issue. This policy does not promise a deletion deadline or backup expiry period that has not been put into operation.

Use the Good Night contact form, select “Privacy request” and use the subject “Himiko data request”. Include your Discord user ID, application ID 1039688984340742144 and whether you are requesting access, correction or deletion. Keep the reference issued after an accepted submission so staff can locate your request.

You can also contact staff through a support ticket in the Good Night Discord server. Staff may need to verify account ownership before releasing or removing records. Do not send passwords, Discord account tokens or other login credentials in a privacy request.

The music features use links and search text to resolve tracks and operate playback. Training or fine-tuning machine learning or AI models with Discord message content is not an authorized use of this service's data. Autoplay track selection does not authorize using your messages for model training.

The bot is intended for users who meet Discord's minimum age requirements in their country. It is not intended for children below that minimum age.