EMERALD · PRIVACY POLICY
Effective 19 October 2026.
This policy explains what the Emerald Discord bot and website process, which features make information visible, how records are retained and how to request access, correction or deletion.
1. Who operates Emerald
Emerald is operated by its bot owner, referred to here as the operator. The contact route at the end of this policy reaches the operator. A Discord server’s managers independently decide which Emerald features to enable and who may use them. Questions about a local moderation decision should also go to that server’s managers.
This policy covers Emerald’s bot, dashboard and supported game interfaces. Discord and services reached through external links or integrations have their own policies, including Discord’s Privacy Policy.
2. Information we process
The records used depend on enabled features and how you interact with them. Emerald does not need every category for every server.
| Category | Examples and purpose |
|---|---|
| Discord identity and server data | User, server, channel, role and message IDs; names, avatars, member roles and relevant permissions to identify users, display results and authorize actions. |
| Activity and invites | XP, levels, message/voice/reaction statistics, daily periods, achievements and recorded joins/invite attribution. Message content or metadata may be inspected for counting, XP safeguards, tracking or moderation. Full message text is not routinely copied merely to increment an activity counter. |
| Submitted content | AFK text, suggestions and attachments, confession content, welcome/embed templates, configured media URLs, saved game identifiers and custom-role appearance. Starboard keeps supported message snapshots for highlights. |
| Moderation and events | Jail/restriction records, reasons, staff actions, suggestion votes/decisions, giveaway entries, eligibility-related records, winner/claim history and game state needed to run or recover sessions. |
| Role and voice automation | Eligibility observations, timers, custom-role friend invitations and cooldowns; creator/room IDs, ownership, trusted/blocked IDs, preferences, companion channels, temporary roles and votes. Emerald does not record voice audio. |
| Birthdays | Server/user IDs, day, month and profile-visibility preference. No birth year is requested by this feature. |
| Dashboard and operations | OAuth identity and authorized guild information, server-side access/refresh tokens, signed browser sessions, request-protection values, audit entries, schedule/delivery receipts and technical logs generated by the deployment or host. |
Staff-configured webhook credentials are stored to deliver the requested feature and omitted from supported displays/exports. Do not submit passwords, Discord account tokens, payment-card details or other sensitive personal information in any content field.
3. Why we process it
Emerald uses information to provide the enabled features: calculate activity, show rankings, assign roles, manage access and moderation, publish submitted content, deliver notifications, operate games, recover supported tasks and verify dashboard permissions. Audit and technical records help investigate failures, abuse and unauthorized changes.
Emerald does not sell Discord API data, provide it to advertising networks or data brokers, or use API message content to train AI models. Data obtained through Discord must be used within the scope of the Discord Developer Policy.
4. Who can see information
- Other members: leaderboards, profiles, role membership, highlights, posted messages, suggestions, giveaway results and other outputs can be visible to the audience of the destination or feature. Some profile/leaderboard pages require server membership.
- Authorized managers: relevant settings, records, submissions and audit information are available according to dashboard grants and moderation permissions. The operator has operational access.
- Discord: receives bot messages, role changes and other actions through its platform. Discord can retain published content independently.
- Infrastructure and integrations: the hosting/database providers process stored data and traffic. Configured webhooks receive the content sent to them; supported external game lookups send the submitted identifier to the configured lookup service. Browsers may request external image URLs shown in a page.
- Required disclosures: information may be disclosed where required by applicable law or necessary to address a substantiated security or abuse issue.
Confessions are not guaranteed to be untraceable: authorized moderation and audit access may identify a submitter. Sharing content in a public destination can allow others to copy it.
5. Retention and backups
Retention differs by record type. A display window is not the same as a deletion schedule.
| Record | Current handling |
|---|---|
| Detailed XP history | Pruned to the last 14 days. |
| Daily activity and totals | Can remain for lifetime statistics. Profiles display the latest 30 days. |
| Dashboard sessions | Server-side sessions last up to seven days and are invalidated on logout or expiry. Expired rows can remain until cleanup. |
| Dashboard audit | Managers can inspect a 30-day window. Append-only records can be retained beyond that window. |
| Completed Temporary Voice votes | Removed after seven days by the feature’s cleanup process. Saved room preferences remain until reset or cleared by authorized management. |
| Other settings and feature records | Retained as needed for operation, recovery, history or administration; disabling a module or removing the bot does not automatically delete every row. |
Operational logs and backups follow the operator’s deployment configuration. Off-host backup copies exist only where configured. This policy does not promise an unverified fixed backup-erasure deadline. The operator can explain the applicable retention and any limitations when handling a request. Copies already posted to Discord or saved by other people are separate from Emerald’s live database.
6. Your choices and requests
You can stop using optional commands, use available DM preferences, sign out, clear browser storage and ask server managers about feature configuration. Authorized managers can disable features or remove Emerald. These actions do not necessarily erase historical records.
- Contact the operator privately using the route below.
- Identify your Discord user ID and, when relevant, the server and feature.
- Explain whether you request access, correction, deletion or another available privacy choice.
- Provide only the verification information needed to establish authority over the relevant account or server.
The operator will assess the request, applicable rights, verification, other members’ rights and any legitimate security, administrative or legal retention needs. If a request cannot be fully completed, the response should explain the relevant limitation. You can also raise concerns with the appropriate privacy authority where applicable. Do not post credentials or private records in a public support channel.
7. Birthdays and public activity
A birthday belongs to one server. After submission, a member can hide or show the date on profiles but cannot directly edit it. A server administrator can remove it through /profile; the member can then submit a different date.
Hiding a birthday affects its profile display only. Configured public wishes can still mention the member and apply a birthday role. To stop participation, request removal of the submission. Removing the date stops future participation but does not retract existing Discord wishes. Likewise, changing notification preferences does not automatically remove previously published activity or giveaway results.
8. Security and access
The dashboard uses signed, HTTP-only session cookies, server-side OAuth tokens, request-protection tokens, permission checks and restricted module access. Supported exports omit designated secrets. These measures reduce risk; no online service can guarantee that every failure or unauthorized access attempt will be prevented.
Keep your Discord account secure, review staff grants and protect webhook URLs. Report suspected exposure privately to the operator. The operator should investigate and provide notifications required by applicable law and Discord’s developer terms. See the Cookies Policy for essential browser storage.
9. Age and international processing
Emerald is intended for people who satisfy Discord’s minimum age and the applicable age requirements in their country. If you believe a child below the required age supplied information, contact the operator so the record and appropriate action can be assessed.
Information may be processed in the countries where the operator’s hosting services, Discord and configured integrations operate. The deployment’s exact locations and providers are not asserted here; request relevant details from the operator.
10. Policy updates
Updates are published at this URL with a revised effective date. Significant changes to data handling should be communicated through an appropriate service notice when practicable. Check the current version before enabling a new feature or submitting information.
11. Contact
For privacy requests, security reports, service questions or complaints, contact the Emerald operator on Discord. General support is also available in the support server.
Contact local server managers for server-specific moderation or configuration. Contact Discord separately for information held by Discord itself.