Hazmob
  • Home
  • Games
  • About
  • Careers
  • Contact
EN
  • EN English
  • TR Türkçe
  • UA Українська
  • RU Русский

Privacy Policy — Pewmon

Effective date: 17 November 2026 · Last updated: 17 November 2026

1. Who we are

Pewmon is a multiplayer arena shooter published by Hazmob. The controller of the personal data described in this policy is Hazmob Bilisim Teknolojileri Anonim Sirketi, Zeytinlik Mah. Fişekhane Cad. Carousel Blok No: 5 İç Kapı No: 17, 34144 Bakırköy, Istanbul, Türkiye (“Hazmob”, “we”, “us”).

  • Privacy requests: [email protected]
  • General support: [email protected]

Hazmob ID is our account system. The same account works in every Hazmob game that supports it.

2. What this policy covers

This policy covers:

  • the web version of Pewmon on the Playgama portal (playgama.com) and on the Pewmon website run through Playgama Wrap (pewmon.com);
  • Pewmon for Android, distributed through Google Play;
  • guest accounts, Google sign-in (Android) and Hazmob ID accounts;
  • our game services: progression, the shop, matchmaking, multiplayer matches, friends, parties, clans and chat.

Where the Android version works differently from the web version, the sections below say so under “On Android”.

Playgama is a separate controller. When you play on a Playgama page, Playgama runs the page, your Playgama account, payments, the ads and the storage that holds the game’s local save. Its own privacy policy covers that processing (see Section 7). We do not receive your payment details.

On Android, Google and AppLovin are separate controllers. Google runs your Google account, Google Play and its payments; AppLovin serves the ads (Section 7). Their own privacy policies cover that processing.

The iOS and PC versions are not covered by this version of the policy. They use other services (for example Sign in with Apple, Steam and app-store payments), and this policy will be updated before those versions are released.

3. Summary

What Why Kept for
Guest account (random browser credential) Save your progress without sign-in While the account exists (Section 9)
Playgama account link Sign-in and account recovery While the account exists
Hazmob ID: sign-in username, password hash, keyed recovery e-mail hash and masked hint Sign-in, password reset While the account exists; deleted-account records are described in Section 11
Game progress, wallet, purchases Provide the game and the items you bought Progress: while the account exists. Purchase records: for the period Turkish commercial and tax law requires (Section 9)
Display name, friends, clans Social features While the account exists
Chat messages Chat between players Up to 30 days, or less (Section 4.6)
Birth year (only if you open written chat) Age check for written chat While the account exists
Network address (temporary) Connections, security, abuse limits Not stored in our database. Short-lived counters: about 2 hours
Gameplay analytics (GameAnalytics; on Android also Firebase) Understand how the game is played and improve it On by default; on Android you can turn it off in Settings (Section 4.11)
Crash reports (Firebase Crashlytics, Android) Fix crashes On by default; you can turn it off in Settings (Section 4.11)
Android guest credential (random, stored in the app on your device) Save your progress without sign-in While the app’s data is on your device; the server account while it exists
Google sign-in link (a keyed one-way value of your Google account ID), Android Sign-in and account recovery While the account exists
Google Play orders (Android) Deliver the items you bought, handle refunds 10 years (Section 9)
Ads on Android (AppLovin) Show ads, including optional reward videos Under AppLovin’s policy (Section 4.12)

4. What we collect

4.1 Guest account

The first time you play, the game creates a guest account for you on our server. You do not need to sign in.

  • Your browser generates a random secret, the guest credential, and keeps it in its local storage. Our server keeps only a one-way verifier of it (a SHA-256 hash). Anyone who copies the credential can use that guest account.
  • If you clear your browser data, or play on another device or browser, the guest account cannot be recovered unless you have linked a sign-in method to it.
  • We record when we first saw the account and when it last played.

On Android. The app creates the guest credential and stores it in the app’s private internal storage on your device, which other apps cannot read.

  • Pewmon keeps no app data in Android’s device backup or in a transfer to a new device. Uninstalling the app, clearing its data or moving to another device therefore leaves the guest account behind: unless you have linked a sign-in method, it cannot be recovered.
  • After you sign in, the app keeps its sign-in record in the same private storage, encrypted with a key held by Android’s keystore on your device.

4.2 Signing in with Playgama

