What is stored, and why
- From Discord, when you log in: your user id, username, display name in the guild's server, and the names of your roles there. Used to know who you are and what you may see. Sessions last 30 days and end at sign-out.
- From Discord, for the guild: the server id, and names of channels the bot posts in. The bot reads only the messages Raid-Helper posts (comps), not chat.
- From Raid-Helper: signups and rosters for the guild's events — character names and Discord ids of who signed up. The guild's admin provides the API key.
- From Warcraft Logs: the guild's public raid reports — who was present, parses, consumable use.
- From the guild itself: roster, loot history, wishlists, resist sets, assignment notes — entered by officers and raiders.
- Billing: handled by Stripe. We store the Stripe customer and subscription ids for the guild, never card details. Stripe's own privacy policy applies to payment.
- Technical: server logs with request paths and errors, kept for 14 days. No advertising, no analytics trackers, no sale of data.
Who can see it
A guild's data is visible to that guild: members see the public pages, officers see officer pages, the guild's admin sees settings and billing. The operator can access data to run the service and fix problems. Nobody else, except when the law requires it.
Where and how long
Data lives on the operator's server in the EU. It is kept while the guild exists. When a guild is removed, its data is deleted within 30 days (the delay allows an "oops" recovery). A person can ask to have their own records removed from a guild by contacting the guild's admin or the operator.
Cookies
Only session cookies that keep you logged in. Nothing for tracking or advertising, so there is no cookie banner.
Your rights
You can ask what is stored about you, have it corrected or deleted, or object to its use. Contact the hub owner, via your guild's Discord. If you are in the EU you may also complain to your data protection authority.