Privacy Map
Read this page as a practical map. First, it describes the static developer website. Then it explains how mobile games may handle advertising, analytics, diagnostics, and related signals.
It does not provide legal advice and it does not rewrite the terms of external providers.
Static Website Practices
This developer site is not an advertising surface and does not install mobile-game SDKs. There is no deliberate fingerprinting, tracking pixel, WordPress login, payment form, or user account system in these static pages.
Like most hosted websites, the server may keep basic logs such as IP address, date and time, page requested, user-agent, response code, and similar security information. Local storage or cookies are limited to simple site functions if any are present.
These hosting records are referred to as server logs in this policy.
Google Play Game Experiences
When a user installs or plays a game, the app may interact with Google Play services, advertising SDKs, analytics tools, diagnostic systems, and device-level settings. Those systems can process data needed for ads, measurement, stability, and abuse prevention.
The site design was informed by titles such as Miami Hero: Rope Hero Spider, Temple Princess Runner, Gun Battle Ops: Offline Games, Modern Gun Strike 2: Gun Games.
Ads, Bidding, and Mediation
Advertising in games may be served through Unity LevelPlay and advertising partners integrated through the mediation platform. Depending on configuration, the flow can include mediation, real-time bidding, in-app bidding, waterfall mediation, rewarded ads, interstitial screens, banner ads, and other supported formats.
No fixed partner list is stated here because the actual partners may change by app, country, release, user choice, and availability.
Mediation may include real-time bidding, in-app bidding, waterfall mediation, and partner routing where configured.
Ad formats may include rewarded ads, interstitial ads, banner ads, and other supported advertising formats where configured.
Ad Signals and Identifiers
For advertising and bidding flows, the game, mediation layer, or ad partners may process the following data categories where permitted and applicable:
- ad clicks
- rewarded-ad completion
- advertising performance
- frequency and campaign information
- fraud-prevention signals
- consent and privacy-choice signals
- advertising identifiers
- device identifiers where permitted
- Google Advertising ID or equivalent advertising identifiers
- IP address
- device type and model
- operating-system information
- app or game version
- language
- general region or approximate location inferred from IP where applicable
- network and connection information
- ad impressions
- ad interactions
Gameplay Signals
Game analytics may be used for crash investigation, gameplay improvement, feature analysis, abuse prevention, and ad measurement. The categories may include:
- game performance
- device information
- app or game version
- crashes
- error logs
- diagnostic data
- performance information
- general engagement statistics
- advertising-related measurement
- country or approximate region where lawfully derived
- game launches
- session duration
- gameplay events
- level progress
- game mode usage
- feature usage
- interaction events
Uses Across Games and Services
The main purposes are operating the apps, understanding gameplay and performance, delivering and measuring advertising, enabling rewarded ads, limiting repetitive ads, supporting attribution, diagnosing crashes, and preventing abuse.
Third-Party Privacy Practices
Google Play handles app distribution and related store activity under Google's own privacy practices. In the games, Unity LevelPlay, ad partners, analytics providers, diagnostic tools, crash reporting, attribution systems, or performance services may also process data according to their own notices.
When Data Moves to Providers
When SDKs or service providers are integrated into a game, they may receive data needed for their role, such as ad mediation, analytics, technical operation, measurement, attribution, crash diagnostics, or fraud prevention.
Data Sharing is described here as provider access or transmission needed for these limited app operations.
Consent and Device Privacy Controls
Where required by applicable law, users may be offered privacy choices for personalized advertising, advertising identifiers, analytics, or certain processing activities. Users can also use Android advertising settings, device privacy settings, reset or delete advertising identifiers where supported, use in-app privacy controls where available, or follow applicable advertising-partner privacy choices.
Family Privacy Notes
This website does not knowingly request unnecessary direct personal information from children. The mobile games may be configured differently based on audience, platform policy, law, SDK settings, and ad-service requirements. Parents and guardians should use public Google Play contact details for concerns.
Children and family privacy questions should use the public Google Play listing contact route.
Retention and Security
Retention periods are not fixed here because they can vary by provider, purpose, SDK, country, and legal obligation. Data may be kept as needed for app operation, measurement, reporting, security, diagnostics, fraud prevention, or compliance.
Reasonable security practices may be used, while recognizing that no system is risk-free.
Regional Rights and International Availability
Because mobile games may be distributed in multiple countries, privacy laws can differ by region. Rights may include access, correction, deletion, objection, restriction, consent withdrawal, and advertising choices where those rights apply.
Third-Party Link Notice
Links from this site may take users to Google Play or other external destinations. Those services are not controlled by this static website and may process data under their own policies.
Keeping This Notice Current
Changes to ads, Unity LevelPlay configuration, analytics, diagnostics, game features, or applicable law may require policy updates. Privacy questions should use the public contact route available on the Google Play listing.