Privacy Policy — One Lane Left

1. Introduction

One Lane Left is published by Dan-Mihai Balean ("we", "us", or "our"). This Privacy Policy explains how information is processed when you use One Lane Left on Android under package identifier com.baleandanmihai.onelaneleft or iOS under bundle identifier com.baleandanmihai.onelaneleft.ios. iOS availability and features depend on the released build.

One Lane Left is a game. We do not provide player accounts or require you to log in to play. The game saves some game and settings information on your device. Online services may process information for consent management, analytics, advertising, or purchases when the relevant feature is used or enabled.

2. Information We Process

Information stored locally by the game

The game stores the following information on your device using app-local storage:

• game progress such as high score, virtual currency total, and daily-mission state;
• game settings, including sound, music, haptics, graphics, camera-motion, and usage-analytics choices;
• a local flag recording a confirmed Remove Ads entitlement;
• local records used to prevent the same validated purchase from being delivered twice; and
• a locally generated random installation identifier used by the daily-mission save system. The game does not submit this daily-mission identifier as a custom analytics field.

This information is used to operate the game, restore local gameplay state, apply your settings, and protect purchase fulfillment. It is not a player account and does not contain a player name, email address, contacts, or payment-card information. Third-party SDKs may use their own installation or device identifiers as described below; those are separate from the game's local daily-mission identifier.

One Lane Left does not request Android precise-location, approximate/coarse-location, or background-location permissions and does not call Android device-location APIs. It also does not request access to contacts, photos or videos, audio files, health or fitness data, calendar data, messages, or direct payment-card credentials. Service providers may still infer approximate location, such as a country or general area, from an IP address.

Usage analytics

The game includes Unity Analytics. The game initializes Unity Services for Analytics and submits Analytics data only if you explicitly grant the separate Usage Analytics choice. If Usage Analytics is declined or remains unset, project analytics submission remains off.

When enabled, the game submits custom gameplay and technical events such as app readiness, app foreground/background state, screen views, button actions, run number, run duration, distance, score, virtual Cash, gameplay outcome, selected graphics tier, and performance measurements. These events include app version and build information. The game does not intentionally place your name, email address, contacts, precise location, raw store receipt, payment-card information, or raw purchase token into its custom analytics events.

Unity Analytics may also automatically process service data such as IP address, an installation-specific identifier, a service user identifier that defaults to the installation identifier, device and app information, diagnostics, performance information, and approximate location derived from IP address. This information is processed by Unity Technologies according to its applicable terms and privacy notice.

The project contains a bounded local crash-context metadata writer for technical game state. Unity's built-in Developer Data Diagnostics is enabled at project level and may transmit essential crash logs, exception and diagnostic information, other app-performance data, configuration metadata, and a unique installation-specific identifier for stability and service-integrity purposes. This diagnostic collection is managed at the project or build level, not by the Usage Analytics choice or UnityConsent. The legacy Unity Cloud Diagnostics service is not enabled.

The current Unity Developer Data project configuration is limited to the Essential Data collection tier and use by the Unity products and services used for this project. Additional Recommended Data is disabled. No Google Analytics or Firebase link, or additional Unity product access, is enabled.

3. Advertising and Advertising Identifiers

The current advertising integration uses Google Mobile Ads/AdMob directly for optional rewarded ads and interstitial ads. Android and iOS use separate AdMob app and ad-unit identifiers. The game no longer calls LevelPlay to initialize, load, or show ads; the installed LevelPlay and mediation components are retained technical dependencies, not a fallback advertising path. The game does not call Unity Ads to request or display ads.

The supported Unity LevelPlay package nevertheless bundles and manages the Unity Ads SDK and adapter. On Android, that bundled SDK registers a process-start component that performs limited SDK and networking-provider setup even when Unity Ads is not configured as a mediation source. One Lane Left does not call the Unity Ads initialization, load, or show APIs. Unity Ads therefore remains disclosed as a bundled technical component, but it is not an active direct advertising provider for this release.

When advertising is enabled and an ad request is permitted, these SDKs and the configured advertising partners may collect or share technical and advertising information. Depending on the provider and your choices, this can include an advertising identifier, other device or app identifiers, device and network information, IP address, approximate location inferred from IP address, app launch and ad interactions such as taps and video views, diagnostics, performance data, ad-delivery and measurement data, fraud-prevention signals, and consent or privacy-choice signals.

This information may be used to deliver, measure, limit, secure, and improve ads, prevent fraud, and personalize ads where permitted by your choices and applicable requirements. Dan-Mihai Balean does not use the advertising identifier as a first-party gameplay identifier.

On iOS, when applicable, Google UMP may present an explanation followed by Apple's App Tracking Transparency (ATT) permission request. ATT controls access to the iOS advertising identifier and permission for tracking covered by Apple's rules. Declining ATT does not prevent core gameplay or automatically prevent all ads; eligible ads can be requested without the IDFA, subject to the separate advertising privacy choices. You can change the ATT permission in iOS Settings. The game does not grant a gameplay reward for allowing tracking.

4. Consent and Privacy Choices