If you sign in with your Playgama account, Playgama gives the game a player identifier and a player name. Our server asks Playgama to confirm that the sign-in is genuine.

  • We do not store the raw Playgama identifier. We store a value derived from it with a secret key, which cannot be turned back into the identifier.
  • We store your Playgama player name and update it at each session. It can become your display name (Section 4.4).

Signing in with Google (Android). If you choose Google sign-in, Android’s Credential Manager asks Google for a sign-in token, which the app sends to our server once. Our server checks the token with Google’s public keys and reads only your Google account ID from it — not your name, e-mail address or picture. We do not store the account ID itself: we store a value derived from it with a secret key, which cannot be turned back into the ID.

4.3 Hazmob ID (username and password)

You can create a Hazmob ID to keep your progress across devices.

  • Username. Your sign-in name is separate from the display name other players see. We keep the sign-in name and a derived matching value. It has 3–20 characters: letters, digits and underscore.
  • Password. We do not store your password in plain text. We store a salted Argon2id hash of it. We check new passwords against a list of common and leaked passwords.
  • Recovery e-mail. Required when you register. We do not store the address itself. We store a value derived from it with a secret key, and a masked hint (for example h***@example.com) that we show only to you on your account screen. We do not check the address when you register, so please type it carefully: if it is wrong, you cannot reset your password. Several accounts may use the same recovery address.
  • Password reset. When you ask for a reset, you type your address. We send it, together with a one-time code and the usernames linked to that address, to our e-mail provider, who delivers the message (Section 7). We e-mail you only for password resets. We do not send newsletters or marketing.
  • Sessions. After sign-in our server issues an access token valid for 60 minutes. In a web browser, the sign-in lasts only as long as the page is open: if you reload or close the page, you sign in again. Our server stores only a hash of refresh tokens.
  • Security counters. To slow down password guessing and mass registration, we count failed sign-ins per username and registrations per network. The counters use values derived with a secret key; no username, password or network address is stored in them. The counters are deleted automatically within about a day.

Linking and merging. You can link several sign-in methods to one account. If a method is already linked to another account, you choose which account’s progress to keep. Merging cannot be undone (see the Terms of Use).

4.4 Game data

To run the game for you, we keep on our server:

  • your wallet (gold, diamonds), heroes, hero cards, levels, chests, quests, season and battle-pass progress, rank and career level;
  • match results: the match, your placement and the rewards it paid; the number of matches you played;
  • MVP votes you cast;
  • your display name and name changes. Display names are 3–16 characters and pass a profanity filter. Other players see your display name, your account level, your clan and the hero you play.

4.5 Friends, parties and clans

  • Friends. Your friend code, friend list, friend requests (valid for 7 days), blocked players, your “last seen” time (visible to friends unless you choose to appear offline) and the last players you played with (up to 20).
  • Parties. Who is in your party and party invites, while the party exists.
  • Clans. Clan membership and role, join requests, contributions, card requests and donations, weekly clan goals and rewards.
  • Invitations. If an invite-a-friend programme is offered, which account invited which, and the rewards it paid.

4.6 Chat and communication

Written chat is available only to players who are signed in to an account (not to guests) and who are above the age threshold (Section 10). There is no global or public chat. Quick-chat lines and map pings are available to everyone in a match.

Channel What we keep How long
Clan chat Message (after the profanity filter), sender, time 30 days; earlier if you leave and the clan forgets you, or you delete your account
Direct messages between friends Message, sender, time 30 days. Deleted at once if the friendship ends (removed or blocked)
Party chat Message and sender, in server memory only, never in the database Up to 24 hours; deleted when the party ends
In-match team chat Message and seat, in the game server’s memory only Until the match ends
Quick chat and pings Not stored —
  • Reports. If you report a message, we keep a copy of it with the 5 lines before and after it as you saw them. The copy is kept until a moderator decides on the report and is then deleted; the record that a report existed is deleted 90 days later.
  • Moderation records. Your acceptance of the community rules (version and time), chat bans (end date and reason category), and players you have muted.
  • Chat text is never written to our server logs or to analytics.

4.7 Your birth year (age question)

The first time you open a written-chat screen, we ask for your year of birth only (no month, no day). We use it for one purpose: to decide whether you may read and write written chat. We do not ask for it anywhere else, we do not use it for ads or analytics, and we never log it. You cannot change your answer yourself; support can clear it on request. Guests are asked too, because guests can read clan chat history.

