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 under Riot's "Legal Jibber Jabber" fan-content policy. This is a fan project, not a business: the ads and the tip jar go toward hosting, and the site is not sold, licensed, or run for profit. 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: Google Analytics (GA4) measures which pages get read, aggregated traffic and rough audience geography - it sets its own cookies. Ezoic supplies the consent manager. Beyond those we run no trackers of our own - nothing on this site profiles you for us.
Advertising: this site shows ads served by Google AdSense. Google, as a third-party vendor, uses cookies to serve ads here. Google's use of advertising cookies lets it and its partners serve ads to you based on your visit to this site and to other sites on the internet. You can opt out of personalised advertising at Google Ads Settings, or opt out of a third-party vendor's use of cookies for personalised advertising at aboutads.info. Third-party vendors and ad networks other than Google may also serve ads here; where they do, their own cookie policies apply and the same opt-outs above cover the ones participating in those programmes. Consent is collected before any advertising cookie is set for readers in the EEA, the UK and Switzerland.
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.
Children's privacy: this site is a general-audience reference for a 15-year-old game client and is not directed to children under 13. We do not knowingly collect personal information from anyone under 13; if you believe a child has created an account or submitted content here, contact us below and it will be removed.
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.
Voting on a build, posting a comment, and reporting a comment all require an account; reading is always open. Each keeps one entry per account, stored against an HMAC-derived key rather than your account id. The site no longer issues a guest identity cookie. If your browser still holds one from before, it is read once when you sign in, so a vote you cast earlier moves onto your account - and only the derived key is ever stored.
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 stay in Netlify's private form store and are copied into the public archive deliberately, by hand - a build publishes on its own, but nobody's uploaded image goes public unlooked-at.
Drafts and saved builds stay private. When a member submits a build for publication, it publishes automatically under their display name - submitting is the explicit publish action. Guest submissions through the anonymous form publish the same way: a build that is playable and complete goes up without waiting on anyone. Moderation happens after the fact, not before it - the site operator can remove any published build at any time, and anyone can report one.
Deleting your account is self-service from your account page and takes effect immediately - no request needed. Your profile, saved drafts, tier list, and images are erased outright. Builds and guides you've already published stay part of the public archive, the same way a comment thread survives its author leaving, but are re-attributed to "Former member" rather than showing your name. If you want a published item removed entirely instead of anonymized, or have any other privacy request, write to the contact below.