Traffic Jam: Clear the Way · Published by DMK Interactive

Privacy Policy

Effective date: 14 October 2026

Privacy at a glance

This Privacy Policy explains how DMK Interactive — the developer name of Dmitrii Kurhaniuk, also publishing as dmkstudio (“dmkstudio”, “we”, “us”, or “our”) — handles information when you play the mobile game Traffic Jam: Clear the Way (“Traffic” or the “Game”) on Google Play or the App Store. dmkstudio is the controller of information it processes for the Game.

Short version: Traffic has no registration and no dmkstudio account. Game progress and settings are saved on your device. The Game can show ads, process in-app purchases through your app store, and, when available, use an anonymous online leaderboard. We do not receive your payment-card details.

Data we collect and why

Data Why we use it Where it goes
Game progress and economy: reached and completed levels, stars, moves and results, coins, boosters, cars and paints, rewards, daily challenge and weekly cup progress, fuel, and purchase entitlements. To save your progress, operate gameplay and rewards, prevent duplicate grants, and restore eligible purchases. Saved on your device. Only the limited leaderboard fields described below are sent off-device if the online leaderboard is enabled.
Preferences: sound, music, haptics, reminders, whether the ads-and-privacy question was answered, and the state of the PERSONALISED ADS and DO NOT SELL OR SHARE MY DATA settings. To remember your choices and apply them on later launches. Saved on your device. When advertising is active, your personalisation choice decides whether Google AdMob is asked for personalised or basic ads.
Gameplay and shop events: the event names and limited parameters listed under “Analytics events”. To understand level difficulty, retention, tutorials, the virtual economy, shop reliability, and ad delivery. Sent to Google Analytics for Firebase, operated by Google, and also written to the Game’s local log. Firebase attaches its own automatically collected data to each event, including an app instance identifier, the device model and operating system, the app version, and the country your IP address indicates. In the European Economic Area, the United Kingdom and Switzerland, these events are sent only if you consent; see “Advertising partners and personalised advertising”.
Advertising data: the device advertising identifier (the Android Advertising ID, or the iOS IDFA where you have allowed tracking), IP address (which can indicate general location), device type and technical device data, app launches, ad requests, impressions, video views, taps and other ad interactions, diagnostic data, and, on Android, the app set ID. To request and measure ads, select basic or personalised ads as permitted, cap frequency, diagnose delivery, and prevent fraud. Sent to Google AdMob, operated by Google, when an ad is requested or shown. See “Advertising partners and personalised advertising”.
Purchase data: product ID, transaction status, and the resulting local entitlement or virtual item. Your platform processes account, price, payment method, tax, receipt, and transaction information. To complete, validate, restore, and support in-app purchases. Sent to Google Play or Apple App Store. We receive the purchase result and information needed to grant the item, but not your full card or bank details.
Leaderboard data, when online leaderboards are available: an anonymous Unity Player ID, generated or chosen driver callsign, journey score, levels completed, and total stars. To authenticate without registration, submit your best score, show rankings, and protect the leaderboard from abuse. Sent to Unity Gaming Services Authentication and Leaderboards. If the online service is not enabled in your version, leaderboard data remains local and synthetic local rows are not presented as real players.
Notification permission and schedule: whether you allowed local notifications and the dates needed to schedule reminders. To schedule rewards and event reminders that you enable. Handled on your device through Android or iOS. Traffic does not use a remote push-notification server.
Support requests: your email address, message, and any information you choose to send. To answer your request, verify it where reasonably possible, and keep a record of the response. Sent to dmkstudio and the email provider used for support.

Traffic reads a device identifier locally to create a default pseudonymous driver callsign. The raw identifier is not deliberately included in Traffic’s analytics events or leaderboard score metadata. Do not use your real name as a driver callsign.

When the Game stops unexpectedly, Firebase Crashlytics sends a crash report to Google: the stack of the failure, the device model and operating system, the app version, the time, and an installation identifier. It is used to find and fix the fault.

Traffic does not ask for precise location, contacts, photos, camera, microphone, phone number, or government identifiers. General location may still be inferred by an advertising provider from an IP address.

Analytics events

