Privacy Policy
TENFLUX is played without an account: no sign-up, no password. If you play, it creates an anonymous identifier and a public nickname — which you can personalise — so your score can appear on a leaderboard, and it shows an ad between runs. If you wish, you can link a Google account to protect and recover your profile (section 3). Gameplay works offline; the leaderboards, the daily, the duels and the account features use our online services.
1. What we do not collect
We do not collect your name, phone number, date of birth, GPS location, contacts, photos, files or messages. TENFLUX requests none of the corresponding permissions. The only free text you can type is your public nickname (section 2) — do not put your real name or any personal information in it.
Your email address is not stored by TENFLUX. If you link a Google account (section 3), it is processed by Firebase Authentication (Google), the service that handles sign-in, and appears neither in our database, nor on the leaderboards, nor in our logs.
There is no analytics and no crash reporting in TENFLUX.
2. The player identifier
The first time you use a feature that needs TENFLUX's online services — starting a run, choosing a nickname, or opening the leaderboard or the daily — TENFLUX creates an anonymous account with Firebase Authentication (Google). Until you protect it (section 3), that account has no sign-in username, no password and no email address: it is a number.
Until you use one of those features, none of this exists: opening the game, looking at it and closing it again creates no account.
Attached to that number are:
- a public nickname — generated automatically (for example
FLUX · 7K3Q) until you choose one, and which you can type or change yourself in the game. It is the only text other players ever see of you: do not put any personal information in it; - the date the account was created and the date of your last session;
- your submitted runs: distance, duration, mode, ruleset version, and the exact sequence of your taps;
- depending on the features you use: your emblem (a visual chosen among the game's own, visible on the leaderboards), your collection (in-game badges and cosmetics) and the list of players you follow (MY PLAYERS — invisible to everyone else, including the players you follow);
- depending on the features you use: your duels — whom you challenged or who challenged you (by nickname), your rounds and their distances, the result and your record (wins, losses, draws) — and the list of players whose challenges you refuse (visible to you alone). This data serves to organise and settle the duel, nothing else. Until a duel is over, your opponent sees how many rounds you have played, never your distances; the sequence of your taps is shown to no one, duels included.
Why the sequence of your taps. TENFLUX replays every submitted run on its server to check that the reported score matches what was actually played. That is what protects the leaderboard from cheating. This data has no other use and is never shown to anyone.
Without a linked Google account, this identifier belongs to the installation: if you uninstall TENFLUX or change phone without having protected your profile, it is lost. A protected profile can be recovered from “I already have an account” (section 3).
3. Google account (optional)
TENFLUX is played entirely without an account. If you wish, you can link your Google account to your profile (“Protect my account”): your TENFLUX identifier stays exactly the same, and you can then recover your profile on another phone (“I already have an account”) — nickname, verified best, level progress and the state of the daily as the server knows them.
Your email address is not stored by TENFLUX. It is processed by Firebase Authentication (Google), the service that handles sign-in, and appears neither in our database, nor on the leaderboards, nor in our logs. Firebase Authentication may process this data outside the European Union, under the terms of Google Cloud's contractual clauses.
4. Advertising
TENFLUX shows an interstitial ad between some runs, served by Google AdMob.
The Google Mobile Ads SDK collects and shares, on its own account:
- your IP address, from which an approximate location is derived;
- your interactions with the ad;
- diagnostic information;
- device identifiers, including the Android advertising ID.
This data is used for advertising, measurement and fraud prevention. It is sent to Google,
which is the controller for it. Google publishes its own description of this collection at
developers.google.com/admob/android/privacy/play-data-disclosure.
You can reset or delete your advertising ID in your phone's Android settings, at any time, without going through TENFLUX.
There is no banner, no rewarded video and no app-open ad. Levels show no ads at all. In the daily, an ad may be shown before each attempt — never during play. No ad ever grants any gameplay advantage.
Your consent
If you are in a region that requires it (European Economic Area, United Kingdom and others), a Google consent screen is shown before any advertising. You can change your choice at any time: Settings → privacy options, inside the game.
That form is Google's own (User Messaging Platform); TENFLUX does not replace it and never guesses your country.
5. Anti-cheat verification
Runs submitted to the leaderboard are replayed on our server, as described in section 2. That is our only verification mechanism.
TENFLUX does not currently use device attestation (Google Play Integrity, Firebase App Check). Our server knows how to receive one, but the app sends none, so no data of that kind is collected. If this changes, this policy will be updated beforehand.
6. What stays on your phone
Your best score, your recent runs, your settings and gameplay telemetry stay on your phone, in a private application folder. Your level progress — and, depending on the app version, your collection — is additionally copied to our servers when a connection exists, so it can be restored if you recover your account (section 3).
Local data is deleted when you uninstall TENFLUX.
Android backup. If Android's automatic backup is enabled on your phone, your local game file (best distance, settings, progression) may be copied by the system into your own Google Drive and restored when you change device. That is your backup, not ours: we have no access to it.
Your sign-in session and your advertising choices are excluded from it by the app: they stay tied to this installation. Changing phone therefore carries neither your account — for that you need to have linked it to Google (point 3) — nor the advertising consent you gave, which will be asked again.
7. Security and transfers
Every exchange between TENFLUX and its server goes over HTTPS, without exception: the app refuses any other address. Google's advertising SDK likewise encrypts its traffic with TLS.
The TENFLUX server and its database are hosted on Google Cloud in Belgium
(europe-west1). The database is reachable by no client: not the
game, not a browser, not a signed-in player — only the TENFLUX server reaches it.
Google, as the provider of authentication, hosting and advertising, may process data outside the European Union. Those transfers are covered by the European Commission's standard contractual clauses and by the commitments Google publishes in its own data processing terms.
8. Retention
- Player identifier, nickname, submitted runs, duels, level progress: kept for as long as the leaderboard exists, or until you delete your account (section 9) — verified runs are then kept without your identifier.
- Server logs: they contain a hash of your identifier, never the identifier itself, and are kept for Google Cloud's default retention period.
- Infrastructure logs: our host (Google Cloud) records the requests the server receives, which includes your IP address. These logs serve the operation and the security of the service, we do not link them to your profile, and they are kept for Google Cloud's default retention period.
- Data on your phone: until you uninstall.
We do not set a period after which an inactive profile would be deleted automatically: a leaderboard only means something if it keeps the scores. You can, however, delete your own account at any time, in seconds (point 9).
9. Your rights
You have the right to access, rectify, erase, restrict and object to the processing of data concerning you.
From the PROFILE → ACCOUNT screen, you can at any time delete your account — profile, nickname, emblem, leaderboard entries, daily history, level progress and, depending on the features you use, collection, MY PLAYERS list, duels, duel record and ignored-players list. A duel in progress is cancelled; a finished one stops carrying your nickname. Verified run records are kept without your identifier (anti-cheat, see section 2). You can also request a copy of your data (a readable JSON file) by email, at the address below.
The full procedure is described on the data deletion page. A
request by email remains possible: write to
privacy@tenflux.fr quoting your in-game
nickname (visible on the profile screen, for example FLUX · 7K3Q).
You may also lodge a complaint with the data protection authority in your country.
10. Children
TENFLUX is not directed at children. The game is intended for an audience aged 13 and over. We do not knowingly collect data concerning a child. If you believe this has happened, write to privacy@tenflux.fr and we will delete the record.
11. What we rely on
To be complete in the GDPR's own vocabulary, here is the legal basis for each processing:
- Player identifier, pseudonym, submitted runs, leaderboards, duels, progression, collection: performance of the service you asked for — there is no world leaderboard without an identifier and a score.
- Anti-cheat replay and the anonymised retention of runs: our legitimate interest in a leaderboard that is not rigged.
- Google account: your consent, given by pressing "Protect my account" — optional, and withdrawn by deleting the account.
- Advertising: your consent, collected by the Google form described in point 4, which you can change at any time.
- Infrastructure logs: our legitimate interest in operating and securing the service.
12. Changes
Any change to this policy will be published at this address, with a new date at the top of the page. Significant changes will be noted in the release notes of the update concerned.