greyBot

Privacy Policy

Last updated 8 September 2026

greyBot is a Discord app that announces a World of Warcraft guild's first Heroic boss kills and posts a summary of raid nights. It is operated by Ryan Grey. This page describes exactly what it stores, where that data comes from, and how long it is kept.

What it stores

• World of Warcraft character names, read from public Warcraft Logs reports. These are used to record who took part in a guild's first kill of a boss, and to work out which of the guild's raid teams filed a given report.
• Raid progress state — which bosses have been announced, how many are dead, and whether the tier's Ahead of the Curve has been posted. This is what stops the same kill being announced twice.
• Operational state — timestamps, raid and boss identifiers, and a record of whether the app can still reach Discord.
• Server records — Discord member, role and channel identifiers; cached server nicknames and avatar URLs; joins, departures and supported audit changes; settings, administrative sign-ins and moderation requests and results.
• Optional message history — captured server message text and observed edit/deletion versions in the private local index. Coverage depends on the bot's access and connection history; unseen or previously deleted messages cannot be recovered.
• Verification records — the member requesting verification, the requested role and the result. Short-lived website sessions identify the signed-in member; member-verification sessions do not grant administrator access.

What it does not store

• The control collector does not import direct messages or records from other servers.
• Discord OAuth access tokens and verification challenge tokens are not retained in the event journal. Credentials used to operate the service are kept separately.
• The metadata journal excludes message text, attachments, invite codes and arbitrary Discord audit reasons. Enabled message text is held in a separate private index.
• The application does not request payment information or sell server records.

Where the data comes from

The raid service queries Warcraft Logs for which bosses died and when, Raider.IO for guild progress and realm rank, and Blizzard's public game data API for boss artwork. Discord supplies server events and member information according to the bot's permissions. Announcements are sent as greyBot to configured channels; full raid scorecards are published separately on the raid website. Discord provides sign-in, and Cloudflare Turnstile processes human-verification challenges. Hosting and verification providers may process connection information under their own privacy policies.

How long it is kept

Raid state and character names are kept for as long as the app runs for that guild, because the whole purpose of the record is to remember that a boss was already announced. There is no automatic expiry for raid state or the current local server archive. The application prevents editing archived events; the NAS owner retains recovery and removal authority. Contact the server administrators or the developer below about access, corrections or removal of stored server data.

Who can see it

Raid state is held in private AWS storage; published raid scorecards can be read by anyone with their URLs. Server history and moderation records are held on the operator's private NAS and available to current server administrators through the authenticated dashboard. Configured Discord audit channels may show selected changes and captured message text to members who can view those channels. The full private event history is independent of those posting filters.

Children

greyBot is intended for users who meet Discord's minimum age requirements and their server's membership rules. It does not ask members to provide their date of birth.

Changes

If what the app stores changes, this page changes with it, and the date at the top is updated.

Contact

Questions, or a request to delete a guild's data: rgrey.web@gmail.com.