TimerDockInformation stored on your device
TimerDock stores timer durations and state, saved presets, control assignments, and your last selected duration on your device. The app and its controls and Live Activities use app-specific shared storage. TimerDock does not provide cloud sync or backup for these settings. The usage and diagnostic information described below is sent to Google through Firebase.
Alarms and Live Activities
Timer alerts use Apple’s AlarmKit. System countdown displays use ActivityKit and WidgetKit. iOS requests your permission to use alarms. You can manage permissions and system displays in iOS Settings.
Firebase Analytics: usage analysis
TimerDock uses Google’s Firebase Analytics to understand app usage and improve features and usability. Depending on SDK behavior, data sent to Google includes automatic app events such as launches, sessions and engagement, app-instance and vendor identifiers (IDFV), device, OS and app versions, approximate region, and in-app purchase events. Approximate location is derived from IP addresses; the app does not use precise device location. TimerDock does not implement custom events that send timer settings or preset contents, or set a custom user ID.
Firebase Crashlytics: crash investigation
TimerDock uses Firebase Crashlytics to investigate failures and improve stability. Reports sent to Google include crash stack traces, occurrence times, app state, device, OS and app versions, and installation or session identifiers. When used with Analytics, automatic events before a crash may be included as diagnostic breadcrumbs. TimerDock does not add custom user IDs, custom logs or custom keys to crash reports.
Advertising, accounts and collection settings
TimerDock has no advertising SDK or Webdia account registration feature. Defaults for advertising storage, advertising user data and personalized advertising are disabled. Analytics and Crashlytics collection is enabled during normal startup in versions that include Firebase. There is currently no in-app setting to disable these collections individually. Website visits are covered by the separate website privacy policy.
In-app purchases
TimerDock Pro uses Apple’s StoreKit to purchase, restore, and verify purchase status. Apple processes payment information; Webdia does not receive your credit card number. The app uses verified purchase information to determine access to Pro features. Information processed by Apple’s services is covered by Apple’s privacy policy.
Managing data and external processing
You can cancel timers and delete saved presets in the app. Local data handling when deleting the app or backing up and restoring a device follows iOS behavior. Usage and diagnostic information sent to Google is processed and retained according to each service’s settings and privacy policy. Please refer to the Google and Firebase information linked below for details about retention and deletion. Deleting the app does not necessarily immediately delete all information already sent.
Contacting support
Information you submit through the support form, such as your email address, message, app version, and device details, is used to reply and investigate issues. Please use the support form to contact us. The shared form uses Cloudflare Turnstile to prevent spam. Timer data is not automatically attached.
Third-party privacy information
Last updated: October 26, 2026