Voidline
Home Privacy Terms Cookies

Legal

Cookie Policy

Effective date: May 2, 2026

Overview Cookies Local Storage Auth Third Parties Manage Contact

Overview

This Cookie Policy explains how Voidline uses cookies and similar technologies on the website and in online game features. A cookie is a small text file stored by a browser. Similar technologies include localStorage, sessionStorage, device storage, tokens, and SDK-managed session data.

The Voidline marketing website does not currently set advertising cookies or analytics cookies. If that changes, we will update this policy and request consent where required.

Cookies We Use

Category Purpose Current Use
Strictly necessary Deliver pages, protect the service, maintain security, and support login or multiplayer sessions when enabled. May be used by hosting, security, authentication, or infrastructure providers. The static marketing page itself does not rely on a first-party login cookie.
Preferences Remember choices such as player name, ship/settings, audio, and display preferences. Stored mainly through local storage in the game, not tracking cookies.
Analytics Measure visits or behavior. Not currently used by the Voidline website.
Advertising Personalized ads or cross-site tracking. Not used by Voidline.

Local Storage

The game uses local storage to remember settings on your device. Current keys include:

  • buro-space-player-name for your remembered player name.
  • buro-space-settings for difficulty, run type, map, ship, weapons, camera shake, UI scale, and HUD margin.
  • buro-space-audio for sound enabled, lobby music enabled, and volume.

Local storage remains until you clear it, reset the app/site data, or the app changes it. It is not sent to us unless the game needs a value for online gameplay, such as your display name or selected loadout.

Authentication and SpacetimeDB Sessions

If Voidline is configured for anonymous online play, SpacetimeDB assigns an identity used for connection, multiplayer, progression, and leaderboards. If login is enabled, Keycloak/OIDC may set authentication cookies or store tokens to keep you signed in. Those cookies are necessary for login and account security, not advertising.

Online gameplay also uses tokens, room tickets, join tokens, token hashes, relay ids, and connection identifiers to route multiplayer sessions. These are operational session data and should not be shared publicly.

Third Parties

Links to Steam, Buro Ventures, email providers, authentication providers, or embedded platform services may set their own cookies once you interact with them or visit their domains. We do not control third-party cookies. Review the relevant provider's policy for details.

How to Manage Cookies and Local Data

You can block or delete cookies through your browser settings. You can also clear site data to remove localStorage values. Blocking strictly necessary cookies or deleting identity/session storage may break login, multiplayer, remembered settings, or anonymous progression continuity.

Because Voidline does not currently use non-essential website cookies, there is no cookie banner on the website at this time.

Changes

We may update this Cookie Policy as Voidline changes. The effective date above shows when this version took effect.

Contact

Cookie and privacy questions: voidline@buroventures.com.

Voidline

Enter the Voidline. Restore the beacons. Recover the logs.

Voidline

About Features Hangar Steam

Support

Buro Ventures Support Press

Legal

Privacy Policy Terms of Service Cookie Policy

© 2026 Voidline Team. Voidline is developed by Harald Roine / Voidline Team.