Effective date: August 11, 2026
LoopTimer ("the app") is a standalone Wear OS interval-training app (HIIT, Tabata, Pomodoro) published by MDz-IT Software ("we", "us", "the developer"). This policy describes what data the app collects and processes.
1. Who we are and how to contact us
Developer: MDz-IT Software Contact: mdzitsoftware+looptimer@gmail.com
Reach out with any questions about this policy or how your data is handled.
2. Diagnostic data collected via Firebase Crashlytics
The app uses Firebase Crashlytics (a Google service) to detect and diagnose crashes so we can keep LoopTimer stable.
When the app crashes, or in other diagnostic situations, Crashlytics automatically sends the following to Google/Firebase:
•Crash reports (crash logs) — stack traces and the point of failure in the app's code.
•Device diagnostic data — device model, OS version, and app state at the time of the crash.
•App installation identifier (Crashlytics/Firebase installation ID) — a randomly generated identifier tied to the app install, not to your identity or Google account.
This data is transmitted from the device to Google/Firebase servers over an encrypted connection (HTTPS) and is used solely to detect, diagnose, and fix bugs in the app. It is not sold, and it is not shared with third parties for marketing purposes. Collection is automatic and cannot be turned off from within the app — there is no in-app setting to disable it.
For more detail on what Crashlytics collects and how it's processed, see Google's Privacy Policy and Firebase's Google Play Data disclosure documentation.
3. What we do NOT collect
LoopTimer does not require sign-in or an account, and it does not collect:
•personal information (name, email address, phone number),
•location data,
•health or biometric data (heart rate, data from health sensors) — LoopTimer uses a health-type foreground service solely so interval countdowns keep running in the background with the screen off; the app does not read any data from Health Services or activity sensors,
•contacts, photos, or user files,
•data for advertising purposes, and it does not sell data.
4. Data stored locally on the device
Timer settings (work/rest durations, round count, sound/haptics preferences, etc.) are saved locally on the watch using Jetpack DataStore. This data never leaves the device — it is not sent to us or to any third party.
5. System permissions
The app requests the ACTIVITY_RECOGNITION permission on Android 14+. This is a platform requirement for starting a health-type foreground service (to keep the timer running in the background) — the app does not read any physical activity or motion-recognition data.
6. Children
LoopTimer is not directed at children and does not knowingly collect data from anyone under the age of 13.
7. Changes to this policy
We may update this policy from time to time. Changes will be published at the same URL with an updated effective date.
8. Contact
Privacy questions: mdzitsoftware+looptimer@gmail.com