Snoozer Bot Central / Privacy draft
Operator review required. This is an operational draft for review by the operator, not legal advice. Confirm that it matches actual bot operation and applicable requirements before treating it as final.
The public-facing operator name is Snoozer Bot Central. This is not a statement that a legal entity exists. This draft describes the Snoozer Bot Central static website and the separate, locally operated Snoozer bot.
The website
The website's own code does not set cookies or use localStorage, sessionStorage, analytics, advertising, or third-party trackers. The cookie notice's dismiss action changes only the current page's in-memory DOM; it saves no preference and may reappear on another page or after a reload.
The site has no contact form, account, external font, or embedded third-party content. GitHub Pages may process ordinary request and security logs under GitHub's own terms and arrangements. Those infrastructure operations are separate from browser storage or analytics implemented by this site.
If an operator configures a public status endpoint, a browser visiting the status page requests the configured URL to retrieve status JSON. The endpoint operator and infrastructure may receive ordinary request metadata. The request omits browser credentials and contains no bot token. The status values are intended to be public. If no endpoint is configured, this site cannot verify live bot status.
Bot data handled locally
The bot is separate from the static website. It saves its private configuration, including the user-provided Yapper API token, in a locally controlled config.json file. Runtime state is saved in a locally controlled data/state.json file. These files are not part of the published website.
Depending on which commands and features are enabled, runtime state may include server settings, user IDs, moderation records and private moderator notes, reminders, poll and giveaway entries, activity XP, Snoozer Coins, and AFK state. The records present depend on use and server configuration. The bot relies on Yapper for platform permissions, actions, and account/server information.
A server manager can configure an event-log channel with /setlogchannel. Snoozer posts event payloads there, including message contents when supplied by Yapper, and existing moderation case logs. The current Yapper bot event API provides messages, member joins/leaves, reactions, voice joins/leaves, interactions, and test events; it does not provide every action (including message edits/deletions or role/channel changes), so these logs are not a complete audit trail. Snoozer skips its own messages and messages posted in the configured log channel to prevent recursive logging. Logs are sent as messages to Yapper and can be read by people with access to that channel; the bot does not add these event payloads to its local state file. Server operators should restrict the channel appropriately and inform members about message-content logging.
The bot operator controls the local machine and its files. This site does not receive or store the bot's local state file or configuration. Do not post tokens, private notes, or state files in community support.
Choices and questions
For questions about the site or community bot, the stated contact route is the Snoozer Bot Central Yapper community. No email address, postal address, deletion process, or response-time commitment is published here. The operator should review requests in light of the relevant platform, local bot operation, and applicable requirements.