MobilePixel.

Mafia Money Privacy Policy

Last updated: 9 October 2026

This policy applies specifically to Mafia Money, developed and published by MobilePixel Game Studio LLC (MobilePixel, MPGS, we or us). Its Android package is com.mpgs.mafiaidle. MobilePixel Game Studio LLC is responsible for the information we handle under this policy.

This policy covers the Android game and our browser version. Features vary by build and platform. Describing a feature here does not mean it is enabled in your version. You do not need an account to read this policy.

Information Mafia Money handles

Player-journey records are events, not screen recordings. Our analytics does not record microphone audio, contacts, passwords or text you type in other apps. We receive feedback text when you send it. Please do not include payment details, passwords or sensitive personal information in feedback.

Optional analytics and gameplay offers

When you consent to studio analytics, the game can send events to our private service at stats.mobilepixelgamestudio.com. Authorized studio staff can review installation-level timelines and grouped reports to understand session length, where players stop, progression, retention, ad performance and revenue. We use internal analysis tools; these player timelines are not public.

Current integration: the event system and upload transport are implemented, but optional analytics stays off unless an in-game consent flow obtains your permission. An unknown or denied choice is not permission. Before offering collection to players, we will provide the applicable disclosure and a way to withdraw consent. Requesting feedback or referral services does not itself grant analytics consent.

Google Analytics for Firebase, only in versions where we enable it: Firebase Analytics is switched off by default and is turned on only in versions where we enable it. Including Google's SDK in the game does not by itself start collection. In versions where it is enabled, it stays off until you allow optional analytics in the game, and the game always tells Google that this data may not be used for advertising storage, ad personalization or ad user data. After you allow it, Google's SDK collects its own documented information, such as app opens, sessions, app and device details and an app instance identifier. Where our Google Play and Firebase accounts are linked and the integration supports it, Google's SDK can also measure Google Play purchases automatically. The game does not send purchases to Firebase separately. The game can also send one event of its own: a first-purchase milestone with the product ID, a label describing how the first purchase was identified, and no amount. This event also carries a pseudonymous event identifier and the version of our measurement rules. This data is linked to an identifier for your installation, so it is pseudonymous, not anonymous. Withdrawing consent turns off new Firebase Analytics collection; it does not delete data Google has already received.

We use these Firebase reports to understand retention and purchases, and to measure our own advertising campaigns. We do not currently have a Google Ads account, and Firebase Analytics is not linked to Google Ads. We will update this policy before making that link.

Some versions use local progression, time since first play, purchase status, recent ad interactions or an experiment assignment to choose eligible offers and ad frequency. Established players who have not purchased may have a different eligible ad schedule from new players or purchasers. These rules use gameplay behavior rather than inferred sensitive characteristics, and remain subject to the game's limits, entitlements and privacy choices.

Advertising

The current Android integration uses Google AdMob through a Capacitor plugin, with Google's User Messaging Platform for advertising consent and Privacy Options. The browser version does not load this native AdMob plugin. The current Mafia integration does not use Unity LevelPlay/ironSource; those services being used by another MPGS game does not mean they receive Mafia data.

When enabled, AdMob and its enabled mediation partners can process device and advertising identifiers, IP addresses, app information, ad views, clicks and diagnostics to serve ads, measure performance, limit repetition and prevent fraud. Where permitted and enabled, ads may be personalized. We can receive impression and estimated ad-revenue reports.

Advertising choices are separate from optional studio analytics. Refusing personalized ads does not necessarily stop all technical processing or non-personalized ads. Advertising Privacy Options, when offered in Settings, let you revisit the provider's choices. Android also lets you reset or delete the advertising ID; doing so does not delete information already received by us or a provider.

We may promote the game through Meta ads on Facebook and Instagram. Meta handles interactions with those ads under its own policy. The game forwards no in-game events to Meta unless we enable Meta app events in a version.

