Saltar al contenido

LEGAL · UPDATED NOVEMBER 2, 2026

Dozens privacy policy

This policy explains what data the Dozens game handles, where it is stored, what the two Google services it includes —AdMob and, in the daily challenge, Play Integrity— collect, and what rights you have. It follows Regulation (EU) 2016/679, the General Data Protection Regulation (GDPR), and Spanish Organic Law 3/2018 on the Protection of Personal Data and the Guarantee of Digital Rights (LOPDGDD).

Controller

  • Company name: Omilium, S.L.
  • Tax ID (NIF): B93915668
  • Registered address: C/ Romanilla, 79, 2.º B, 04740 Roquetas de Mar (Almería), Spain
  • Email: hello@omilium.com

Scope

This policy covers the Dozens app for Android, package name com.omilium.dozens, distributed on Google Play.

What the game does not do

  • No account or sign-up. You are not asked for a name, an email address or any other data to play.
  • Your regular games do not leave the device. Games, records and settings are computed and stored on your device. Our server only stores the daily challenge results of those who play it (see “The daily challenge”).
  • No analytics. The game does not measure how you play or send usage statistics to anyone: what the daily challenge sends is only used as explained in “The daily challenge”.
  • No purchases. Dozens sells nothing inside the app.

Of everything it stores on the device, Dozens only sends what the daily challenge needs, and only if you play it (see “The daily challenge”). What leaves the device is the requests to our server, described in “What Omilium receives”, what Google Play Integrity collects when it verifies what you send, and what the Google AdMob SDK and its consent form collect, described below. The link to this policy in the game’s Settings opens your browser; what happens when you visit omilium.com is covered by the website’s privacy policy (in Spanish).

What is stored on your device

The game keeps, in a local file on the device itself:

  • the game in progress, if you leave in the middle of one;
  • your points record and the best level you have reached;
  • the Hall of Fame, with the initials you type next to each score;
  • the daily challenge: today’s board, the attempts you have used today, your best result today, whether you have asked not to see its help again and, from the first time you open it, your install ID and any results waiting to be sent;
  • statistics about the dozens you have cleared;
  • your settings: music, sound effects, vibration, language, whether ads are on and whether your challenge results are verified;
  • whether you are 16 or over, if the game has asked your age (not the year you were born);
  • whether “Privacy options ›” has to appear in Settings;
  • whether you have already seen the tutorial.

If you are shown the consent form, your answer is also stored on the device; it is stored by the Google SDK, not by the game.

Apart from what the daily challenge sends (see “The daily challenge”), nothing the game stores leaves the device: Omilium does not receive it and has no way to see it. It is deleted when you uninstall the app or clear its data from the Android settings (Apps › Dozens › Storage › Clear data).

What Omilium receives

From the game, the only things that reach us are the requests to our server explained just below and in “The daily challenge”. Your data also reaches us by two other routes: Google Play and email.

Through our server

When you tap DAILY CHALLENGE, the game downloads that day’s board from our server, unless it already has it stored; that request carries no identifier of yours. If you play, at the end of each attempt it sends your result and asks for the day’s comparison, and from Settings you can ask for your results to be deleted: all of this is explained in “The daily challenge”. When you open the Hall of Fame, if you have played the challenge before, the game asks for the day’s table, also without any identifier of yours. If you do not play the challenge, the game does not talk to our server.

Like any internet connection, each request carries your device’s IP address. Our server uses it only to answer you and, in memory, to limit how many requests come from the same address. It does not store it or write it to any log. The legal basis is giving you what you ask for (Article 6(1)(b) GDPR) and our legitimate interest in protecting the server from abuse (Article 6(1)(f) GDPR). The server, dozens-api.omilium.com, is in Germany, within the European Union, and is hosted by Hetzner Online GmbH as Omilium’s processor.

Through Google Play

Google shows us, in its developer console, Play Console, data that it obtains itself, not the game:

  • your reviews of Dozens, with the public name you post them under, and our replies;
  • the app’s crash and freeze reports, with data about your device, such as the model and the Android version;
  • aggregated statistics on installs, ratings and usage, which do not identify you.

We use them to reply to reviews and fix bugs. The legal basis is our legitimate interest in maintaining and improving the game and in replying to those who review it (Article 6.1.f GDPR). We do not copy this data outside Play Console: Google keeps it, for the periods set by its policy. You can object to our processing it by writing to us at hello@omilium.com.

When you write to us

