Last updated: September 11, 2026
What this system is for
The Old Gods tools help members and authorized guild leadership coordinate chapters, review guild activity, coordinate recruiting and events, manage the guild bank, and maintain operational records. They are not intended to monitor activity outside the guild information made available through World of Warcraft, the addon, or information a player submits directly.
Information we process
- Account information used to sign into this website, including display name, email address, roles, chapter membership, and authentication security records.
- Guild roster information such as character name, realm, rank, public and officer notes, guild join or departure events, and activity timestamps exposed to authorized guild officers.
- Guild bank balances, inventory, item IDs, deposits, withdrawals, repairs, player names, and transaction timestamps.
- Guild calendar, recruiting, raffle, and configured chat-channel records synchronized by authorized users.
- Bug reports, feedback, contact information, attachments, administrator notes, and resolutions submitted through this website.
- Technical records required to operate and secure the service, including login cookies, request logs, synchronization results, timestamps, and error logs.
Addon and Companion behavior
The addon stores guild data in World of Warcraft SavedVariables. The desktop Companion reads configured SavedVariables locally. Uploading to the guild website occurs only when a user configures the service and enables guild data upload. The Companion also keeps a local synchronization queue so interrupted uploads can be retried. Users should protect their computer account and Companion sign-in session. The Companion signs in with website credentials; chapter API keys are no longer used for access.
How information is used
Information is used to provide guild administration features, show authorized chapter dashboards, detect incomplete or unusual bank activity for human review, prepare guild communications, troubleshoot software, respond to feedback, and protect the service. Automated indicators are review aids; they should not be treated as proof of misconduct without human verification.
Access and disclosure
Access is restricted by authenticated account, global role, and chapter membership. Members can read assigned chapters. Officer notes and officer chat require management access for that chapter. Only Super Admins can access all chapters and global administration. We do not sell player information. Data may be disclosed when necessary to operate the hosting service, investigate security incidents, comply with law, or protect the guild and its members.
Optional Battle.net linking
If you choose to link Battle.net, Blizzard handles authorization. We import your Battle.net account identifier, BattleTag, selected region, character names, character and realm identifiers, levels, and synchronization time. We do not receive your Blizzard password or retain the OAuth access token. Synchronization runs when you authorize linking or refresh it. Unlinking removes the imported account link and character list; it does not delete historical guild records supplied by other authorized sources or revoke consent at Blizzard. Chapter permissions are assigned separately.
External services
The website uses Blizzard's APIs to retrieve public World of Warcraft item metadata and artwork. Blizzard receives the normal technical information associated with those API requests, which are made by the server rather than by each player's browser. Links to Discord or other external services are governed by those services' own privacy practices.
Clip submissions and social posts
If you submit a clip, we store your character, realm, contact email, video or share link, notes, and your membership and sharing declarations for private administrator review. Approved content may be edited and shared on the guild website and social channels with your permission. Embedded Facebook, TikTok, and Instagram content connects your browser directly to those platforms, which may receive technical information and use their own cookies under their privacy policies.
Cookies and security
The website uses an essential authentication cookie to maintain signed-in sessions and an antiforgery cookie to protect forms. These are not advertising cookies. Connections should use HTTPS. Passwords are stored using ASP.NET Core Identity's protected password hashing, and website passwords are never displayed back to administrators.
Retention and corrections
Records are retained while they are reasonably needed for guild operations, security, historical accountability, troubleshooting, or legal obligations. Retention may vary by record type. Members may request review or correction of information associated with them, subject to guild recordkeeping and security requirements.
Questions or requests
Use the bug reports and feedback page to ask a privacy question, request a correction, or report a concern. Do not include passwords, API keys, or other secrets in a submission.