Privacy Policy

Last updated: 28 July 2026

Before publishing: fill in the contact method, the retention period for ticket archives, and who operates the service. Each is marked [TBD] below. Do not publish with placeholders — this document is linked from Discord's Developer Portal and is read as a binding statement.

Who this covers

This policy applies to the Group Finder's Guide Discord application and the web apps at event.gfgpug.com and feedback.gfgpug.com. These are operated by [TBD: person or group responsible] for the Group Finder's Guide World of Warcraft community. They are not affiliated with or endorsed by Discord Inc. or Blizzard Entertainment.

What we collect and why

DataSourceWhy we hold it
Discord user ID and username Discord To record who registered for an event and to show your own registrations back to you.
Your roles in our Discord server Discord To decide who can administer events in the Event Portal and the feedback app. We read role membership only for the specific staff roles used for access control.
Messages and file attachments in closed support tickets Discord When a support ticket channel is closed, its contents are archived so the officer team can review past tickets. This includes message text, the author, timestamps, and any files attached.
Character name, realm, class, item level, and Mythic+ or PvP rating Battle.net, with your permission To validate the character you register and to organise groups by key level. You authorise this yourself through Battle.net's login screen, and you can revoke it there at any time.
Event registrations and group assignments You To run the weekly key event.

We do not collect message content from anywhere other than closed ticket channels, we do not read direct messages, and we do not collect presence or activity information.

Where it is stored, and who else sees it

Data is stored on servers we control. We do not sell it, and we do not share it for advertising. It reaches the following third parties only as part of running the service:

Google
Event registrations are copied to a Google Sheet as a backup, which includes your Discord username and the character details you registered.
Cloudflare
Our sites are served through Cloudflare, which processes network traffic to reach them.
Our hosting provider
The servers running these apps are rented from [TBD: hosting provider].

Officers and administrators of the Discord server can see event registrations and archived tickets as part of running the community.

How long we keep it

Event registrations
Kept across seasons so the app can order your character list by what you have used recently. Removed when you ask us to.
Archived support tickets
[TBD: state a period, for example 12 months after the ticket is closed], after which they are deleted.
Everything else
Deleted when it is no longer needed for the purpose it was collected for, or when you ask us to remove it.

Seeing or deleting your data

You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Contact [TBD: email address, or a named Discord channel or role] and we will action it.

Deleting your data removes your registrations and your messages from any archived ticket. Some records may remain where we are required to keep them by law. If you leave the Discord server or remove the app, tell us if you also want your stored data deleted — leaving on its own does not trigger deletion.

You can revoke the app's access to your Battle.net account at any time from your Battle.net account settings, independently of us.

Security

Access to stored data is limited to the people who operate the service and to Discord server staff for the parts described above. Credentials for the apps are stored separately from the code and are not published.

Children

Discord requires users to be at least 13, or older where local law sets a higher minimum. We do not knowingly collect data from anyone below that age. If you believe we have, contact us and we will delete it.

Changes

If we change what we collect or how we use it, we will update this page and change the date at the top.