Cookie Policy
Last Updated: July 15, 2026
This Cookie Policy explains how the Knight Clock application ("Application") uses cookies, tracking identifiers, and similar local storage technologies.
1. Cookies in Mobile Applications
Unlike desktop browsers, mobile applications do not utilize standard cookies (small text files saved inside browser folders). Instead, mobile apps rely on unique hardware/software identifiers, SDK parameters, and local device storage to save your system preferences and enable platform services.
2. Types of Identifiers & Storage Used
We use Android's local storage system to save your custom chess timer configurations, selected sound presets, and haptic preferences. This information stays 100% on your device and is never uploaded online.
The Google AdMob SDK uses your Google Advertising ID to support advertisement tracking, limit the number of times you see a specific ad, and provide customized ad content (if you have opted-in for personalized ads).
When loading advertisements, the AdMob SDK may store transient configuration files, ad units, and diagnostic cache locally inside the application's sandboxed cache folder to ensure fast loading times.
3. Third-Party Disclosures
Google utilizes advertising identifiers and analytics diagnostics to serve marketing assets within our application. Google's use of these identifiers enables it and its partners to serve ads based on your visit to this and/or other apps on the Internet.
4. How to Revoke/Manage Consent
Users within the EEA/UK can revoke or alter their cookie and tracking preferences at any time by navigating to the About / Privacy Settings section in the app settings, where they can re-trigger the Google User Messaging Platform (UMP) consent screen.
Additionally, all Android users can opt-out of personalized marketing or delete their AAID identifier at any time via their Android Device Settings (Settings > Privacy > Ads > Delete/Reset Advertising ID).