Metro Mogul Privacy Policy

1. Introduction and scope

This Privacy Policy explains how LightTerm Studio handles information in Metro Mogul (Android package: com.metromogul.game) and its online services, including purposes, recipients, retention, and your choices.

Metro Mogul offers Single Player against bots, Tutorial, Pass & Play on one device, and Online with Friends using a room code. Local saved games are not uploaded to our servers. They are separate from online match checkpoints stored on our servers.

2. Who operates Metro Mogul

Metro Mogul is developed and operated by LightTerm Studio. For privacy questions and support, contact lightdevs2005@gmail.com.

3. Information stored on your device

The game stores information locally to work and remember your choices, including:

• your Guest name and profile;
• language, audio, and animation preferences;
• theme and character selections;
• progress, checkpoints, and local saved games;
• cached content ownership information (an entitlement cache);
• a random installation ID for redeem features; and
• Guest session credentials and content access tokens.

Guest session credentials and the entitlement cache use encrypted storage on your device. This does not mean all saved games or preferences are encrypted, or that local storage is completely protected.

Using online features can send relevant data described below, such as your player name and character when joining a room. Local play does not upload local saved games to the developer's servers.

4. Guest identity and online connections

The game does not offer email/password registration, Google login, social login, or single sign-on (SSO). The former email/password account and personal cloud save features are disabled; password recovery and personal cloud save uploads are not available.

For online features, the server creates an internal Guest identity, user ID, and session token to recognize you and allow reconnection. This identity is not a Google account and does not require an email address.

Guest does not mean fully offline: AdMob, purchases, purchase restoration, multiplayer, and redeem features can communicate with the relevant services.

5. Online multiplayer

When you create or join an Online with Friends room, the server can process and store:

• Guest IDs and session information;
• player names, room codes, and room membership;
• characters and appearance choices needed for the match;
• ready and connection status;
• maps and match settings;
• turns, game actions, commands, checkpoints, and match results; and
• temporary visual data used to show movement and minigames to spectators.

Production connections use HTTPS and secure WebSockets (WSS). Match and session data that need to persist are stored in PostgreSQL so they can be recovered after a server restart. Stored checkpoints are distinct from temporary visual frames; not every animation frame is saved.

Other players in your room can see your name, character, status, and relevant game actions. They do not receive your session tokens or purchase evidence. The game has no public chat, private chat, voice chat, photo uploads, or contact list access.

The server and infrastructure providers receive connection information such as IP addresses. This information can be used to operate the service, limit requests, and address abuse. We do not use it for GPS or precise location tracking.

6. Redeem and access codes

You can choose to redeem a code to unlock certain maps or themes. These codes control content access; they do not provide an ad-free feature.

When you redeem a code or the app checks that access, information sent and potentially stored includes:

• the random installation ID generated by the app;
• your Guest ID and player name;
• platform or operating system and device model;
• the reference to the redeemed code or promotion;
• the list of content granted;
• redemption time and the most recent access-check activity;
• access status, including active or revoked; and
• access tokens needed to check your entitlement (permission to use content).

The installation ID is not an IMEI, phone number, or device serial number.

We use this information to grant and maintain content access, check validity, manage redemption limits, prevent abuse, handle support, and revoke access when needed. The developer can view redeem records through a restricted administration dashboard. After redemption, the app can check access status again when used.

Revoking access does not automatically delete redeem records or related data. Data deletion is a separate process described in Your choices and privacy requests.

7. Advertising and privacy choices

The Android game uses Google AdMob / Google Mobile Ads SDK and Google User Messaging Platform (UMP). The current ad format is a full-screen interstitial after a match ends, when an ad is available and the display conditions are met. Ads are not guaranteed after every match; availability and service conditions vary. Testing builds may use test ads.

According to Google's Mobile Ads SDK data disclosure, the SDK can collect and share:

• IP addresses, which may be used to estimate a device's general location;
• identifiers, including Android Advertising ID, App Set ID, and, where applicable, other identifiers associated with accounts signed in on the device;
• app and ad interactions, such as app launches, taps, and ad or video views; and
• diagnostics, including app launch time, hang rate, and energy usage.

Google describes purposes including advertising and ad measurement, analytics, security, fraud prevention, and detecting invalid traffic. Approximate location inferred from an IP address is different from GPS location. Metro Mogul does not request or collect precise GPS location.

Your ad privacy choices:

• UMP may show consent or privacy messages depending on your region and configuration.
• Ad privacy choices is available in the game's Settings when UMP reports that this option is required.
• You can manage your Advertising ID through Android settings; controls and wording vary by device and Android version.
• Declining ad personalization does not automatically stop all ads, transmission of IP addresses, or necessary data processing. There is no game control that disables all SDK diagnostics or collection.

LightTerm Studio has not intentionally integrated a separate analytics service in the game at present. The advertising SDK can still perform its own measurement and analytics.

For details about Google's processing and controls, see:

• Google Privacy Policy
• How Google uses information from sites or apps that use its services
• Google advertising technologies
• Google Mobile Ads SDK: Play data disclosure

8. Google Play purchases

Purchases of maps and theme packs are optional. Google Play Billing handles payments. LightTerm Studio does not receive card numbers, bank account credentials, or payment passwords.

The game and server can process product IDs, purchase status, purchase tokens or receipts, and entitlements. Purchase evidence can be sent to the server and checked through the Google Play Developer API, particularly to verify premium map access when you are the room leader. We use ownership information to unlock content, restore purchases, and prevent forged purchase evidence.

