Privacy Policy

Your data / Clear information

Last updated

  • Steam identifies your account. We never receive your Steam password, and ordinary player accounts do not require an email address.
  • We keep account settings, social activity and match records to run the service. Eligible profiles and results can be public and appear in search engines.
  • Daily backups are kept for seven days. This does not automatically erase account or match history from the live service.
  • For privacy questions, access or deletion requests, join our Discord and contact staff privately.

B44 REVIVAL is the United Kingdom-based operator of this service, created by Nox and Ncj. B44 REVIVAL decides how personal information is used for the website, its API and the match services it operates. This is the role called the data controller.

This policy covers B44 Revival accounts, matchmaking, hosted matches and staff administration. Steam, Discord and the game's own services also have their own privacy policies. B44 Revival is an independent community project and is not affiliated with Bulkhead or Valve.

Our contact route is the B44 Revival Discord server. Join and ask to speak privately with staff about a privacy request. We do not offer a privacy contact email. Do not post passwords, recovery codes or identity documents in a public channel.

Information comes from you, Steam, your use of the website and hosted game servers. Reports and moderation records can also contain information supplied by other players or staff. A player can appear in match records before creating a website account.

  • Steam identity: SteamID64, public display name, avatar and Steam profile link, together with account creation and sign-in times. Public Steam information may supply a country, which you can replace or clear in your account.
  • Account choices: optional country and bio, online-status and invitation preferences, notification and sound settings, server-region choices, and Armory favorites or equipped selections.
  • Social and matchmaking activity: friend requests and friendships, parties, invitations, queue entries, ready-check answers, teams, veto choices and party messages.
  • Match records: participant identities, teams, maps, round events, scores, results, gameplay statistics and rating history. Recorded game events can include purchases, damage, kills, ping, in-game positions, text chat, votes, reports, disconnects and administrative actions. In-game positions are not your real-world location.
  • Safety and administration: player reports, case summaries, staff notes, warnings, restrictions, cooldowns, appeals, supporting information and attributed records of staff decisions. A report is an allegation, not an automatic finding.
  • Technical and security information: IP addresses, browser user-agent information, request paths and response details in relevant server logs; sign-in and security events; session and challenge records; and information needed to limit abusive traffic.
  • Authenticator information, if enabled: an encrypted authenticator secret, hashed one-use recovery codes, security status and optional remembered-device records. Staff accounts additionally have a staff email, role and status.

Your Steam identity connects the same player to their account, friends, teams and results. Account settings provide the choices you select. Queue and match information let us form teams, host matches, calculate ratings and show results.

Reports, chat records and security information help staff investigate abuse, correct disputed results, protect accounts and explain decisions. Logs help diagnose outages and suspicious traffic. Aggregate activity and match statistics help us understand how the service is running.

For UK data-protection purposes, processing necessary to provide your account and requested playing features is based on performance of our service agreement. Our legitimate interests are maintaining a fair competitive history, protecting players and accounts, preventing abuse and keeping the service reliable, while considering your rights and interests. We may also process information where a legal obligation requires it.

The current website has no advertising pixels, third-party advertising analytics or session-recording software. The dashboard's operational statistics come from service activity and match records. Search ownership tags and sitemaps help search engines discover public pages; they are not advertising trackers.

Where public access is enabled, your player identity, avatar, country, bio, rating, level, rankings and eligible match information can be visible to visitors. Detailed statistics and histories follow the platform's public-statistics setting. Eligible public pages may appear in sitemaps, search results and link previews.

These access settings apply to the platform as a whole. Your online-status and profile-invite choices do not make your entire profile private. Turning off public profiles requires visitors to sign in. Turning off public statistics limits detailed statistics for signed-out visitors, but does not hide every identity or rating. Signed-in players can still access the player views the service allows them to see.

Party messages are shown to the relevant party; live rooms and join details are restricted to their participants. Raw game chat, reports, moderation evidence, internal notes, staff audit records and authentication secrets are not published in ordinary public profiles or match summaries. All active dashboard staff roles can review player and moderation records; permissions for making changes differ.

Avoid putting information you want to keep private in a bio or message. A message removed from live party chat can remain in the staff-review archive. Removing a page from search discovery does not automatically remove copies already held by search engines or people who viewed it.

Our own cookies support sign-in and account security, rather than advertising. Production authentication cookies are restricted to the relevant site, sent over HTTPS and unavailable to ordinary browser JavaScript. Blocking them prevents sign-in and protected features. Cloudflare may also use its own security cookies when its protection features require them.

  • Website session: keeps you signed in for up to 30 days, unless sign-out, security changes or access revocation end it sooner.
  • Steam sign-in state: a temporary cookie lasting up to five minutes connects the return from Steam to the browser that started sign-in.
  • Authenticator challenge: a temporary cookie lasting up to ten minutes supports an unfinished second-factor sign-in.
  • Remembered device: if selected, a separate security cookie lasts up to 30 absolute days. It remembers proof of your factor, not your Steam identity; fresh Steam sign-in is still required. Website and dashboard device trust are separate.
  • Staff dashboard session: lasts at most eight hours and expires after 30 minutes of inactivity.
  • Local storage remembers the collapsed-sidebar setting until it or browser storage is cleared. Session storage remembers an announcement dismissal for the current browser tab/session.