Meta app events, only in versions where we enable them: in those versions, the game can share app activity with Meta, which runs Facebook and Instagram, to measure and optimize our ads. What happens depends on the answer Google's consent tools give when the game starts. In the European Economic Area, the United Kingdom and Switzerland, and wherever else those tools indicate that consent is required, the game asks you first and sends nothing to Meta unless you choose Allow. Where those tools indicate that consent is not required, the game shares this activity without asking, and you can turn it off at any time in Settings. If the game does not get a current answer when it starts, it sends nothing to Meta. Once sharing is on, the game starts Meta's SDK, turns on advertising-ID collection and can send app activation, a first-purchase milestone with the product ID, and validated purchases with the amount, currency and product ID. Each of these events also carries a pseudonymous event identifier and the version of our measurement rules. Meta's SDK also collects its own technical information, such as device and app details, and Meta may combine this information with information it already has. The game does not forward feedback text, save data, email addresses, passwords or raw purchase receipts or tokens to Meta. Turning sharing off in Settings stops new events from the game, turns off advertising-ID collection and discards events not yet sent, but does not retract information Meta has already received.

TikTok app events, only in Android versions where we enable them: in those versions, the game can use TikTok's Business SDK to share app activity with TikTok to measure and optimize our TikTok ads. The browser version never includes it. TikTok has its own choice in the game, under Settings > TIKTOK SHARING. Allowing Meta app events, accepting Google's advertising consent form or allowing studio analytics does not turn TikTok on. In the European Economic Area, the United Kingdom and Switzerland, and wherever else the game's consent tools indicate that consent is required, the game asks you first and does not start TikTok's SDK unless you allow TikTok. Where consent is not required, TikTok app events can run until you turn them off in Settings > TIKTOK SHARING. If the game cannot determine whether consent is required, or if you have declined TikTok, the game does not start TikTok's SDK.

Once TikTok app events are on, TikTok's SDK automatically records app installation and app launch, and the game can send two kinds of events of its own: completing the tutorial and reaching levels 5, 10, 20 and 50. TikTok's SDK also collects its own technical information, including app and device information, identifiers such as your advertising ID where available and permitted, install referrer information and network information. TikTok may combine this information with information it already has. The game does not send purchases, purchase amounts, achievements, in-game currency spending, rewarded ad views, feedback text, save data, email addresses or passwords to TikTok.

Turning TikTok off in Settings > TIKTOK SHARING saves your choice and stops the game from sending new activity to TikTok. Activity already queued or being sent by TikTok's SDK may still reach TikTok. If you later turn it back on, sharing resumes only after you fully close and reopen the game. Turning TikTok off does not retract or delete information TikTok has already received.

Mafia Money does not use a mobile measurement partner to attribute installs. These advertising measurement choices are separate from advertising consent for AdMob.

Crash reporting

Where crash reporting is enabled, the game uses Firebase Crashlytics, a Google service, to tell us when it crashes or hits an error in its own code. This section applies only to Android versions in which we have enabled crash reporting. Describing it here does not mean your installed version has it.

According to Google's documentation, a Crashlytics report can include the crash stack trace, device and operating system details, the app version, timestamps and installation identifiers created by Firebase. Crashlytics also records app sessions so we can measure how often the game runs without crashing. These installation identifiers are random and belong to your installation. They are not your advertising ID, but they are pseudonymous identifiers, not anonymous ones.

The game adds only its web build version and whether the error stopped the game. For errors in the game's own code, it shortens the message and removes email addresses, web address query details, long numbers and long token-like strings before passing it to Crashlytics. The game does not intentionally add your save data, feedback text, email address, purchase tokens or receipts to crash reports. Google's SDK collects its own technical information directly, so the game's filtering does not control everything Google receives.

We use crash reports to find and fix crashes and errors. Crash reporting is separate from Firebase Analytics and from your analytics and advertising choices, because it supports the game's basic functioning. Google states that it keeps Crashlytics crash data for 90 days and then begins removing it from its live and backup systems. See Privacy and Security in Firebase, linked under Google in the providers list. This is Google's own retention and is separate from how long we keep studio records.

Feedback, referrals and reviews

Feedback goes to our private studio inbox. The in-game form does not require an email address. If a feedback reward is enabled, the form explains its amount and minimum message requirement before submission. A receipt prevents duplicate rewards. Rewards do not depend on positive or negative sentiment.