If you write to us, at hello@omilium.com or from the Dozens listing on Google Play, we process your email address, your name and whatever you tell us, in order to reply. If it is a support request about the game, the legal basis is the contract for the use of Dozens (Article 6.1.b GDPR); if it is anything else, such as a suggestion, our legitimate interest in replying to whoever writes to us (Article 6.1.f GDPR). We delete the conversation once 6 months have passed since its last message, in a review every three months, so no email is kept for more than 9 months. The details are in the section Cuando nos escribes of the website’s privacy policy (in Spanish).

The daily challenge

The daily challenge is a board that changes every day and is the same for everyone. It is the only part of Dozens that sends your data to Omilium, and only if you play it: your result, to compare it with everyone else’s and put it on the day’s leaderboard.

What is sent

The first time you tap DAILY CHALLENGE, the game creates an install ID: a random code that is stored on your device, is only used for the challenge and is not used for ads or anything else. At the end of each attempt, the game sends our server that ID, the day, the attempt number, your initials, your moves and your points. If you do not have initials yet, it asks you for them first; if you do not enter them, that attempt is not sent. Without a connection, the result waits on your device and is sent the next time you finish an attempt or go back to the menu with a connection; if the challenge day closes first, at 12:00 UTC the next day, it is discarded without being sent. After sending it, the game asks for the day’s comparison, and includes your ID to find out your position, unless you have turned verification off. The challenge help, which opens by itself the first time you enter, tells you this before any result is sent.

What our server stores

  • your install ID;
  • the day, the attempt number and the time each result arrived;
  • your initials, as you typed them, even if they are published as ***;
  • your moves, while the challenge day is open;
  • your points, both those the game computes and those our server recomputes, and the size of the biggest dozen you cleared;
  • whether the result was verified and, if not, why;
  • your streak: how many days in a row you have sent a result;
  • when the day closes, the percentage of players you beat, if your result was verified;
  • whether your alias is masked as *** after a report.

We use them to compute and verify your result, give you your position and your streak, publish the day’s leaderboard and its figures, and review suspicious results. We do not use them for anything else or combine them with any other data.

What anyone can see

While the challenge day is open, anyone can see the day’s leaderboard, in the game or by asking our server for it: the top ten verified scores, each with its initials, its points and its attempt number. The number of players, the median, a histogram of the scores and the day’s biggest dozen are also published, and they identify no one. Your ID is never published. When the day closes, the leaderboard is no longer published and only the number of players, the median and the histogram remain. The initials you enter do not have to be yours: do not use your real initials, your age or your year of birth. By saving them you agree that they are not offensive. Initials whose three letters spell a rude word in any of the game’s languages are published as ***, and we do the same with a reported alias if we find it offensive; masking it does not delete it from our server.

If you see an offensive alias on the leaderboard, tap “Report an alias ›” below the day’s leaderboard: it opens your email with a message to hello@omilium.com that carries the day and the aliases on the leaderboard; keep the ones you are reporting and tell us why.

Verification with Google Play Integrity

To keep the leaderboard fair, our server only counts results from the original game, as distributed by Google Play, on a genuine Android device. It checks this with Play Integrity, a Google Play API: when it sends a result, and when it asks for the comparison with your ID, the game asks Google for an encrypted token tied to that request, and our server passes it to Google to decrypt.

According to the Play Integrity API terms (consulted on October 29, 2026; the page was last updated on October 6, 2026), with each request Google collects what the app puts in it, which in Dozens is a fingerprint of the request (a SHA-256 hash), not your ID or your moves; data about the app (its package name, version and signing certificate); the Google Play license status of the accounts signed in on the device; and device information, namely a key attestation certificate and a device attestation token generated by Google Play services. According to Google, it uses them to verify the integrity of the app and the device and to check the license status; it encrypts them, does not transfer them to any third parties and deletes them after a set retention period, without saying how long.

Our server does not read the license or the account details, and does not store the token or Google’s response: only whether the result was verified and, if not, the reason. A result that is not verified is stored all the same, with the same time limits, but does not enter the leaderboard or the day’s figures.

What Play Integrity collects is processed by Google as a controller, under its own terms: those of Google Play and of its APIs. You can read Google’s privacy policy.

You can object to verification at any time, without giving reasons (Article 21 GDPR): turn “Verify my results” off in the game’s Settings. With verification off, the game asks Google for no token, asks for the comparison without your ID, and your results are stored unverified, so they do not enter the leaderboard. You can turn it back on at any time.

