IronMove Privacy Notice

1. Scope

This notice applies to people who use the IronMove mobile application and related services.

2. Who is responsible for your data

IronMove needs to replace the placeholders below with the real operator details before production publication.

• Legal entity name: pending confirmation
• Registered address: pending confirmation
• Primary privacy contact: currently routed through support

Until a dedicated privacy mailbox is finalized, privacy questions and rights requests can be sent to support@ironmove.fr.

3. What data IronMove uses

• Account and authentication data such as email address, sign-in identifiers, and account security records.
• Private profile data and limited public social profile data such as username, display name, and optional profile photo.
• Workout history, workout plans, workout progress, and shared workout participation data.
• Nutrition goals, meal logs, water logs, and reduced meal thumbnails.
• Friend graph data, invites, social notifications, and social activity records.
• Consent records, deletion/export workflow records, and device or security metadata needed to protect the service.

Optional features may add:

• AI meal-scan inputs and outputs.
• Health-sync data imported from supported device ecosystems.

4. Public profiles and visibility choices

IronMove separates limited social identity data from the rest of your private account data. This helps users be discoverable in social features without exposing more data than necessary.

• Searchable social identity data is limited to your public profile projection.
• Friend discovery can still work when your profile visibility is set to private.
• If you choose private visibility, your social presence is masked and shown as offline to others.

5. Why IronMove uses this data

• To create and secure your account.
• To provide workout, nutrition, hydration, social, and shared workout features.
• To store your history across sessions and devices.
• To provide optional AI meal scan when you explicitly enable it.
• To provide optional health sync when you explicitly enable it.
• To fulfill privacy-rights requests such as export, deletion, and consent withdrawal.
• To detect abuse and protect the service.

6. Legal bases

IronMove's current engineering position is that core account, workout, nutrition, hydration, and social features are processed to perform the user contract. Optional AI meal scan and health sync are treated as consent-based features in EU launch planning. Security, fraud-prevention, and some support operations may rely on legitimate interests, and certain rights-handling activities may rely on legal obligations.

This wording still requires confirmation from counsel before production publication.

7. Optional features and your choices

AI meal scan

AI meal scan is optional. Meal images and any related AI output are sent only after in-app consent. You can withdraw this consent in the app's Privacy Settings. Withdrawing consent stops future AI meal-scan requests.

Health sync

Health sync is optional. IronMove asks for in-app consent before the device-permission flow. You can withdraw consent in Privacy Settings. Device-side permissions may also need to be disabled in your system settings.

8. Who receives data

IronMove uses technical service providers to operate the service.

• Google Cloud / Firebase for authentication, database, storage, cloud functions, messaging, and abuse protection.
• OpenAI for the optional AI meal-scan feature.
• Apple and Google platform services for optional sign-in, push delivery, device attestation, and optional health integrations.

The final production notice should stay aligned with IronMove's subprocessor register and transfer documentation.

9. International transfers

Some providers used by IronMove may process data outside your country. The final production notice should explain which safeguards are relied on and how users can request more information about transfer protections.

10. How long data is kept

• Account and core profile data are kept while your account is active unless you delete them sooner where the product allows it.
• Meal thumbnails are kept while at least one of your meals still references them, or until account deletion.
• Export artifacts expire after 7 days.
• Some operational records, such as deletion or export tracking, may be retained for a limited audit period.

11. Your rights

Depending on your region, you may have rights to:

• access your data,
• export your data,
• delete your account,
• withdraw optional consents,
• ask questions about IronMove's privacy practices, and
• complain to a supervisory authority where applicable.

12. Children and age-sensitive use

IronMove still needs a final business and legal decision on age and child-directed use. The production privacy notice should align with the final eligibility wording in the terms of use.

13. Security

IronMove uses authentication and authorization controls, protects data in transit and at rest with industry-standard encryption and secure key storage, encrypts sensitive offline caches on device, and applies server-side validation for exports and shared-workout mutations.

IronMove does not rely on a proprietary encryption algorithm. The service instead uses established platform and provider protections together with access controls, signed export delivery, and ongoing abuse-prevention work such as App Check.

14. Contact

General support and privacy requests: support@ironmove.fr

Before production publication, IronMove should confirm whether a dedicated privacy alias will replace or supplement this address.