Mahmut · Privacy Policy

How Mahmut handles your data

Last updated: July 5, 2026 Applies to: the Mahmut iOS app Need help instead? Support

Overview

Mahmut is a small arcade game. It doesn't have accounts, logins, or in-app purchases. This page explains, plainly, what it sends off your device: anonymous gameplay analytics, crash reports if something breaks, and — only if you allow it — an advertising identifier used to measure our ad campaigns.

Nothing here was written from a legal template first and reverse-engineered to fit; it describes what the app actually does, point by point.

Information we collect

Usage & analytics data (via Firebase)

The app uses Firebase Analytics (provided by Google) to understand how the game is played. It logs a small set of custom events, plus a standard baseline Firebase attaches to every app that integrates it:

EventWhat it tells us
game_startA run began.
game_overA run ended, with the score reached.
new_high_scoreA personal best was set, with the score.

Alongside those, Firebase automatically attaches standard technical fields to every event: device model, OS version, app version, language/country (from your device's locale, not GPS), timezone, session length, and an anonymous per-install identifier generated by Firebase itself.

This does not include Apple's advertising identifier (IDFA). The Firebase module used in this app is configured without IDFA support, so Firebase never sees or stores it.

Crash & diagnostic data (via Firebase Crashlytics)

The app also uses Firebase Crashlytics to catch and diagnose crashes. This only activates if the app actually crashes — nothing is collected during normal, working sessions. When it does fire, a crash report is generated containing:

Advertising & attribution data (via Meta)

Separately, the app integrates the Meta (Facebook) SDK — not to show ads inside the game, but to measure the performance of ad campaigns we run for Mahmut on Facebook and Instagram. It logs the same three milestones (game_start, game_over with score, new_high_score with score) to Meta, so we can tell whether people who saw an ad actually played the game.

If you grant tracking permission when asked (see Tracking & advertising below), this data is linked to your device's advertising identifier (IDFA). If you decline, Meta still receives the anonymous event counts, but without anything tying them to your specific device.

Locally stored data

Your best score and recent run history are saved directly on your device (iOS's standard app storage) so they persist between sessions. This never leaves your device and we never see it.

What we don't collect

Name, email, or account information Precise location (GPS) Contacts, photos, camera, or microphone Payment information Anything typed or entered by you

How we use it

We do not sell your data, and we do not share it with anyone beyond the service providers named in this policy.

Third-party services

Two external services process data on our behalf, each under their own privacy policy:

ServicePurposeTheir policy
Firebase (Google LLC)Anonymous gameplay analytics & crash reportingpolicies.google.com/privacy
Meta Platforms, Inc.Ad campaign measurement & attributionfacebook.com/privacy/policy

Tracking & advertising

The first time you open Mahmut, iOS will show Apple's standard App Tracking Transparency prompt, asking whether the app can track your activity across other companies' apps and websites. This exists specifically because of the Meta integration described above.

Allowing tracking lets us attribute app installs and in-game milestones to specific ad campaigns via your device's advertising identifier.

Declining has zero effect on gameplay — every feature works identically either way. It only means our ad measurement is less precise.

To be clear: Mahmut does not display any ads inside the app. The Meta SDK here is used only to measure ads we run externally on Facebook/Instagram — never to serve ads to you while you're playing.

Storage & retention

Analytics and attribution events sent to Firebase and Meta are retained according to those providers' own data retention schedules, which we don't control directly. Your locally stored best score and run history remain on your device until you delete the app — there is currently no in-app reset option.

Children's privacy

Mahmut is a general-audience game and is not directed at children under 13. We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, contact us using the details below and we'll address it.

Your choices

Changes to this policy

If what the app collects changes — say, we add a new analytics event or a new provider — we'll update this page and the "Last updated" date at the top.

Contact

Questions about this policy or your data can be sent through the Mahmut support form.