Privacy Policy – Trackly Time Tracking

Last updated: December 6, 2025

This Privacy Policy explains how the Android app “Trackly Time Tracking” handles personal data. The app is designed to record working hours locally on your device. Additionally, the app uses Firebase services (Google) for anonymous usage analytics and crash reporting.

1. Data Controller

The responsible party for data processing within this app is:

Marius Klausa
Email: contact@marius-klausa.de

2. Types of Data Collected

2.1 Data you enter (stored locally on your device)

The app stores only the information you manually enter, such as:

• Time tracking entries (start time, end time, duration)
• Project and category names
• Optional notes for entries

These data are stored exclusively on your device. They are not transmitted to the developer or to third parties.

2.2 Usage and diagnostics data (via Firebase)

The app also uses Firebase Analytics and Firebase Crashlytics. These services may collect the following types of data:

• Information about how you use the app (e.g. which screens you open)
• Device information (device model, OS version, language settings)
• App information (app version, install timestamp)
• Error and crash information (e.g. stack traces, technical logs)
• A Firebase installation ID to distinguish app installations
• IP address (used by Google for region detection and security)

Your time tracking content (projects, durations, notes) is not intentionally sent to Firebase.

3. Purpose of Processing

3.1 Local data for time tracking

Your data are processed solely to provide the core app functionality:

• Creating, editing, and displaying working time entries
• Local calculations and statistics (e.g. total hours)

3.2 Usage analytics (Firebase Analytics)

Firebase Analytics helps understand how users interact with the app to improve usability and functionality.

3.3 Error detection and app stability (Firebase Crashlytics)

Firebase Crashlytics collects crash reports to identify technical issues and improve the reliability of the app.

4. Storage, Access, and Sharing

4.1 Local app data

• Your time tracking data remain stored only on your device.
• No local data are transferred to the developer or external servers.
• No third party, including the developer, has access to your local data.

4.2 Data transferred to Google (Firebase)

Usage and diagnostic data described in section 2.2 are transmitted to servers operated by Google LLC, which may be located outside the European Union, including in the United States.

You can review Google’s privacy documentation here:

• Firebase Privacy Information
• Google Privacy Policy

5. Details on Firebase Services Used

5.1 Google Analytics for Firebase

The app uses Firebase Analytics to collect anonymized event data such as:

• App start and close events
• Screen views
• Simple interactions (e.g. creating a new time entry)

These analytics help improve the app. I receive only aggregated reports, not data tied to individuals.

5.2 Firebase Crashlytics

Crashlytics captures crash-related diagnostics, such as:

• Device model and OS version
• App version
• Crash logs, stack traces, and technical context

These reports are used solely to fix bugs and improve stability. They do not contain personal content from your time entries.

6. Legal Basis

The following legal bases apply under the GDPR:

• Local processing of time tracking data:
  Art. 6(1)(b) GDPR – processing necessary to provide the app’s core functionality.
• Firebase Analytics and Crashlytics:
  Art. 6(1)(f) GDPR – legitimate interest. My legitimate interest is improving app stability, usability, and reliability.

7. Retention and Deletion of Data

7.1 Local app data

• You control how long your data are stored on your device.
• You may delete entries inside the app (if supported by the app UI).
• Uninstalling the app removes all locally stored app data.

7.2 Firebase data

Firebase stores analytics and crash data according to Google’s retention policies. Details can be found at:

• https://firebase.google.com/support/privacy
• https://policies.google.com/privacy

8. Data Security

Local data are protected by Android’s app sandboxing mechanisms. Since no personal time tracking data are transmitted to servers, there is no risk of server-side breaches for this data.

You can enhance protection by:

• Using a device lock (PIN, password, fingerprint, etc.)
• Preventing unauthorized physical access to your device
• Keeping your device and app updated

9. Changes to This Privacy Policy

This Privacy Policy may be updated to reflect technical changes, legal requirements, or new features. The most recent version will always be available at the URL you accessed.

10. Contact

For any privacy-related questions, please contact:

Marius Klausa
Email: contact@marius-klausa.de