How long it is kept

  • while the challenge day is open, every attempt, with its moves;
  • when the day closes, at 12:00 UTC the next day, only the last attempt of that day is kept for each ID, without its moves, and anything from earlier days is deleted: just what your streak and your last result need;
  • if 90 days go by without any result of yours arriving, everything under your ID is deleted;
  • anything that arrives after its challenge day has closed, which the game never sends, is deleted after 48 hours;
  • each day’s figures (the number of players, the median and the histogram) carry no identifier and are kept with no time limit.

Our server makes an encrypted backup of its database every day, which is kept for 35 days in Hetzner’s storage in Nuremberg (Germany) and which no one can delete or change before then. So whatever is deleted, because its time is up or because you ask, may remain in the backups for up to 35 days. Each deletion you ask for leaves a fingerprint of your ID (a SHA-256 hash, with no other data) on record for those 35 days, so that it can be deleted again if a backup ever has to be restored.

How to delete it

You can delete your results whenever you like from the game, without writing to us: in Settings, tap “Delete my challenge history ›” and tap again to confirm. Our server deletes everything under your ID right away, and the game deletes from your device the ID, your best result today and any results waiting to be sent; attempts you have already used today stay used. If there is no connection, nothing is deleted, either on the server or on the device: try again when there is one. The next time you tap DAILY CHALLENGE, the game creates a new ID. The link does not appear in the middle of an attempt, because that attempt still has to be sent.

If you uninstall the game or clear its data without deleting your challenge history first, your ID is lost and you can no longer delete your results from the game: they are deleted automatically 90 days after your last result.

Google AdMob

AdMob, by Google, is the only ad service in Dozens. The game shows just one kind of ad, a rewarded video, and only when you ask for it to get the second chance in a game. If you have accepted advertising in the form described below, or it is not needed where you play, when the game starts the AdMob SDK is initialized and loads an ad in advance, so that it is ready if you ask for it: that is why it talks to Google even if you never watch an ad. If you have refused the form or are under 16, nothing is loaded in advance: the SDK is initialized and requests the ad from Google when you tap WATCH AN AD. And if you turn “Ads” off in the game’s Settings, the SDK is not initialized and the game requests no ads.

According to the data disclosure Google publishes for its ads SDK (consulted on September 29, 2026; the page was last updated on that same date), the SDK automatically collects and shares this data:

  • The device’s IP address, which may be used to estimate its approximate location.
  • App interactions: app launch, taps and video views.
  • Diagnostic information about the performance of the app and the SDK: app launch time, how often the app hangs, and energy usage.
  • Device and account identifiers: the app set ID and, if applicable, other identifiers related to signed-in accounts on the device. The disclosure also names the Android advertising ID, which Dozens does not let the SDK read (see below).

Google uses this data for advertising, analytics and fraud prevention, and transmits it encrypted with the TLS protocol. Omilium does not receive the individual data the SDK collects.

Omilium and Google are jointly responsible, as joint controllers (Article 26 GDPR), for collecting this data within Dozens and sending it to Google: Omilium decides to include AdMob in the game, and Google decides what its SDK collects. Omilium takes care of informing you, asking for your consent, letting you withdraw it and handling your rights over that collection. What Google does with the data afterwards (advertising, analytics and fraud prevention, for its own purposes and with its own retention periods) is Google’s alone, as controller. You can read Google’s privacy policy and how Google uses information from sites or apps that use its services.

Dozens does not read the advertising ID. The app removes the permissions that give access to the Android advertising ID and to the Privacy Sandbox advertising features, so neither Omilium nor the AdMob SDK can read it: Android returns a string of zeros to them, whether or not you give your consent. That is why ads in Dozens are not personalized for anyone.

The app set ID is a Google identifier scoped to the apps of a single developer on your device. The SDK reads it without asking for any permission, for fraud prevention and for analytics. Omilium does not receive it.

The consent form

If you play from the European Economic Area (the European Union, Iceland, Liechtenstein and Norway), the United Kingdom or Switzerland, Dozens asks for your consent to advertising before requesting any ad. It does so with Google’s consent tool, the User Messaging Platform (UMP), which is part of the same AdMob SDK.

