Contents
Local workout recordsOptional Health ConnectCSV, notifications and widgetsGoogle Play purchases and SDK diagnosticsRetention and deletionSupport and public pagesStackWorks explains how Gym Note for Android handles your data.
Local workout records
Exercises, weights, reps, set types, dates, notes, routines, settings and the active rest timer are stored in the app’s private device storage. These records are not sent to the developer’s servers. No login or independent account is used. Automatic OS backup and device transfer are excluded by app configuration. Files use the OS app sandbox; the app does not add its own file encryption.
Optional Health Connect
Only after you enable Save workouts to Health Connect, review the explanation and grant exercise write permission, completed strength training start/end times, titles and record IDs for deduplication are written to Health Connect. Other apps permitted in Health Connect may access them under that service’s settings. We read no health records from other apps, and obtain no heart rate, body weight, calories, locations or routes. Fitness records are not used for advertising, medical or research purposes. All recording features work without this connection. Demo records are never written. Failures are shown and can be retried from Settings.
Revoke permission in Health Connect. Disabling the connection, editing or deleting a local workout does not change records already written to Health Connect. Manage and delete those records in Health Connect.
CSV, notifications and widgets
Import/export accesses only the documents and destinations you choose. CSV is readable plain text; cloud destinations apply their own policies. No broad storage permission is requested. Rest and active workout notifications may display workout titles, exercises, weights and reps on the lock screen. Control notification permission and lock-screen visibility in Android settings, and ongoing controls in app settings. Widgets use regular records and the verified purchase state.
Google Play purchases and SDK diagnostics
Plus purchases, restoration and status checks use Google Play Billing Library 9.1.0. Google Play handles product identifiers, purchase status and tokens. The app caches verified Plus status locally. Payment card details are not entered in this app.
The Billing SDK may send Google technical success/failure and connection diagnostics, app/SDK/Android versions and SDK-generated random billing-client session identifiers. This may occur during initialization, connection and product queries even without a purchase. The app has no separate opt-out for SDK diagnostics. The observed session ID is not evidence of an advertising ID or permanent device ID. Workout contents are never passed to Billing. No independent advertising or user-interaction analytics SDK is included. Google-managed data follows Google’s policies; we do not claim control of its retention or deletion.
Retention and deletion
Delete individual workouts from History or all workout records from Settings. Clear app storage or uninstall to remove custom exercises, routines and settings as well. Export CSV first if needed. Exported files, Health Connect records and Google Play data are managed in their respective destinations. Demo data stays in separate memory and never changes regular records or purchase entitlement.
Support and public pages
If you email support, we use your email address and the contents you choose to send to respond. You do not need to send health records or purchase tokens. This website is hosted by GitHub Pages; browser visits follow GitHub’s policies. Contact contact@stack-works.dev. Changes are reflected in the update date.