serenity1. Who handles your data
This Privacy Policy explains how the Serenity bot operator (“we” or “us”) handles personal data when you interact with Serenity on Discord, use its features, submit feedback, or contact support. The operator is responsible for the data held in Serenity’s own storage and can be contacted at niftyserenitybusiness@gmail.com. Support is also available through Serenity Support on Discord.
Discord operates its own platform and processes information under its Privacy Policy. Server administrators separately decide how to configure their servers and who can access server messages. This policy covers Serenity’s processing; it does not control Discord’s processing or every action taken by independent server staff.
The data handled depends on the features you use, the features enabled in a server, and the permissions granted to the bot. Serenity does not need your Discord password, authentication token, or payment-card details.
2. Data Serenity accesses or stores
| Feature or context | Information handled | Purpose |
|---|---|---|
| Discord identity and settings | User, server, channel, role, and message IDs; usernames, display names, avatar references, membership and permission information; language, prefix, theme, and relevant configuration. | Identify the right user and server, enforce permissions, and apply preferences. |
| Commands and interactions | Command text and arguments, button or menu choices, form submissions, timestamps, cooldowns, and feature-specific action records. | Perform requested actions, prevent abuse, and operate interactive features. |
| Moderation and server security | Actor and target IDs, action and reason, warnings and cases, timestamps, outcomes, audit-log evidence, incidents, and relevant role or channel configuration snapshots. | Moderate servers, detect configured security events, and preserve accountability. |
| Message and event logging | Available message content, edits and deletions, author identity and avatar reference, attachment names and URLs, IDs, and relevant server events. | Send the logs configured by server administrators. Content available in the bot’s temporary cache can appear in edit/delete logs. |
| Message reports | Reporter and reported author IDs and names, reported message content, message links and IDs, attachment metadata, report reason, timestamps, staff destination, and review status or reviewer. | Preserve evidence and let authorized staff review a report. |
| Support tickets | Owner and participant IDs, ticket subject, channel ID, assigned staff member, status, reasons, and action timestamps. Discussion is also stored as messages by Discord in the ticket channel. | Create and manage tickets and their access permissions. |
| Reminders, timers, and time settings | User and server IDs, reminder text, schedule, destination, time-zone settings, and delivery or cancellation status. | Deliver requested reminders and display appropriate times. |
| Economy, games, and progression | User and server IDs, virtual balances, transaction ledger, inventory, virtual assets, game outcomes, wagers and fairness records, levels, rewards, and cooldowns. | Operate entertainment features and maintain consistent progress and virtual transactions. |
| Optional community features | Poll questions and votes, birthday month/day and opt-in settings, group membership, counters, and other feature-specific selections. | Provide the optional feature you or a server administrator enabled. |
| Diary | Your user ID, the text of your entries, entry IDs, and creation timestamps. | Store and retrieve the diary you choose to create. Entries are held in the bot’s database and are readable by the operator. |
| Image utilities | Submitted images or Discord attachment data and public avatar images used by a requested feature; generated output. | Create the requested image or animation and return it through Discord. |
| Feedback | Suggestion text, user ID and name, server ID and name if applicable, channel ID, command message ID, and submission time in UTC. | Receive and review your suggestion. Each submission is stored as a separate local feedback file. |
| Premium access | User or server ID, grant scope, granting operator ID, creation time, and expiry. | Determine access to premium features. A grant is not itself a payment record. |
| Direct support | Your email address or Discord identity, correspondence, and the information you choose to provide. | Respond to support, privacy, deletion, and security requests. |
Message content is processed when needed for commands, reports, configured logging, or other enabled functionality. Receiving a Discord message does not mean every message is permanently saved in Serenity’s database. Some data is only held temporarily in memory; reports, diary entries, moderation records, reminders, feedback, and other feature records can be persistent.
Do not send sensitive personal data or credentials. Do not include unnecessary personal information about other people in a report, diary entry, ticket, or feedback submission.
3. Where information comes from
Information comes from Discord’s APIs and events, commands and forms you submit, settings chosen by authorized administrators, information supplied in support correspondence, and records generated when Serenity performs an action. A moderation record or message report may relate to someone who did not personally run the command.
Serenity only has the Discord access made available to it through its permissions and approved capabilities. It does not gain access to other applications on your device simply because you use the bot.
4. How information is used
We use information to deliver the stated features, identify the correct accounts and destinations, apply preferences, check access, maintain game state, deliver reminders, preserve report evidence, support moderation, handle feedback and support, investigate misuse, and meet applicable legal and platform obligations.
The bot implementation does not sell data, provide advertising profiles, or send message content to train AI models. We do not use Discord API data for advertising, unrelated profiling, or purposes outside the bot’s permitted functionality. Any use of API data for general product improvement must be aggregated or de-identified in accordance with Discord’s requirements.
Where a legal basis is required, processing is based on the basis appropriate to the activity: providing a service you request, legitimate interests in operating and securing that service where lawful and balanced against your rights, legal obligations, or consent when required for an optional activity. You may withdraw consent where processing relies on it; withdrawal does not invalidate earlier lawful processing.
6. Storage and security
Serenity’s persistent bot records are held in databases and local files on the operator’s hosting computer or configured infrastructure. Feedback is saved separately from the main database. Copies may also exist in operator-maintained backups. Content the bot posts to Discord remains on Discord’s systems, and support emails remain in the support mailbox.
The bot applies Discord permission checks and feature-specific access restrictions. Those controls limit normal user access; they do not make the underlying records unreadable to the operator. Bot database records, diary entries, and feedback files are not end-to-end encrypted. This policy does not represent that every local file or backup has application-level encryption.
No system can guarantee perfect security. Please report suspected unauthorized access to niftyserenitybusiness@gmail.com. The operator will investigate and take appropriate containment and notification steps as required by applicable law and Discord’s requirements.
Your data can be processed in the locations used by the operator and relevant providers, which may differ from your country. Where applicable law requires safeguards for an international transfer, the operator is responsible for ensuring the required safeguards are in place.
7. How long records remain
Retention depends on the purpose of the record. Settings and feature state remain while needed to provide the feature; diary entries remain until deleted or otherwise removed; report evidence, moderation history, virtual transaction records, ticket metadata, and feedback can remain after the originating action. Completed, cancelled, or reviewed status does not necessarily erase the underlying record.
The current implementation does not apply a universal automatic expiry period to all stored records. Removing the bot from a server, leaving a server, deleting the original Discord message, or disabling a feature does not automatically erase every related database entry, report copy, feedback file, or backup.
The operator must retain Discord API data only as long as necessary for Serenity’s permitted functionality, and promptly delete it when no longer needed, when the relevant user or Discord requests deletion, when legally required, or when the service stops operating, except where retention is required by law. These requests may require manual processing.
Backups and copies under the operator’s control must be addressed as part of a deletion request; a request is not limited to the live database. If a legal requirement prevents deletion of specific information, the operator will explain the applicable limitation where legally permitted. Discord messages and independent copies held by server staff are handled separately under the control of their respective custodians.
8. Your choices and privacy rights
Depending on applicable law, you may have rights to ask for access to your data, correction, deletion, a portable copy, restriction of processing, or to object to certain processing. You may also have a right to withdraw consent and complain to a competent data-protection authority. These rights vary by jurisdiction and can have lawful exceptions.
You can stop using optional features, adjust available preferences, cancel reminders, and delete individual diary entries using the supported commands. Administrators can disable features, adjust channel permissions, or remove the bot. These controls do not replace the right to request deletion of other stored information.
For access, correction, or deletion, email niftyserenitybusiness@gmail.com with a subject such as Serenity privacy request. Include your Discord user ID, any relevant server ID, and the type of request. You do not need to publish this information in a public channel. If you cannot use email, contact the operator through Serenity Support on Discord and ask for a private way to submit the request.
We may ask for proportionate evidence that you control the relevant account so that another person cannot obtain or delete your data. Never send your password, token, payment details, or an identity document through the bot. We will address requests promptly and within the deadlines required by applicable law. There is no blanket requirement to buy premium access to make a privacy request.
Deleting feature data can remove preferences, virtual progress, or the ability to deliver a reminder. If you continue using the bot afterwards, new records may be created for that subsequent use. For a message posted in a Discord server, you may also need to contact that server’s administrators or use Discord’s controls to address the platform copy.
9. Children and age-limited use
Serenity is not intended for anyone under 13 or under a higher minimum age required by Discord or local law. We do not knowingly seek personal data from people below that threshold. If you believe such data has been collected, contact niftyserenitybusiness@gmail.com so that the operator can investigate and remove it as appropriate.
Birthday features use the month and day supplied by the user; they are not a general identity-verification service. Adult-only functionality, where available, is subject to the age and channel restrictions described in the Terms of Service.
10. These policy pages
These pages are static documents. Their page code does not include advertising trackers, analytics scripts, contact forms, or application cookies, and you do not need to provide bot information to read them. The hosting infrastructure may process standard request information, such as your IP address, requested URL, browser details, and request time, for delivery and security under the hosting provider’s policies.
Opening the support-server invite or sending an email uses the relevant external service. These documents do not override those providers’ privacy policies.
11. Policy changes and contact
We may update this policy when Serenity’s features or data practices change. The latest policy and its effective date will remain available at this URL. Material changes will be communicated through an appropriate bot or support notice where reasonably practical. A policy update does not, by itself, authorize a new use of data that requires consent or Discord approval.
Privacy, deletion, correction, and security contact: niftyserenitybusiness@gmail.com.
Support server: Serenity Support on Discord.
For feature suggestions, use ;provide feedback. Use the privacy email for sensitive privacy requests rather than posting personal information in a public support channel.