Privacy policy.

Clan Finder may store public clan names, clan chat names, source identifiers and URLs, source verification flags, public image URLs, member counts, home worlds, aggregate experience or efficiency statistics, source update times, and fetch times from attributed public directory sources such as Wise Old Man.

The initial source-directory pilot stores aggregate group facts rather than member rosters or copied clan 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 RuneScape identity snapshots, stated clan role, verification method, clan 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, Wise Old Man verification codes, or other secrets as ownership evidence.

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

Clan listing submissions may include clan name, clan chat name, headline, description, requirements, region, timezone, language, member count, home world, public contact links, Discord invite, uploaded clan 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, Clan Finder may store Discord ID, username, avatar URL, sync timestamps, OAuth state cookies during sign-in, and Discord moderation workflow references. Clan Finder requests Discord identity access only and does not request or store the email address attached to a Discord account.

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

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

RuneScape name and Wise Old Man sync are optional trust signals. If used, Clan Finder may store the linked RSN, Wise Old Man player ID, display name, and sync timestamps.

When a clan enters a competition, Clan Finder may store the entered WOM group, public group membership, player identifiers and display names, metric values captured at event boundaries, calculated gains, leaderboard placement, synchronization warnings, and competition review status. Competition standings, clan scores, contributing player names, and verification labels may be displayed publicly.

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

Clan 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 Clan Finder only as a one-way hash; clearing browser data or using another browser may create another count. Traffic counters do not require RuneScape names, clan data, or gameplay data.

The Clan Finder RuneLite plugin reads approved public clan listings, listed member totals, banner thumbnails, and event data from osrsclanfinder.com. These requests may include normal request metadata such as IP address, user agent, request time, and requested API or image path.

Member totals shown in the plugin are listing data from the website. They may come from connected Wise Old Man group stats or from a manually entered listing count, but they are not live online status for clans or clan members.

The RuneLite plugin does not send RuneScape account names, clan membership, chat messages, live online status, or a plugin client ID.

Clan 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 clan owner enables Discord forum publishing or linked-owner visibility, approved listing details and the selected Discord owner signal may be shown in Clan Finder Discord forum posts.

Approved public listing content is visible on the site, may be available through public API or plugin 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.

Competition comments are public and may include the account display name, avatar, comment body, event reference, status, and timestamps. Comment reports store the reporter account, selected reason, supplied details, and related moderation state.

Deleted or reported comments and associated reports may be retained where needed to enforce site rules, prevent repeated abuse, resolve disputes, or protect competition integrity.

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

Signed-in users may favorite clans and events. Clan 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.

Clan 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 RuneScape login details. Clan Finder does not need RuneScape credentials, bank PINs, authenticator codes, recovery answers, bank information, private in-game chat, private clan membership data, or gameplay automation data.

The RuneLite plugin is read-only and uses approved public listings only. It does not automate gameplay, join clans, send messages, detect live online clan/member status, or scrape private OSRS 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.

Competition data is used to register clans, capture WOM scoring boundaries, calculate and publish standings, investigate synchronization or fair-play issues, validate results, and operate community prizes.

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

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

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

Clan 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 clan name may remain as an asset-free, unclaimed public index record based on public information.

Suspended, rejected, report, payment, 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.

Competition registrations, snapshots, calculated results, and review records may remain with the published event history after an account or listing is removed. Clan Finder may anonymize player-level data when it is no longer needed for result integrity, dispute handling, abuse prevention, or legal compliance.

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

Clan 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 clan 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.

Clan 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.