The game has a separate Usage Analytics choice in its first-run and Settings experience. That choice sets Unity's Developer Data AnalyticsIntent and controls project analytics submission. Unity IAP can read and include that intent in its service telemetry. The choice does not authorize advertising and does not replace the separate UMP advertising-privacy flow.

The game uses Google's User Messaging Platform (UMP) to manage advertising privacy choices on Android and in iOS builds with advertising enabled. At each eligible app launch, the game asks UMP to refresh the applicable consent status and determine whether a privacy message or privacy-options entry point is required. UMP may communicate with Google and store or update consent and privacy-choice signals for this purpose.

When UMP requires an initial form, the game asks UMP to load and show it. AdMob initialization and ad requests stay blocked until UMP reports that ads may be requested. If UMP requires an ongoing privacy-options entry point, the game exposes a Privacy Choices control in Settings so that the UMP form can be opened again. If an update fails, the game does not infer consent; it relies only on the status returned by UMP, including any valid status retained by UMP from an earlier session.

The privacy message shown and the choices available depend on your region, the applicable requirements, and the advertising partners configured for the game. Google's UMP consent and privacy-options interface may list additional Google-certified advertising technology providers, Authorized Buyers, Open Bidding partners, or other Google demand sources that may be eligible to process data through Google's advertising ecosystem. The current partner list and each partner's disclosures are presented in that interface when applicable. Inclusion in that list describes eligibility or capability and does not mean that every listed provider receives data for every ad request.

Some UMP partner disclosures use generic language about precise geolocation because a listed provider has registered that capability. One Lane Left itself does not request Android location permission, obtain GPS-level location, or intentionally send precise location to an advertising SDK. This generic partner capability is not a statement that the game actually collects precise location.

5. In-App Purchases

When purchases are enabled, the game uses Unity IAP 5.4 or later to offer Google Play purchases on Android and Apple App Store purchases through StoreKit 2 on iOS. Products include consumable virtual Cash packs, guaranteed virtual-item bundles, and a non-consumable Remove Forced Ads product. Some beta builds may have purchases disabled.

When purchases are enabled, Google Play or Apple processes the payment and supplies purchase information to the app. Unity IAP connects the game to the corresponding store. On iOS, the game requires a transaction verified by StoreKit before granting a purchase. Dan-Mihai Balean does not collect or store payment-card or bank-account numbers.

Unity states that IAP 5.4 and later processes personal data for the service. Depending on the available services and purchase flow, this may include a Unity installation identifier, an Authentication Player ID if Authentication is present, device information, session identifiers, country or approximate location, app and SDK information, product and purchase history, transaction identifiers or store payload data, diagnostics, performance information, and device or other identifiers. Unity's service-level Google Play disclosure also lists an end-user email address as required ephemeral app-functionality data. The game does not request an email address, include a player-account or Unity Authentication flow, or configure a direct-to-consumer payment provider.

Unity IAP 5.4 or later does not provide its own player-consent interface. The game sends the Usage Analytics decision to Unity as the Developer Data AnalyticsIntent. Unity IAP reads that signal and, when analytics is enabled, can include an optional Analytics identifier. Denying or leaving Usage Analytics unset does not stop the essential transaction and service data needed to provide purchases.

Advertising privacy choices remain managed separately through UMP. The game does not infer a Unity Developer Data advertising-consent signal from UMP's aggregate CanRequestAds result. In the current integration, Unity IAP therefore does not access optional advertising or linked Google Analytics/Firebase identifiers that its SDK gates on an explicitly granted advertising intent.

For purchase fulfillment, the game stores a local entitlement or Cash delivery record together with a one-way hash of the validated purchase token to prevent repeated local delivery. Eligible Remove Forced Ads purchases can be restored with the same account for the corresponding store. On iOS, a verified Apple revocation may deactivate Remove Forced Ads; the game does not treat a failed connection or a missing local entitlement as proof of revocation. Existing virtual Cash and other delivered items are retained by this entitlement update. Consumed Cash purchases do not reconstruct a lost local balance or progression state after app data is cleared or the game is reinstalled.

6. How Information Is Used

Depending on the services enabled and used, information is processed to operate the game and retain local settings and progress; remember and apply privacy choices; understand game usage and technical performance when Usage Analytics is enabled; deliver, measure, secure, and improve advertising when advertising is enabled and permitted; process, validate, fulfill, and restore eligible in-app purchases when purchases are enabled; and meet applicable legal, security, and fraud-prevention obligations.

7. Legal Bases for EEA/UK Users

If you are in the European Economic Area or the United Kingdom, we rely on the following legal bases where applicable to the processing described in this policy:

• Consent: for Usage Analytics, and for advertising-related storage, access, personalization, or other processing where applicable law requires consent. You may withdraw consent through the relevant in-game privacy control where available. Withdrawal does not affect the lawfulness of processing performed before consent was withdrawn.
• Performance of a contract or steps taken at your request: to provide the core game functionality you request and to initiate, validate, fulfill, or restore a purchase you choose to make.
• Legitimate interests: to protect the security and integrity of the game and services, prevent fraud and duplicate fulfillment, investigate abuse, maintain service reliability, and perform necessary technical diagnostics, where those interests are not overridden by your data-protection rights and interests. We do not rely on legitimate interests instead of consent for processing that legally requires consent.
• Legal obligations: when processing is necessary to comply with applicable law, regulatory requirements, lawful requests, accounting requirements, or consumer-protection obligations.

