HEX MOMENTUM

Version 1.2 · effective 21 September 2026

Privacy

Controller and contact

Dmitrii Khriashchikov, Germany, operates Hex Momentum and is responsible for this notice. Contact: [email protected].

Data we use

Why we use it

We use this data to create and secure your account, run matches and community features, deliver requested notifications, provide support, prevent abuse, and maintain the service. Account and game data are needed to provide the requested service. You may use password sign-in or, where offered, choose Google sign-in; browser and Android notifications are optional.

Where the GDPR applies, the usual legal bases are performance of the service you request, legitimate interests in security and operation, and consent where an optional feature asks for it.

Who receives data

Authorized operators access data only as needed to run and support the service. netcup GmbH provides hosting infrastructure. Google receives data required for Google sign-in when you choose that method. Browser notifications are delivered through the push service used by your browser. Android notifications are relayed through Expo Push Service and Google Firebase Cloud Messaging. These providers receive the device push token and the limited notification delivery data needed to route the requested notification. Other players can see information that the game or community feature makes visible, such as your display name, avatar, match activity, and messages.

Retention and deletion

We keep account and game data while your account is active and only as long as needed to operate the service. Technical logs are kept for the operational period needed for security and diagnostics. Exact operational log and backup retention periods are not yet published.

You can request account deletion from web Settings after signing in, or use the support path on that page if you cannot sign in. The request immediately disables account access, then an erasure job removes direct account records and authored chat text. Deleted chat is left only as an identity-free placeholder so conversation structure remains intact. Shared match history may retain de-identified technical game records. A minimal internal record that deletion completed is retained for the erasure process; once it finishes, the same Google identity may create a new Hex Momentum account without restoring the erased one. An active moderation restriction may independently limit access as described in the Terms.

Cookies and device storage

Hex Momentum does not use advertising, analytics, or attribution cookies. A strictly necessary, HttpOnly refresh-session cookie is used on the web to keep you signed in. The Android app stores its refresh token and the opaque identifier of an enabled Android notification endpoint in Android SecureStore. The web app may cache static files for installation and store the identifier of a browser-push subscription after you explicitly enable notifications. These are used for account, app, and notification functions, not tracking. No cookie banner is shown for this necessary storage.

Your choices and rights

Depending on applicable law, you may request access, correction, deletion, restriction, objection, or a copy of your personal data. You may disable notifications for the current browser or Android device in app Settings and may also revoke notification permission in system settings. Email [email protected] and include enough information, such as your nickname, for us to verify and handle the request. You may also complain to a competent data-protection supervisory authority.

Changes

We may update this notice when the service or its data processing changes. The current version and effective date are shown at the top of this page.