Privacy policy.

Site accounts have public player profiles by default. Your display name or supplied GW2 name, public avatar and shared profile details may appear in the player directory and Community feed. Public site actions such as guild recommendations, bumps, approved memberships and discussion contributions may appear with your profile.

You can connect a guild listing to your profile using a guild invite or the profile editor. Accepted friendships appear publicly on both players’ profiles. Friend requests are private to the people involved, and either player can remove a friendship. Private, staff-hidden and deleted profiles are omitted from public friend lists.

You can make your profile private or change activity sharing in your player profile settings. Email addresses, authentication details, private reports and staff moderation notes are not included in public player profiles. Staff-hidden content and deleted accounts remain excluded.

When you request to join a guild’s site roster, we store your chosen GW2 player name, site account, approval status and review history. Your site display name, player name and guild association become public after you agree and a guild owner or recruiter approves your request. Pending and declined requests are visible to you and authorised guild recruiters. Player names are member-supplied and do not verify ownership of a GW2 account.

When banner advertisements are enabled, clicking an ad records the campaign, click time, and a keyed hash derived from your IP address. The ad click records do not store your raw IP address or use an advertising cookie. The hash is retained to count an IP address once per campaign, including repeat visits on later days.

Aggregate unique click totals and their value at $0.20 USD per click are shared with the advertiser through a Discord counter. Individual IP addresses and their hashes are not sent to Discord.

Guild Finder may store public guild names, guild tags, source identifiers and URLs, source verification flags, public image URLs, member counts, source update times, and fetch times from attributed public directory sources.

The initial source-directory pilot stores aggregate group facts rather than member rosters or copied guild descriptions. Source profiles are labeled unclaimed and are kept separate from owner-submitted recruitment listings.

A claim request may store the claimant account, connected Discord and Guild Wars 2 identity snapshots, stated guild role, verification method, guild Discord URL, evidence supplied for review, delivery status, decision, reviewer identifiers, review notes, expiry time, and an audit history. Claim material may be sent to a private Discord moderation queue and retained to prevent impersonation or resolve ownership disputes. Never submit passwords, recovery data, authentication codes, or other secrets as ownership evidence.

Guild Finder stores owner account details such as display name, account role, account creation time, account settings, and email address or password hash when provided.

Guild listing submissions may include guild name, guild tag, headline, description, requirements, region, timezone, language, member count, public contact links, Discord invite, uploaded guild image or banner, tags, and moderation status.

Report submissions may include the reported listing, reason, report details, optional reporter email, and related moderation status.

Discord login or account connection is optional. If used, Guild Finder may store Discord ID, username, avatar URL, sync timestamps, OAuth state cookies during sign-in, and Discord moderation workflow references. Guild Finder requests Discord identity access and permission to join servers for you (guilds.join). When you authorize Discord sign-in or connection, we use that permission to add you to the Guild Wars 2 Guild Finder Discord server. The access token is used during that callback and is not retained for later joins. We do not request or store the email address attached to a Discord account.

If a connected Discord account joins and verifies in the Guild Finder Discord server, Guild Finder may record server verification timestamps and assign Discord roles such as Linked, Guild Owner, Guild Admin, or Event Manager based on the account's active or pending guild listing access.

When you accept guild staff access, your Guild Finder display name, profile avatar, and staff role may be displayed publicly on that guild's listing. Private account identifiers such as your email address and Discord user ID are not shown in the public staff section.

These connected-service signals help users manage accounts and help moderators review ownership or trust signals. They do not require Guild Wars 2 login credentials.

Guild Finder uses cookies for owner sessions, CSRF protection, and Discord OAuth state during sign-in or account connection. Session cookies are used to keep owners signed in, and CSRF cookies help protect account and listing actions.

A cookie preference control lets users accept all optional cookies, reject optional cookies, or choose categories. Necessary cookies are always active because the site needs them for security, account access, consent storage, and core functionality.

Optional analytics cookies help measure site usage and improve search, listings, and performance if enabled. Optional cookies are off unless the user chooses to allow them.