The release analytics schema contains the following events. Parameters are limited to level and chapter numbers; session duration and levels played; moves and boosters used; loss reason; coin source, destination, amount and balance; shop origin and product ID; stable error codes; ad placement; and tutorial lesson and step. Our own parameters do not include a name, email address, free text, precise location, raw advertising ID, IP address, board seed, or every individual tap; the device model, operating system and country come from Firebase’s automatic collection, described above.

Show all 26 event names

session_started, session_ended, level_started, level_won, level_lost, level_abandoned, coins_earned, coins_spent, shop_opened, shop_product_shown, shop_product_tapped, shop_purchase_started, shop_purchase_succeeded, shop_purchase_cancelled, shop_purchase_failed, shop_restore_started, shop_restore_succeeded, shop_restore_nothing_to_restore, shop_restore_failed, ad_offered, ad_shown, ad_reward_granted, ad_no_fill, tutorial_step_shown, tutorial_step_completed, and tutorial_abandoned.

These events are sent to Google Analytics for Firebase and are also written to the Game’s local log. Google AdMob separately collects its own ad-request, impression, and diagnostic events, as described in its policy and in the table above.

Partners and disclosures

We disclose only the data needed for the service involved. These providers process data under their own terms and privacy policies:

Traffic uses Google AdMob directly and has selected no advertising mediation partner. If we add a mediation partner or a further analytics provider, we will update this list before that provider starts receiving data.

Legal bases for processing

Where the GDPR or similar law applies, we rely on:

  • Contract: to provide the Game, save progress, grant virtual items, process purchases, and provide requested leaderboard features.
  • Consent: for personalised advertising, for game analytics, and, where required, access to an advertising identifier or tracking across apps and websites. You may withdraw consent at any time.
  • Legitimate interests: to operate basic ads, secure transactions, prevent fraud and abuse, diagnose faults through crash reports, and answer support requests, where those interests are not overridden by your rights.
  • Legal obligation: to keep records or respond to lawful requests where the law requires it.

Advertising partners and personalised advertising

Traffic is free to play and uses Google AdMob, operated by Google, for interstitial and optional rewarded ads. When an ad is requested or shown, Google receives the device advertising identifier where your platform settings allow it, your IP address, the device type, and events about the ad — that it was requested, shown, watched, or closed — and uses them to select and measure ads, cap how often you see them, diagnose delivery, and prevent fraud. Basic ads use context such as the Game and the general location an IP address indicates. Personalised ads may also use the advertising identifier and past activity to infer interests, where the law and your platform settings allow it.

In the European Economic Area, the United Kingdom and Switzerland, Traffic asks for consent on first launch through Google’s User Messaging Platform, a consent management platform certified by Google. Your answer there decides two things: whether ads may be personalised, and whether game analytics are collected. If you do not consent, Traffic requests basic ads only and sends no analytics events to Google Analytics for Firebase; crash reports are still sent so that faults can be fixed. Refusing does not block the Game. To change your answer later, open the Game’s Settings, then TERMS & PRIVACY, then PRIVACY OPTIONS.

Elsewhere, no consent form is shown. You can turn PERSONALISED ADS off or on in the Game’s Settings at any time; turning it off applies to future ad requests. You can also limit app tracking or reset or delete the advertising identifier in your Android or iOS privacy settings.

Ads are shown only in a build where the ad network is configured. In a build without it, Traffic requests no ad, and none of the advertising data described above leaves your device.

In-app purchases

Real-money purchases are processed by the store from which you installed Traffic. A purchase request sends the product identifier to Google Play or Apple App Store. The platform handles your store account, payment method, local price, currency, taxes, receipt, and transaction. dmkstudio receives the status and information needed to grant or restore the item. We do not receive your full payment-card or bank-account details.

A build without a working store connection cannot charge you: purchases are shown as unavailable rather than given away. Any build that accepts money uses the platform’s official purchase system.

Children, COPPA, and Google Play Families

Traffic is not directed to children under 13, and children under 13 must not use the Game. We do not knowingly collect personal information from a child under 13. If you believe a child has provided personal information, contact us at dmkstudio.dev@gmail.com. We will investigate and delete it where required by the Children’s Online Privacy Protection Act (COPPA) or other applicable law.

Traffic is not intended to be listed in the Google Play Families program or to include children under 13 in its target audience. We do not knowingly use an advertising identifier from a child. Where local law requires a person older than 13 to obtain parental consent for personalised advertising, Traffic must use basic ads unless valid consent has been obtained. If the target audience changes, we will first add the age controls, child-directed ad configuration, approved SDKs, disclosures, and protections required by Google Play Families and applicable law. Personalised ads will not be served to children.

