1. Scope
This policy applies to the Zug Zug website, Discord-connected bots, desktop applications, game addons and bridges, verification tools, and related community services. Third-party websites and services have their own privacy practices.
2. Information we collect
Discord and account information
We may store your Discord user ID, username, display name, avatar, server nickname, membership status, relevant roles, linked website account, preferred character, and synchronization timestamps. Discord authentication also provides the information required to complete sign-in.
Characters and community participation
We may store linked and verified characters, ownership records, character mains, guild and community membership, raid participation, team assignments, Guild Rep balances and events, voice or message reward activity, verification attempts, and related moderation state.
Game and population observations
Zugbot, addons, roster synchronizers, and related integrations may collect character names, levels, classes, races, guild names, zones, online observations, last-seen times, roster changes, progression, auction information, population snapshots, and other game-related records.
Content and activity
We store content you submit or interact with, including posts, comments, reactions, guides, images, gear lists, raid information, signups, reserves, settings, and administrative actions.
Technical and security information
We may process session identifiers, cookies, desktop access-token records, IP addresses, user agents, request metadata, timestamps, error logs, security events, and administrative audit records. Passwords and raw desktop access tokens are not intended to be stored as readable account data.
3. Where information comes from
Information may come from:
- You, when you sign in, verify characters, change settings, or submit content.
- Discord, including OAuth, server membership, role, profile, voice, and message events.
- Game clients, Zugbot, guild addons, roster exports, and population scans.
- Public game, armory, auction, raid, repository, and community integrations.
- Administrators performing moderation, support, synchronization, or corrections.
4. How we use information
- Authenticate users and maintain sessions.
- Verify character ownership and connect Discord identities to characters.
- Operate rosters, profiles, population tools, raids, teams, Guild Rep, and community features.
- Synchronize eligible Discord roles and opted-in character nicknames.
- Publish community content and game information intended for public display.
- Moderate abuse, enforce rules, secure services, diagnose errors, and maintain audit records.
- Understand aggregate website usage and improve reliability and usability.
5. Information that may be public
Character directories, population observations, guild rosters, character profiles, class and level information, guild names, raid activity, leaderboards, Guild Rep totals, posts, comments, guides, reactions, and other community contributions may be publicly visible.
Population and game records are maintained independently from website accounts. Historical character observations may remain available after a character changes guilds or a person leaves a Discord community. Private ownership identifiers are not intentionally exposed through public population APIs.
8. Data retention
We retain information for as long as reasonably necessary to operate the services, maintain community history, enforce rules, resolve disputes, prevent abuse, satisfy legal obligations, and protect the integrity of verification and audit records.
Account sessions and access tokens may expire or be revoked. Public game observations, submitted content, moderation history, security records, and audit logs may be retained after account deletion when reasonably necessary. We may remove, aggregate, or de-identify information when it is no longer needed.
9. Your choices and requests
You may update certain preferences through website or Discord commands, revoke desktop tokens in settings, leave the relevant Discord communities, or ask Zug Zug administrators to review, correct, unlink, or delete account information.
We will delete account, session, and token data when reasonably possible after verifying the request. Some security, audit, legal, moderation, public community, and historical game records may be retained. Requests are handled according to applicable law and the technical relationship between account data and community records.
10. Security
We use reasonable technical and administrative measures intended to protect information. No online system is completely secure, and we cannot guarantee that unauthorized access, loss, or disclosure will never occur. Never send passwords or raw access tokens to administrators.
11. International access
Zug Zug is operated as a United States community service and may process information in the United States or wherever its service providers operate. If you access the services from another country, your information may be transferred to jurisdictions with different data-protection rules.
12. Age requirement
Zug Zug services are intended only for people who are at least 18 years old. We do not knowingly provide website accounts or community services to minors.
13. Changes to this policy
We may update this policy as our services or practices change. The effective date at the top of this page identifies the current version. Material changes may also be announced through community channels when practical.
14. Contact
Contact Zug Zug administrators through the official Discord server for privacy, correction, unlinking, or deletion requests. We may ask for reasonable verification before acting on a request.