Scope and contact
This policy describes data handling for the Android app Daymotive (練日常), package life.muscle.beach. Its English and Traditional Chinese store titles are Daymotive: Workout Log and 練日常:健身菜單與訓練紀錄.
Developer / privacy contact: Natural Intelligence Studio
Email: testfornewin1@gmail.com
Contact us about privacy, data handling or deletion guidance. Correspondence you send will be handled through our email service to respond to your request. Avoid including unnecessary workout records, photos or other sensitive information.
Data handled by the app
Fitness data comes mainly from what you enter, the workout actions and timing you initiate, and images or files you choose to import.
- Workout and fitness records
- Workout dates and time zones, start and end times, duration, exercises, sets, repetitions, training loads and units, completion or skip status, and notes. Cardio entries may include duration, distance, resistance and machine-reported calories. Training load is not a body-weight measurement.
- Plans, exercises and equipment
- Custom exercises and instructions, targets, rest periods, cycle order, equipment names, venue text and settings you enter, personal notes, and snapshots preserved when a workout begins.
- Images you select
- Exercise images and captions added through the system file picker, including images in imported packages. Images are copied into the app's storage. The current image workflow does not remove metadata that may already be embedded in the original file.
- Preferences and operational records
- Appearance, screen-on, rest alerts, workout notifications and assistant preferences; workout focus, countdown and assistant position. Record and revision identifiers, update times, deletion markers and image integrity information support storage, merging and recovery.
- Advertising-related data
- Google AdMob processes the data described in the advertising section below, separately from manually entered fitness content. The app also stores a local flag indicating whether content has been viewed, to help decide when to show an ad.
Purposes and storage
Fitness content supports workout recording, plans, rest alerts, journals, trends, and the import, export, backup and recovery actions you request.
Workout records and preferences are primarily stored in the app's local database. Images and device state are stored in its private file space. The fitness workflow does not require an app account and does not provide automatic synchronization to a developer-operated account server. Advertising data is handled separately as described below.
The app configuration disables Android Auto Backup and excludes app data from cloud backup and device transfer rules. Files that you explicitly export or back up are separate from these rules.
Local storage relies on Android app isolation and device protections. The app does not add app-level database encryption or password encryption for backup files. Use a device lock and protect your exported files.
Exports and cloud backups
You can choose a destination in the system file picker for text summaries, CSV files, plan files or full backups. A destination may be device storage, Google Drive or another installed document provider.
- Text / CSV: workout information from the range you select, for reading or analysis.
- Plan files: selected plans, exercise instructions, targets, related images and an optional cycle; these are not full workout-history backups.
- Full backups: plans, personal text and images, equipment, cycles, workout snapshots, preferences, related images and deletion markers. They exclude Google account credentials, system permissions and running rest countdowns.
The app does not automatically publish backup links. The selected provider handles account access, synchronization, folder permissions and cloud retention under its own policies. A successful write in the app does not prove that cloud synchronization is complete; verify that with the provider.
Retention and deletion
No fixed number of days is currently set for automatic deletion of local workout records. You can edit or delete workout history, or archive supported content through the app.
Deleting workout history removes its detailed content and set entries, but retains deletion markers and some index information to prevent unintended restoration during a backup merge. This includes record identifiers, revision and deletion times, workout date, title and source plan identifier. Archived content and historical snapshots may remain.
Before merging or restoring, the app creates a local recovery copy. After a new copy is verified, it normally rotates these copies to keep the latest three. They may contain content that was later edited or deleted. Removing an image reference does not mean that its file or historical copies disappear immediately.
To remove all local app data, use Android's clear-storage function or uninstall the app. This affects your current workout records; decide first whether you need a backup.
Clearing app data does not delete exported files or cloud backups. Delete those separately in your file manager, Google Drive or the relevant service. Its trash, retention and other-copy rules apply. The app has no cloud-backup deletion interface.
Advertising data held by Google is subject to Google's retention rules and controls. Local deletion or an advertising-ID reset does not guarantee erasure of records already held by Google. We cannot delete all Google-held records on your behalf or promise a fixed retention period for them. Contact correspondence is retained as needed to handle requests and applicable obligations, rather than for a specified fixed term.
Permissions and reminders
Notifications, vibration, scheduled alarms, foreground services and wake locks support user-started workouts and rest alerts. The optional assistant uses permission to display over other apps for a workout shortcut and countdown.
You can manage these preferences and authorizations in the app or Android settings. Disabling them may limit reminders or the assistant. Notifications and floating windows may reveal workout information on screen; adjust them and your lock-screen settings to suit your privacy needs.
The fitness features use a system file picker for files you select, without broad photo-library or storage access. They do not request location, camera or microphone access. AdMob uses network access and may use advertising identifiers according to its configuration and your device settings.
Google AdMob and your choices
The app integrates Google AdMob through the Google Mobile Ads Next-Gen SDK for banner, interstitial and app-open ads. Google receives and processes advertising data under its own privacy policies.
The SDK automatically collects and shares data for advertising, measurement and analytics, and fraud prevention. This includes IP addresses (which can indicate approximate location), app and ad interactions, performance and diagnostic information, and device, app or account-related identifiers. Examples include an advertising ID, app set ID and, when enabled, publisher first-party ID. Available data depends on SDK settings, device controls and privacy choices. Processing can occur without an ad click.
Consent and advertising choices
The app uses Google's User Messaging Platform (UMP) to update consent information and display applicable consent forms. SDK initialization and ad requests are controlled by the consent status reported by UMP. UMP communicates with Google to determine and present applicable privacy choices; available forms and choices depend on region and configuration.
When UMP indicates that a privacy-options entry point is required, you can reopen the form from Settings → Ad privacy options (「設定 → 廣告隱私選項」). This option is shown when applicable, not for every user at all times.
Android settings may let you reset or delete your advertising ID; availability and labels vary. Google also provides advertising controls and explanations. Non-personalized or limited ads can still involve data processing and do not mean that no data is collected.
Fitness content stays separate from ad targeting
The app does not supply workout records, personal notes or photos as custom ad-targeting inputs. Workout-session state and the local content-viewed flag help decide when to show an ad; they do not supply the contents of your fitness records for ad targeting.
Third-party services and this website
This page is hosted on GitHub Pages. GitHub may process visitor IP addresses and request information to provide and protect its hosting service. This policy page itself embeds no ads, analytics, third-party fonts or data-entry forms.
The language switch changes only this page. It does not use cookies or persistent storage; a fresh load starts in English. Following an external link takes you to a service governed by its own policies.
Policy changes
This policy may be revised when app features, service providers or data handling change. Updated versions identify their update and effective dates on this page. Where a change requires notice or consent, we will provide the applicable information and choices.
English and Traditional Chinese are provided for the same policy.