Cookies & Storage

Current summary

No ad cookies No third-party analytics SDK

The current core Hub uses storage primarily to provide the features you request. The privacy notice is therefore informational rather than a fake “Accept all” choice for trackers that are not actually present.

First-party session cookie

gaming_hub_session (name reflected by the current server configuration) is used to authenticate an account. The server constructs it as an HttpOnly, SameSite cookie and adds Secure on HTTPS as appropriate. JavaScript cannot read an HttpOnly cookie. Signing out/expiry invalidates the session according to the server's session rules.

Local storage

Abyss uses localStorage for functional state such as game progress/preferences, music settings, graphics choices, collection-dashboard preferences and shared game profile/cosmetic state. These values stay in that browser unless the feature also synchronizes them through your signed-in account.

Session storage

sessionStorage is used for short-lived browser-tab state, including the compact Offline Access session handoff used when launching an unlocked offline copy.

Cloudflare Turnstile

If the operator enables public bot protection, the login/register page loads Cloudflare Turnstile for security. This is not an advertising feature. Cloudflare may use cookies or similar technical signals as part of its security service; see Cloudflare's Privacy Policy.

Managing storage

You can remove cookies/site data in your browser settings. Doing so may sign you out, erase local game/preferences data, disable an offline copy, or require settings to be configured again. The “Privacy choices” control on Abyss records only that you have seen the current notice; the current site does not enable advertising/behavioral tracking when you press it.