The service stores hashed session tokens, authentication tokens for email verification and password reset, rate-limit records, and hashed IP addresses or hashed client identifiers where practical for spam, fraud, report abuse, and service protection.

Operational counters may store hashed identifiers where needed for rate limiting, abuse prevention, aggregate traffic totals, and service health. Public traffic totals count page views, unique browsers across the tracking period, and unique browsing sessions by UTC day. The browser identifier is generated locally, stored in browser storage, and saved by Guild Finder only as a one-way hash; clearing browser data or using another browser may create another count. Traffic counters do not require Guild Wars 2 names, guild data, or gameplay data.

Guild images, banners, and optional account profile images may be uploaded. Images are checked, sanitized, converted to WebP, resized or optimized as needed, and stored for public display where used.

If a guild owner enables Discord forum publishing or linked-owner visibility, approved listing details and the selected Discord owner signal may be shown in Guild Finder Discord forum posts.

Approved public listing content is visible on the site, may be available through public API surfaces, and may be copied or indexed by users, search engines, or third-party clients.

Reports, moderation actions, approval decisions, rejection notes, owner notifications, Discord approval requests, Discord announcement references, and related site records may be stored to review abuse, resolve disputes, protect users, and keep the directory reliable.

Reports may be reviewed by moderators and may be sent to moderation channels or tools, including Discord-based moderation workflows. Reporter email is optional and is used only if follow-up is needed.

Signed-in users may recommend guilds. Guild Finder stores recommendation records so the site can count recommendations, prevent duplicate recommendations, and notify listing owners.

Signed-in users may favorite guilds and events. Guild Finder stores favorite records so the site can count favorites, prevent duplicate favorites, and personalize account actions.

Account notifications may store notification type, title, body, link, metadata, read status, and creation time so owners can review listing, moderation, report, and recommendation activity.

Guild Finder may send account verification, password reset, listing review, moderation, and operational emails. Email delivery records may include recipient, message type, subject, body, delivery mode, sent time, and creation time.

Email services, hosting providers, logging tools, and moderation tools may process limited information needed to deliver, secure, troubleshoot, and operate the service.

Do not enter Guild Wars 2 login details. Guild Finder does not need Guild Wars 2 credentials, authenticator codes, recovery answers, bank information, private in-game chat, private guild membership data, or gameplay automation data.

Information is used to operate owner accounts, publish and manage public listings, review submissions, handle reports, prevent abuse, provide search and discovery, deliver notifications, and maintain security.

Moderation and trust signals are used to make review decisions, investigate reports, resolve listing disputes, and protect users from unsafe or misleading listings.

Public listing information is shared publicly by design after approval. Report and moderation information may be shared with authorized moderators and moderation systems.

Guild Finder may use third-party services such as hosting providers, database providers, Discord, email delivery providers, analytics or logging tools, and security tools where needed to operate the service.

External guild links, Discord servers, websites, and application forms are controlled by third parties. Their privacy practices are separate from Guild Finder.

Guild owners can withdraw managed profiles and delete owner accounts through account controls where available. Custom assets, recruitment content, posts, contacts, and management access are removed; the guild name may remain as an asset-free, unclaimed public index record based on public information.

Suspended, rejected, report, recommendation, notification, email, rate-limit, security, and moderation records may be retained when needed for safety, fraud prevention, accounting, dispute handling, abuse history, service reliability, or legal compliance.

Deleted accounts may be deactivated or anonymized while records needed for security, moderation, accounting, or compliance are retained.

Guild representatives may request correction, merging, or removal of an unclaimed source profile. Source and claim records may be retained where needed to prevent duplicate profiles, impersonation, repeated disputes, or abuse.

Users may request access, correction, deletion, or review of personal information associated with their owner account, report, or listing. Requests may require proof that the requester controls the relevant owner account, email address, Discord account, or guild listing.

Listing concerns should be submitted through the listing report function. Account deletion and listing removal should be handled through account settings where available. Privacy requests may also be sent through the public support or community channel listed on the site.

Guild Finder may update this privacy policy as features, processors, data flows, legal requirements, or moderation practices change.

Material updates will be reflected by changing the last updated date on this page.