Privacy Policy
How Myo handles workout, HealthKit, purchase, diagnostics, and support data
Draft revised: September 6, 2026
Release draft: the consent and younger-user protections described here must be implemented and verified before publication. Set the effective date when this policy takes effect and remove this draft note.
Myo is a workout journal. It helps you record training, review your history, and understand your progress without prescribing your routine.
Your detailed workout journal and profile are stored on your device. Myo also uses external services for purchases, app configuration, diagnostics, and usage analytics. Some derived workout statistics are included in analytics, as explained below. Local storage does not mean that every piece of information about your use of Myo stays on your device.
We do not sell your personal data. We use analytics to improve reliability, understand app growth and usability, and evaluate marketing campaigns. We do not use analytics to establish your real-world identity. However, installation and purchase identifiers can distinguish an installation or customer over time, so we do not describe this information as anonymous.
Myo is operated by Maksim Kruk, a sole trader established in Poland. CaptureContext is the umbrella brand for his independent developer work, not a separate company or legal entity.
For privacy questions or requests, contact privacy.myo@contact.capturecontext.dev.
The operator is responsible for personal data processed on its behalf through Myo's service providers and support channels. The descriptions of local app storage below also explain information that you keep and manage on your own device.
Myo stores information you enter or create, including:
Myo uses this information to provide its journal, history, statistics, estimates, presets, and related features. It does not currently operate an account system or its own cloud-sync service for your workout database. The app's configured analytics events do not include your profile name or image, journal notes, individual rep and weight entries, or raw heart-rate samples.
If you grant HealthKit permission, Myo can read supported activity and body-measurement data from Apple Health and write supported workouts, active energy, and body measurements to it. These permissions are optional. Without them, features that depend on Apple Health will be unavailable, but you can keep a journal manually.
You can change Health permissions in Apple Health or iOS Settings. Revoking access does not automatically erase data previously written to Apple Health or imported into Myo.
We do not use your health or fitness data for advertising, marketing, or sale to third parties. This includes fitness information entered directly into Myo, as well as information obtained through HealthKit.
Myo uses Google Analytics for Firebase to understand which features people use, where flows can be improved, and how the app grows. Events can describe app activity, onboarding, paywall and purchase interactions, and workout completion or abandonment.
Workout analytics currently include the workout source and ranges for duration, exercise count, and set count. They do not transmit your complete workout journal. Firebase may also process an app-instance identifier, device and operating-system information, app version, language, and approximate location derived from an IP address. Myo does not request GPS location for this analytics purpose.
These identifiers help measure activity across sessions. They are not your profile name, and a Myo account is not required, but they may still be personal data.
We plan to offer optional measurement of differences between actual repetitions and estimated trends to improve the accuracy of estimates. That specific measurement is not part of the current analytics described above. Before introducing it, we will explain the data involved, update this policy, and obtain any necessary permissions. We will not use that fitness information for advertising.
Myo uses Firebase Crashlytics to investigate crashes and other technical failures and improve app stability. Reports can include crash traces, error categories, technical logs, device and operating-system information, app version, and installation identifiers. When usage analytics is enabled, related analytics breadcrumbs may also be available to help explain the events preceding a failure.
Crash reporting has a separate control from general usage analytics. Disabling usage analytics does not itself disable Crash Diagnostics. Diagnostic reports are not necessarily anonymous simply because they omit your name.
Firebase Remote Config supplies feature flags and operational settings. It can process an installation identifier and technical app or device information needed to return configuration values. It operates separately from the optional usage-analytics and crash-reporting controls.
Myo uses RevenueCat to manage purchases, subscriptions, entitlements, trials, and purchase restoration. RevenueCat processes an app user identifier, purchase and transaction information, subscription status, and related technical information. The app user identifier can persist across sessions even though Myo has no login account.
We use purchase and subscription information to provide paid features and understand subscription growth, conversions, and retention through business reports. Apple handles App Store payment processing. Myo does not receive your full payment card details.
Purchase information needed to provide or restore paid features is separate from optional usage analytics. Turning off Usage Analytics does not stop processing necessary to manage your purchases.
We want to understand which marketing campaigns lead people to install Myo or purchase paid features, so we can assess which campaigns are useful. We do not use workout contents, body measurements, or HealthKit data for this purpose.
When you authorize Apple's App Tracking Transparency permission, the current app can submit Apple's advertising and vendor identifiers, an IP address, device information, and a Facebook SDK anonymous identifier to RevenueCat for attribution. Despite its name, that Facebook identifier should not be treated as proof that the information is anonymous.
RevenueCat integrations that forward attribution information to advertising partners are not currently configured. If we enable an advertising-partner integration, we will update this notice to identify the recipient, information shared, and purpose, and obtain any required consent before that processing begins. Measuring campaigns by linking app activity with an advertising partner's data may constitute tracking even when we do not learn your name.
You can manage Apple's tracking permission through Support App Growth in Myo's privacy settings and through iOS Settings. Declining it does not prevent you from using the workout journal or purchasing paid features.
If you contact us, we use Resend to receive and send support emails. We process the email address, message, attachments, and technical details you choose to send. Myo's feedback composer may include its version and build number. We use this information to respond, investigate problems, and improve the app. Providing it is optional, although we may need relevant details to resolve your request. Please avoid sending health information that is unnecessary for support.
Exports can contain workout history, exercises, presets, body measurements, and other selected app data. You choose where to save or share them. A storage, email, or other service you select may receive the exported information under its own terms. Importing a file does not by itself upload it to a Myo-operated server.
Myo does not currently provide its own cloud backup service. Copies you export or include in device backups are separate from the app's active local database. Deleting the app does not delete copies you have saved elsewhere.
Under the GDPR, a purpose for using data and the legal basis for doing so are separate matters.
| Processing | Legal basis |
|---|---|
| Providing and restoring purchased features | Performance of the contract for those features, to the extent the processing is necessary |
| Responding to support requests | Performance of a contract where necessary to provide support for the service; otherwise our legitimate interest in responding to enquiries and resolving problems |
| Meeting applicable legal obligations | Compliance with the relevant legal obligation, where one applies |
| Optional usage analytics and advertising attribution | Your consent |
| Optional crash diagnostics | Your separate consent |
| Operational configuration | Our legitimate interest in providing a working, reliable app, using the technical data necessary for that purpose |
| Subscription business reports derived from purchase records | Our legitimate interest in understanding revenue, subscription growth, and the sustainability of the app, using data limited to those purposes |
Optional analytics and diagnostics are separate from information necessary to provide purchases or operational configuration. We ask for consent before starting consent-based collection. Any additional device-access consent required by applicable law is also obtained before that access. Consent to analytics does not authorize us to use health or fitness information for advertising.
Our current telemetry does not send your raw HealthKit records or detailed body measurements. Before introducing optional collection of health data for estimate calibration, we will explain that processing and obtain explicit consent where required. This is separate from granting the app access to Apple Health on your device.
In Myo, open Settings → Privacy to manage:
These are separate controls. Disabling one does not necessarily disable another service. Disabling Crash Diagnostics also requests deletion of unsent crash reports. Changing a setting stops the relevant future collection but does not automatically erase information already uploaded.
Where processing is based on consent, you can withdraw it at any time. Withdrawal does not affect the lawfulness of processing before withdrawal. Contact us if you also want previously collected personal data deleted.
The services involved include:
Where providers process personal data on our behalf, we remain responsible for that processing and require appropriate contractual safeguards, restricted purposes, and protection consistent with this policy. Apple also processes information for its own services under its own privacy terms.
Some providers and their subprocessors operate outside the European Economic Area, including in the United States. For transfers made on our behalf, we use the applicable provider data-processing agreements and their transfer safeguards, including European Commission Standard Contractual Clauses where required or an applicable adequacy decision covering the recipient and transfer. These safeguards address protection of data outside the EEA; they do not replace a legal basis for collecting it.
Information and contractual safeguards are available in Firebase's privacy information, Firebase's data-processing terms, Google Analytics' data-processing terms, RevenueCat's data-processing addendum, and Resend's data-processing addendum. Contact us to obtain information about the safeguards relevant to your data. Apple's independent processing is explained in Apple's privacy policy.
Deleting Myo does not automatically cancel a subscription or delete records held by service providers. Manage subscriptions through your Apple account and contact us for requests concerning personal data processed on our behalf. We may need to retain limited information where a legal obligation or another applicable lawful exception requires it; we will explain any relevant limitation when responding.
Depending on the processing and applicable law, you can request access, correction, deletion, restriction, or a portable copy of your personal data. You can object to processing based on legitimate interests and withdraw consent where consent is the basis.
Contact privacy.myo@contact.capturecontext.dev. We may need limited information to locate the relevant records and verify that the request relates to you. Because Myo has no login account, we may need an available app or purchase identifier. We do not require you to send your workout journal merely to make a privacy request. If we cannot identify the relevant records, we will explain that limitation.
We normally respond within one month. If a permitted extension is necessary, we will explain why within that first month. You can complain to the President of Poland's Personal Data Protection Office, UODO, or another competent data-protection authority.
Myo is intended for users aged 13 and older. Its App Store age rating concerns content suitability and does not determine whether a younger user can independently consent to personal-data processing.
We ask for an age bracket during onboarding to determine eligibility for optional data collection. We do not need your exact date of birth for that decision. The age decision is kept on your device and is not sent as an analytics event.
For users under 16, optional usage analytics and attribution remain disabled. Crash reporting is considered separately and is enabled only where the required consent can validly be given, including parental authorization where necessary. Without that authorization, optional crash reporting remains disabled too. This does not prevent younger users from keeping a local workout journal.
We will update this policy when our data practices change and identify the effective date. For material changes, we will provide an appropriate notice before the new processing begins and obtain new consent where required. A policy update does not by itself authorize a new use of your data.