Ludo privacy policy

Last updated: 11 October 2026 · About Ludo

Ludo is a board game made by Echo, a software studio from Brčko, Bosnia & Herzegovina, played against the computer or online against other players. This policy covers the game on Android and on every other platform it is released on.

In short

• The game never asks for your name, email or any account, and the game itself sells no data.
• The Android version is free and shows ads from Google AdMob, never during a game and never while you are in an online room. Google collects data for them as the Ads section below describes, and in the EU and wherever the law requires it, asks for your consent first.
• The Android version sends data to Google's Firebase services, which process it for us:
  • crash reports, always, so that errors can be found and fixed;
  • usage statistics, only if you agree. The game asks once, at its first start. Until you answer Yes, nothing of them is collected.
• You can change your answer about usage statistics at any time, in Settings → Share usage statistics.
• Online play, on every platform that has it, signs you in anonymously and keeps the game room on Firebase until the room is deleted, as the Online play section below describes. Settings → Delete online data deletes your anonymous user ID at once.

Crash reports (Android)

When the game crashes or runs into an error, it sends a crash report to Firebase Crashlytics. A report holds:

• what went wrong: the error and where in the game's code it happened;
• what the game was doing: the screen, your colour, the turn and how many pieces each player has home, and a short log of the screens and games before it;
• your device: its model, its Android version, its free memory and storage, the graphics chip, and the game's version;
• a random installation identifier, which counts how many players a problem hits. It isn't tied to you, your Google account or anything else on the phone.

Crash reports don't depend on your answer about usage statistics: they are needed to keep the game working.

Usage statistics (Android, only if you agree)

If you answer Yes, the game sends two kinds of usage statistics.

How the game is used, to Google Analytics for Firebase:

• which of the game's screens you open: the main menu, the colour choice, the game, the pause menu, How to play, Settings and the statistics at a game's end;
• each game you start and how it ends: your colour, which settings it was played with (how the pieces travel, auto-playing the only move, hints), the result, the number of turns, and your pieces home, sixes, pieces bumped and fields moved, and how long it was played;
• which settings you change, and to what;
• Firebase's own information about the app's use: when the app is installed, opened and updated, how long it is used, and in which session.

How well the game runs, to Firebase Performance Monitoring:

• how long the game takes to start and to open a game;
• how smoothly a game plays: how many frames it drew, how many were slow, how long they took, the most memory it used and how many turns it had, with the graphics renderer;
• the app's start and how long it stays on the screen, and in some sessions how much of the processor and memory it used.

With either, your device's model, its Android version, the game's version and your language, and for performance data your mobile network operator and connection type (Wi-Fi or mobile). Google works out your approximate location from your IP address: the country, and for usage statistics also the region and city. The game never asks for your location. Each comes with a random identifier of the app's installation, which counts players and sessions and is reset when the game is reinstalled.

Usage statistics never include your name, email, contacts, files, precise location or anything you type. Usage statistics turn off everything advertising-related: they don't use the advertising ID, don't collect the Android ID, and deny Firebase every use of the data for ads or ad personalization. The ads are separate, and the Ads section below describes them.

If you answer No, or later turn Share usage statistics off, Google Analytics and Performance Monitoring stop collecting on your device. What was already collected is deleted after the times below.

Online play

When you play online, the game signs in to Firebase Authentication anonymously. It gets a random user ID, without your name, email, phone number or Google account. The ID is kept in the game's storage on your device. Reinstalling the game makes a new one on Android and iOS; on a desktop it stays in the game's user data folder until you delete it with Settings → Delete online data or remove that folder.

Firebase Realtime Database, on servers in Belgium (EU), holds the room of an online game:

• each player's random user ID and player name. The name is two words the game picks from a list, such as “Lucky Six”;
• the moves and the state of the game, and the host's saved copy of it, which a new host needs to carry on if the host's device drops;
• the room code you share to invite friends;
• when the room was made and last heard from, and when each player was last connected, to notice who left.

There is no chat, free text or profile picture. The other players in the room see your player name and your moves, and their devices receive your anonymous user ID, which the game never shows. A search for players also reads and writes a pointer to the room that waits for players: the room's internal id and the time it was written, nothing of yours.

After a game, its room stays at most 2 minutes, for the final results, then it is deleted, unless its players chose to play again. A room is deleted at once when its last player leaves it during a game, and its code as soon as the game starts. A room that every player abandoned without leaving it (the game closed, or the network gone) has no fixed time to go: a device that meets it after 24 hours deletes it, but a room is met only by its code, or while the matchmaking pointer still names it, so nothing may ever lead a device to it, and it may stay indefinitely, with its names, user IDs and moves.

