Workout is developed by Julien Sagot (“I”, “me”). I am responsible for the personal information processed to operate and support Workout. You can contact me about privacy at contact@juliensagot.fr (mailto:contact@juliensagot.fr).
This policy covers the Workout iOS app and its widgets and file previews. Services you choose to use with Workout, such as Apple Health, your backup storage provider, and your email provider, also have their own privacy policies.
Workout stores its primary workout database on your device. This includes your exercises, images you add, programs, routines, schedules, training dates, sets, repetitions, weights, and preferences. You do not need to create a Workout account. Workout does not provide an online account or cloud synchronization service for your workout library.
Some information is shared locally with Workout’s widgets and system features to display your next training, rest timers, and file previews. Depending on your device settings, workout information can appear on your Home Screen or Lock Screen.
Your device’s backup or migration services may copy app data, including to iCloud if you have enabled Apple’s backup features. That is separate from a Workout-operated synchronization service. The network services used by the app are described below, including usage diagnostics.
When you export a backup, Workout creates a file containing your workout records. Sharing a routine or program creates a file containing the selected content and its associated exercise information. You choose where these files go using the system’s sharing and file tools. Workout does not upload them to a backup server operated by me.
Anyone you give an exported file to may be able to read or import its contents. Keep backups and shared files in a location you trust. If you save them with a cloud provider or send them through another app, that service handles its copy under its own policy. Restoring a backup imports its records into Workout on your device.
Apple Health export is optional and off by default. If you enable it and grant permission, Workout saves completed trainings to Apple Health as strength-training workouts, including their start and end times, title, and a workout identifier. Workout does not request access to read your existing Health records.
You can disable future exports in Workout’s training settings or revoke permission in Apple’s settings. This does not remove workouts already saved to Health; manage those records in Apple Health. Deleting a training in Workout does not delete its Health copy. Apple controls Health storage and any Health synchronization you enable. See Apple’s Health privacy information (https://www.apple.com/legal/privacy/data/en/health-app/).
Rest-timer notifications and alarms are also controlled by device permissions. You can change those permissions in system settings.
Apple processes App Store payments. Workout uses RevenueCat to check subscription access and support purchases and restores. Subscription processing involves an app user identifier, purchase and transaction information, product and subscription status, and technical information needed to deliver the service. Subscription information comes from the app and Apple’s purchase services. I can view subscription records through RevenueCat to manage access and support purchase issues.
Workout does not receive your payment-card details. Your workout database and Apple Health records are not inputs to subscription verification.
RevenueCat processes subscription information on my behalf under its Data Processing Addendum (https://www.revenuecat.com/dpa). Apple’s handling of App Store information is explained in its App Store privacy notice (https://www.apple.com/legal/privacy/data/en/appstore/).
Workout sends usage events to TelemetryDeck to help me understand which screens and features are used and identify reliability problems. Examples include app launches, tab changes, settings actions, and database-startup failures. The subscription release also records paywall and purchase-flow events.
Events include technical context such as app and operating-system versions, device type, and an installation-related identifier processed by TelemetryDeck. Database-startup diagnostics currently include an error description; technical error text can contain runtime context. Workout does not send its complete workout database as an analytics attachment.
TelemetryDeck describes its standard identifiers as anonymized and states that it does not retain IP addresses. This does not make arbitrary diagnostic text anonymous. See TelemetryDeck’s privacy information (https://telemetrydeck.com/privacy/) and data-collection explanation (https://telemetrydeck.com/docs/guides/privacy-faq/).
Workout does not display third-party advertising or use these events to target advertisements across other companies’ apps or websites. I do not sell your personal information.
Workout downloads built-in exercise images from Apple’s public CloudKit service and caches them on your device. These requests identify the image being requested and involve the network information needed to deliver it. This image service does not synchronize your workout library. You can clear the image cache from Workout’s settings. Apple’s services are covered by Apple’s privacy policy (https://www.apple.com/legal/privacy/).
If you send feedback or request support, I receive your email address, message, and any attachments you choose to include. Workout’s feedback email pre-fills your app version, build number, and operating-system version; you can review and edit it before sending. My email service processes the correspondence to deliver and store it. Please avoid sending workout backups or sensitive information unless they are needed for your request.
Where data-protection law requires a legal basis, subscription verification and purchase support are necessary to provide the service you request. Responding to other correspondence and resolving technical problems serve my legitimate interests in supporting users and maintaining a reliable app. Optional Health export operates at your request and with your permission; where consent is the applicable legal basis, you can withdraw it without affecting earlier lawful processing. Information may also be retained where a legal obligation requires it.
Apple, RevenueCat, TelemetryDeck, and service providers involved in support or a transfer you initiate receive information for the purposes described above. Their processing may take place outside your country, including outside the European Economic Area. RevenueCat’s DPA provides Standard Contractual Clauses for covered restricted transfers. You can contact me for information about safeguards applicable to personal information processed on my behalf.
Providing purchase information is necessary to verify subscription access. Contacting support and exporting to Health or other destinations are optional. Declining those optional features does not prevent local planning and access to existing records.
You can view, edit, delete, and export your local records in Workout. These data-management functions remain available when your trial or subscription ends. You can also control Health and notification permissions and choose whether to send support messages or share files.
Depending on applicable law, you may request access, correction, deletion, restriction, or a portable copy of personal information held about you, object to processing based on legitimate interests, and withdraw consent where processing relies on it. Contact contact@juliensagot.fr (mailto:contact@juliensagot.fr). I may need enough information to verify and locate your request. I cannot retrieve your device-only workout database remotely, and anonymous statistics may not be attributable to you.
You may complain to your local data-protection authority, including the CNIL in France (https://www.cnil.fr/fr/adresser-une-plainte).
I will update this policy when Workout’s handling of information changes. The published policy will show its effective date. Significant changes will be brought to your attention through an appropriate notice in the app or the policy page before the new processing begins where required.