Even though ads in Dozens are not personalized, the form is still needed: the SDK stores and reads information on your device, and that requires your consent.

  • When it appears. The first time you open the game, over the loading screen, after the age question described in “Children”, and only if you are 16 or over. Your answer is stored on the device and you are not asked again on later launches, unless Google needs to ask you again. Outside those regions the form never appears. If there is no connection when the game starts, the game does not wait: it goes on to the menu and requests no ads until consent has been resolved.
  • What you can choose. You can consent, not consent, or manage your options in detail, by purpose and by ad partner.
  • What happens if you do not consent. You can still play the whole game and ask for the second chance just as if you had consented; the ad is requested from Google when you tap WATCH AN AD, not before. According to Google’s AdMob documentation (consulted on September 29, 2026), when you do not consent to storing or accessing information on your device, Google serves limited ads, which disable the collection, sharing and use of personal data to personalize ads; the IP address is still used to deliver the ad to you, and Google uses local storage only to detect invalid traffic and prevent fraud. If you consent to storage but not to personalization, ads are non-personalized: they are not based on your past behavior, although they still use device identifiers to prevent fraud, cap how often you see the same ad and produce aggregated reports. With your full consent they could be personalized, but in Dozens they are not, because the app does not let the advertising ID be read. With limited ads, the SDK still stores its own cache and that of the ads it downloads on your device and, if it serves ads from other networks through Google, cookies used only to detect invalid traffic. We consider this technical storage, which does not need your consent (Article 22(2) of Spanish Law 34/2002): it is only used to show you the ad you ask for and to prevent fraud, not to personalize ads or to measure you. According to Google, limited ads do not use identifiers to cap how often you see an ad or to measure either.
  • How to change it later. In the game’s Settings, below “Privacy policy ›”, there is a “Privacy options ›” link that opens the form again so you can change or withdraw your choice at any time. It only appears where the form is required and if you are 16 or over.

Google’s sources are the User Messaging Platform guide for AdMob, the AdMob help page on GDPR messages, the help page on limited ads and the help page on how ads are served depending on TCF consent, all consulted on September 29, 2026.

Legal basis

  • Advertising in the European Economic Area, the United Kingdom and Switzerland: your consent (Article 6(1)(a) GDPR, and Article 22(2) of Spanish Law 34/2002 on information society services for access to information on your device), which you give or refuse in the form described above and can withdraw at any time from “Privacy options ›”, without affecting what was processed before. In Dozens, consent covers the SDK storing and reading information on your device; advertising is not personalized even with it.
  • Limited ads, when you refuse the form or are under 16: our legitimate interest in funding the game with the advertising you ask for and in preventing ad fraud (Article 6(1)(f) GDPR). Limited ads do not use your data for personalization. You can object at any time, without giving reasons (Article 21 GDPR): turn “Ads” off in the game’s Settings. With ads off, the game does not initialize the AdMob SDK, does not check the consent form and requests no ads, and there is no second chance. You can turn them back on at any time. You can also write to us at hello@omilium.com.
  • The daily challenge: storing what you send when you play it, comparing it with everyone else’s and publishing what anyone can see is giving you the service you ask for (Article 6(1)(b) GDPR). The install ID is stored on your device without asking for your consent because it is strictly necessary to give you that service (Article 22(2) of Spanish Law 34/2002).
  • Verification with Play Integrity: our legitimate interest in keeping the day’s leaderboard fair and preventing cheating (Article 6(1)(f) GDPR). The Play Integrity check reads information on your device, and we do not ask for your consent because it is strictly necessary for the security of the service you ask for (Article 22(2) of Spanish Law 34/2002). You can object at any time, without giving reasons (Article 21 GDPR), as explained in “The daily challenge”.
  • The other data stored on your device is not received by Omilium, so there is no processing on its part that needs a legal basis. The legal basis for the IP address that reaches our server, for what we see on Google Play and for your email is in “What Omilium receives”.

Android permissions

Dozens asks for three permissions:

  • Internet (INTERNET), used by the ads and the daily challenge, and network state access (ACCESS_NETWORK_STATE), used by the ads.
  • Vibration (VIBRATE), for haptic feedback while playing, which you can turn off in the game’s Settings.

The AdMob SDK also adds to the app the technical permissions it needs to work; Dozens removes the advertising ID and Privacy Sandbox ones. None of them, neither Dozens’ nor the SDK’s, is a sensitive permission: the app does not ask for access to your location, contacts, camera, microphone, photos or files.

Recipients and international transfers

The recipients of data are Google, through the AdMob SDK described above and through Play Integrity, if you play the daily challenge with verification on, and Hetzner Online GmbH, which hosts our server and its backups in Germany as Omilium’s processor (see “What Omilium receives” and “The daily challenge”). What the daily challenge publishes can be seen by anyone. Omilium does not sell or hand over data to anyone else.

Google may process data outside the European Economic Area, mainly in the United States. Those transfers are covered by the EU-U.S. Data Privacy Framework, under which Google is certified, and by the standard contractual clauses approved by the European Commission.