If you close the game in the middle of an online game, your device keeps that room in the game's storage, and the next time the main menu opens it asks the database whether that game still goes on, so that it can offer Rejoin game. This happens only while such a game is kept.

With every request, Google's servers also receive your device's IP address and its user agent (the kind of program asking), as any server does. Firebase Authentication keeps the IP addresses it logs for a few weeks, and the Realtime Database keeps IP addresses and user agents for a few days, to keep the service working and safe (Firebase's privacy page).

The anonymous user ID stays in Firebase Authentication, without anything attached to it, until it is deleted. Settings → Delete online data deletes it at once, after it gives up a game you could rejoin, and the game forgets the ID; the next online game makes a new one. An ID written into a room stays there until the room is deleted. Firebase Authentication runs in Google's data centres in the United States.

Online play works the same whatever your answer about usage statistics, and it sends nothing about you but what this section lists. If the game runs into an error while you play online, its crash report may also hold the internal id of the room, a random code the game made, which is not personal.

Ads (Android)

The Android version of Ludo is free and shows ads from Google AdMob, which Google runs:

• a full-screen ad at a natural break, at most one every 4 minutes: after an offline game ends, before its statistics, and on the main menu after you leave an online game. Never on your first day with the game, never in your first game of a session, never during a game, and never while you are in an online room or waiting for one;
• a banner at the bottom of the main menu and of the search screen, which covers nothing;
• a short video you may choose to watch, No ads for an hour: watched to its end, it turns every ad off for an hour. The game keeps the end of that hour, and when it first started, in its own storage on your device.

What AdMob collects. To show ads, measure them and prevent fraud, Google's Mobile Ads SDK collects and shares with Google: your device's IP address, from which Google estimates your approximate location; how you interact with ads (the app's launches, taps, video views); diagnostic information about the app's and the SDK's performance; and device identifiers: the Android advertising ID and the app set ID. It travels encrypted. Google uses this data as its own policy says, not only for us: How Google uses information from sites or apps that use our services.

Your consent. In the European Union, the European Economic Area, the United Kingdom and Switzerland, and wherever else the law requires it, Google's consent form (Google's User Messaging Platform) asks you, on the game's main menu and before any ad is requested, whether Google may use your data for personalised ads. Your choice decides whether the ads you see are personalised. Settings → Ad privacy options opens the form again whenever it applies to you.

Your choices. In Android's settings (Privacy → Ads, or Google → Ads, depending on the device) you can reset or delete your advertising ID, after which no app can use it. No ads for an hour turns ads off for an hour; closing its video early gives nothing.

Permissions. For the ads, the Android version also has the advertising ID permission, which Android grants at install without asking.

How the data travels and how long it is kept

Everything goes over an encrypted connection (HTTPS). Google processes it for us, as a service provider, and keeps it for a limited time (the ads' data excepted, which Google uses under its own policy, as the Ads section says): crash reports for 90 days; performance data for 30 days where it is linked to an IP address and 60 days for the rest; usage statistics for the retention period set in Google Analytics, 2 months. Online play's data is kept as the Online play section says: a room's until the room is deleted, the anonymous user ID until it is deleted.

To send it, the Android version has the internet and network-state permissions, which Android grants without asking. On the other platforms the game sends nothing but online play's data: only when you play online, and when the main menu checks, as above, a game you left open.

What stays on your device

Your settings, including your answer about usage statistics, your online name, and your anonymous user ID with the token that signs it in and the room of a game you may rejoin, are saved on your device, in the game's own storage. Apart from what online play sends and the settings usage statistics report, as above, none of it leaves your device, and nobody else can see it. Uninstalling the game deletes it on Android and iOS; on a desktop it stays in the game's user data folder until you remove that folder, and Settings → Delete online data deletes the user ID.

Your choices

• To stop usage statistics, turn off Settings → Share usage statistics.
• To send nothing for online play, don't play online.
• To delete your anonymous user ID from Firebase Authentication at once, use Settings → Delete online data, before you uninstall the game.
• To change your choice about personalised ads, use Settings → Ad privacy options where it applies to you, or reset your advertising ID in Android's settings.
• To stop crash reports as well, uninstall the game.
• To have the data from your device deleted sooner, including your anonymous user ID, use the form at the bottom of this page.

Children

Neither crash reports, usage statistics nor online games hold anything that identifies a player, children included. The game is meant for players 13 and older, and its ads are not directed at children.

Changes

If a future version changes any of this, this page will be updated before that version is released, and the date above will change.

Contact

Questions about this policy: write to us through the contact form on this website.