Legal
Legal & disclaimers
Riot Games fan-content policy
lolclassicwiki.com was created under Riot Games' "Legal Jibber Jabber" policy using assets owned by Riot Games. Riot Games does not endorse or sponsor this project. (That sentence is the notice Riot asks every fan project to display, and we mean it.)
Not affiliated with Riot Games
lolclassicwiki.com is an independent fan project. It is not affiliated with, endorsed, sponsored, or specifically approved by Riot Games, Inc. League of Legends and all related names, marks, and imagery are trademarks or registered trademarks of Riot Games, Inc. League of Legends © Riot Games, Inc. Our wordmark and the rune-page artwork on the home page are original work; no Riot logo is used anywhere on this site.
Content accuracy
We strive for accuracy and label unverified data clearly, but content is provided "as is" without warranty. Values marked DATA_PENDING are not yet confirmed.
Game imagery
Original-era champion splash art is preserved via the community's League wiki file archive; it is shown for the classic look and is not necessarily the art the Classic client displays in-game. Champion splash art, portraits, ability icons, rune icons, and item icons are game assets © Riot Games, served from Riot's public Data Dragon asset library and used non-commercially under Riot's "Legal Jibber Jabber" fan-content policy. Reveal-card screenshots are from the League Classic reveal. If you represent Riot or another rights holder and want an asset reviewed or removed, email help@lolclassicwiki.com.
Privacy
Analytics: no analytics service is currently enabled on this site. If one is ever added it will be Plausible, a cookieless, privacy-focused service that counts pageviews in aggregate - no cookies, no personal identifiers, no cross-site tracking - and this page will say so.
Newsletter: if you sign up for the launch email, we store your email address, the signup time, and the page you signed up from, on our hosting provider's database (Netlify). It is used solely to send launch-related email - never shared, never sold. To be removed, reply "stop" to any email or write to help@lolclassicwiki.com; privacy requests use the same inbox.
Community accounts are optional. When community services are enabled, Netlify Identity handles sign-in and the site stores your chosen display name, private drafts, submission snapshots, your personal tier list, and account-backed votes. Email addresses and provider identifiers are not shown on public profiles. You can continue browsing, planning, sharing links, and using the anonymous submission path without an account.
Profiles are private by default. If you switch your profile to public in the account panel, your display name and your tier list become visible to anyone on the community tier lists page; switching back to private hides them again immediately. Nothing else you save is ever shown publicly without publishing.
Affiliate links: some outbound links (currently NordVPN) are affiliate links, always labeled as such where they appear. If you buy through one, the site earns a commission at no extra cost to you. Affiliate partners receive no data from this site - the link is an ordinary outbound click.
An anonymous voter cookie keeps one active vote per build in the current browser. It is an opaque browser token, not proof of a unique person and not an account credential. The server stores only an HMAC-derived voter key. Clearing browser data or changing browsers creates a different token.
Screenshot retention: signed-in screenshots stay private while a draft or review needs them. They are decoded and re-encoded before storage; abandoned, unreferenced files are eligible for cleanup. Screenshots submitted through the anonymous form remain in Netlify's private moderation workflow. Approved images are copied deliberately into the public archive.
Drafts and saved builds stay private. When a signed-in member submits a build for publication, it publishes automatically under their display name - submitting is the explicit publish action. The site operator moderates after the fact and can remove any published build. Guest submissions through the anonymous form are still reviewed by a human first. Published contributions remain part of the public archive after account deletion because publication was an explicit user action; you may request removal or anonymization through the privacy contact below.