Privacy Policy

Guild Wars Revival is an independent, volunteer-run Guild Wars community website. We are not affiliated with or endorsed by ArenaNet or NCsoft.

Questions about this policy or use of your information can be sent to security@gwrevival.com.

We collect information you choose to provide and limited technical information needed to operate and secure the website. This may include your Discord account details, Fashion Wars submissions, votes, moderation records, saved map progress, filter presets, private custom farm markers, and structured LFG posts or memberships.

LFG records contain structured activity, start time, region, language, party capacity, experience or role requirements, and an allowlisted in-game meeting place. They do not provide a public roster, free-text contact details, or Discord identity fallback. Membership and organiser identity remain access-controlled; public and operational reports use only anonymous counts.

Map treasure-hunt records contain the hunt and clue version, your private sequential position, action timestamps, completion state, and a bounded failed-attempt count used to prevent abuse. Submitted map targets and future clue solutions are not published with your account or added to analytics metadata.

Standard server logs may record IP address, browser details, requested pages, timestamps, and security events. We use this information to keep the service reliable, prevent abuse, and diagnose faults.

For member-only community features, we keep a private participation ledger of successful, meaningful actions, such as completing supported map progress, submitting a challenge answer, joining an event, or creating or joining an LFG request. It records the member account, type and time of action, related feature record, and limited campaign information where a Guild Wars Revival Dispatch link led to the action.

This ledger is first-party and authenticated. We do not add anonymous visitor activity to it, and it does not contain Discord identifiers, email addresses, IP addresses, device fingerprints, character names, answer text, screenshots, or free-text submissions. Dispatch attribution measures assisted completed actions, not opens or clicks, and does not use a new analytics cookie or cross-site identifier.

When you sign in with Discord, Discord provides the account identifier, username, display name, avatar, and verified email address authorised by the sign-in request. We use the stable account identifier to recognise you and the remaining details to display and maintain your member account.

We do not receive your Discord password, private messages, server membership, or friend list.

We use information to authenticate members, operate community features, publish approved Fashion Wars entries, record votes, measure meaningful participation in aggregate, moderate abuse, maintain security, answer requests, and improve site reliability.

LFG membership state is used to enforce one active group, capacity, leave, cancellation, expiry, restriction, and moderation rules, and to show a signed-in member a relevant private dashboard action.

Treasure-hunt progress is used to unlock clues in order, preserve completed progress, correct verified hunt errors, prevent abuse, and report anonymous aggregate completion only where the minimum cohort is met.

Our lawful bases under UK data protection law are performance of the service you request, our legitimate interests in operating and securing the community, consent where specifically requested, and compliance with legal obligations.

Approved Fashion Wars entries may publicly show the character name, profession, screenshot, armour, weapons, dyes, vote total, round placement, and the submitter's Discord username. Rejected or pending submissions are not shown in the public gallery.

Challenge, hunt, and participation results are anonymous by default. A feature may show an approved public display name only when a member separately chooses that feature's public-attribution option; a Discord identity is never used as the fallback display name. Turning off attribution removes public identity promptly, while non-identifying aggregate results may remain.

LFG cards show structured activity and availability, not organiser or participant names. Members meet at the selected in-game rendezvous; the site does not publish personal contact details or a participant roster.

Map treasure-hunt progress, clue attempts, completion time, and member identity are private. A hunt may publish only an anonymous aggregate completion count after reveal and only when at least ten members qualify; it never publishes names, ranks, streaks, or completion times.

Your email address, Discord account identifier, moderation history, private map data, and other account administration details are not intentionally published.

We do not sell personal information. Information may be processed by infrastructure and authentication providers needed to run the website, including our hosting provider and Discord. Those providers handle information under their own terms and privacy policies.

We may disclose information where required by law or where reasonably necessary to protect members, the service, or another person's rights.

We keep account and community records only while needed for the purposes described above. Identifiable participation-ledger events are planned to be retained for 24 months from the event, then deleted and represented only in non-identifying monthly totals. This period is configurable and remains subject to formal legal review before production launch.

Published contest history may remain available as part of the Fashion Wars archive. Security, moderation, backup, and legal records may be retained longer where necessary to prevent abuse, preserve contest integrity, or meet legal obligations.

Active LFG posts and memberships are kept while needed to operate the group and enforce safety rules. Expired groups are archived; restricted moderation evidence may be retained under the moderation period described by our operating policy. Formal retention approval remains required before the LFG flag is enabled.

Identifiable treasure-hunt progress follows the configured participation retention period, currently planned as 24 months. Cancelling or disabling a hunt does not bypass support, correction, moderation, deletion, or retention duties.

You can ask us to review or delete personal information as explained in Your Data Rights.

We use reasonable technical and organisational measures to protect information, including access controls, authenticated administration, upload quarantine, and moderation processes. No online service can guarantee absolute security.

Depending on your circumstances, you may have rights to access, correct, erase, restrict, or object to processing of your information, and to receive a portable copy. Read Your Data Rights for request instructions.

Use of this website is also governed by our Terms of Use.