Service requests and scheduling
Data: Character name, faction, class, spec, Discord, contact field, preferred window, selected product, notes, quoted gold price.
Lawful basis: Steps requested before a service arrangement and legitimate interest in running a safe request desk.
Parse review requests
Data: Warcraft Logs URL, target parse, character context, and notes supplied by the player.
Lawful basis: Steps requested before a parse review and legitimate interest in qualifying requests honestly.
First-party analytics
Data: Page path, referrer, UTM fields, language, screen size, user agent, approximate geo headers when available, and hashed IP/session identifiers.
Lawful basis: Legitimate interest in understanding which pages lead to useful requests. No advertising cookies are used.
Notifications and operations
Data: Request details sent to configured email and Discord webhook destinations so staff can respond.
Lawful basis: Legitimate interest in operating the request queue and responding quickly.
Public proof ledger
Data: Only approved anonymized completed-request details: service title, class/spec, quote, completion date, and internal proof ID. Admin keeps the private consent note.
Lawful basis: Legitimate interest in showing real completed work while minimizing private data exposure after publication approval.