Privacy notice

Who processes your data

Data controller: not configured, registered office at not configured, VAT no. not configured. Contacts: email not configured · Certified email not configured.

If you are the client of a professional who uses Muvee, that professional is the controller of your clinical data. Muvee acts as a processor (Article 28), processes the data only on that professional's instructions and does not use it for its own purposes. To exercise your rights over that data, contact the professional or contact us and we will forward your request.

What data we process, why, and on what legal basis

Professional accounts

Name, email, role, language and sign-in credentials, so you can use the platform. Legal basis: performance of a contract (Article 6(1)(b)).

Data about clients receiving services

Medical history, allergies and intolerances, weight, skinfolds, circumferences, bioimpedance, body photographs, meal plans and workout programmes. These are health data, a special category under Article 9. Legal basis: explicit consent (Article 9(2)(a)), collected by the professional through a purpose-specific form and withdrawable at any time.

Apple Health and Health Connect

Synchronisation is optional and starts only after operating-system permission and your health-data consent. The app reads Apple HealthKit on iOS or Health Connect on Android and sends only the daily and workout summaries needed for your programme to the professional organisation you selected. We do not store raw samples, GPS routes, health-account identifiers or tokens. You can disconnect the source and withdraw consent.

Hydration and reminders

Amounts drunk, the goal and reminder times stay in the app's local storage. Reminders are local notifications scheduled by the device. On iOS, and only with your permission, the app reads and writes water amounts in HealthKit; the Muvee server does not receive the hydration log.

Push notifications and device

If you enable notifications, we keep the push token, a random installation identifier, platform, app version and technical delivery outcomes. Delivery uses Expo Push Service and then Apple APNs or Google FCM. The lock-screen payload contains only generic text and an identifier; the app downloads full content after authentication. You can withdraw permission in device settings.

Messages

Conversations between client and professional, including any attachments. They remain separated by organisation: if two practices support you, each sees only its own conversation.

Payments

Billing details, prepaid-credit transactions and issued documents. Legal basis: contract and accounting obligations (Article 6(1)(b) and (c)). Card data never passes through or is stored by us: Stripe handles it.

Newsletter

Email, optional name, language and evidence of consent (date, IP address and browser at sign-up). Legal basis: consent (Article 6(1)(a)), collected through double opt-in: subscription becomes effective only after you confirm through the message we send. We record opens and clicks to understand what is useful; you can unsubscribe with one click from any message.

How long we keep data

• Clinical data: for the duration of the relationship with the professional, then for the period the professional sets according to their professional obligations. It is deleted immediately on request.
• Account: until closure, which you can request.
• Accounting documents: ten years, as required by law. They remain after account closure, as expressly permitted by Article 17(3)(b).
• Newsletter: until consent is withdrawn. Unconfirmed subscriptions are deleted automatically.

Who else sees the data

Only suppliers needed to operate the service, acting as processors and unable to use the data for themselves: list not configured. The complete, current list is available on request.

We do not sell, disclose or exchange data with anyone for commercial purposes.

Your rights

• Access (Article 15): find out what data we hold about you.
• Rectification (Article 16): correct inaccurate data.
• Erasure (Article 17): have data erased, except where the law requires us to retain it.
• Restriction (Article 18) and objection (Article 21).
• Portability (Article 20): receive it in a format another program can read. The platform exports JSON.
• Withdrawal of consent (Article 7(3)): at any time and as easily as you gave it. Withdrawal does not affect earlier processing.

To exercise these rights, write to the privacy address that will be shown here. If you believe your data is being processed unlawfully, you may contact the competent data protection supervisory authority.

How we protect data

• Every table is protected by database-enforced access rules, not only application code: a code defect alone is not enough to expose another practice's data.
• Photographs and attachments are held in private storage and can be reached only through expiring signed links.
• Medical histories and measurements are not accessible to administrative staff, only to the practice's healthcare professionals.
• Every administrative action leaves an immutable audit trail.

No measure makes a system invulnerable. If a breach creates a high risk to your rights, we will inform you as required by Article 34.

Cookies

We use technical authentication cookies and first-party preference cookies; in the current configuration, we do not use them for profiling. Categories and patterns are described in the cookie notice.