Privacy policy

Clan listings and saved source records

The public directory contains user-submitted listings and approved ownership claims. Existing claimed and verified profiles remain available. Automatically imported and historical records without a submission or approved claim are not published.

Previously collected public-source records are saved privately for possible future restoration. They can include clan identities, post text, titles, public author handles, source URLs and observation dates from public recruitment sources and community wikis. Source-author handles and original post excerpts are not included in the public directory export. An archived record does not prevent a representative from submitting the clan.

Public sources and private information

We do not sign into private clan accounts, read private Discord channels or direct messages, or collect private membership lists. Private support tickets, account credentials, and ownership evidence are not published as recruitment listings. A public invite check does not provide access to private server conversations.

Publicly available information can still concern an identifiable person. A clan name or community link is not necessarily personal information about its members, but names, handles, and links can identify individuals in context. We assess the information concerned rather than treating everything found online as exempt from privacy protections.

Information you provide

Email accounts provide a display name, email address, and password. Passwords are stored as salted hashes, not readable passwords. Clan and Recruit Me forms, uploaded clan artwork, verification evidence, tickets, and support messages contain what you choose to submit.

Discord information

Discord sign-in provides your Discord user ID, username, display name, and avatar. We request identify and guilds.join; we do not request your Discord email. Discord also processes your use under its own policies.

How information is used

We use account data to sign you in, publish message-board posts, clan artwork and Recruit Me profiles, record likes, hourly bumps and recommendations, process private reports, enroll Discord users in the community server, assign verified roles, process claims and submissions, prevent abuse, keep audit records, and answer support requests.

Cookies and browser storage

Essential cookies maintain signed-in sessions for up to 30 days and temporary Discord sign-in state for up to 10 minutes. Session identifiers are stored server-side in hashed form. Compare selections and the directory-view preference use local storage in your browser without an automatic expiry. You can remove those preferences by clearing this site’s browser storage.

Player profiles and community

Your Clan Finder account includes a public player profile with your display name, avatar and join date. You can add a bio, interests, a chosen clan and photos. Public activity includes community posts, conversations, clan recommendations, vouches and clan recognition. Accepted friendships are visible on both public profiles; pending requests and moderation reports stay private. Your email, password and private account details are not displayed on player profiles.

Use your player profile settings to make your profile private, hide activity and conversations, or remove the link to your Recruit Me listing. Making a profile private removes it from the player directory, community feed and public friend lists. You can remove your posts, comments and photos or withdraw vouches. Account export includes your community data.

Public information

Approved clan names, artwork, descriptions, links, tags, requirements, activity details, verification status, and aggregate bump or recommendation counts become public. Recruit Me profiles publish the player details submitted plus the connected Discord display name, username, avatar, and contact identity. Approved, active player listings are also published as embeds in our community Discord player feed. Editing your listing updates the embed; marking it as found, removing it, expiry, or staff removal removes the embed after synchronization. Clan offers remain private in the website account, and our bot sends the player an offer notification by Discord direct message when their settings allow. We retain delivery status and message identifiers to retry failed deliveries and avoid duplicates. Message-board posts, replies, display names, avatars, roles, and like totals are also public; reports remain private. Never submit private credentials, personal addresses, or evidence intended only for staff into a public field.

Recruitment offers and match history

Clan managers can send private offers to active Recruit Me profiles. We store the offer message, sender and recipient account identifiers, clan, timestamps and response status. Offers are visible to the sending account and the recipient; staff can review reported offers. An accepted offer closes the player’s listing and creates a private match record.

The player can choose to share their in-game name, clan name and acceptance date on the public Matched players page. Offer messages and Discord contact details are not included in that history. Sharing is optional, and the player can hide the public entry from Manage recruitment. Acceptance records the player’s response on this site; it does not verify in-game clan membership. Offer and match records may be retained for account history, operation and abuse handling after an offer expires. Contact support for deletion requests.

Service and security data

Cloudflare and hosting infrastructure process network and request information needed to deliver and secure the site. Discord processes information for connected account and support features under its own policies. Rate limiting uses request identifiers such as IP addresses to reduce abuse. We do not use this data to build advertising profiles.

Retention and deletion

Submitted, claimed and verified clan records are retained with their listing history. Previously imported clan records are saved privately and are no longer automatically published. These source archives are separate from personal account data.

Automatic source imports are currently disabled. Saved source archives and backups are retained for possible restoration; they are not automatically erased when a clan leaves public results. Recruit Me profiles expire from public results after 30 days and can be removed earlier by their author. Sessions expire or are removed when you sign out. Replaced artwork and account, claim, moderation, report, and listing history may be retained while needed for operation, dispute handling, security, and abuse prevention. Ask support to review or delete eligible account data.

Listing analytics

We count visible directory appearances, profile views, owner-provided Discord-link clicks and claim-link clicks on published clan listings. Public profiles show aggregate activity; authorized owners can view date-range reports and download daily totals, including activity recorded before a listing was claimed. Reports also summarize website recruitment offers, accepted matches and current community engagement without identifying visitors.

Analytics uses no tracking cookies or persistent browser visitor identifier. An IP address and browser user-agent are processed to create a keyed digest that changes daily, to reduce repeated events within a 30-minute window. Raw IP addresses, user-agents, full referring URLs and search queries are not stored in the analytics database. Duplicate-prevention digests expire after that window and are pruned during routine cleanup; daily aggregate counts are retained for up to 365 days. Separate security logs and rate limits are described elsewhere in this policy.

We respect the browser’s Do Not Track and Global Privacy Control signals for this collection. Known automated traffic and signed-in listing-owner interactions are excluded where identifiable. Counts are estimates of interactions, not unique people or verified in-game joins. No historic traffic is invented or backfilled.

Sharing and sale

We use information with Discord and essential infrastructure providers only as needed to operate the service, comply with law, or protect users. We do not sell personal information.

Your choices

You can browse without an account, use email for ordinary site access, disconnect by signing out, remove browser comparison data, request listing correction, or contact support about access to and deletion of personal data.

Listing corrections and privacy requests

Clan representatives can submit a profile or maintain an existing listing through My clans. Imported records without a submission or approved claim are kept off the public site.

Request corrections to factual errors or report concerns about your personal information through our private support-ticket system. Include the listing URL and the specific information concerned. You do not need to pay or claim a listing to raise a privacy concern.

Personal-information requests can concern public pages, saved source records or backups and are assessed under the process below.

Personal-data requests

Depending on applicable law, you may have rights to access, correction, erasure, restriction, objection, portability, or withdrawal of consent. We assess requests individually and respond within the applicable legal deadline. Where UK or EU GDPR applies, this is normally one month, subject to permitted extensions and identity checks. We explain any refusal and applicable complaint routes.

We may ask for proportionate evidence when needed to identify the information or prevent an unauthorized change. We do not routinely require government ID, passwords, or private membership lists. You do not need to prove clan ownership to raise a concern about your own personal information.

Correcting or erasing personal information on a public page and handling internal records are separate actions. We may keep a minimal suppression record to prevent republication, or narrowly necessary records for security, legal duties, or disputes. Requests concerning internal source copies and backups are assessed separately. We cannot directly erase another website’s original post or independent cache, but will take further steps where required by applicable law. Nothing on this page limits your statutory rights.

Contact and changes

Privacy questions and requests should be opened through the private support-ticket system. Material policy updates will be dated on this page.