Cookies
Last updated: November 3, 2026.
This page describes the cookies and similar identifiers this archive actually sets or allows. It is not a game-server status page. L2Echoes is a fan archive, not NCSoft, and signing in here does not log you into Lineage II.
Essential cookies
Signed-in play uses Supabase Auth. The browser client is configured to store the session under the cookie name sb-<project>-auth-token. When that value is too large for one cookie, the Supabase library this site uses splits it into numbered chunks with the same name plus .0, .1, and so on.
During Google or Discord sign-in, the same library can set short-lived PKCE cookies on that storage key: a -code-verifier cookie, a -flows-code-verifier index, and a -flow-…-code-verifier slot for the attempt in progress. Those exist so the login handshake can finish. They are not advertising profiles.
The session cookie is scoped to path /, uses SameSite=Lax, and is marked Secure in production. HttpOnly is left off because the browser client has to read the refresh token to keep the session alive. If you block these cookies, login and the archive tools that require an account will not stick.
The language picker stores your choice in l2echoes_locale (English, Portuguese, or Spanish). That cookie lasts up to one year, uses SameSite=Lax, and is not HttpOnly. It only remembers the chrome language. It is not required to read public chronicle and location pages.
Advertising
Pages load a Google AdSense script. Google may set cookies and other identifiers on your browser to serve and measure ads. Whether those ads are personalized or non-personalized depends on your region and on the choices Google offers you. Read How Google uses information from sites or apps that use our services.
Analytics
The root layout renders Vercel Web Analytics. Vercel’s documentation says that product does not use cookies. It identifies a visit with a hash created from the incoming request, and Vercel says that hash resets each day and is not a cross-site profile. The script can record page views, including client-side route changes, along with details Vercel lists such as URL, referrer, browser, device type, and a coarse location. The archive does not pass a custom redaction callback, so paths are sent the way the default component sends them.
How to control them
Use your browser’s cookie settings to block or delete cookies for this host. Blocking the Supabase session cookie signs you out and keeps you out. Blocking or deleting l2echoes_locale only resets the language picker. Ad personalization is controlled in Google Ads Settings, and you can also use the ad controls in your Google account. Browser controls and Google’s tools are separate: clearing one does not always clear the other.
Questions about this page go through the feedback form or contact. The broader account and advertising description is on Privacy.