4.8 Purchases

Payments are made through Playgama. We never receive your card or bank details. When you buy something, we keep:

  • a purchase intent we create when you start the purchase (an identifier, the product and the time);
  • the order: Playgama’s order identifier, the product, the portal and the time we delivered it.

Our server asks Playgama to confirm each order before it delivers the item, and delivers each order once.

On Android. Purchases are made through Google Play Billing. Google takes the payment; we never receive your card or bank details. When you buy something:

  • the app attaches a random purchase-binding code of your account to the order, so the order can only be credited to the account that made it. The code is not used for anything else, and it is not an advertising or analytics identifier;
  • our server asks Google to confirm the order before it delivers the item, and delivers each order once;
  • we keep the order: a one-way hash of Google’s purchase token, the product, the account and the time we delivered it. To confirm the purchase to Google (“acknowledge” it), we keep the purchase token itself, encrypted, for at most 70 hours, and delete it as soon as Google has the confirmation;
  • refunds and reversed payments: our server regularly asks Google which orders were refunded, cancelled or charged back, and records them (the hashed order, the time and the reason Google gives). The Terms of Use, Section 6, say what happens to the items;
  • test purchases made with Google’s licence-testing accounts are recorded as test orders and are delivered only to accounts we have marked as test accounts.

4.9 Connection and security data

  • Like every online service, our servers and providers see your IP address when your device connects. Our own database does not store it. To limit abuse we keep short-lived counters derived from your network address with a secret key (for IPv6, from the /64 network). They are deleted about 2 hours after the hour they count.
  • Our service logs record the request type, the path, the result code and the duration. They do not record your IP address, the query string, request headers, e-mail addresses or chat text. A path can contain an account identifier.
  • Our hosting, network and game-server providers keep their own access logs, which can include your IP address (Sections 7 and 9).

4.10 Multiplayer matches

When you play an online match against other people, your device connects to a game server run by PlayFlow (Section 7). The server receives your inputs (movement, aim, shots), your display name, your hero and your team chat for the length of the match, and your IP address as part of the connection. If no other player is found, the match runs in your browser with computer-controlled players, and only the result is sent to our server.

4.11 Gameplay statistics (analytics)

The game measures a fixed list of gameplay moments (for example “match started”, “tutorial step finished”, “reward video watched”) with one number or short label each, together with the game version, the platform, the portal, whether it is your first session and the number of days since your last visit. Gameplay analytics never include chat text, your birth year, your password or your e-mail address.

On the web version. The events are sent to GameAnalytics and, on Playgama pages, also to Playgama’s analytics. This measurement is on by default. GameAnalytics creates a random identifier for your browser and keeps it in the browser’s local storage, and a random identifier for each session. The web version has no in-game switch to turn it off; you can clear your browser data, or write to [email protected] to object. We do not use Firebase on the web version.

On Android. Two settings, both on by default, can be turned off at any time in Settings → Privacy. A choice you have saved always wins.

Setting Service What it sends
Gameplay analytics Google Analytics for Firebase; GameAnalytics The gameplay moments above, the app version, device model and OS version, and the identifiers these services create for the app installation and the session. Firebase also receives the estimated revenue of each ad shown (amount, ad format and ad network; not which placement). Firebase is told that ad storage, ad user data and ad personalisation are denied; GameAnalytics advertising-ID tracking, error reporting and hardware tracking are switched off.
Crash reports Firebase Crashlytics When the app crashes: the crash trace, the app and OS version, the device model and the installation identifier. Automatic collection is always off: a report is sent at the next start only if crash reports were allowed in the session it came from and are still allowed; otherwise it is deleted on the device.

When you turn a setting off, the service stops receiving data from the app at once. We do not use these services to build advertising profiles.

4.12 Ads

Pewmon on Playgama shows ads served by Playgama: an ad when you return from a match result to the lobby, and optional reward videos (for example, to double a match reward). Playgama and its ad partners decide what data they collect for ads, under Playgama’s policy. We do not receive advertising identifiers. On the Wrap website, the site also shows its own ads.

