1. Who this policy covers
This policy describes the handling of information by Tennessee Utilities, a Discord bot and associated management dashboard (collectively, the “Service”). It applies when the bot is installed in a Discord server, when you use its commands or interactive features, or when an authorized administrator uses the dashboard. Discord separately handles information under its own privacy policy.
2. Information processed
Depending on enabled server features, the Service may process Discord user, server, role, channel and message IDs; display names and basic profile information; relevant role and membership information; messages and content submitted to commands, suggestions, forms, or Components V2 messages; message content examined by configured automatic moderation; voting activity; account and server-join times used for anti-spam protections; moderation records, reports, reasons, and timestamps; session and staff participation information; configuration settings; and command-use, operational and error logs. Dashboard sign-in using Discord OAuth2 processes the Discord identity information needed for login and authorization. We do not ask for your Discord password.
3. Why information is used
Information is processed to provide requested bot features; run suggestions, moderation, security, sessions, voting, automations and builder messages; apply permissions and prevent abuse; let authorized server staff review records; maintain backups; troubleshoot errors; and operate the administrative dashboard. Only enable features and access data needed for the Service.
4. Visibility and disclosure
Suggestions, votes, published builder messages, session details, and some moderation notifications may be visible to members or staff of a participating Discord server, depending on the feature and server settings. Authorized server administrators can access applicable dashboard records. Data passes through Discord's APIs, our hosting infrastructure, and optional service providers or integrations configured for the server. Optional off-site backups may be transferred to the operator's configured storage endpoint. We do not sell personal data or use it for targeted advertising.
5. Storage and retention
The Service primarily uses a SQLite database, bot-managed JSON files, and operational log files on the operator's hosting. Command-activity and application-error records are designed to be deleted after 90 days by the scheduled cleanup job. Local backup rotation defaults to seven backups, configurable by the operator; separate off-site copies may have different retention. Other records, including suggestions, moderation cases, configuration, staff/session history and saved builder drafts, can remain until deleted by the operator or when no longer needed. The Service does not currently promise automatic deletion of all records when a bot is removed from a server. Requests for deletion are handled under Section 7; applicable legal or security retention obligations may limit a request.
6. Security
We use authentication, authorization checks, access restrictions and appropriate application safeguards intended to protect stored information. Secrets used for bot access and dashboard login are held in server-side configuration, not published as page content. Optional off-site backup uploads support encryption when properly configured. No system is completely secure. The operator is responsible for securing hosting, storage, backups and administrator access.
7. Your choices and deletion requests
You may stop using the commands, ask a server administrator about enabled features, or remove the bot from a server if you have the required permissions. You may request access, correction, or deletion of data associated with your Discord account by contacting the operator using the contact method below and providing your Discord user ID and the relevant server ID (if applicable). Do not submit passwords, tokens, or sensitive identity documents. We may need to verify that you control the relevant account. Some records may also be managed by server administrators. We will review requests under applicable law and Discord's developer requirements.
8. Age and sensitive data
The Service is intended for Discord users who meet Discord's minimum age requirement in their jurisdiction. Do not submit payment card data, account passwords, health information, or other sensitive personal information through suggestion forms, builder inputs, or commands. The Service is not designed to intentionally collect such information.
9. Changes
This policy may be updated when the Service changes. The effective date on this page will be updated for material revisions. The current policy will be accessible through the public URL listed in Discord's application profile.
10. Contact
Operator/privacy contact: [REPLACE WITH YOUR SUPPORT EMAIL OR PUBLIC SUPPORT SERVER LINK BEFORE PUBLISHING]. Use this contact to report privacy issues, request data deletion, or ask questions about the Service. Do not publish this document until a working contact method has been supplied.