
Privacy Policy
Kickback Privacy Policy
Effective date: September 8, 2026
Bluega LLC ("Bluega," "we," "us," or "our"), based in Boston, Massachusetts, United States, operates Kickback. This Privacy Policy explains how we collect, use, disclose, and retain personal information when you play Kickback, use its statistics features, or contact us about the game.
Bluega LLC is responsible for the processing described in this policy. You can contact us about privacy or request deletion of your information at Support@bluegastudios.com.
1. Information we process
Account and authentication information. We process platform account identifiers, display names, and authentication and entitlement information to identify players and verify access to the game. For Steam players, this includes Steam IDs, persona names, and authentication tickets. For the planned Meta Quest version, when available, this includes Meta user IDs, Horizon usernames, and account-verification proofs. We do not ask you to provide your Steam or Meta password to Bluega.
Gameplay and statistics. We process multiplayer sessions, teams, maps, game modes, character state, and match events. Stored statistics include information such as kills, deaths, revives, objective results, weapon use, shots, hits, damage, movement distance, and connection quality. These records may be associated with your platform account. Our statistics system supports player history, the public stats website and API, and spectator tools.
VR movement and interactions. Kickback processes headset and controller positions, orientations, and interaction inputs to control your character and synchronize gameplay. Other players and spectators receive the character and gameplay information needed to present the multiplayer experience. Movement-derived statistics may also be stored as described above.
Voice communication. When voice chat is active, microphone audio is processed and transmitted through Photon Voice to other players. Bluega uses this audio for live communication and does not save voice recordings. Other participants may independently record or broadcast audio they receive.
Technical information. Our game and infrastructure providers process connection information, including IP addresses, session identifiers, latency, and diagnostic information, to connect players, operate services, and troubleshoot problems.
Reports and support. We process player reports, including reporting and reported account identifiers, categories, timestamps, and moderation outcomes. When you contact us, we receive the email address, message, attachments, and other information you provide.
2. How we use information
We use information to authenticate accounts; provide multiplayer gameplay, voice chat, statistics, and spectator features; display player names and match results; diagnose problems; respond to support and privacy requests; investigate reports; and enforce game rules and access restrictions.
Our moderation system can apply automated rules using player reports and moderation history to restrict access. You can contact Support@bluegastudios.com with concerns about an account's information or a moderation decision.
Kickback does not display advertisements or integrate third-party analytics services. Bluega uses its own statistics system. Where Meta-derived data is used to develop product-level analytical insights, those insights must not identify individual users or devices. Account-linked player statistics remain personal information.
Where applicable law requires a legal basis, we process information as necessary to provide the services you request, for legitimate interests such as service security and support where permitted, to meet legal obligations, or with consent where required. Consent to optional sharing can be withdrawn.
3. Public statistics and multiplayer visibility
Individual player statistics are publicly viewable. The current Steam stats website and public API show player names and Steam IDs, including links to Steam profiles. Anyone may view, copy, or share public information.
In-game scoreboards and the desktop spectator API use display names. The spectator API also includes a session-specific player number. Character movements, match activity, and relevant statistics are visible to other players and spectators. Names and gameplay may appear in broadcasts, and voice is audible to its intended recipients.
The Meta Quest integration is planned. Before publishing a Meta player's username and account-linked statistics on the public website or API, we will obtain the player's express direction or consent as required. Raw Meta account IDs will not be published. General acceptance of an EULA does not replace the separate sharing choice. Information about that choice and withdrawal will be provided when the feature becomes available.
4. Service providers and other disclosures
We use Amazon Web Services for backend hosting and storage, Photon / Exit Games for multiplayer networking and voice, and Webador / JouwWeb B.V. for our support mailbox. These services process information needed for their respective functions. Support emails may include account identifiers and request details supplied by players.
Steam and Meta also process information independently to operate their accounts, stores, devices, and platform services under their own privacy policies.
Meta User Data is shared only as permitted by Meta's requirements: at the user's express direction or with consent, with providers operating the game under the required agreements, or when required by applicable law or regulation. Additional restrictions apply to raw Meta IDs, access tokens, and app secrets. A business transfer does not create an additional permission to disclose Meta User Data.
5. Retention
Retention is determined by the purpose of each record and applicable legal and platform obligations. Account-linked statistics support ongoing player history. Reports and moderation records support investigations, restrictions, appeals, and necessary repeat-abuse prevention. Support correspondence supports resolution and relevant follow-up.
Persistent statistics and reports do not currently have a general automatic expiry. This does not override deletion rights or permit retention after the information is no longer necessary. Uninstalling the game does not automatically delete backend records. Privacy requests are handled through the email process below.
Temporary records, logs, caches, and backups may have different service-specific retention cycles. Applicable deletion requirements extend to relevant copies held by our providers. Any information that must be preserved for a specific legal obligation is limited to that purpose and remains subject to applicable platform requirements.
Anonymous aggregate statistics may be retained longer where they cannot reasonably be linked to a player, account, or device. Replacing an identifier with a linkable hash does not, by itself, make data anonymous.
6. Privacy choices and deletion requests
Email Support@bluegastudios.com to request access, correction, or deletion of your information. For deletion, the suggested subject is "Kickback data deletion request." Include your platform and an account ID or profile link, if available. The exact subject wording is not required. Do not send passwords or authentication tickets.
We may request information reasonably necessary to verify account control. We handle requests without undue delay and within applicable legal and platform requirements. Deletion addresses the relevant account-linked information and public statistics under our control, including applicable exports and provider copies. It may remove your game history or affect account-linked features. We cannot necessarily remove copies independently made by others.
For Meta User Data, deletion obligations also arise when the information is no longer necessary, when Meta requires deletion, and when the underlying account is deleted or no longer exists, subject to Meta's permitted de-identification provisions. Moderation records are not subject to a blanket exemption from these requirements.
Bluega cannot delete your underlying Steam or Meta account; contact that platform for account deletion. You can manage microphone access through device permissions; disabling it prevents voice chat from functioning.
Depending on your location, applicable law may also provide rights to obtain a portable copy, object to or restrict processing, withdraw consent, or complain to a privacy regulator. Contact us to exercise applicable rights.
7. Security and international processing
We use technical and organizational measures intended to protect personal information. No system can guarantee absolute security. Bluega is based in the United States, and information may be processed in the United States and other countries where our providers operate, subject to applicable data-protection and transfer requirements.
8. Age eligibility
Kickback is intended for players aged 14 and older and is not intended for children under 14. Players must also meet any higher requirements imposed by applicable law or their platform. Where parental authorization is legally required for particular processing, that requirement still applies.
If you believe a child has provided information contrary to these requirements, contact Support@bluegastudios.com so we can investigate and take appropriate action.
9. Changes to this policy
We may update this policy to reflect changes in the game, our practices, or applicable requirements. Updates will appear on this page with a revised effective date. We will provide additional notice or obtain consent where required.
10. Contact
Bluega LLC Boston, Massachusetts, United States Privacy, support, and data-deletion requests: Support@bluegastudios.com