On Android. Pewmon shows ads served by AppLovin (AppLovin MAX):

  • an interstitial ad when you return from a match result to the lobby (not in your first three matches, then at most every second match, and never within two minutes of another full-screen ad);
  • optional reward videos, which you choose to watch: to double a match reward (at most three a day), to skip a chest timer, for quest progress, battle-pass rewards, shop offers and a second daily login reward.

When the app starts, AppLovin’s consent form — Google’s User Messaging Platform — asks you where the law requires it (for example in the EU/EEA, the UK and Switzerland, and in US states with such laws) whether ads may be personalised. If you refuse, you still see ads, but they are not personalised. You can change your answer at any time in Settings → Privacy → Manage ad choices. AppLovin and its partners may collect your device’s advertising ID, IP address and device information under AppLovin’s privacy policy. You can also reset or delete your advertising ID in your device’s settings. We do not receive your advertising ID.

If the app is closed while a reward video is on screen (for example because Android ended it to free memory), the app keeps a note on your device of which kind of reward video was open, tells you at the next start that the video was interrupted, and deletes the note. No reward is given for an interrupted video.

5. Why we use your data, and our legal bases

Purpose Data Legal basis
Create and run your account, save your progress, sign-in, linking, merging, deletion 4.1–4.4 Performance of a contract (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c))
Matches, matchmaking, friends, parties, clans, chat 4.4–4.6, 4.10 Performance of a contract (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c))
Age check for written chat 4.7 Legitimate interests in protecting younger players (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f))
Deliver purchases and prevent an order being used twice 4.8 Performance of a contract (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c))
Keep purchase records for tax and accounting 4.8 Legal obligation (GDPR Art. 6(1)(c); KVKK Art. 5(2)(ç))
Security, cheat and fraud prevention, moderation, stopping deleted accounts being reopened 4.3, 4.6, 4.9, 11 Legitimate interests (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f))
Gameplay analytics and crash reports 4.11 Legitimate interests in improving the game and fixing crashes (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)); on Android you can object at any time with the switches in Settings
Password reset e-mails 4.3 Performance of a contract (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c))
Ads (Android) 4.12 Personalised ads: your consent in the consent form where the law requires it (GDPR Art. 6(1)(a); KVKK Art. 5(1)). AppLovin decides its own processing as a separate controller
Google Play purchases, acknowledgement, refunds 4.8 Performance of a contract (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c)); refund and tax records: legal obligation (GDPR Art. 6(1)(c); KVKK Art. 5(2)(ç))
Google sign-in (Android) 4.2 Performance of a contract (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c))

We do not sell your personal data. We do not use it for profiling with legal or similarly significant effects. The profanity filter masks words automatically; decisions on reports and chat bans are made by a person.

6. Storage on your device and cookies

The game itself does not set advertising or tracking cookies. On the web, it uses your browser’s storage as follows:

Item Where Purpose How long
Guest credential Browser local storage Signs your guest account in Until you clear browser data
Guest sign-in step in progress Browser local storage Finishes linking a guest account if the page closes Removed when finished
Game save and settings (volume, controls, graphics, tutorial state, privacy answers, last visit date (day only), a copy of your wallet) Playgama’s storage module (on your device, or in Playgama’s cloud if you are signed in to Playgama) Settings and offline play Until you clear it, or as Playgama keeps it
Hazmob ID sign-in Page memory only Keeps you signed in while the page is open Until you reload or close the page
Game files cache Browser storage (IndexedDB) Faster loading Until you clear browser data
GameAnalytics identifier Browser local storage, created by GameAnalytics Gameplay analytics (Section 4.11) Until you clear browser data

The Playgama page and the Wrap website may set their own cookies, including for ads. The game does not control them; see Playgama’s privacy policy.

On Android, the app stores:

Item Where Purpose How long
Guest credential App private internal storage, excluded from backup Signs your guest account in Until you uninstall the app or clear its data
Sign-in record App private internal storage, excluded from backup, encrypted with an Android keystore key Keeps you signed in Until you sign out, uninstall or clear app data
Game save and settings, privacy choices, interrupted-reward-video note App private storage Settings, offline play, Section 4.12 Until you uninstall or clear app data (the note: until the next start)
Firebase, GameAnalytics and AppLovin identifiers App storage, created by those services Sections 4.11 and 4.12 Removed with the app’s data

None of the app’s data is included in Android’s device backup or device-to-device transfer.

7. Who we share data with

Service providers (processors) that run parts of the service for us, only on our instructions:

Provider Role Data Location
Render (Render Services, Inc., USA) Hosts our backend server and database All account and game data in Section 4 Frankfurt, Germany (EU)
Cloudflare (Cloudflare, Inc., USA) Network edge in front of our hosting; carries and protects traffic IP address, request data in transit Cloudflare’s global network
PlayFlow (PlayFlow Cloud, USA) Runs the multiplayer game servers IP address, match inputs, display name, team chat during a match Game servers in the EU-West region; the provider also processes data in the USA
Resend (Plus Five Five, Inc., USA) Delivers password-reset e-mails Your e-mail address, the code, your usernames on that address USA
GameAnalytics (GameAnalytics ApS, Denmark) Gameplay analytics (web and Android) As in 4.11 Under GameAnalytics’ data processing terms
Google (Google LLC / Google Ireland Ltd.) — Firebase Analytics and crash reports (Android) As in 4.11 Google’s data centres, including in the USA

Independent controllers:

  • Playgama runs the portal and the Wrap website, your Playgama account, payments, refunds through its payment partners, the ads and the save storage. We send Playgama the sign-in and order data it needs to confirm a sign-in or an order. Playgama’s privacy policy: playgama.com/confidential. On Playgama pages Playgama also receives the gameplay analytics events (Section 4.11).
  • Google runs Google Play, Google Play Billing and your Google account. We send Google the purchase token to confirm, acknowledge and check refunds of your Android orders; Google’s sign-in token is checked with Google’s public keys. Google’s privacy policy: policies.google.com/privacy.
  • AppLovin (AppLovin Corporation, USA) serves the ads in the Android version under its own privacy policy (4.12).
  • Other players see your display name, account level, clan, hero, the messages you send them and, if you allow it, when you were last online.
  • Authorities, when the law requires us to disclose data.
  • A buyer or successor, if Hazmob’s business or this game is transferred, under this policy.

Not used by the web version: Google sign-in, Firebase Analytics and Crashlytics, AppLovin MAX and Google Play Billing; they apply to the Android version as described above. Not used by any version covered here: Sign in with Apple, Steam and Xsolla.

8. International transfers

Our database is in the EU (Frankfurt, Germany), but some providers are based outside Turkey and outside the EU/EEA, mainly in the USA (Section 7). For transfers out of Turkey we use the standard contracts provided under Article 9 of the KVKK where they are required. For transfers out of the EU/EEA or the UK we rely on the standard contractual clauses in each provider’s data processing terms, or on an adequacy decision (such as the EU–US Data Privacy Framework) where the provider is certified. You can ask us for a copy of the safeguards at [email protected].

9. How long we keep data

Data Retention
Account, progress, social data, birth year Until you delete your account
Clan chat, direct messages 30 days
Party chat Up to 24 hours, memory only
Team chat Until the end of the match
Report copies Until the report is decided; the report record 90 days after that
Friend requests Valid for 7 days; deleted with the account
Security counters Network counters: about 2 hours. Sign-in and e-mail counters: within about a day
Purchase orders 10 years from the end of the year of the purchase, as Turkish commercial and tax law requires; order-owner fields are pseudonymized after deletion (Section 11)
Purchase intents 10 years from the end of the year of the purchase; they keep a reference to the deleted account (Section 11)
Deleted-account record (Section 11) As long as we run the Service; it holds no progress, contact data or messages
Google Play orders and refund records 10 years from the end of the year of the purchase, as for other purchase records
Encrypted purchase token for acknowledgement Deleted when Google has the acknowledgement, and in any case after 70 hours
Firebase Analytics (Android) Event-level data: the retention period set in our Google Analytics property, at most 14 months; aggregated reports are kept longer
Firebase Crashlytics (Android) 90 days
GameAnalytics Under GameAnalytics’ retention policy
AppLovin Under AppLovin’s own policy
Backups Overwritten within 7 days
Provider access logs Render: up to 14 days. Cloudflare, PlayFlow and Resend: under their own retention policies

10. Children