For an online premium map, the room leader needs access; joining players can play that map without purchasing it themselves.

Deleting local or developer-held data does not automatically refund a purchase or remove transaction records held by Google. Refunds follow Google Play's processes and policies. Google's processing is described in the Google Privacy Policy.

9. Support communications

If you voluntarily email lightdevs2005@gmail.com, we receive your email address and message contents to handle questions, bugs, or privacy requests. This external email correspondence is separate from the game: the app does not offer email login.

Do not send passwords, session tokens, content access tokens, full purchase tokens, card numbers, or other secrets. We do not require these as a condition of a privacy request.

10. How information is used

Information is used to:

• run the game and remember local preferences and progress;
• recognize Guest sessions, support reconnection, and operate online rooms and matches;
• grant, verify, maintain, and restore content access through purchases or redeem codes;
• display ads and manage ad privacy choices through Google;
• protect services, limit excessive requests, and prevent abuse or fraudulent access;
• provide support and respond to privacy requests; and
• meet applicable legal obligations.

11. Who receives information

• LightTerm Studio, as operator, processes information needed to run the game and its services, including restricted administrative access to redeem records.
• Google processes information for AdMob, UMP, Play Billing, and purchase verification as described above and under its own policies.
• Hosting and infrastructure providers process information on our behalf to run online services. These services currently use a Hostinger VPS.
• Other players in your room receive only information needed for the match, such as your name, character, status, and game actions, not session tokens or purchase evidence.
• Authorities may receive information when required by law or lawfully necessary to address abuse, fraud, or security issues.

Some regional privacy laws define "sale" or "sharing" broadly, and advertising-related processing may fall within those definitions depending on the circumstances. We do not make a blanket legal classification of personalized advertising. The ad privacy options described above may help you manage relevant choices where available.

12. Retention and backups

Retention considers service operation, recovery, support, security, and legal obligations. Where no fixed period has been established, we do not promise a specific deletion deadline.

• Local data remains until deleted, overwritten, or removed by clearing app data. Device backup mechanisms may retain or restore copies and affect removal.
• Online data and content access records, including required session, match, entitlement, and redeem data, are stored in the database. Database backups can retain copies for service recovery.
• Guest sessions currently have a validity period of approximately 30 days. Rooms can expire after approximately 6 hours of inactivity. These are access and recovery-eligibility rules, not guarantees that all database copies, backups, or related records are deleted at those times.
• Room and session cleanup occurs during certain service operations. We do not promise precisely timed deletion by a scheduled job.
• Redeem records do not currently have an established automatic deletion schedule.
• Database backups do not currently have a fixed retention schedule that we can promise. Backup copies must be considered when handling deletion requests.
• Support emails are retained according to support, recordkeeping, security, and legal needs; no fixed retention period is currently specified.
• Data held by Google follows Google's policies and your Google settings.

13. Your choices and privacy requests

To request access to, correction of, or deletion of developer-held data, email lightdevs2005@gmail.com with the suggested subject "Metro Mogul Privacy Request".

Explain your request and provide your player name and available nonsecret details that may help locate records, such as the approximate time of a redemption or room activity. A player name alone may not identify the data owner. We may need proportionate verification and may not always be able to locate or verify records from the information provided. We will not ask for passwords, session tokens, access tokens, full purchase tokens, card numbers, or other confidential credentials.

Please keep these distinctions in mind:

• Uninstalling the app or clearing device data does not automatically delete server database records or data held by Google. Device backups may also retain copies.
• Leaving a room does not delete all related data.
• Revoking redeem access does not delete redeem records or related data.
• Deleting developer-held data does not automatically delete Google purchases or give you a refund.
• Backup copies need to be considered as part of a deletion request. If some data must be retained for a lawful reason, we will explain the reason in responding to your request as applicable law requires.

Privacy requests are handled through email; there is no in-app self-service deletion button or automatic deletion endpoint currently offered. We do not promise a fixed completion time that has not been established.

Depending on your location and applicable law, you may have additional rights to receive a copy of your data, object to or restrict processing, withdraw consent, or complain to a data protection authority. Contact us to discuss your request. You can also manage advertising choices as described in Advertising and privacy choices.

14. Children and intended age group

LightTerm Studio's currently stated target audience for Metro Mogul is players aged 13 and older. The game is not presented as child-directed. This stated audience does not itself establish compliance with children's privacy, consent, or Google Play Families requirements.

If you are a parent or guardian with concerns about a child's information in connection with Metro Mogul, contact lightdevs2005@gmail.com. Describe your concern using nonsecret information so we can assess it and discuss appropriate steps under applicable law.

15. Security

Production services use HTTPS and WSS, and production database connections use TLS. Administrative access is restricted. Guest session credentials and the entitlement cache use encrypted storage on the device.

These measures do not mean all stored data is encrypted or that communications are end-to-end encrypted. No security measure guarantees complete protection against unauthorized access, disclosure, or loss. Local developer tests may use different local connections; those tests do not describe the production connections used by players.

16. International processing

Google and our hosting or other infrastructure providers may process information across countries, including countries other than where you live. Data protection laws may differ between those countries.

17. Third-party services and links

Google and other providers have their own privacy policies for their processing. Ads or external links may take you to services we do not control. Their policies do not replace this policy, and this policy does not replace theirs.

18. Changes to this policy

We will update this policy to reflect changes to the game or our data practices and revise the "Last updated" date. Please review this page for the current policy.

19. Contact

LightTerm Studio

Privacy and support: lightdevs2005@gmail.com