Last updated October 9, 2026
First of all, thank you for choosing Wit!
Alfredo Jimenez built the Wit app as a Free app. This SERVICE is provided at no cost and is intended for use as is.
Here you will find all the information regarding your privacy while using Wit App.
In Short - Wit does not operate its own servers to collect or store users’ health data. However, the app uses Firebase to provide the workout sharing feature described below. Certain data, such as heart rate and burned calories, may be processed and stored locally on the user’s device. If the user grants the relevant permissions, Wit may also write workout records, burned calories, and heart rate data to Google Health Connect. Wit does not transmit health data to the developer’s servers as part of this integration.
In addition, the app uses third-party services described below:
Google Play Services: Wit may use Google Play services to provide app functionality. For information about Google’s privacy practices, visit this link.
Firebase (Authentication and Firestore Database): To enable the workout sharing feature, the app uses Firebase Authentication with anonymous sessions and Firebase Firestore Database.
The processing of information for the workout sharing feature is based on Contractual Necessity (Article 6(1)(b) of the GDPR), to the extent that it is necessary to provide the workout sharing service requested by the user.
Firebase Authentication creates a temporary technical identifier (UID). This identifier does not contain direct identifying information (such as name or email) and is used solely and strictly to make the requested workout sharing functionality possible. The UID is automatically deleted from the backend systems after 30 days.
Firestore Database stores the content of the workout you share (for example, “do push-ups for 30 seconds”), along with the date it was shared and the date it was last accessed. These records are not intended to directly identify users, but technical identifiers and other information may qualify as personal data under applicable data protection laws. Workout records are automatically deleted 10 days after their last access through an automated process implemented in the app’s backend.
Health Data (Wear OS)
Heart rate data is considered health data under applicable data protection laws. If the user explicitly grants permission, the app accesses heart rate data during workout sessions.
Additionally, the app may estimate burned calories based on workout activity and heart rate data. This information is calculated and stored locally on the user’s device. It is not transmitted to the developer’s servers. However, if the user grants the relevant permissions, Wit may also write the corresponding data to Google Health Connect, as described below.
Foreground Service & Background Access: To ensure your workout and heart rate tracking are not interrupted when the watch screen turns off or when you switch apps, Wit uses a Foreground Service (HEALTH) and Background Sensor access. This is strictly necessary to provide continuous monitoring and accurate timing during high-intensity training sessions.
Local Storage (Room): This data is processed and stored locally on the user’s device using a Room database to display statistics and graphs. Wit does not transmit this locally stored health data to the developer’s servers. The app does not provide cloud synchronization for this local health data, except for the optional writing of authorized data to Google Health Connect described below.
Activity Recognition permission is used to automatically detect exercise status and optimize stopwatch accuracy.
This data is not used for advertising, profiling, or third-party analytics services.
Legal basis for health data processing
The processing of health-related data, including heart rate measurements and health-related workout metrics, is based on the user’s explicit consent under Article 9(2)(a) of the GDPR, where applicable. Where consent is also relied upon as the legal basis under Article 6, Article 6(1)(a) of the GDPR applies.
Android and Health Connect permissions control the app’s technical access to the relevant data. Granting a device permission does not, by itself, replace any separate consent or information requirements applicable under data protection law.
Users can withdraw their consent and revoke the relevant permissions at any time. Withdrawal does not affect the lawfulness of processing carried out before withdrawal.
Data storage and deletion
Health metrics (including heart rate and burned calories) and workout records are stored locally on your device. Exceptions include workouts you explicitly choose to share through Firebase and data you authorize Wit to write to Google Health Connect.
Wit does not transmit health data to the developer’s servers as part of its Health Connect integration.
You can manage your data as follows:
Local Data Deletion: You can delete locally stored Wit records by clearing the app’s storage in your device settings or by uninstalling the application.
Firebase Data: Shared workout records and associated technical identifiers are deleted according to the retention periods described in the Firebase section above.
Health Connect Data: Revoking a permission prevents future writes for the corresponding data type but does not automatically delete data already written to Health Connect. You can review and delete these records through Health Connect’s data management settings. Deleting data from Health Connect does not automatically delete the corresponding records stored locally by Wit, and deleting local Wit data does not automatically delete records already stored in Health Connect.
Android Backups: The app does not manage Android’s automatic backup system, which may back up local app data depending on your device and account settings.
Google Health Connect Integration
The app provides optional integration with Google Health Connect to write workout records and associated fitness data to Health Connect.
Data Written to Health Connect:
If you grant permission, the app exclusively writes the following data:
Exercise sessions: activity type, date, start/end times, and duration.
Calories burned: active energy burned during the workout.
Heart rate: heart rate samples recorded during the session.
(The app does not read any existing data from Health Connect; its access is write-only).
Granular Permissions and Control:
Health Connect permissions are managed separately for each supported data type. You can grant or deny each permission individually. Wit only writes a particular data type to Health Connect when the corresponding permission has been granted.
If you deny a permission, Wit will not write that data type to Health Connect. The data may still be stored locally by Wit in accordance with the app’s existing functionality. Denying a permission does not restrict the app’s core workout timing functionality.
Compliance with Google Health Connect Policy (Limited Use):
The handling of data accessed via Health Connect complies with the Google Health Connect Permissions Policy, including the Limited Use requirements:
Data is never shared with third parties, data brokers, or advertising networks.
Data is never used for advertising, commercial profiling, or credit scoring.
Data is never sold.
Revoking Access:
You can change or revoke these permissions at any time via your device settings: Settings > Security & privacy > Privacy > Health Connect > App permissions.
If you have any questions or suggestions about this Privacy Policy, do not hesitate to contact us at oumuamuasoftware@pm.me.