Privacy policy

1. Data we collect

We collect what is needed to run the game, save your progress, fix crashes, show ads and measure our own advertising.

• Automatic account: on first launch the app creates an anonymous account (Firebase Authentication) with a random identifier. Your progress is saved to our cloud database under this account, and leaderboards use it. It contains no name or e-mail address, and you do not have to sign in for it.
• Sign-in (optional): if you sign in with Google (or with Apple on iOS), we receive the e-mail address, name and account identifier that the provider shares, and with Google the address of your profile photo. Your progress is then linked to that account so you can continue on another device. You can play without signing in.
• Nickname and leaderboards: the game gives you a nickname, which you can change. When you appear on a leaderboard or in a tournament, that nickname and your score are visible to other players. Your real Google or Apple name is never published. In versions with Bardino membership, members use one nickname across Decimo, Colmo and Palmo (see section 7).
• Newsletter (optional): if you enter your e-mail address in the in-game newsletter field, we store it only to tell you about updates. It is not required to play.
• Game progress and statistics: levels completed, stars, coins, gems, purchases, settings and play statistics. Stored on your device and in our cloud database (Firebase Firestore), whether or not you sign in.
• Device information: device model, operating system and app version, the device's language and region setting, time zone, the Firebase Analytics app instance ID and, on iOS, the identifier for vendor. Stored with your account record. The region comes from your device settings; the app does not ask for your location.
• Usage and analytics: in-game events (for example level started, completed or failed, power-ups used), session information and basic device information, via Firebase Analytics. Used in aggregate to balance and improve the game.
• Crash diagnostics: crash logs, the state of the device at the time of a crash, the level being played and your account's random identifier, via Firebase Crashlytics.
• Notifications: the app stores a push notification token for your device (Firebase Cloud Messaging) with your account. Notifications are shown only if you allow them.
• Advertising: ads are served by Google AdMob. Depending on your consent, ads may use your device's advertising identifier. Where consent is required (for example in the EEA and the UK) we ask for it before showing ads. On iOS the advertising identifier is only available if you allow tracking when the app asks. Ad content is limited to the G rating.
• Ad measurement on Android: while data collection is on (see section 5), the Android app sends a few events to Meta through the Meta (Facebook) SDK so that we can measure our ads on Facebook and Instagram: app installs and launches, finishing the tutorial, winning the first level, purchases (amount and currency) and ad impressions with their value. The Meta SDK may also receive your advertising identifier. The iOS app sends nothing to Meta.
• Purchases: in-app purchases are processed by Apple (App Store) or Google (Google Play). We do not receive your card details. We receive a purchase confirmation, which our server checks with Apple or Google before delivering the item, and we keep a record of each purchase (product, order number, date). On Android, subscriptions and the Remove Ads purchase are also managed through RevenueCat, which receives the purchase details and your account's random identifier.
• Achievements and platform leaderboards: if you are signed in to Google Play Games (Android) or Game Center (iOS), the game sends your achievements and scores there. How they are shown depends on that service's own settings.

We do not sell your personal data.

2. Why we use it

• To provide and save your game progress, and to let you continue on another device when you sign in.
• To run leaderboards, tournaments and the daily puzzle.
• To diagnose crashes and fix bugs.
• To understand usage in aggregate, balance difficulty and improve the game.
• To send the notifications you allowed.
• To show the ads that keep the game free, measure our own advertising and process optional purchases.

3. Third-party services

These providers process data on our behalf under their own terms and policies:

• Google Firebase (Authentication, Firestore, Cloud Functions, Analytics, Crashlytics, Cloud Messaging, Remote Config, App Check)
• Google AdMob (advertising)
• Google (Google Play purchases, Sign in with Google, Google Play Games)
• Apple (App Store purchases, Sign in with Apple, Game Center)
• RevenueCat (purchases on Android)
• Meta (ad measurement on Android)

4. Retention and deletion

• Local data stays on your device until you uninstall the app or clear its data.
• Cloud data is kept while your account exists, including the automatic anonymous account. Uninstalling the app does not delete it.
• You can delete your account and its data in the app: Profile > Delete Account. This deletes your cloud progress, account record, coins and gems, purchase history, scores (including past daily and tournament entries), push tokens and newsletter address, clears the game data on your device and signs you out. Purchase records are kept without your account identifier, because they stop the same purchase from being redeemed twice. Details: Account deletion.
• Deleting your account does not end a Bardino membership; Leave Bardino membership in Settings does (see section 7).
• Data already sent to Firebase Analytics, Crashlytics, AdMob or Meta is kept by those services for their own retention periods.

5. Your choices

