Privacy Policy

At a glance

Race Riot mobile releases with Firebase use gameplay analytics, crash diagnostics and remote configuration to help us understand use of the game, improve stability and adjust game settings. We do not sell personal information or use it for cross-app advertising. Our website uses optional Google Analytics only after your consent. Local progress, purchases and support are described separately below.

Website analytics and cookie choices

With your permission, makalu.games uses Google Analytics 4 to understand visits and improve the website. The Google tag is not loaded until you choose “Allow analytics” in our cookie banner or have a saved choice allowing analytics. Choosing “Decline analytics” leaves the website available without this tracking.

When allowed, Google receives information such as page addresses and titles, referral sources, browser and device details, approximate location and interactions such as scrolling and outbound link clicks, depending on the measurement settings enabled. Analytics cookies distinguish browsers and sessions; this information is not necessarily anonymous. Google also receives connection information when your browser contacts its services. See Google’s Privacy Policy.

Our website tag denies advertising storage, advertising user data and advertising personalisation, and disables Google signals and ad personalisation signals. Website analytics is separate from the Firebase integration inside Race Riot described below.

We store your analytics choice in your browser’s local storage under makalu.analytics-consent.v1 until you change it or clear that storage. When allowed, the tag uses _ga and _ga_285MDMQNKF cookies at the website’s root path, with a configured lifetime of 180 days that can be renewed during use. Your browser may shorten their lifetime. If browser storage is unavailable, your choice applies to the current page and we ask again on a subsequent page load.

Open “Cookie settings” in the footer of any main website page to change your choice. Declining after allowing analytics stops further collection by this website tag and removes these analytics cookies for this website. It does not delete information already sent to Google; contact us about a deletion request. These website controls do not change the settings inside our games.

Game progress and preferences

Our games and applications store progress and preferences on your device so you can continue using them. Depending on the project, local records may include in-game items, currency balances, upgrades and a record of accepting the applicable Terms & Conditions. Local storage by itself does not send these records to us.

Device or operating-system backups may retain copies according to your settings. Removing the app or its data may remove local progress; it does not automatically remove information already sent to support or service providers.

Firebase in Race Riot

Firebase-enabled Race Riot releases on iOS and Android use Google Analytics for Firebase, Firebase Crashlytics and Firebase Remote Config. These services process information about an installation and its use, even if you do not create an account. Installation and app-instance identifiers can distinguish one installation from another; the data is not necessarily anonymous.

In these mobile releases, Analytics and Crashlytics are enabled automatically when the services initialize. The current game settings do not provide a player-facing switch for them. Remote Config also connects automatically. The desktop versions for Windows, macOS and Linux do not initialize this Firebase integration. These Firebase services are not embedded in this website.

Our mobile integration is configured to disable advertising storage, advertising user data and advertising personalisation. This does not disable the gameplay analytics and diagnostics described here.

Gameplay analytics

We use Google Analytics for Firebase to understand which features are used, where loading or purchase flows fail and how players progress. Our game events can include:

• Sessions, menus opened, buttons used, tutorial steps and changes to game settings or language.
• Race starts, finishes and results, race times, tracks, chapter downloads and loading outcomes.
• Car selection and acquisition, upgrades, collections, in-game currency earned or spent, and purchase or restore-flow outcomes. Purchase events can include the product, price and currency.
• App version, build, platform, store, language, operating mode, event times and generated session and event identifiers.

The Analytics SDK also collects app-instance identifiers, device and operating-system details and automatic events such as first use and sessions. Depending on the platform, it can record in-app purchase information automatically. Google can derive approximate location from connection information such as an IP address. This is separate from our custom game events.

Our custom event fields exclude names, email addresses, account and transaction identifiers, payment receipts, authentication tokens and free-text input. This restriction does not make SDK-generated information anonymous. See Google’s Analytics data-disclosure guidance and Privacy Policy.

Firebase crash diagnostics

Firebase Crashlytics helps us investigate crashes and errors. Reports can include exception messages, stack traces, application state, device and operating-system details, app version, installation identifiers and session information. We attach technical labels for platform, store, release environment, app version and build.

When Analytics is active, Crashlytics can include a history of events leading up to a crash, called breadcrumbs. Reports can also include Remote Config rollout information, such as the configuration version and affected values, when a rollout is in use. We do not attach a player account ID as a custom Crashlytics user ID. Diagnostic messages may still contain information produced by the app or its libraries.

Remote game configuration

Firebase Remote Config delivers settings for game balance and existing features, including cars and in-game prices, upgrades, rewards, campaign rules, opponents, nitro and recovery. The game stores the last valid settings on your device so it can continue using them offline; gameplay changes are applied between races.

Requests use a Firebase installation identifier and technical details such as app and SDK versions, platform, language, country and time zone. When combined with Analytics, Remote Config can also use Analytics user properties and the time of first use to select settings. Google receives connection information when these services are contacted. See Firebase’s privacy and security information.

Unity services in other releases