For referrals, our service associates participating installation identifiers, the shared code, joining time, qualification status and reward receipts. This lets it issue the joining and daily rewards described in an enabled offer and reject duplicate claims. Sharing a code uses the service you choose, not an uploaded address book. Another player cannot access your feedback or analytics timeline.

The current referral integration leaves a code pending until a qualifying progress record reaches the server. It does not send an optional analytics event without permission. If no qualifying record is available, the reward remains unconfirmed; a pending code is not proof that a reward has been granted.

Supported Google Play builds may ask for a review after a milestone or verified purchase. Google decides whether to display its native prompt and handles the review. We do not reward store reviews or route players differently based on a proposed star rating. The browser version cannot display the native Play review sheet.

Who receives information

Authorized studio staff and service providers handle information for these purposes. Hosting providers process service records for us. Advertising and store providers also have their own purposes and policies.

We do not sell personal information for money. Some laws define advertising-related transfers more broadly, including sharing for targeted advertising. We honor applicable rights described below. We may disclose records to comply with law, investigate fraud or security incidents, protect rights, or complete a business transfer with appropriate notice and safeguards.

Legal bases, choices and requests

Where a law requires a legal basis, we rely on consent for optional analytics, including Firebase Analytics, and for advertising processing that requires consent, including Meta app events and TikTok app events where consent is required; providing a requested service for feedback, referrals and any purchases; legitimate interests where permitted for security, fraud prevention, reliability and crash diagnosis; and legal obligations for required financial or legal records. We do not use legitimate interests to bypass a consent requirement.

You can choose not to send feedback, use referrals or submit a review. Withdrawing optional analytics consent stops new optional collection and clears queued optional events; it does not automatically delete server records or cancel essential service requests you choose to make. If a control is unavailable in your installed build, contact us below for help or a privacy request.

Depending on where you live, you may have rights to access, correct, delete or obtain a copy of information, withdraw consent, object to or restrict processing, or opt out of certain advertising-related disclosures. Contact us to exercise these rights. You may also complain to your local privacy regulator. We respond as required by applicable law and do not penalize you for exercising privacy rights.

Include the game name and, if available, your player or installation ID. We may request limited verification to find your data without disclosing another person's records. Do not include an installation secret, password, full payment details or identity documents in an initial email.

Clearing app or browser data removes local information but does not ask us to delete server records. Contact us before clearing identifiers if you want us to locate existing records. Mafia Money does not currently require an MPGS email/password account.

How long we keep information

Retention depends on providing requested services, resolving support issues, fulfilling or preventing duplicate rewards, investigating errors or fraud, and accounting, legal or dispute requirements. We delete or de-identify information when it is no longer needed for these purposes. We do not promise a fixed automatic 90-day deletion period.

Feedback messages and anti-duplicate reward receipts are separate records. Verified deletion requests cover associated installation, feedback and referral data, subject to necessary legal or security exceptions. A limited suppression record can remain to prevent deleted data from being uploaded again. Backups and providers' own records may have separate retention processes; contact us about your request. Provider retention is separate from ours: Google's Crashlytics retention is described in the crash reporting section, and Google and Meta keep analytics and app-event data under their own retention settings and policies.

Security and international processing

Our website and studio services use HTTPS. Private reports require authentication, and online feedback and reward requests authenticate the installation. No system guarantees absolute security.

We and our providers can process information outside your province or country, including in the United States, where privacy laws may differ and authorities may lawfully access records. We apply safeguards required by applicable law for these transfers.

Children

Mafia Money is intended for teenagers and adults, not children under 13. We do not knowingly collect personal information from children under 13. Higher local age requirements for particular consent or features still apply. Contact us if you believe a child provided personal information so we can investigate and delete it as appropriate.

This webpage and policy changes

This is a public HTML page with no login, required download or scripts. It loads no advertising pixel or analytics script. The host receives technical request information, such as an IP address, requested URL and time, to serve and protect the site.

We change the date above when we update this policy. Before a material change to collection, use or sharing, we provide any additional notice and obtain any new consent required. A policy update does not enable a disabled SDK or grant analytics permission.

Privacy contact and deletion requests

Contact the privacy team at MobilePixel Game Studio LLC. Include Mafia Money in your request.

mobilepixelgamestudio@gmail.com