Cookie Policy

This Cookie Policy explains how the 101st Doom Battalion website uses cookies and similar browser-storage technologies.

The current site uses storage only for strictly necessary security or functionality requested by the user. It does not use advertising or behavioural tracking cookies, so it does not currently display a marketing-cookie consent banner.

The website uses its own account and session system backed by the self-hosted PostgreSQL database. Cookies beginning with doom_native keep signed-in users authenticated and allow permission checks on protected pages.

Normal login sessions last up to eight hours unless the user signs out or the session is revoked earlier. These cookies are required for account access and protected administration features.

The Steam linking flow uses the short-lived, HTTP-only doom_steam_link_session cookie to match the browser session that began Steam authentication with the callback returned by Steam.

It is used only for the requested linking process, is unavailable to client-side JavaScript, uses SameSite protection, and expires after 30 minutes.

The HTTP-only gc_shop_access cookie remembers successful access to the protected GC Shop tool for up to eight hours. It uses strict SameSite protection and is not used for tracking.

The HTTP-only hammer_ridealong_access cookie confirms that the shared password for the Hammer ridealong report form was entered successfully. It is a signed browser-session cookie, expires internally after eight hours, and is not used for tracking.

The attendance-admin-formation value remembers an administrator's selected attendance formation on that browser until it is changed or site data is cleared.

Temporary per-tab updater values prevent duplicate deployment notices and allow the page to resume correctly after an update. These interface values do not contain passwords or authentication tokens.

Hosting, security, or proxy providers may use technical storage where necessary to deliver the website, prevent abuse, route traffic, or protect against attacks.

Cloudflare may set strictly necessary security cookies or process request data as part of its security and performance services when enabled.

No Google Analytics, Plausible, PostHog, advertising tracker, or similar optional analytics script was in use when this policy was updated.

The website links to or interacts with services such as Discord, Steam, GitHub, and Cloudflare. Those services may set their own cookies or storage when you visit or use their systems.

External profile images or Discord emoji images may also cause the browser to request content from a third-party server.

You can delete or block cookies and browser storage through your browser settings. Blocking necessary cookies will prevent login, Steam linking, restricted tools, or protected website features from working correctly.

Clearing site data also removes saved interface preferences. If optional analytics, advertising, or other non-essential storage is introduced, the site will add an appropriate consent choice before using it.

This policy may be updated if the website adds new storage, analytics, monitoring, embedded content, or integrations.

Questions about this policy can be sent to CXO 72149 Akhari through the official unit communication channels.