Some other Makalu Games applications or earlier releases may use Unity’s crash-reporting and diagnostics service. When enabled, it sends technical reports to Unity so we can identify errors and improve stability. Reports can contain crash logs, error details, game and operating-system versions, device and hardware information, performance information and a unique installation-specific identifier. These reports are not used by us to build advertising profiles. Race Riot’s current configuration disables Unity cloud crash diagnostics and uses Firebase Crashlytics on mobile as described above.

Unity processes diagnostic information on our behalf. See Unity’s Game Player and App User Privacy Policy for its handling of information. You can contact us to request access to or deletion of diagnostic information; we may need details to locate the installation concerned and to coordinate the request with Unity.

Apple purchases

Where optional in-app purchases are available through the App Store, Apple handles payment. Makalu Games does not receive your full payment-card details. Apple handles payment and store-account information under Apple’s Privacy Policy.

Where a game uses Unity’s purchasing software to connect to Apple’s store, Unity’s policy linked above describes its handling of information for that service.

The game and purchase-validation services may process product identifiers, transaction identifiers, receipt information and an associated player or installation identifier to verify a transaction, deliver the item, prevent duplicate grants and resolve purchase problems. Connecting to these services also exposes technical connection information, such as your IP address, to the service handling the request.

Purchase information is used to provide and protect purchases, not for advertising. Apple retains its own transaction records; requests concerning those records should be directed to Apple.

When you contact support

We receive your email address, message and any attachments or diagnostic details you choose to send. We use this information to respond, investigate problems and handle purchase or privacy requests. Our email service providers process correspondence to deliver and store it.

Please do not send passwords, authentication codes, payment-card numbers or unrelated personal information. Screenshots and logs may contain personal information, so review them before sending.

Why we use information

Where data-protection law requires a legal basis, we process information as necessary to provide the game and purchases you request, to comply with legal obligations, and for our legitimate interests in resolving support issues, preventing fraud and maintaining a reliable game, subject to your rights. Website analytics relies on your consent and helps us understand visits. Game analytics helps us evaluate game usage and balance; Remote Config delivers operating settings. Any legal requirement for consent to device storage, analytics or other processing applies separately and cannot be replaced by accepting these terms or this policy. Consent, where relied upon, can be withdrawn.

Accepting the Terms & Conditions is not consent to advertising, tracking or optional analytics.

Who receives information

Information is handled by Denys Huch and the providers needed for the features you use: Google for consented website analytics and Race Riot’s Firebase services, Unity for its purchasing integration and diagnostics in releases that use them, Apple for App Store purchases, and hosting and email providers for purchase validation and support. Information may also be disclosed when required by law or necessary to protect legal rights.

Google generally processes Firebase service data on our behalf under its data-processing terms; Google Analytics has separate service terms. Authorised personnel and service providers receive access as needed for these purposes.

Providers may process information outside your country, including in the United States. Where applicable law requires safeguards for international transfers, those requirements apply, including appropriate contractual or other recognised safeguards. Contact us for information about a transfer affecting your data.

Retention and security

We keep information only as long as needed for the purposes described here. Support correspondence is kept as needed to resolve the request and related follow-up. Purchase records may need to be kept to fulfil purchases, prevent repeated grants, address disputes and meet applicable legal obligations. Unity diagnostic reports, where applicable, follow the retention limits of the service in use.

• Analytics: user-level and event-level information follows the retention setting of our Google Analytics property. Google’s retention controls do not apply in the same way to standard aggregated reports. Contact us for the current setting and to request deletion of information that can be linked to your browser or installation. See Google’s retention documentation.
• Crashlytics: Google states that crash traces and associated installation identifiers are kept for 90 days before removal from live and backup systems begins.
• Remote Config: Google retains Firebase installation identifiers until a deletion request through its API; removal from live and backup systems can take up to 180 days after that request. These provider periods are described in Firebase’s retention information.

When information is no longer needed, it is deleted or de-identified, subject to applicable retention requirements and backup cycles. We use reasonable measures to protect information, but no storage or transmission system is completely secure.

Your choices and rights

You can choose not to make purchases or send optional support attachments. Depending on where you live, you may have rights to access, correct, delete or receive a copy of your information, restrict or object to processing, withdraw consent, and complain to your local data-protection authority.

Send requests to support@makalugames.com. We may ask for the minimum information needed to verify the request and find the relevant records. We will explain any lawful reason why information cannot be deleted. We may need to coordinate with Google, Unity or another provider and identify the installation concerned. We cannot remove Apple’s independent records or backups under your control.

There is currently no in-game Analytics or Crashlytics opt-out control. You can contact us about an objection, withdrawal or deletion request. Deleting local app data or uninstalling does not by itself delete reports already sent to Google, and reinstalling can create new installation identifiers.

Children’s information

Parents and guardians should supervise purchases and any information a child sends to support. Where parental consent is required for processing a child’s information, it must be obtained before that processing. If you believe a child has provided personal information without the required permission, contact us so we can investigate and take appropriate action.

Changes and contact

We update this policy when our practices change and revise the date above. We will provide additional notice or seek consent where required by law.

Responsible person: Denys Huch, Makalu Games.
Privacy and support: support@makalugames.com.