FitLog · Privacy Policy

FitLog Privacy Policy

Effective date: September 30, 2026 · Last updated: October 28, 2026 (analytics, crash reports and own exercises in voice capture)

This policy explains what data the FitLog app, published on Google Play by Jorge Guerrero M (Jorge Andres Guerrero Montes, GeojorgCO), processes, why, and what choices you have. FitLog is a strength-training log: you record your sets by voice or manually, review them and they are saved on your phone.

1. Data FitLog processes

• Voice recordings. When you tap record, the app records a voice note with the microphone to log your workout. It only records while recording is active on screen, never in the background.
• Workout data. Exercises, sets, reps, loads, dates and notes that you enter or confirm.
• Preferences. Preferred weight unit, default bar weight and weight per level of the stack machine.
• Routines. Named templates you create from a saved workout (exercises and sets).
• Own exercises and names. Exercises you create, names you give them and names the app learns when you correct a voice note. In versions that support this feature, a limited list of local IDs, names and aliases may be sent to the server during voice extraction to help the model recognize them.
• Exercise library. The app downloads updates of the exercise catalog (names and aliases) from the FitLog server, sending the installation identifier and the integrity token; it never sends your workouts.
• Installation identifier. A random code the app creates the first time you send a voice note. It is not linked to your identity or Google account; it is used to apply the daily note limit and count usage per phone. The server only keeps a hashed summary of it.
• Integrity check. With each note the app sends a Firebase App Check token (using Google Play Integrity) that proves the request comes from the original app installed from Google Play. Voice notes without a valid token are rejected. It contains no personal data.
• Technical metrics for each note. Date and time, app version, audio size, tokens processed by the model, response time, result (success or error type) and number of exercises and sets detected. They never include the audio, the transcript or exercise names.
• Usage analytics and diagnostics (Firebase Analytics and Crashlytics). In production releases, FitLog sends Google Firebase technical events about feature usage (for example, completing setup, recording or processing a voice note, saving a manual or voice workout, viewing the subscription screen, managing a purchase, using the timer, or creating a routine). Events use a fixed set of names and categories; they do not include exercise names, weights, transcripts, audio, notes, or other text you enter. Analytics also automatically generates basic usage data (sessions, app opens, version, device model and operating system) and subscription purchase events with the product identifier and price. From the IP address, Google derives an approximate geographic location (such as region or country); Analytics discards the raw IP address without storing it. It does not access GPS or request location permission. Crashlytics receives crash reports with technical stack traces, relevant app state, and device and operating system information. Firebase associates events and reports with pseudonymous installation identifiers, including recent-action breadcrumbs that help diagnose a crash. This can recognize an installation, but not your name or a FitLog account; the data is not used for advertising or cross-app tracking.
• Subscription. If you subscribe to voice notes, Google Play processes the payment; FitLog never receives your name, email or payment method. The server receives the Google Play purchase token from the app, asks Google for its status (trial, active, canceled, expired), renewal date and whether it is a test purchase, and stores this with the hashed identifiers of up to 3 linked phones.

FitLog does not require an account and does not collect your name, email, contacts, precise location or advertising identifiers. Analytics does derive an approximate location from the IP address, as explained above. Your workout history stays on your device; some exercise names and aliases may be sent as explained above. Firebase Analytics and Crashlytics are Google services that process usage events and diagnostics for the developer; they are not used for advertising or tracking.

2. How data is used and shared

Usage analytics is enabled by default in production and you can turn it off at any time in Settings → Usage analytics; that choice is stored on your device. When disabled, FitLog stops sending Analytics events. Crashlytics crash reports are sent in production releases, and this switch does not disable them. Firebase processes these data on the developer's behalf. FitLog does not use the data for advertising, combine it with advertising profiles, or track you across apps or websites.

To interpret a voice note, the app sends that note's audio over HTTPS to the FitLog server: a Firebase function (Google Cloud, United States region) operated by the developer. The server forwards the audio to the Google Gemini API (Google LLC), which returns a transcript and a structured workout proposal that the app shows you for review. Google processes the data under the Gemini API Additional Terms of Service, the Firebase Terms and the Google Privacy Policy.

The server does not store the audio or the transcript. So that a retried note is not processed twice, it keeps the result for 10 minutes and then deletes it. The technical metrics above are used only to control costs, usage limits and errors. Your full history, loads, notes and routines are not sent as part of that list. Own exercise names and aliases sent are included in the request to the AI provider to interpret the note. Data is not sold or used for advertising.

3. Storage and retention

• Audio: stored temporarily in the app's private storage and deleted from the phone as soon as it is interpreted or discarded. Any leftover recording is deleted automatically after 24 hours.
• Workouts, routines and preferences: stored only on your device, with no account or cloud sync, and not included in Android cloud backups. They are kept until you delete them or uninstall the app.
• On the server: a note's result is deleted after 10 minutes; per-note technical logs after 30 days; daily usage summaries per installation (hashed identifier, number of notes, tokens and errors) after 13 months. Subscription data is kept while the subscription exists and deleted on request.

4. Permissions

• Microphone (RECORD_AUDIO): requested the first time you tap record. You can deny it and keep logging manually.
• Internet: needed for voice notes, library updates and the analytics and diagnostic services described above. Manual entry, history and charts work offline.
• Notifications, foreground service, vibration and keeping the device awake: only for the rest timer you start. While it runs it shows the countdown in a notification and, when it ends, plays the phone's alarm sound and vibrates even with the screen off. The timer stores and sends no data. If you deny notifications, it keeps working inside the app.

5. Your choices and rights

• Delete a workout from its detail screen, or all of them from Settings → Delete all workouts.
• Rename or delete routines from Settings → Routines.
• Rename, merge or group exercises and forget learned names from Settings → My exercises.
• Turn off usage analytics in Settings → Usage analytics. This does not disable crash reporting in production releases.
• Discard a voice note before it is interpreted.
• Cancel the subscription in Google Play (FitLog → Settings → Subscription → Manage). See the Terms of Use.
• Revoke the microphone permission in Android settings.
• Uninstall the app, which removes all of its data from the device.

You may exercise your rights to access, update, correct and delete your data (Colombian Law 1581 of 2012 and other applicable laws) by writing to jorge.guerrero.montes@gmail.com. Your workouts are only on your phone, so most of these actions are available directly in the app; the server's technical metrics do not identify you and are deleted within the periods above.

6. Security

Communication between the app, the FitLog server and the Gemini API uses HTTPS. The Gemini access key is stored only on the server (Google Cloud Secret Manager), not in the app. Firebase App Check limits use of the server to the original app. Local data is kept in the app's private storage, which other apps cannot access.

7. Children

FitLog is not directed to children under 13 and does not knowingly collect data from children. If you believe a child has used it, please contact us.

8. Previous versions

The app previously used the Habito name and was a habit-tracking app. Updating to FitLog deletes the old habit data stored on the device.

9. Changes to this policy

Any changes will be posted here with a new update date. Significant changes will be announced on the Google Play listing or in the app.

10. Contact

Jorge Guerrero M (Jorge Andres Guerrero Montes, GeojorgCO) · Medellín, Antioquia, Colombia · jorge.guerrero.montes@gmail.com