Apple, Unity, Google, or an advertising provider may act as an independent controller for some processing and determine its own legal bases. Refer to the relevant provider's privacy notice for that processing.

8. Data Sharing and Service Providers

Dan-Mihai Balean does not operate a player-account system or a first-party cloud-save service for the game. Information may be made available to the following service providers as described in this policy:

• Unity Technologies, for Developer Data Diagnostics, Unity Analytics, Unity LevelPlay/ironSource, Unity IAP, and the bundled Unity Ads technical component described above;
• Google, for UMP consent and privacy messaging, Google Mobile Ads/AdMob, and Google Play Billing on Android;
• Apple, for App Store payments and StoreKit purchase, refund, and eligible permanent-purchase restoration on iOS. Apple handles payment and Apple Account information; the game receives transaction information needed to verify and deliver purchases, without receiving payment-card credentials;
• Google advertising demand sources used by the current direct AdMob integration, when advertising is enabled and permitted; and
• additional Google-certified advertising technology providers, Authorized Buyers, Open Bidding partners, or Google demand sources disclosed through UMP, when eligible, selected, and permitted by the user's choices.

These providers may process information under their own policies, use subprocessors, or process information in other countries. We do not directly sell personal information for money. Whether a disclosure is legally treated as a "sale" or "sharing" depends on the enabled provider, applicable law, and the user's privacy choices.

9. Data Retention and Deletion

App-local game and settings information normally remains on your device until it is changed, reset by an available in-game control, cleared through Android settings, or removed when the app is uninstalled. Android backup, device-management, or platform behavior may affect information stored outside the app's local storage.

The game has no player account, so it has no in-app account-deletion flow. Apple, Unity, Google, and advertising providers retain information according to their applicable policies and service requirements. Requests involving Unity Diagnostics data associated with an installation-specific identifier are handled through Unity's Dashboard or Support process. Unity states that its IAP 5.4 service has no native self-service access or deletion feature; requests involving Unity IAP data are handled manually through the process described in Unity's IAP privacy documentation.

For a privacy inquiry or request relating to developer-controlled information, contact balean.danmihai.dev@gmail.com. Please do not send payment-card details or raw store receipts unless specifically required through a secure support process. Requests concerning provider-controlled information may also need to be directed to Unity, Google, or the relevant advertising provider.

10. Children's Privacy

One Lane Left is not directed to children. The game does not provide a player account or knowingly ask children to submit a name, email address, or other account information to Dan-Mihai Balean. Advertising, analytics, consent, and purchase providers have additional requirements for child-directed apps and minors. If you believe a child has provided personal information directly to the developer, contact balean.danmihai.dev@gmail.com.

11. Security

We use reasonable measures appropriate to the services we operate, but no method of storage or transmission is completely secure. Third-party providers apply their own security practices to information they process.

12. International Processing

Unity, Google, and advertising partners may process information in countries other than the country where you live. Their privacy notices describe their processing and transfer practices.

13. Your Privacy Rights

Depending on where you live, you may have rights to request access to personal data, correction, deletion, restriction, objection, portability, or withdrawal of consent where consent is used. Withdrawal of consent does not affect the lawfulness of processing based on consent before its withdrawal. You may also be able to change Usage Analytics or advertising choices through the relevant privacy controls made available in the app or through device and platform settings.

To make a request concerning developer-controlled information, contact balean.danmihai.dev@gmail.com. We may need information reasonably necessary to verify and respond to a request. Requests concerning information controlled by Unity, Google, or an advertising provider may also need to be directed to that provider.

You also have the right to lodge a complaint with a competent data-protection supervisory authority. In Romania, the supervisory authority is the National Supervisory Authority for Personal Data Processing (ANSPDCP) (www.dataprotection.ro). Where applicable, you may instead contact the competent supervisory authority in the EEA country of your habitual residence, place of work, or the place of the alleged infringement.

14. Third-Party Privacy Notices

• Unity Game Player and App User Privacy Policy — Unity Developer Data Diagnostics, Unity Analytics, Unity LevelPlay, Unity Ads, and Unity IAP.
• Unity IAP Privacy and Consent — Unity IAP 5.4 data handling and request information.
• Google Privacy Policy — Google Play, UMP, and Google Mobile Ads/AdMob.
• Apple App Store & Privacy and Apple Privacy Policy — App Store purchase processing and StoreKit transaction information.
• Google UMP for Unity — advertising privacy-message behavior.
• Unity LevelPlay Legal Resources — LevelPlay privacy and regional compliance materials.

Third-party policies may change. This policy may be updated if providers, adapters, or release configuration change.

15. Changes to This Privacy Policy

We may update this Privacy Policy when the game, its data practices, or applicable requirements change. The updated version will show a revised effective date.

16. Contact