Privacy Policy

2. Information we collect

Information you provide

• Username. The handle you choose to show opponents. A display name is separate from an account and is not guaranteed to be globally unique.
• Optional account. If you sign in, Supabase processes your email address and authentication information. We use an account identifier and session credentials to recognize your account and associate account features or purchases with it. Your sign-in email is not shown to other players.
• Purchases, when enabled. Stripe processes checkout and payment information. Outmark receives payment references and status, the purchased item, and the account information needed to provide and restore ad-free access. We do not receive or store your full payment-card number. Stripe handles payment data under its Privacy Policy.
• Game interactions. Moves, challenge and Party-room participation, rematch choices, reactions, scores, round results, and similar gameplay events.
• Privacy and support requests. Information you submit through our privacy or support forms, such as an email address and the details of your request.
• Safety reports. If you report another player, we may receive the reported username, game or Party code, report reason, optional details, a player slot where relevant, and one-way hashes of the reporting device/session identifiers so we can investigate abuse without storing the raw identifiers in the moderation record.

Information generated when you play

• Game and session data. Challenge codes, board state, turn state, queues of live marks, timestamps, and random session credentials used to authorize moves.
• Local browser storage. Your browser may store your username, account session, game token, side assignment, sound preference, blocked-player choices, Terms/Privacy acceptance version, analytics and advertising preferences, a random analytics device identifier, separate Daily and Brutal statistics identifiers, notification preferences, local bot-ladder progress, and similar state so the Game can continue on the same device. A separate random session identifier may be stored for the current browser session. These service and preference records are separate from any advertising-provider storage described below.
• Optional first-party gameplay analytics. If you enable gameplay analytics, we record limited events such as app opens, game starts/completions, challenge joins, rematches, bot play, Fair Start choices, sharing, reactions, and game length. Opting in also enables visit counting: a random browser identifier is stored on your device and used to create a daily hash, alongside the page path and approximate country supplied by our hosting provider. The traffic identifier is not created before you opt in. The analytics database stores hashes rather than raw browser identifiers. These records are pseudonymous: a hash can still connect multiple events from the same browser. Gameplay events may include a game reference, validated player side, app build, and non-sensitive gameplay metadata. We do not put your username, game-session token, email address, or raw analytics identifier into the analytics event record. Turning analytics off stops new optional events and visit counts; ordinary hosting and security logs are separate.
• Daily Position aggregate stats. When you finish a Daily Position, the Game may submit the Daily date/number, outcome, move count, and a one-way hash of a separate random Daily identifier. This lets us show functional features such as the number of players, clear rate, best-move ranking, and approximate percentile without requiring an account or storing the raw Daily identifier in the results table. This feature is separate from optional gameplay analytics and does not include your username.
• Brutal Boss verified stats. When you finish a round against the Brutal bot, the Game may submit the game code, your existing private player token for server-side verification, and a separate random Brutal-stats identifier. The server verifies that you actually participated in a finished round against the Brutal bot, stores only a one-way hash of the Brutal-stats identifier, and records limited result information such as win/loss/draw, attempts, and total round moves. The raw player token is used to verify the result and is not stored in the Brutal statistics tables. These records power aggregate boss features such as verified challenger count, win rarity, daily Brutal record, and boss win streak. They are separate from optional gameplay analytics and do not include your username.
• Optional web-push reminders. If you turn on reminders, we store the browser push subscription endpoint and cryptographic delivery keys supplied by your browser, a one-way hash of the same random Daily-device identifier used for functional Daily stats, your browser time zone, platform category, reminder preferences, and limited links showing which side or Party slot that browser controls in an active game. We use this information only to deliver the reminders you enable: a Daily reminder around 9 AM local time when that Daily is still unfinished, your-turn alerts, rematch requests, and Party-ready/Party-turn alerts. The raw game token is used only to verify which side or Party slot may register for notifications and is not stored in the push-link record. We do not use push subscriptions for advertising or third-party marketing.
• Technical and security information. Our hosting and infrastructure providers may process IP address, browser/device information, request timestamps, diagnostics, and security logs as part of delivering and protecting the service.

3. How we use information

• Provide challenge links, Party rooms, matchmaking, bot games, rematches, reactions, scorekeeping, bot-ladder progress, verified Brutal Boss rarity/record features, and optional functional reminders you choose to enable.
• Authenticate accounts and game actions, prevent one player from controlling another player’s side, and provide or restore a verified purchase.
• Operate, secure, debug, and maintain the Game.
• When you opt in to anonymous analytics, measure aggregate gameplay patterns, balance, reliability, feature usage, challenge conversion, rematch behavior, and retention using our first-party analytics system.
• Respond to privacy, legal, security, and support requests.
• Enforce the Terms, review safety reports, support blocking controls, and protect users, the service, and others from abuse.

Advertising and your choices

Advertising is not currently active. We are preparing Google AdSense H5 Games Ads. Ads remain disabled while the required approvals and setup are completed. The planned limit is a possible ad when you choose to continue after your third completed game in a browser-tab session, then after games five, seven, and so on. Ads will appear only between games, never during a turn. Availability and Google's frequency limits may mean fewer ads.

When advertising is enabled, Google and the advertising partners identified in the consent controls may receive your IP address, the page address, browser or device information, ad interactions, and cookies or similar identifiers. These may be used to deliver and measure ads, prevent fraud, and personalize advertising when permitted by your choices. Read how Google uses information from partner sites and Google's Privacy Policy. You can also review Google's ad settings; those settings are separate from your choices on Outmark.

