Lobby
Mogammon

Legal

Privacy Policy

This policy explains what information Mogammon processes when you create an account, play matches, use social features, or visit the service.

Last updated October 25, 2026

1. Scope

This Privacy Policy applies to the Mogammon website, installable web application, native iOS app, game services, and related account features (collectively, the "Service"). The operator of Mogammon is referred to as "we," "us," or "our."

2. Information we collect

Account and identity information

  • Your email address, Supabase user identifier, verification status, and authentication provider.
  • If you use Google Sign-In or Sign in with Apple, the account information the provider makes available with your permission, such as your email address and provider identifier. Apple may provide a private relay email address if you choose Hide My Email.
  • Your chosen Mogammon username and, during the temporary account migration, the result of verifying legacy credentials. Legacy passwords are not retained after a successful link.

Game and social information

  • Ratings, rankings, wins, losses, match results, game records, analysis scores, achievements, and cosmetic selections.
  • Friend relationships, friend requests, challenges, matchmaking activity, and account presence.
  • A randomly generated browser identifier for guest play where guest access is permitted.

Technical information

  • Session cookies, request timestamps, IP-derived abuse signals, browser and device information, diagnostic logs, and security events.
  • Basic site usage information collected through Vercel Analytics, such as pages visited, referring pages, and device characteristics.
  • If you enable challenge notifications on iOS, an Apple Push Notification service device token, an app installation identifier, and the notification environment are associated with your account to deliver challenges to your device.
  • During TestFlight testing, Apple collects crash logs and usage information and shares beta testing data with us. Feedback you choose to submit may include screenshots, comments, device details, and contact information.

3. How we use information

  • Authenticate users and maintain secure sessions.
  • Operate matches, matchmaking, ratings, history, analysis, social features, optional challenge notifications, achievements, and cosmetics.
  • Detect abuse, enforce rate limits, investigate failures, and protect players and the Service.
  • Maintain, understand, and improve performance and usability.
  • Comply with legal obligations and enforce our Terms of Service.

We do not sell personal information or use account information for third-party behavioral advertising.

4. Service providers and disclosures

We disclose information only as needed to operate the Service, protect users, comply with law, or complete a business transition. Providers currently used by the Service include:

  • Supabase for authentication and identity sessions.
  • Google when you choose Google Sign-In.
  • Apple for Sign in with Apple, iOS push notification delivery, and TestFlight beta distribution and diagnostics.
  • Vercel for application hosting and analytics.
  • Cloudflare for realtime game and presence delivery.
  • Database and infrastructure providers used to store account and match data.

Each provider processes information under its own terms and privacy commitments.

5. Cookies and local storage

Mogammon uses cookies required for authentication, session refresh, guest identity, security, and game continuity. Browser storage may remember display preferences, guest names, match settings, and cached profile information. Blocking required storage can prevent account or game features from working.

On iOS, account session cookies are also saved in the device Keychain so you can remain signed in between launches. The app does not persist your password or Apple identity token. Local device storage keeps preferences, guest names, offline matches, and notification settings. Signing out clears the saved account session; it does not delete your server account.

6. Retention

We retain account and game information while an account is active and as reasonably needed to operate rankings, match history, security, dispute resolution, and legal compliance. Provider logs and authentication audit events follow the relevant provider's retention settings.

When an account is deleted, some match records may be retained in a limited or de-identified form to preserve results, rankings, fraud prevention, and the records of other players.

7. Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, or receive a copy of personal information, or to object to certain processing. You may also revoke Mogammon's Google access from your Google Account security settings. You can manage Sign in with Apple connections in your Apple Account settings. Disabling an identity provider connection does not by itself delete your Mogammon account. Optional challenge notifications can be disabled in the app or in iOS Settings.

In the iOS app, open Settings, then Delete account to remove your account. If you have not chosen a username, Delete account is also available on the profile setup screen. Apple-linked accounts confirm deletion with Apple. Signing out alone does not delete your account.

Retained game records replace your name with Deleted player and remove your account and seat identifiers. A minimal deletion marker containing an opaque authentication identifier prevents an in-progress deletion from recreating your profile. Transient realtime snapshots and matchmaking entries expire under their existing short lifetimes. Infrastructure logs and backups remain subject to their provider retention settings.

Contact jcbutter.dev@gmail.com for privacy questions or help with a deletion that could not finish. You do not need to email support to initiate deletion in the app.

8. Security and international processing

We use technical and organizational safeguards intended to protect information, including verified authentication, restricted database access, encrypted transport, request validation, and rate limiting. No service can guarantee absolute security. Providers may process information in countries other than your own.

9. Children

The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, contact us so it can be reviewed and removed as appropriate.

10. Changes and contact

We may update this policy as the Service changes. We will revise the effective date on this page when material changes are made. Send support questions and privacy requests to jcbutter.dev@gmail.com.