Privacy & your data
This policy covers Four Battle: Four in a Row (also listed as Connect 4 Battle), Android package dk.pohl.battleconnect, and its online game services. The developer and data controller is Michael Pohl. Contact [email protected] about privacy or support.
Updated 24 October 2026 · Advertising described below applies to Android version 0.3.4 and later. Earlier versions do not display ads.
Your guest profile
The game signs you in as a guest using Firebase Authentication. No email, password, real name or phone number is required to play. A random account identifier and session credentials let the server recognize you and save your results. This guest profile is tied to the app installation; clearing app data or reinstalling can lose access to it.
What the game processes
- Account identifiers: your Firebase user ID, authentication tokens and a generated public player alias.
- Game activity: matchmaking and friend-room requests, game moves, match participants and results, ratings, wins, losses, streaks and achievements. Live connections and games are counted to operate the service.
- Technical connection data: IP addresses and basic app, SDK and device-platform information processed by Firebase Authentication and network infrastructure to connect you, secure the service and prevent abuse.
- Support requests: your email address, support ID and information you choose to send when contacting the developer.
The app does not include purchases, chat, location permissions, contacts access, Firebase Analytics or Crashlytics. It does not ask for camera, microphone or photo access.
Banner advertising and your choices
Android version 0.3.4 and later uses Google AdMob to display a banner below the game. Google's Mobile Ads SDK may collect and share your IP address (which can indicate approximate location), device and advertising identifiers, app and ad interactions, and diagnostic information such as performance and crash data. These are used to deliver and measure advertising, prevent fraud, and operate and improve the advertising service. The game does not send your Firebase account ID, rating or match history to AdMob.
Google's consent message appears where required before ads are requested. Where available, you can revisit your choices in ⋯ → Privacy & support → Ad privacy choices. The game remains playable if an ad cannot be shown. Your choices and applicable rules determine whether ads may be personalized; non-personalized ads may still process data for delivery, measurement and fraud prevention. You can also manage or delete your advertising ID in Android's privacy settings.
Google and the advertising partners identified in the consent message process advertising data under their own policies and retention periods, which are separate from the game's guest profile. See Google's Privacy Policy and how Google uses information from apps that use its services. Advertising data is transmitted using encryption. Where consent is required, processing depends on your consent; you may change your choices through the controls above.
Why and who can see it
Account and game data are used to provide multiplayer games, reconnect sessions, calculate rankings and show progress. Operational measurements help maintain the service. Opponents can see your generated alias and game actions; the leaderboard displays top players' aliases, ratings and wins. Do not use the support ID as a public nickname.
The game backend runs on infrastructure operated by the developer. Google Firebase provides authentication and Firestore storage as service providers. Data may be processed in countries other than your own; see Firebase's privacy and security information. Guest account and match records are not sold or provided to advertisers. The separate advertising data described above is processed by Google and its advertising partners. Limited information may be disclosed when legally required.
Where applicable, processing to provide the game is necessary to deliver the service you request; security and aggregate operational monitoring serve the legitimate interest of keeping it reliable. Support data is used to answer your request.
Security and retention
The app connects using encrypted HTTPS and secure WebSockets. Account credentials are stored in the app's private storage. Backend data access is restricted to the service and authorized operators.
Guest profiles and game records remain stored until deletion is requested and completed. Live presence, queues and room data expire as sessions end. Monitoring history is retained for up to 360 days, subject to storage limits. It includes aggregated activity and leaderboard snapshots with generated aliases. Firebase has its own service-log and backup retention periods, described in its privacy information.
Request account and data deletion
In the app, open ⋯ → Privacy & support → Request account & data deletion. This opens an email draft to [email protected] with your support ID. You choose whether to send it.
You can also email that address directly with the subject Four Battle account and data deletion. Include your support ID if available, found in the same in-app panel. If you no longer have the app or its ID, explain this in your request; support will help identify the account where possible. Do not send passwords or sign-in tokens.
After verifying ownership, the developer removes the guest authentication account and player profile, including rating and achievement data, and removes or de-identifies account references in historical matches and identifiable monitoring records. Anonymous aggregate counts and records required by law may remain. Support will explain any necessary exception. Deleting the app alone does not delete server data.
Your choices
You can contact the developer to request access, correction or deletion of your personal data, or raise a privacy concern. Depending on your jurisdiction, you may also have rights to restrict or object to processing and to complain to your local data-protection authority. In Denmark, this is Datatilsynet.
Changes
This page will be updated when the game's data practices change. The effective date identifies the current policy.