Delete your data

This section explains how to delete the data of the game Dozens, by Omilium, S.L.

How to request deletion

  1. What the game stores on your device you delete yourself, without writing to us: uninstall Dozens or, on Android, go to Settings › Apps › Dozens › Storage › Clear data.
  2. What the daily challenge sends to our server you also delete yourself, from the game and without writing to us, as explained in “The daily challenge”. Delete it before uninstalling.
  3. What AdMob collects is kept by Google, not by Omilium. You can ask Google to delete its data through its privacy policy. If you ask us, we will help you do it.
  4. If you would rather ask us, write to hello@omilium.com with the subject “Delete my Dozens data” and say that you are exercising your right to erasure.

What data is deleted

  • the game in progress, if you leave in the middle of one;
  • your points record and the best level you have reached;
  • the Hall of Fame, with the initials you type next to each score;
  • the daily challenge: today’s board, the attempts you have used today, your best result today, whether you have asked not to see its help again and, from the first time you open it, your install ID and any results waiting to be sent;
  • statistics about the dozens you have cleared;
  • your settings: music, sound effects, vibration, language, whether ads are on and whether your challenge results are verified;
  • whether you are 16 or over, if the game has asked your age (not the year you were born);
  • whether “Privacy options ›” has to appear in Settings;
  • whether you have already seen the tutorial;
  • on our server, what the daily challenge sends to it (see “The daily challenge”).

What the game stores on your device is deleted completely when you uninstall the app or clear its data. If you uninstall the game or clear its data without deleting your challenge history first, your ID is lost and you can no longer delete your results from the game: they are deleted automatically 90 days after your last result.

What data is kept, and for how long

What the game stores on your device is deleted with it. Our server does not keep your IP address, and it keeps what the daily challenge sends to it for the periods explained in “The daily challenge”. The data the AdMob SDK collects is kept by Google for the periods set by its own policy, and Omilium cannot delete it. What we see in Play Console is kept by Google, and your email for 9 months at most (see “What Omilium receives”).

Your rights

You can exercise your rights of access, rectification, erasure, objection, restriction of processing and portability at any time by writing to hello@omilium.com. Say which right you want to exercise. You can withdraw your consent to advertising yourself, at any time, from Settings › “Privacy options ›”. If we have reasonable doubts about your identity, we may ask you to prove it.

Right to object to ads. You can object to our processing your data to show you ads, without giving reasons (Article 21 GDPR): turn “Ads” off in the game’s Settings. With ads off, the game does not initialize the AdMob SDK, does not check the consent form and requests no ads, and there is no second chance. You can turn them back on at any time.

Right to object to verification. You can object to verification with Play Integrity, without giving reasons (Article 21 GDPR): turn “Verify my results” off in the game’s Settings. With verification off, the game asks Google for no token, asks for the comparison without your ID, and your results are stored unverified, so they do not enter the leaderboard. You can turn it back on at any time.

Only the game knows your install ID, and initials are not unique: if you write to us, we have no way of knowing which challenge results are yours. That is why you can delete them yourself from the game (see “The daily challenge”).

For the collection and sending that AdMob does within the game, you can contact us or Google. For what Google does with that data afterwards, contact Google through its privacy policy: Omilium does not receive it and cannot delete it.

If you believe your data has not been handled correctly, you can lodge a complaint with the Spanish Data Protection Agency (Agencia Española de Protección de Datos, www.aepd.es).

Children

Dozens is for players aged 13 and over, and does not knowingly collect data from children under that age. If you play from the European Economic Area, the United Kingdom or Switzerland, before asking for your consent to advertising the game asks you the year you were born. It does not store it: it only stores whether you are 16 or over, and it does not ask you again.

  • If you are 16 or over, you see the consent form described above.
  • If you are under 16, we do not ask for your consent, either at start-up or from Settings. With every ad, the game tells Google that you are a minor, and only limited ads are served, which do not use your data for personalization; the ad is requested when you tap WATCH AN AD, not before. According to Google’s documentation (consulted on October 19, 2026), with that signal Google does not personalize ads or send the advertising ID. You can turn ads off in Settings, like any player (see “Legal basis”).

Anyone who plays the daily challenge may appear on its leaderboard, minors included. That is why it only publishes initials, points and an attempt number, and the game warns you, when it asks for your initials, that there is no need to use your real ones, your age or your year of birth.

Changes to this policy

We may update this policy if what the game does or the law changes. The date of the last update appears at the top of the page, and the new version replaces the previous one at this same address.