Privacy policy
Effective 2026-11-11. OpenLog is operated by OpenLog LLC. Contact: phil@openlog.gg.
Your workouts
An OpenLog account is required to enter the Android app. After signing in, workout logging remains available offline while you stay signed in. Routines, schedules, exercise tags, body weight, body-fat inputs and goals, diet projections and dated calorie-deficit changes, sets, effort, notes, cardio records, history and preferences are stored on your device. We do not sell training records or use them for advertising. This release includes no advertising, marketing analytics or third-party crash-reporting SDK.
Weight and body measurements, progress photos and reminders
When you sign in, your dated weight entries, body measurements, diet plan and dated deficit adjustments sync privately across your devices. Measurement units, app preferences, favorite exercises, and meal and body-logging reminder schedules also sync. You can attach photos from your gallery or device camera. Temporary camera captures are removed when canceled or after they are imported into private photo storage. Progress photos and their local file paths stay on the device. OpenLog excludes them from private sync, cloud backups and shared routine links. You can export copies to a folder you select, labeled with date and weight; that folder may be managed by another storage provider you choose. Deleting a weigh-in on the device where you attached its photos also removes those OpenLog photo copies there. Uninstalling the app removes its private photos, so export photos you want to keep. Each device schedules notifications locally using its Android notification and alarm permissions.
Private routine library and workout history
When you sign in, OpenLog automatically syncs your routine library and completed workout history across your devices through Google Firebase Cloud Firestore. This includes routines, folders, schedules, planned weights and reps, custom exercises, tags and saved exercise or routine notes. Completed sessions include their dates, names, durations, exercises, recorded sets, weights, reps, effort, cardio, tags and session-specific notes. Body weight recorded for a bodyweight exercise is part of that session. Only your signed-in account and authorized service operations can access these records. Completed sessions sync into history. Recovery copies may also include unfinished workouts. Offline changes sync when connected. Progress photos stay local. Creating a public sharing link is a separate action.
Accounts and automatic cloud backups
Firebase Authentication processes your email address and account identifier, plus your Google account identity and name when you use Google sign-in. Google handles Google sign-in; OpenLog does not receive your Google password. If you choose email/password sign-in, the app sends your password securely to Firebase Authentication; it is not stored in workout backups or local app preferences. Firebase handles password authentication, verification emails and password-reset emails. The app records the accepted terms version, a document hash, acceptance time, app version, account identifier and acceptance method locally on the device; this record is excluded from cloud backups and private sync. Signing in enables automatic recovery copies of saved app data in Google Firebase Cloud Storage, along with a device label and backup timestamps. A new installation can use an earlier account backup to recover missing data automatically. Backups are accessible to your signed-in account and authorized service operations; they are encrypted in transit and by the storage provider at rest, but are not end-to-end encrypted.
Optional lock-screen workouts
Lock-screen workout access is off by default. If enabled, anyone holding the device can open the active workout from its notification and view or change its sets, previous performance and notes, use timers, or finish the session without unlocking. Other app screens require unlocking. The choice is stored only on this device and is not restored from cloud backups. You can turn it off in Workout preferences.
Optional Health Connect
Health Connect export is off by default and works locally on this Android device without an internet connection after signing in to OpenLog. If you enable it and grant exercise-write permission, OpenLog writes completed workout summaries: workout name, activity type, start and end times, and duration. Existing history is exported only when you choose Export existing workouts. OpenLog does not read other apps’ Health Connect records or export exercise notes, individual sets, body measurements, heart rate or estimated calories through this integration. Other apps can access these summaries only under the permissions you manage in Health Connect. Corrections and deletions of exported workouts update their Health Connect copies while connected. Turning export off stops future writes and leaves existing copies in Health Connect; you can revoke access or delete those copies in Health Connect settings. Cloud account deletion does not remove these device-managed copies. Permission choices and export bookkeeping stay on this device and are not included in OpenLog cloud backups. Health Connect data is not used for advertising or sold. OpenLog’s use of Health Connect complies with the Health Connect Permissions policy, including its Limited Use requirements.
Workout sharing
Creating a sharing link sends the routine or folder title, exercise names and planned settings, including optional per-set weight, rep, effort and time targets, to Firebase. Anyone with the link can view and copy that snapshot. Logged workouts, recorded weights, private notes, equipment tags and schedules are excluded. Disabling a link stops future retrieval through OpenLog; it cannot erase copies others already saved. Blocking a sender is stored on this device.
Optional ChatGPT connection
If you connect OpenLog to ChatGPT, you explicitly authorize the permissions shown on the connection page. Depending on those permissions, ChatGPT can retrieve your synced routines, exercise library, completed workouts and notes, weight and body measurements, and diet plan; it can also create or correct routines, completed workouts, weight entries and measurements. These requests send the selected records to OpenAI, which processes them under your ChatGPT account settings and its own privacy policy. Progress photos and Health Connect records are not exposed by this connection. Review proposed changes before approving them in ChatGPT. Disconnect at Manage ChatGPT connections to stop future access; disconnecting does not erase data already received by OpenAI or undo saved edits. We store permission grants, hashed credentials, bounded request identifiers and usage counters to secure the connection and prevent duplicate edits. Connection grants expire after 30 days unless reauthorized. Account deletion removes these records.
The connection website uses a short-lived encrypted, secure browser cookie for sign-in authorization and Firebase App Check with Google reCAPTCHA Enterprise for abuse prevention. Google processes browser, network and interaction signals for these security checks; workout contents are not sent to reCAPTCHA. Firebase handles the account sign-in. OpenLog does not send your password to ChatGPT.
Who receives data
Google Firebase and Google Cloud, and their service providers, process account information, synced records, backups and service metadata to provide authentication, hosting, storage, synchronization and security. Authorized OpenLog personnel access information only as needed to operate the service, respond to support requests or investigate abuse. People with a sharing link receive the routine information described above. When you export history, weight or body measurements, or photos to another app or storage location, the destination you choose receives that export and handles it under its own privacy practices. Apps you authorize in Health Connect can receive the workout summaries described above. Support emails are processed by our email service provider, Google Workspace.
Changes in business ownership
If OpenLog undergoes a merger, acquisition or transfer of its business, personal data may transfer as necessary to continue the service, subject to applicable law and the privacy commitments made when it was collected. A successor must honor those commitments. We will provide required notices and obtain consent where required before materially different uses. This does not authorize a separate sale of your health or fitness information.
App security checks
OpenLog uses Firebase App Check with Google Play Integrity to help detect unauthorized clients and protect cloud services from abuse. Google processes app and device integrity signals and returns integrity tokens for these checks. Firebase SDKs also send technical information such as device model, operating-system version, installation source and SDK versions to provide, maintain and improve their services. These checks do not send your workout contents or progress photos to Play Integrity. Security checks may run when the app connects to Google services, including before sign-in.
Service and support data
Google infrastructure may process IP addresses, request metadata, authentication activity and security logs to operate and protect the service. In-app and web sharing reports send the reported link, a reason and any details you enter to our private review queue, without requiring sign-in. We keep short-lived hashed network-address counters for up to two days to limit report spam. If you email support, we receive your email address and the information you choose to send. Do not include passwords or unnecessary personal training data. We do not automatically attach workout history to support messages. We use support reports only to respond, fix problems and address abuse. Service providers process data where their infrastructure operates, which may be outside your country.
Retention and deletion
Local data remains until you remove it or uninstall the app. Private sync applies edits and removals to your routines, workout history, body measurements, weight logs, diet plans, reminder schedules and preferences. Deleted sync records can retain an identifier and a deletion marker so an offline device will not reintroduce an old entry. Deleting your OpenLog account removes its synced data and deletion markers. Cloud backup retention keeps the three newest copies; temporary additional copies may exist while cleanup completes. Shared links remain until disabled or the account is deleted. Request account deletion in Settings → Account & cloud, or through this page. Account data and cloud backups are removed, usually within 24 hours after an authenticated request; manual requests require identity verification and are handled within 30 days. Local workouts remain unless you erase them; the Android app requires sign-in to access them. Deleting an account does not transfer its local data to a different account. A minimal account identifier and deletion timestamps are retained for up to 30 days to prevent interrupted uploads recreating deleted data. Provider logs and storage recovery copies may remain for their configured retention periods; they are not available through the app. Support and abuse correspondence is retained only as needed to resolve the request, normally no longer than 90 days after resolution unless a legal or security obligation requires longer retention.
Your choices
After signing in, you can log offline while you remain signed in. Signing out stops syncing and automatic backups on this device and returns you to sign-in. You can export training history and local progress photos, disable shared links, or request account deletion. Notification permission is optional and used for workout timer alerts and active-workout controls. OpenLog does not request GPS, contacts or microphone access in this release.
Audience and changes
OpenLog is intended for adults and is not directed at children. Contact us if you believe a child has submitted personal information. We will update this page when data practices change and provide additional notice when required.