• Play without signing in if you do not want to share your e-mail address and name. Your progress is still saved under the anonymous account.
• Turn off usage statistics, crash reports and, on Android, ad measurement in Settings > Data Collection.
• Change your ad consent in Settings > Ad privacy options, which appears where the consent form applies.
• Reset your advertising identifier or limit ad tracking in your device settings; on iOS you can also turn off tracking for Decimo.
• Turn off notifications in the game's settings or in your device settings.
• Delete your account and data at any time (see section 4).

6. Children

Decimo is intended for a general audience and is not directed to children under 13. We do not knowingly collect data from children under 13. If you believe a child has given us data, contact us and we will delete it.

7. Bardino membership (optional)

Decimo, Colmo and Palmo are made by the same developer. In versions of Decimo that offer it, Bardino membership is a free, optional membership shared by the three games: one nickname across them, a daily streak that any of the three can keep going, and gifts. It works with a Google sign-in (or Apple on iOS) and is open only to people aged 13 or over. What Bardino's server keeps, for how long, on what legal basis and how to use your rights is set out in the membership's own privacy notice. This section covers only what Decimo itself sends and stores. Versions of Decimo without the membership send nothing to Bardino's server.

• Before you join: Decimo asks Bardino's server (europe-west1-bardino-shared.cloudfunctions.net) whether membership is open. That request carries no identity. Decimo also has its own switch in Firebase Remote Config: while it is off, a player who has not joined, or whose membership this device does not know about yet, sends nothing at all to Bardino's server, not even that question, and sees no membership card. If both say it is open and you have signed in with Google or Apple, Decimo also sends your sign-in token so that the card can show whether you are already a member. This happens when the main screen or Settings opens, when you come back to the game and after you sign in; a recent answer is reused for up to five minutes. A player who has not signed in with Google or Apple never sends a token.
• Your sign-in token: every request except the question whether membership is open carries it. Firebase issues it for your Decimo account, and it contains the account's identifier and e-mail address (with Apple, the relay address if you chose to hide yours). It can also carry the name and, with Google, the profile photo address that the provider shared with Decimo (see section 1); the notice says what the server takes from it. The token of an anonymous account is never sent.
• When you join: the join sheet shows a short summary and links to the membership terms and the privacy notice, and Join only works after you tick I am 13 years old or older. Decimo then sends the version of the membership texts you were shown, that confirmation and, for a new membership, your current Decimo nickname if it is 2 to 20 characters long. If you are already a member through Colmo or Palmo, the button reads Link Decimo and no nickname is sent.
• While you are a member: Decimo asks for your membership status as above, and sends the date of each daily puzzle you win (your local day), a nickname you change and the identifier of each gift you claim; the welcome gift is claimed right after you join. In return it receives your shared nickname, the games you have linked, your badges, your shared streak and your gifts. Claimed gifts are added to your Decimo coins and power-ups and become part of your game progress (see section 1). Once this device knows you as a member, Decimo keeps these requests going whatever the switches say; leaving stops them.
• Your nickname: a member has one nickname in all three games, and the one on Bardino's server wins. A nickname set in Colmo or Palmo therefore becomes your Decimo nickname and, like any Decimo nickname, is shown to other players on leaderboards and in tournaments. A nickname you change in Decimo changes in the other two games too, and while you are a member it can be at most 20 characters long. The name on your Google or Apple account is never used as the nickname.
• On your device: which Decimo account the membership is linked to, and a daily puzzle win or nickname change that could not be sent yet, for example while offline; it is sent the next time the game reaches the server. These stay in the app's local settings and are not part of your cloud save.
• Analytics: Decimo logs these events to Firebase Analytics: the membership card was shown (as an invitation, as an offer to link Decimo or as a member's card); you joined (a new membership or Decimo linked to an existing one, and how many games are linked); joining failed (an error code); a gift was claimed (its identifier, kind and coin amount); you left (how many games were linked); a sibling game's store page was opened (which game). Coins from a gift also show up in the usual coins-earned event, with Bardino as the source. On Android the store link carries only a tag saying the visit came from Decimo's Bardino card. None of these events carries your e-mail address or your nickname, and like all analytics they are not sent while usage statistics are off in Settings > Data Collection.
• Leaving: Leave Bardino membership in Settings, shown only to members, deletes your membership record for all three games once you confirm. Your Decimo progress, the gifts you already claimed and your current Decimo nickname stay, and the membership's records on the device are removed. Signing out of Decimo or deleting your Decimo account (see section 4) removes the membership's traces from the device, including anything not yet sent, but does not end the membership. If you want both gone, leave Bardino first.

8. Security and changes

We use industry-standard measures (encrypted transport, Google Cloud infrastructure). No method is 100% secure, but we work to protect your data. We may update this policy; material changes will be posted here with a new "last updated" date.

9. Contact