We use hosting and network providers to deliver the service. The current deployment uses LuxVPS infrastructure, managed with Coolify, and Cloudflare in front of the public website. Hosting operators can process server data to provide infrastructure; Cloudflare handles web traffic and technical information for delivery and security.

Steam provides sign-in and public player information. Your browser goes to Steam to authenticate, and a Steam-hosted avatar creates a normal image request to Steam's servers. We do not receive your Steam password, Steam Guard code, payment details or private Steam email.

Discord is our community and support service. Opening the invite and using Discord is optional for playing, but is currently how you contact staff. This website does not link your Discord account to your Steam account. Information sent to staff through Discord is also processed under Discord's policy.

Joining a game server sends the network connection and player information needed to play. Battalion and its shipped Steam or Easy Anti-Cheat components can have their own data handling. B44 Revival does not operate a separate client anti-cheat. Usable replay recording and this older build's anti-cheat backend have not been fully verified.

Other recipients include players who see the information described above, authorized staff and, where legally required, relevant authorities. Search engines can read public pages. Optional IndexNow notifications send eligible published URLs to its search service when enabled; private accounts and room secrets are not sent in those notifications.

B44 REVIVAL is based in the United Kingdom, but processing is not limited to the UK. LuxVPS publishes its current server locations as Frankfurt, Germany. Cloudflare, Steam and Discord operate internationally, including in the United States and other countries.

Cloudflare and LuxVPS publish processing terms describing safeguards for relevant international transfers, including UK additions to standard contractual clauses. Steam and Discord explain their own international processing in their privacy policies. A server's location alone does not describe every provider or onward transfer.

Contact staff privately on Discord for details about the current hosting arrangement or applicable provider safeguards.

Accounts, match and rating history, party-chat archives and moderation records have no general automatic deletion period in the current service. They are retained for account operation, a consistent competitive history, reports and appeals, security and accountable staff decisions. Ask staff about information you want corrected or removed; an unused account is not automatically erased when you stop signing in.

Sign-in transactions are valid for five minutes, authenticator setup and challenge state for ten minutes, and remembered-device records for 30 days. Expired pending authenticator setup is unusable but its encrypted record is not necessarily erased at that moment. Session records are scheduled to expire about one day after their effective expiry or revocation; sign-out can remove them earlier. Database cleanup can occur after the scheduled time. Sign-in, refused-sign-in and sign-out audit events have a 90-day retention period.

Database backups are created once a day and kept on a rolling seven-day schedule. On day eight, the oldest daily backup is deleted as the new one is added. This is backup retention, not a seven-day lifetime for the live database. A backup may hold an earlier version of information until it rotates out.

Proxy, container and game-server logs follow their operational logging configuration; we do not currently state one fixed time limit for all of those logs. Information relevant to an unresolved safety issue, appeal or legal obligation may need longer retention. Staff can explain the applicable reason when handling a privacy request.

We use website HTTPS, restricted staff access, authenticated service connections, rate limits and attributed administrative records. Authenticator secrets are encrypted in the database; recovery codes and stored session or remembered-device tokens are hashed. This does not mean every account field, chat message or log is encrypted at rest or end-to-end encrypted.

An authenticator is optional for ordinary website accounts and required for all active dashboard staff. A lost factor can be reset through the authorized staff recovery process with a recorded reason; a reset invalidates associated sessions and remembered devices.

No online system can guarantee absolute security. Use Steam's account protections, keep recovery codes private, sign out on shared devices and contact staff if you suspect unauthorized access.

Matchmaking, ready checks, ratings and some queue cooldowns are calculated automatically. Inputs include queue participation, teams and results, opponent ratings and whether you accepted or joined a match. These calculations affect the games offered to you, your competitive rating and when you can queue.

Staff can review disputed results and restrictions. Use support to question an automatic outcome, or the account appeal route when an eligible restriction offers it. We do not use this information to build advertising audiences.

You can edit or clear optional bio and country, change preferences, manage friendships, sign out and manage an authenticator through the website. Clearing cookies or local storage changes the browser's saved state; it does not delete your account or match history.

Depending on the law and processing involved, you can request access, correction, erasure, restricted use or a portable copy of your personal information. These rights have conditions and exceptions. Deleting every historical match can affect other players' records, and limited information may need to remain for safety, a dispute or a legal obligation. A restriction or ban does not remove your privacy rights.

You have the right to object to processing based on our legitimate interests, including the competitive-history, safety and operational uses described here. We will consider your circumstances and whether there is a lawful reason to continue.

There is currently no self-service account-deletion or complete data-export button. Join our Discord and contact staff privately, identify the Steam account concerned and explain your request. We may ask for proportionate proof that the account is yours. Never send a Steam password, authenticator secret or recovery code.

For UK data-rights requests, the usual response period is one month, subject to the legal rules on identity checks and extensions. You can complain to the UK's Information Commissioner's Office or, where applicable, your local data-protection authority.

B44 Revival does not set a separate minimum player age. You must still meet Steam's requirements, the game's applicable age requirements and the rules where you live. Steam does not permit subscriber accounts for children under 13. Obtain parental or guardian involvement where required.

The ordinary player account form does not collect a date of birth. A parent or guardian can contact staff privately through Discord about a young person's information.

We will update this page when data handling changes and show the new date above. Material changes will be highlighted through the website or community announcements. Please revisit the policy when new features are introduced.