Privacy
Belligerents is an online strategy game. This page explains the information used to sign in, keep games working, connect players, deliver optional notifications, and protect the service.
Privacy settings
Loading your analytics choice… You can also change it in Edit profile.
Age range
Belligerents is intended for teens and adults ages 13 and older. Sign-in does not verify a player’s age. If you believe someone under 13 has created an account, contact support@belligerents.app.
Account and sign-in
Sign-in is provided by Clerk and can use email, Google, or Apple. Clerk handles your login details, email address, and account identifier. Your sign-in provider may also supply an account name or photo. Belligerents uses the account identifier to connect your profile and game activity. Sign-in security records can include your IP address, browser and device details, and approximate location. Google and Apple also process information when you choose their sign-in methods. Read Clerk’s privacy policy, Google’s privacy policy, and Apple’s privacy policy.
Profile and game information
Profiles may include a username, optional biography, and profile photo. You choose profile photos through Clerk. After consented screening or operator approval, the app publishes an approved copy in Supabase Storage and stores its URL with your profile. Existing profile photos remain until you replace or remove them, or an operator acts on a report. Other players may see profile and campaign details in the places where the game displays them.
Belligerents stores campaign names and settings, players and seats, game state, moves, history, replays, and ranking records to operate online games. This information is shared with campaign participants and may appear in public game or ranking features according to the feature you use.
Messages, community, and reports
When you use social features, the service stores direct messages, recruiting-room messages, friend requests, reactions, blocks, and related status. To join, you accept the Terms and Community Rules and allow safety screening: the exact username, biography, profile photo, direct-message text, or recruiting-room message you submit is sent to OpenAI’s Moderation API to check it against those rules before other players see it. This includes a profile photo imported from your sign-in provider. We do not intentionally include your account identifier in these requests, and OpenAI states that API data is not used to train its models. Generated player names and the default unit artwork are not sent. A proposed text change or message is not published if it is flagged or the check is unavailable; the app keeps your draft so you can edit or retry. Previously published text is not automatically scanned.
A photo that is flagged, or that cannot be checked, is not published: your previous public photo or the default unit artwork stays in place, and the proposed photo is queued for operator review. Pending review metadata includes its hash, image type and size, screening categories or failure status, and the eventual decision. An authorized operator can retrieve the matching photo from Clerk to review it. We do not publish it unless screening or operator review approves it.
We record the version of the Terms and the screening permission you accepted and when you accepted them. You can turn safety screening off in Edit profile; while it is off you keep playing, reading, reporting and blocking, but you cannot post new names, bios, photos or messages. For players in the European Union and the United Kingdom, we screen submitted content on the basis of our legitimate interest in keeping the community safe. Reports may include a selected reason, optional written details, the reported account, a direct-message conversation/message reference, or a copy and timestamp of the selected direct or recruiting-room message. Reports and related evidence are available only to authorized service operators for safety review. When a report is filed or a photo is held for review, we receive an email alert containing only its type, reason and time. We review reports promptly as part of daily operations, but cannot guarantee a specific response time. Automated screening can reject a submission; it does not automatically suspend an account. After review, an operator may remove content or suspend access to social posting. In-app report and block controls appear only in supported parts of the product; you can also contact support@belligerents.app.
Rules assistant
The optional rules assistant is currently unavailable. Earlier questions and recent conversation were sent to OpenAI with relevant rulebook material to generate an answer. OpenAI processes API requests, including moderation, under its API data controls and separate security and retention policies.
When you create an account, Belligerents sends one welcome email to your verified email address. We also send essential account and security emails and replies to support requests. Creating an account does not subscribe you to a newsletter or marketing emails.
Optional Belligerents emails include an unsubscribe link that works without signing in. Unsubscribing stops optional email; essential account and security emails, requested support replies, and push-notification settings are handled separately. We retain email delivery and opt-out records to operate email and honor your choices.
Resend sends Belligerents service emails and receives support email, including your return address, message, and attachments. Copies of support correspondence are kept in Gmail so we can respond. Supabase stores email delivery records and optional-email preferences in private tables that other players cannot access. Read Resend’s privacy policy and Google’s privacy policy. Clerk separately handles authentication emails such as verification codes and password resets.
Notifications, optional analytics, and service providers
If you enable push notifications, Belligerents stores the app installation and platform details, a push token, your notification preference, and delivery status. Apple Push Notification service or Firebase Cloud Messaging handles delivery to your device and may receive the notification payload needed to display it.
Share usage and diagnostic data is one optional choice. Choosing Allow helps us diagnose broken moves, save failures and slow screens, and understand how people use Belligerents. Until you choose Allow, we do not send optional usage or detailed diagnostic reports. Choosing No thanks does not affect game saves, history, replays, rankings, player statistics, HQ charts or battle calculations. Accepting the Terms or allowing OpenAI safety screening does not give analytics permission.
With your permission, PostHog records visits and button or link clicks outside the gameboard, including Discord links, as well as errors, game-saving results and performance. Our first-party performance and onboarding reports use the same choice. Site activity uses fixed page and control identifiers and a browser/session identifier. A signed-out visitor can allow collection before signup; only activity after that permission is collected. Signing in can associate consented activity with your account identifier after your account’s permission is verified. We never reconstruct activity from before consent.
Change the choice in Edit profile or in Privacy settings above, including while signed out. Withdrawing permission stops new optional reporting on that device immediately and discards its queued reports. Other active devices check your saved choice on resume and at least every 60 seconds while visible; reporting stops if their permission check expires. Switching accounts clears the local analytics identity and pending reports. We keep the notice version, revision and timestamps of your choice privately so we can honor it. Withdrawal stops future collection; account deletion also requests erasure of linked PostHog data.
Optional reports exclude form values, message text, player names, invite tokens, credentials, full game snapshots, and raw URLs or query strings. Selected diagnostics can include static map and unit identifiers and counts, game phase, machine-coded save or display outcomes, your account identifier, browser and operating system, screen size, a page route with private details removed, and a session identifier. PostHog’s built-in automatic page-view collection, session recordings, and IP collection in app analytics are disabled. We do not use these events for advertising or tracking across unrelated companies. PostHog may also use data it anonymizes and aggregates to improve its own AI features; its terms prohibit third-party model training on that data.
Clerk provides sign-in; Supabase stores game and account data; Vercel hosts the service; PostHog provides diagnostics; Apple and Google provide sign-in and notification services. Requests to hosting and sign-in services can include your IP address and browser details. Invitation and room abuse checks use a hashed form of an IP address. Our own performance and request diagnostics are kept for 30 days and exclude message bodies, game contents, passwords, and raw IP addresses. Providers may keep separate security or access records under their service settings and policies.
Retention and account deletion
Active account, social, and shared game records are kept to operate the service. Deleting an account removes its Clerk identity, private notes, push registrations, consent records, pending photo-review metadata, and app-owned profile-photo objects. Its public profile is replaced with a pseudonymous identity, and its own direct-message and campaign-room message text is redacted, including quoted previews and report copies. Other participants’ messages and shared campaign history, moves, replays, and ranking records remain under a pseudonymous player identity. Moderation reports may retain their structured reason and pseudonymous participant IDs while free-text details and copied direct-message and room-message text are cleared where the deleting account was involved.
New account-deletion requests also erase linked PostHog profiles and events. App-data cleanup starts promptly. Erasing optional analytics history may take several days because PostHog processes event deletion during off-peak periods, including weekends. Your deletion receipt remains pending until erasure is verified; a provider’s initial acceptance is not treated as completion. Keep the receipt to check progress and confirm completion. Temporary failures are retried; previously completed requests are not reopened.
Account deletion does not automatically erase support email or every provider security, access, and backup record. These follow separate retention settings and policies; the 30-day limit above covers only our own request and performance logs. To ask about or request removal of these records, contact support@belligerents.app. Requests require ownership checks and may be limited by lawful retention requirements.
To request deletion in a browser, follow the account deletion steps. If you cannot sign in, contact support@belligerents.app and ask for deletion help. Replaced or removed app-owned photos are queued for storage cleanup; cached copies may remain briefly. Previously shared or independently saved copies cannot be recalled. We do not publish a single retention deadline for all shared game and social records.
Questions or privacy requests
Contact support@belligerents.app for a privacy question, report, or account request. Please do not email passwords, verification codes, or payment information.