Do Not Sell or Share My Personal Information

We do not sell personal information for money. When PERSONALISED ADS is on, sending identifiers and activity to an advertising partner for interest-based advertising may be considered “sharing” for cross-context behavioural advertising under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA/CPRA).

To opt out, open the Game’s Settings and turn on DO NOT SELL OR SHARE MY DATA. This is a separate control from PERSONALISED ADS, and it is the stronger one: while it is on, Traffic requests basic ads only, whatever the personalisation setting says. You may also email dmkstudio.dev@gmail.com with the subject “Do Not Sell or Share”. We will not discriminate against you for exercising this choice. We do not knowingly sell or share personal information of anyone under 16.

California residents may also request to know and access the categories and specific pieces of personal information we hold, request correction or deletion, and ask about the categories of sources, purposes, and recipients. An authorised agent may submit a request where permitted by law. We may need to verify a request using the limited information reasonably available to us.

The CCPA categories that can apply to an ad-enabled release are identifiers, internet or other electronic network activity, approximate geolocation inferred from IP address, commercial information about purchases, and inferences used to select ads. The recipient categories are advertising providers, app-store and payment platforms, and—if enabled—online leaderboard providers. We use and disclose them only for the purposes listed in “Data we collect and why”. We do not use sensitive personal information to infer characteristics about you.

Your GDPR and other privacy rights

Depending on where you live, you may have the right to access, correct, delete, restrict, or receive a portable copy of your personal data; object to processing based on legitimate interests; withdraw consent; and complain to your local data-protection authority. Withdrawing consent does not make earlier lawful processing unlawful.

To exercise a right, email dmkstudio.dev@gmail.com and describe your request. Because Traffic has no registration or dmkstudio account, we may hold no direct identifier that lets us match server data to you. We may ask for limited information available in the Game or a platform transaction reference. Do not send a password, full card number, or unnecessary identity document. We will respond within the time required by applicable law.

Data deletion and retention

Data on your device

Traffic has no dmkstudio account. Your progress, settings, consent choice, local leaderboard state, and local analytics or diagnostic files remain on the device until you clear the Game’s storage or uninstall the Game. Uninstalling or clearing app data deletes this local data, subject to any device or platform backup you control. Local progress cannot currently be recovered from us.

Data sent to a provider

Uninstalling does not automatically delete data already processed by an ad network, app store, or online leaderboard. Email dmkstudio.dev@gmail.com to request deletion of server-side data that dmkstudio controls. We will delete or de-identify identifiable server records within the legally required period and send requests to processors where required. You may also use the privacy controls or request channels offered directly by Google, Apple, or Unity.

Retention periods

  • Local progress and settings: until you clear app data or uninstall.
  • Analytics events and crash reports held by Google: retained under our Firebase project settings and no longer than 24 months after your last activity.
  • In-memory analytics on the device: until the app process ends, subject to a 256-event capacity. A local debug analytics file, if enabled, remains until app data is cleared or the Game is uninstalled.
  • Leaderboard and any other dmkstudio-controlled server records: no longer than 24 months after the last activity, unless you request earlier deletion or law requires longer retention.
  • Purchase, advertising, and platform records: retained by Google, Apple, or Unity under their own policies and legal obligations.
  • Support correspondence: only as long as needed to resolve the request, document the response, prevent abuse, or meet legal duties.

International data transfers

Google, Apple, Unity, and support providers may process data in countries outside your own, including the United States. Where required, we and our providers use recognised safeguards such as adequacy decisions, Standard Contractual Clauses, or another lawful transfer mechanism. Provider privacy policies describe their locations and safeguards in more detail.

Security

We limit the data Traffic creates and use platform services for payments. Providers state that network data is encrypted in transit. No security method is perfect, so we cannot guarantee absolute security.

Changes to this Policy

We may update this Policy when the Game, its providers, or legal requirements change. We will post the new version at this address, change the effective date, and provide any additional notice required by law. Material new uses that require consent will not be treated as accepted only because you keep the Game installed.

Contact dmkstudio

For privacy questions or requests, email dmkstudio.dev@gmail.com.

Developer: DMK Interactive (Dmitrii Kurhaniuk), publishing as dmkstudio