Pewmon is a general-audience game. It is not directed at children under 13, and children under 13 may not use it. If you are under 18 (or under the age of majority where you live), please play with the permission of a parent or guardian.

  • The age question (Section 4.7) is neutral: you enter your birth year freely.
  • The current written-chat threshold is 15. Because only a birth year is collected, the game conservatively allows written chat from 1 January 00:00 UTC of the birth year plus 16. Until then, players cannot read or write written chat (clan, party, direct messages, team). Quick-chat lines and pings in matches stay available.
  • We do not show personalised ads ourselves. On the web, ads are served by Playgama under its own policy; on Android, by AppLovin as described in Section 4.12.
  • On Android, the analytics, crash-report and ads services start only in builds released for our 13+ audience. Pewmon is not part of Google Play’s Designed for Families programme and is not directed at children.
  • If you believe a child has given us personal data in a way that is not allowed, contact [email protected] and we will delete it.

11. Deleting your account

You can delete your account in the game (Account screen) or on the web at api.hazmob.com/account/delete, where you sign in with your Hazmob ID username and password to confirm. Deletion cannot be undone. If you cannot sign in that way in either place (for example, you only have a guest account), e-mail [email protected] and we will verify that the account is yours and delete it for you.

Deleted: your progress and wallet, heroes and cards, season and quest progress, friends, requests, blocks, direct messages, your recent-players list, invitations, your birth year, your Hazmob ID password and recovery e-mail data, your sessions, and your display name. Your clan messages and the reports you were part of are removed or put under a pseudonym.

Retained records: the owner fields of purchase orders and certain clan-history and contribution records are replaced with random “deleted player” identifiers. Purchase intents keep a reference to the deleted account record. These retained records are pseudonymized, not fully anonymous. We keep them for accounting, tax and security reasons, for the periods in Section 9.

Deleted-account record: we keep the one-way values derived from your sign-in methods, marked as deleted, so that a deleted account cannot be restored by mistake. If you sign in again later, a new, empty account is created; deleted progress is not restored.

If the connection drops at the moment you confirm, the deletion page cannot tell you afterwards whether the deletion was completed. In that case, write to [email protected] and we will check. Copies in backups are overwritten within 7 days.

Clearing browser data removes a guest credential from that device; it does not itself delete the server account.

On Android. You can delete your account in the game (Account screen). The web page asks for your Hazmob ID username and password; if you play on Android only as a guest or with Google sign-in, write to [email protected] and we will verify that the account is yours and delete it. Uninstalling the app does not delete your server account. Refunds Google reports after a deletion are recorded against the deleted-account record; nothing is taken back from it.

12. Your rights

Depending on where you live (including under the GDPR, the UK GDPR and Article 11 of Turkey’s KVKK), you can ask us to:

  • tell you whether we process your data and give you a copy;
  • correct it;
  • delete it;
  • restrict or object to processing based on legitimate interests;
  • give you your data in a portable format;
  • withdraw consent at any time, without affecting processing before that;
  • tell you which third parties received it, and inform them of a correction or deletion;
  • object to a result produced solely by automated processing, and claim compensation for unlawful processing.

Send requests to [email protected]. We will check that the account is yours by reasonable means, for example by asking you to sign in or by sending a code to your recovery address. We do not ask for identity documents or your password in an e-mail or support message. The account’s sign-in and reauthentication forms use your password. We answer within 30 days (KVKK) or one month (GDPR), which may be extended where the law allows.

You can also complain to a supervisory authority: the Turkish Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu, kvkk.gov.tr) or, if you live in the EU/EEA or the UK, the data protection authority of your country.

13. Security

We hash passwords with Argon2id. We keep your sign-in username, keyed one-way matching values, and a masked recovery e-mail hint; the full recovery address is not stored. Traffic is encrypted (HTTPS and WSS). Access to the database is restricted to our backend. No system is perfectly secure; if a breach affects you, we will tell you and the authorities as the law requires.

14. Changes

We will publish changes here and update the date above. If a change is significant, we will also tell you in the game.

15. Contact

Hazmob Bilisim Teknolojileri Anonim Sirketi, Zeytinlik Mah. Fişekhane Cad. Carousel Blok No: 5 İç Kapı No: 17, 34144 Bakırköy, Istanbul, Türkiye · Privacy: [email protected] · Support: [email protected]

Hazmob

No risk, no victory. Face the hazard.

GamesAboutCareersContact
Google PlayApp StoreCrazyGamesPlay in browser
[email protected]
© 2026 Hazmob Bilişim Teknolojileri A.Ş.. All rights reserved.
Privacy PolicyTerms of UseData Deletion