When enabled, Google's Privacy & messaging service will provide regional consent and opt-out controls. Use Privacy choices / Do not sell or share in the game footer to revisit the available controls. Outmark suppresses ad requests when required permissions are denied or unknown, when your browser sends Global Privacy Control, or while an ad-free account cannot be verified. A tab-local game count and game references help limit how often ad breaks can occur; they are separate from optional analytics.

Optional gameplay analytics, advertising choices, and notification permissions are separate. Accepting the Terms, creating an account, or making a purchase does not by itself consent to optional analytics or personalized advertising. You do not need to buy anything to decline optional advertising tracking. An ad-free purchase removes advertisements for the signed-in account; it does not remove the information processing needed for accounts, purchases, game operation, privacy choices, or support.

4. Bot play

Standard computer opponents calculate moves in your browser. Brutal can calculate moves on our server using the game state and a credential that verifies the player’s participation. Moves and game state also pass through the game infrastructure for validation. These opponents use game algorithms; they do not require sending gameplay to a third-party generative-AI service.

5. When we disclose information

We disclose information only as reasonably necessary for the service, including:

• Service providers. We use Netlify for hosting and form submissions and Supabase for authentication, database, and backend services. Stripe processes payments when purchases are enabled. The planned advertising services are Google AdSense H5 Games Ads and Google Privacy & messaging; advertising remains disabled pending approval and setup. Any additional advertising partners will be identified through the advertising privacy controls. These providers process information to deliver their services and under their own privacy terms where applicable.
• Other players. Your username, reactions, moves, score, and other game-visible activity are shown to participants in the same game. Challenge links may be forwarded by recipients, so treat them as shareable links.
• Legal and safety reasons. We may disclose information if reasonably necessary to comply with law, respond to lawful process, protect rights or safety, investigate fraud or abuse, or defend legal claims.
• Business changes. If the Game or its operating business is reorganized, sold, financed, or transferred, relevant information may transfer as part of that transaction subject to applicable law.

6. Retention

We aim to keep personal information only as long as reasonably necessary for the purposes described above, including operating active games, maintaining service integrity, resolving disputes, preventing abuse, and satisfying legal obligations. Because the Game is still in active development, specific automated deletion windows may change as the service matures.

Browser-local data remains on your device until it is overwritten, cleared by the Game, or removed through your browser’s site-data controls. Local blocking choices and legal/analytics preferences are likewise stored on that device.

Safety reports and support messages may be retained as reasonably necessary to investigate abuse, protect users, document moderation decisions, resolve disputes, and comply with legal obligations. We generally aim to delete or de-identify closed moderation/support records when they are no longer reasonably needed. Account and purchase records may be kept to provide access, restore purchases, handle refunds or disputes, and meet applicable recordkeeping obligations. Deleting browser data does not delete an account or purchase record.

Clearing site data also removes the locally stored anonymous analytics identifier; previously recorded one-way-hashed analytics events may remain in aggregate historical data subject to our retention practices. Game, Daily aggregate-result, Brutal Boss aggregate-result, push-subscription/notification-delivery, moderation, and analytics records stored in our backend may persist after a match ends until removed under our operational retention practices or in response to a valid deletion request.

7. Your choices and privacy rights

• Use a non-identifying username rather than your real name. Usernames are screened for format and many inappropriate terms, but automated filters are not perfect.
• You can turn anonymous gameplay analytics on or off from the in-game Privacy & safety panel. Turning analytics off stops new first-party analytics events from being sent from that browser.
• You can turn web-push reminders on or off from the in-game reminder panel, choose which functional reminder types you want, and also revoke notification permission in your browser or device settings. Turning reminders off deactivates the corresponding server subscription for that browser.
• You can block a player in the current game on your device. Blocking hides that player’s reactions and prevents rematches with that blocked rival in that game. This control is scoped to the device and game; it is not a permanent account-level ban.
• You can sign out of an optional account. To request deletion of an account, use the form below with the account email. We may need to verify that you control the account before making a change.
• You can clear locally stored Game data, including the local anonymous analytics identifier and blocking/preferences, using your browser’s site-data/storage controls.
• Depending on where you live, you may have rights to request access, correction, deletion, portability, information about disclosures, or limits on certain uses of personal information.
• We do not discriminate against users for exercising privacy rights protected by law.

If a privacy law gives you a specific right that applies to us, we will honor that right subject to applicable verification requirements and legal exceptions. Guest records may be difficult to identify without a game code or other relevant context. Do not send passwords, private game credentials, sign-in links, or verification codes in a request.

8. Children’s privacy

The Game is a general-audience service intended for users age 13 and older and is not directed to children under 13. We do not knowingly seek to collect personal information from children under 13 without appropriate authorization. If we learn that we have collected personal information from a child under 13 in circumstances where parental consent is required, we will take appropriate steps to delete it or otherwise comply with applicable law.

9. Security

We use reasonable technical and organizational measures appropriate to the nature of the service. For example, multiplayer actions use randomly generated game-session credentials, and the backend validates which side a session may control. No internet service can guarantee absolute security, and you should avoid placing sensitive personal information in a username or reaction.

10. International use

The Game may be accessed from multiple countries, while our service providers may process information in the United States and other locations where they operate. Where required by law, we will use appropriate mechanisms for cross-border processing.

11. Changes to this policy

We may update this policy as the Game changes. We will change the “Last updated” date and, when legally required or appropriate, provide additional notice. Material changes will apply prospectively unless law permits otherwise.