Last Epoch Terms of Use 2025 update
⚠️This article has been marked as incomplete. Sourcing or verifiability needs additional work.
#appeals channel in either Zulip or Discord to request removal.Articles must provide verifiable, credible evidence for their claims and avoid relying on forum posts, personal blogs, or other unverifiable sources. You can help by replacing weak citations with reputable reporting, corporate communications, receipts, repair logs, or independent investigative coverage that demonstrates the systemic relevance required by the Mission statement and Moderator Guidelines.
🧽🫧This article needs cleanup. It contains sources and content but lacks proper formatting/structure.
Common issues include not following the correct preload outline (incident, company, product), references that don't use <ref></ref> or Cite web, leftover "WIP" markers, or long quotes not wrapped in Quote. You can help by applying the relevant preload sections, converting raw URLs into proper citations, and removing editor notes.
Eleventh Hour Games replaced its Terms of Use for Last Epoch with a combined "Terms of Use and privacy policy" effective 25 September 2025, roughly two months after the studio was acquired by KRAFTON, Inc..[1] From Patch 1.5 (Season 5, 1 October 2026) the game client refuses to proceed until the agreement is accepted, and contains no code path to decline.[2]
Key points
[edit | edit source]- The agreement applies retroactively to copies purchased before it existed: "IF YOU DO NOT AGREE WITH ALL OF THE TERMS, YOU MAY NOT INSTALL, USE, OR OTHERWISE ACCESS ANY ELEVENTH HOUR GAMES PRODUCT OR SERVICE."[1]
- Section 10 permits revision "at any time," effective "immediately upon posting," with continued use constituting consent.[1]
- New disclosures include device fingerprinting, precise location via GPS/WiFi/Bluetooth, purchase of data from data brokers, Facebook pixels/SDKs, and crash reports containing "a portion of the memory state" of the running game.[1]
- Accounts may be cancelled "for any other reason whatsoever" without prior notice or explanation.[1]
- KRAFTON is not named as a contracting party; the counterparty remains Eleventh Hour Games, Inc.[1]
- The agreement contains no arbitration clause and no class-action waiver.[1]
Technical analysis
[edit | edit source]The client is Unity IL2CPP; the following identifiers appear in `Last Epoch_Data/il2cpp_data/Metadata/global-metadata.dat`, build 1.5.1.1 (Steam depot). Reproducible with `strings -n 5`.[2]
| Finding | Evidence (verbatim strings) |
|---|---|
| Acceptance recorded server-side against the account | ToS: Authentication service reported that the account has no acceptance on record, requesting one.ToS: The login service recorded the acceptance of version …login error type LatestTosNotAccepted
|
| Local record also kept, keyed to a version | ToS: Version 1.5.0 is not accepted locally (recorded: …)TosAcceptedVersion, TosAcceptedTimestamp, TosAcceptedLanguage
|
| No decline path exists | AcceptTosAsync, AcceptTosEndpoint, AcceptTosRequest, AcceptOfflineTosEndpoint, GetTOS — no decline/reject counterpart
|
| Closing the panel does not dismiss it | TosPanel: Refused to leave acceptance mode while the player is being asked to accept the terms of service.TosAcceptanceFlow: The TOS panel closed before the player accepted the terms of service, acceptance was not recorded.
|
| Agreement text is not shipped with the game, fetched at runtime | no terms/legal asset in StreamingAssets; TosPanel: No TOS content is defined for the selected locale or the fallback locale.
|
| Endpoints are mutable without a client patch | LoginWithSteamEndpoint, AcceptTosEndpoint, AcceptOfflineTosEndpoint are settable properties served via config.prod.api.lastepoch.com/public/gameclientconfig
|
| Parent-company platform code ships in the client | https://gpp.krafton.io/v4/public/namespaces/
|
Unintended bypasses exist, both bugs rather than options:[2]
TosAcceptanceFlow: The persistent UI is not active, the terms of service cannot be shown. The player keeps playing without being asked to accept them.TosAcceptanceFlow: The client stayed in {0} for {1} seconds, so the terms of service were never shown.