Effective date: 2026-10-21 Last updated: 2026-10-21
Twindial is a chess clock for two players at a real board: it times each side’s moves under the time control you choose, and keeps each finished game with every move’s time. We do not create accounts, do not ask for your email, and do not ship any analytics or tracking SDK. Your time controls, your games and their move times stay on your phone. Twindial never sends them anywhere and never reads your location. They leave the phone only if you share a game’s text, or save a backup where you choose. A backup file is a plain file and is not encrypted.
Twindial asks for no permission at runtime - no location, camera, microphone, contacts, photos, media, storage or notification permission. The clock, the time controls and the history all work on the phone, so timing a game never uses the internet. The app contains no code that can reach a server at all, apart from the advertising SDK described below, which receives nothing from your games.
If that’s all you wanted to know, you’re done. The sections below spell it out in detail.
com.dashfusion.listchessclock)The following is created and kept locally, in the app’s private storage:
Your games are kept here and nowhere else. They leave the phone only when you act: a game’s text you share goes to the app you choose in Android’s share sheet; a backup you save goes where you choose. Twindial never sends them anywhere itself.
The app explicitly opts out of Android cloud backup and device-to-device transfer, so Android never copies your time controls or your games to Google Drive or to another phone. A new phone starts with no time controls of your own and no history unless you restore a backup you saved. The app says so in Settings.
You can delete a time control or a finished game, use Settings → Delete the history, or uninstall the app — Android removes the local data with it. We have no servers and no cloud storage. We cannot see your games and we cannot recover them if you lose your device.
The app contains the Google Mobile Ads SDK. It shows an occasional full-screen interstitial ad — only after a finished game is left for the home screen, never during a game, a pause or a rematch, never on the way into a game and never as the app opens — plus an optional rewarded ad you can choose to watch to remove ads for 24 hours, which is not offered while a game is at the table. There are no banner ads. Google may collect and process:
AdMob receives nothing from your games: no name, no game, no time, no keyword and no content URL. Like any ad in any app, an ad request does name the app it comes from. The approximate location above is Google’s estimate from your internet address; it is never your phone’s location, which Twindial cannot read. Google’s handling of the data above is governed by Google’s own policies:
Consent (EEA, UK and Switzerland): on first launch the app shows Google’s certified consent form, and you choose whether personalised ads are allowed. You can change your answer at any time from Settings → Advert privacy options inside the app. You can also opt out of personalised advertising via your device’s system settings (Android: Settings → Privacy → Ads).
None. We don’t run any backend. We have no analytics SDK, no crash reporter that phones home, no Firebase, and no custom telemetry. There is no HTTP client anywhere in the app’s own code, and the build fails if one is ever added.
AD_ID) — required by Google Play for apps that serve ads; used by AdMob as
described above.That is all of them. Twindial asks for no permission at runtime: Android never stops to ask you about one. It has no access to your location — no GPS, no fine or approximate location, no background location — and none to your camera, microphone, photos, media, files, contacts, messages or calendar, and it asks for none of them. It sends no notifications and asks for no notification permission: the clock runs only while the app is on the screen, and a running game pauses when you leave it. The screen is kept on during a game by the app’s own window, which needs no permission.
A few more permissions are merged into the final app package by the libraries the app is built on, so the list Google Play shows you is slightly longer than the one above. They are the Android Ad Services permissions, from the Google Mobile Ads SDK; wake-lock and foreground-service, from the Android scheduling library the ads SDK brings in; and one permission that only lets the app’s own parts talk to each other. None is a permission Android stops to ask you about, and none is used by any code we wrote: Twindial holds no wake lock and runs no foreground service of its own. A test reads the built app’s own merged manifest on every run and fails the build if that list ever changes, or if any location, camera, microphone, media, storage or notification permission appears in it.
Twindial is for adults who time a game between two players at a board - a club’s blitz evening, a weekly game, a Go match - and is intended for adults. It is not directed to children under 13, and we do not knowingly collect data from children — and, as above, we collect no personal data from anyone.
Twindial measures time and says whose time is up. It decides no result - a flag, a draw or an arbiter’s call is the players’ - predicts nothing, plays no game and records no money: no stake, no prize and no bet.
If we change the data we collect or the third-party services we integrate, we will update this page and bump the “Last updated” date above. Material changes will be flagged in the app’s release notes as well.
Questions, requests, complaints: dash.fusion@outlook.com.