# Mouve — full legal and policy documents

The complete text of every public Mouve legal and information document, in Markdown.
Index: https://mouve.it/legal/index.json · Discovery: https://mouve.it/llms.txt
Each document is preceded by its key, version and effective date.

---

<!-- document: privacy-policy | version: 2.19 | effective: 2026-10-25 -->
Document: privacy-policy
Version: 2.19
Effective: 2026-10-25
Canonical: https://mouve.it/privacy-policy
Markdown: https://mouve.it/privacy-policy.md

# Privacy Policy

Version 2.19 | Last updated: October 25, 2026 | Effective: October 25, 2026

**California residents:** Mouve does not sell your personal information. Only if you opt in to Advertising measurement (Section 3.9) do we share limited data with advertising platforms, which California law may treat as “sharing” for cross-context behavioral advertising; you can opt out at any time in Cookie settings. For your full California privacy rights under CCPA/CPRA, including the right to know, access, delete, correct, and limit use of sensitive personal information, see [Section 15](#california-rights). To exercise your rights, contact [privacy@mouve.it](mailto:privacy@mouve.it).

<a id="introduction"></a>

## 1. Introduction

Welcome to Mouve (“we,” “our,” or “us”). Mouve is a social fitness network that helps you track workouts, log nutrition, and connect with a fitness community. We are committed to protecting your privacy and processing your personal data in accordance with the General Data Protection Regulation (GDPR), the ePrivacy Directive, and, where applicable, the EU AI Act, the Digital Services Act (DSA), and other relevant European data protection laws.

This Privacy Policy explains how we collect, use, share, and protect your personal data when you use our website at mouve.it and our progressive web application (collectively, the “Service”).

By using Mouve, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with our practices, please do not use our Service.

<a id="data-controller"></a>

## 2. Data Controller

The data controller responsible for your personal data is:

**Mouve Technology OÜ**
Registered Address: Sõpruse pst 8-31, Kristiine linnaosa, 10615 Tallinn, Harju maakond
Country: Estonia
Email: privacy@mouve.it

For any questions regarding this Privacy Policy or your personal data, please contact us at the email address above.

Your account is internally identified using a unique user ID generated during account creation. This ID is not derived from personal information and is used solely for internal data association.

<a id="categories"></a>

## 3. Categories of Personal Data We Collect

We collect various categories of personal data depending on how you interact with Mouve:

### 3.1 Account Information

- **Email address** (required for account creation)
- **Authentication data** from Google or Apple if you choose to sign in with these providers
- **Username** (unique identifier you choose)

### 3.2 Profile Information (Voluntarily Provided)

- First name and last name
- Profile picture and cover image
- Bio (up to 500 characters)
- Location
- Website URL

### 3.3 Health and Fitness Data

This data is considered **special category data** under GDPR Article 9. We process this data based on your explicit consent:

- Date of birth, sex/gender, height, and weight (if provided)
- Workout data: exercises, sets, repetitions, weights, duration, calories burned
- Nutrition data: meals logged, calories, macronutrients (protein, carbohydrates, fats), fiber, sugar, sodium
- Workout history and fitness statistics

### 3.4 Social and Interaction Data

- Users you follow and users who follow you
- Likes, comments, and shares on workouts and posts
- Meals and days you choose to share from your food diary (food names, portions, nutrient values and totals, a title, an optional caption and an optional photo), who you shared them with, and the likes, comments and saves they receive (see Section 4.4)
- Direct messages with other users
- Community memberships

### 3.5 Media Content

- Workout videos you upload
- Food images for nutrition analysis
- The photo you attach to a meal you share, if you add one
- Profile and cover images

### 3.6 Payment Information

If you subscribe to premium features, payment processing is handled entirely by Stripe. We do not store your credit card numbers or bank details. We only receive and store:

- Stripe customer ID (to link your subscription)
- Subscription status and tier
- Subscription period dates

### 3.7 Technical Data

- IP address
- Browser type and version
- Device information
- Push notification tokens (if you enable notifications)
- Cookies and similar technologies (see Section 12)

### 3.8 Usage Analytics and Session Replay

We measure how the Service is used with PostHog, an analytics tool that we run on our own servers in the EU. Nothing described in this section is sent to PostHog Inc. or to any other third party. Apart from the tap count described below, nothing runs in your browser, and nothing is stored on your device, for analytics until you choose “Accept all” or switch Analytics on in the cookie banner or in Cookie settings.

- **Counting visits to our public pages, before you decide anything:** when you open any of our public pages (home, pricing, blog, comparisons, guides, exercises, help, legal pages, sign-up and log-in) our *server* records one anonymous count of the visit — which page, the campaign tags in the link (the `utm_` parameters, and only whether an advertising click identifier was present, never its value), a referral code if the link has one, the website you came from (its domain only), your country as reported by our network provider, the kind of device (phone, tablet or computer) and the browser family. There is no cookie and no script in your browser, and nothing is stored on your device. To estimate how many different people visit in a day, the count carries a one-way code computed on our server from your IP address, browser details and the site, mixed with a random secret that is generated fresh every 24 hours, is shared between our servers through a short-lived cache entry that is deleted after 48 hours, and is never stored together with your IP address, browser details or the code: the code cannot be reversed, cannot be recomputed once the secret has been deleted and cannot be linked to you, to another day or to an account. Your IP address and browser details are not sent to our analytics system or stored. Visits by search-engine, AI and social-media crawlers are counted separately by crawler name and never as people; other automated visits are not counted. This is the only way we can tell how many people reach the service from a link or an ad, including those who decline everything. Legal basis: legitimate interest (Art. 6(1)(f)).
- **Counting taps on the App Store and Google Play buttons:** when you tap one of those two buttons on any of our pages, the link goes through our own server first, which records the tap and then sends you on to the store. The record holds the store, the page the button was on, the campaign tags in the link (the `src` or `utm_` parameters), the time, the kind of device, your country and the same one-way daily code described above. There is no cookie, nothing is read from or stored on your device, and your IP address and browser details are not stored, so the record cannot be linked to you. The campaign tag is also passed to the App Store or Google Play so the store can report which campaign an install came from. Taps are kept for 13 months. Legal basis: legitimate interest (Art. 6(1)(f)). It is the only way we can tell how many people who arrive from an ad go on to the store, including those who decline everything.
- **Product events when you are signed in:** our servers record a small set of events about what happens in your account (for example that a workout was completed, not what it contained), keyed by your internal user ID only — never by name or email. Legal basis: legitimate interest (Art. 6(1)(f)). You can object at any time: refuse Analytics in Cookie settings or Settings → Privacy and we stop recording these events for your account.
- **In your browser, only after you accept Analytics:** we store an analytics identifier on your device so that returning visits can be recognised, we record which buttons, links and form fields are used (the kind of element only — never the text on it or what you type), and we may record a **session replay** — a reconstruction of how you moved through the web app (layout, scrolling, taps and clicks, the pages you visited). Replays are masked before they leave your browser: all text you see or type is replaced with asterisks; every image, video, camera frame and chart is replaced with an empty box; and your messages, body measurements and the food scanner are excluded entirely. A replay therefore shows the shape of what you did, not the content — not your weight, not your meals, not your messages. Console output, network requests and their contents are not recorded.

The legal basis for the part that runs in your browser is your consent (Art. 6(1)(a)), and for the storage on your device ePrivacy Art. 5(3). You can withdraw it at any time; withdrawal stops recording immediately and resets the analytics identifier. Session replays are deleted 30 days after they were recorded. See Section 12 for the storage involved and Section 13 for retention.

### 3.9 Advertising Measurement

If, and only if, you choose “Accept all” or switch on** Advertising measurement** in the cookie banner, Cookie settings or Settings → Privacy, we measure our ads with three platforms: **Meta Platforms Ireland Limited** (Facebook, Instagram), **TikTok Technology Limited** (Ireland) and **Google Ireland Limited** (Google Ads). It has two parts.

- **Pixels on our public pages.** On the home, Mouve+ plans, sign-up, log-in and invitation pages, and only while you are signed out, the platforms' scripts run in your browser and set their cookies. They learn that your browser opened that page. Because the script is loaded from the platform, it receives the details every web request carries (your IP address, browser and device type, the page address) and the platform's own cookies. These scripts never run on the screens you use once signed in, or on any page that shows food, nutrition, body, workout or profile content; leaving a public page for one of those reloads the page so that no platform script stays active.
- **Sign-up and subscription.** When you create an account or take out a subscription *on the web*, our servers tell the platforms that this happened, together with a scrambled (hashed) form of your email address, the advertising click identifier and the platform cookie values we hold from your visit, and the time. Purchases made inside the iOS or Android apps are never sent.

**What the platforms never receive:** anything about your food, meals, scans, body measurements, workouts, goals, date of birth, messages or search queries, and the address of any page inside the app. We check every message against a list of forbidden content before it leaves our systems.

- **Legal basis:** your consent (Art. 6(1)(a)) and ePrivacy Art. 5(3) for the cookies and scripts. Because the fact that someone uses a fitness and nutrition app could be read as information about their health, we ask for your explicit consent (Art. 9(2)(a)) to the extent that applies. Declining costs you nothing: Mouve works the same.
- **Who is responsible:** for collecting your data through the pixels and passing it to the platform, Mouve and the platform are joint controllers (CJEU C-40/17 *Fashion ID*). After that, each platform is an independent controller for its own purposes and under its own privacy policy: they may use the data to measure and improve advertising and to show ads to you and others. Mouve decides nothing about that use.
- **Withdrawing:** at any time, in Cookie settings (link at the bottom of our pages) or Settings → Privacy. From then on we load no pixel, we delete the platform cookies from your browser, we stop sending sign-up and subscription events, and we keep no new click identifiers; those already stored are deleted after 90 days at the latest. What a platform already received is governed by its own policy — you can ask it to delete it.

<a id="health-data"></a>

## 4. Health Data Consent

Special Category Data - GDPR Article 9(2)(a)

Certain data you provide to Mouve constitutes health data under GDPR, which requires your explicit consent before we can process it.

### 4.1 What Constitutes Health Data on Mouve

The following data is classified as health-related special category data:

- Workout logs (exercises, sets, reps, weights, duration, calories burned)
- Nutrition logs (meals, calories, macronutrients)
- Body measurements (height, weight, body composition)
- Fitness statistics and progress data
- AI-generated nutritional analysis of your food, once you save it to your nutrition log
- AI-generated meal plans based on your dietary preferences, once you save them to your account

**How AI features relate to this consent.** The AI features themselves — food image analysis, food log text parsing, meal planning, workout generation, and progress insights — run only when you actively start them: when you submit a photo, type a food description, or press generate. They are not placed behind a separate consent step, and we do not ask you to agree to AI processing before your first request. Instead, every AI result carries an in-app notice that AI results are estimates and can be inaccurate, and that you should check the numbers before logging them. What you then choose to save to your nutrition or workout log is health data and is covered by the consent described in this section. Section 8.3 describes exactly what is sent for each AI feature and which AI provider receives it.

### 4.2 How Consent Is Collected

Your consent for health data processing is collected separately from your acceptance of these Terms of Service. When you first use a health-related feature (such as logging a workout or tracking nutrition), you will be presented with a specific consent prompt explaining what data will be processed and why. This consent is:

- **Freely given** - you can use Mouve's social features without consenting to health data processing
- **Specific** - consent covers clearly described processing purposes
- **Informed** - you are told exactly what data is processed and how
- **Unambiguous** - requires a clear affirmative action (opt-in checkbox)

**Sharing health data with an app or AI agent you connect.** Separately from the consent above, if you authorize a third-party application or AI agent to access your account (see Section 8.8) and the requested access includes workout, nutrition, or body data, the authorization screen lists that access explicitly and asks for your explicit consent before any of it is shared. We keep a record of which apps you authorized, when, and with which permissions, and you can see and end these connections at any time in Settings → Connected apps.

### 4.3 Withdrawing Consent

You may withdraw your consent for health data processing at any time through your account settings. Withdrawal of consent:

- Does not affect the lawfulness of processing carried out before withdrawal
- Will disable health-related features (workout tracking, nutrition logging, body measurements, progress photos)
- Does not by itself stop AI features. AI food analysis, food log text parsing, meal planning, workout generation, and progress insights run only when you start them and are not gated on a separate AI consent. If you do not want data sent for AI processing, do not use those features — see Section 8.3.
- Your existing health data will be preserved but no longer actively processed - you may request its deletion separately
- Social features (posting, following, messaging) remain fully available

**Withdrawing consent from a connected app.** For third-party applications and AI agents, withdrawing your consent means disconnecting the app: open Settings → Connected apps and remove it. Disconnecting revokes the app's credentials so it can no longer obtain access to your account; any short-lived token it already holds expires within one hour at most. Withdrawal does not affect the lawfulness of sharing that happened before it, and data the app already received is handled by that app under its own privacy policy (see Section 8.8).

### 4.4 Sharing Meals With Other Users

On the web app you can share a meal, or a whole day of meals, from your own food diary. What you eat can reveal information about your health, so sharing is a separate choice from logging food. Before your first share we ask for your explicit consent to make that health data visible to other users (GDPR Art. 9(2)(a), with Art. 6(1)(a) alongside). The consent you give when you scan or log food does not cover sharing, and you can keep using every other feature without giving it.

- **You decide each time.** You pick the entries to share, a title, an optional caption and an optional photo. Nothing is shared automatically and nothing is public by default.
- **What is shared.** A copy taken at the moment you share: the food names, portions, nutrient values per 100 g and totals for the entries you picked, plus the title, caption and photo. Nothing else in your diary becomes visible. If you later edit or delete the diary entries, the share does not change, and the share never reveals the entries themselves. Foods you created yourself are copied by value, so their private records are not exposed.
- **Who can see it.** You choose the audience for each share. *Followers* means only people whose follow you approved, and is what the share dialog proposes. *Everyone* means the share is not limited to your followers: it may be shown to any Mouve user, for example in Discovery, and may be visible to people who are not signed in where Mouve shows public posts. Keeping a meal to yourself is not sharing, so there is no “only me” option. People you blocked, and people who blocked you, never see your shares, and our moderation and reporting tools apply.
- **What other people can do.** Anyone who can see a share can like it, comment, save the post, and use “Log this” to copy its foods and portions into their own diary. That copy is their own diary entry. It is theirs, they process it under their own consent like any food they log, and it keeps no link to you. You only see how many times a share was logged, never who did it.
- **What we cannot undo.** Anyone who can see a share can also copy it outside Mouve, for example with a screenshot. Once that has happened we cannot take it back, so choose Everyone only for meals you are comfortable having seen by anyone.
- **Stopping.** You can delete a share at any time: the copy is then deleted for everyone and the post that carried it disappears, so its comments and likes are no longer shown. You can withdraw the sharing consent in your account settings at any time: that deletes every meal you shared and removes the posts that carried them. Copies other people already logged into their own diaries are not affected. Withdrawal does not affect the lawfulness of sharing before it. Deleting your account deletes your shares as well.

### 4.5 Steps, Apple Health and Health Connect

In the mobile app you can connect Apple Health (iPhone) or Health Connect (Android). This is optional and covered by the health data consent above. Once connected, the app reads your daily steps, active energy, distance, heart rate, sleep, weight and workouts on your phone and sends daily totals and workout summaries to Mouve, so you can see them in the app. Mouve never sells this data.

- **Counting steps with your phone.** To keep your step count accurate, Mouve reads your phone's motion sensors: the step counter on Android (this needs the “Physical activity” permission, which you can decline or switch off at any time) and the motion coprocessor on iPhone (“Motion & Fitness”). The sensor readings and the hourly step counts built from them stay on your phone, for at most 14 days; only the resulting daily step total is sent to Mouve. This works without connecting Apple Health or Health Connect: we ask for the permission when you first open a screen that shows steps, and if you have not connected either, Mouve uploads its own daily step totals as a separate source (never in addition to a connected one). On Android, Google Play services can also keep a short step history on your phone for apps that ask for it; Mouve reads it on the phone and it is not sent to Google by Mouve.
- **One count per day.** If your watch or another health app already records your steps in Apple Health or Health Connect, Mouve uses that count, and its own sensor count only when nothing else has your steps for that day. The two are never added together.

<a id="how-collect"></a>

## 5. How We Collect Your Data

- **Directly from you:** When you create an account, fill in your profile, log workouts, track nutrition, upload media, or communicate with other users.
- **From third-party sign-in providers:** If you authenticate using Google or Apple, we receive basic profile information from these services.
- **Automatically:** Technical data is collected automatically when you access our Service.
- **From food databases:** When you scan barcodes, we retrieve nutritional information from Open Food Facts, an open food products database.
- **From AI analysis:** When you use our food image scanning feature, an AI model analyzes your food photo to estimate its nutritional content. Section 8.3 lists the AI providers involved.

<a id="legal-basis"></a>

## 6. Legal Basis for Processing

Under GDPR, we process your personal data based on the following legal grounds:

| Purpose | Legal Basis (GDPR Articles 6 and 9, where applicable) | Retention Period |
| --- | --- | --- |
| Creating and managing your account | Contract performance (Art. 6(1)(b)) | Until account deletion |
| Product emails: updates about Mouve, and one short question asking why you stopped using the app and what we should improve. Sent to adults only, never to accounts under 18 or without a date of birth. | Legitimate interest (Art. 6(1)(f)) in telling our own customers about our own similar service, as permitted by Art. 13(2) of the ePrivacy Directive and section 103¹ of the Estonian Electronic Communications Act. We use the email address you gave when you signed up. The sign-up screen tells you this and lets you opt out right there; every email has a one-click unsubscribe link, and you can switch it off at any time in Settings. If you switch it on yourself in Settings, the basis is your consent (Art. 6(1)(a)). Once you unsubscribe we never turn it back on. | Until you unsubscribe or delete your account. We keep the record that you unsubscribed only until account deletion. |
| Processing related to optional health and fitness features (workout tracking, nutrition logging, body measurements, progress data) | Contract performance (Art. 6(1)(b)) where requested by the user, together with explicit consent for special category data (Art. 9(2)(a)) | Until consent withdrawal or account deletion |
| AI features you actively start (food image analysis, food log text parsing, meal planning, workout generation, progress insights) | Processing carried out to deliver a feature you actively request — we process only when you submit a photo, type a food description, or press generate. No separate consent is collected for AI processing; you are informed in the app that AI results are estimates and can be inaccurate. | Request data you do not save: a food scanner photo you have not logged stays in your History as “Not logged” for 30 days (you can log or delete it there), then it and its crops are deleted; other scanner photos and descriptions you do not save are deleted within 24 hours; other AI requests are not stored. The AI provider that handled the request keeps it only for the abuse-monitoring period set by its terms, then deletes it; the period for each provider is listed in Section 8.3. Saved results: until you delete them or your account |
| Social features (following, likes, comments, messaging) | Contract performance (Art. 6(1)(b)) | Until account deletion or content deletion |
| Sharing a meal with other users (Section 4.4) | Explicit consent for special category data (Art. 9(2)(a)) together with consent (Art. 6(1)(a)) | Until you delete the share, withdraw your consent or delete your account |
| Content moderation | Legal obligation (Art. 6(1)(c)) - Digital Services Act | Moderation records retained for 6 months after action |
| Processing payment subscriptions | Contract performance (Art. 6(1)(b)) | 7 years (tax/legal obligations) |
| Push notifications | Consent (Art. 6(1)(a)) | Until consent withdrawal or account deletion |
| Authentication cookies | Strictly necessary - ePrivacy Art. 5(3) exemption | Up to 7 days (refreshed while active) |
| Improving our Service | Legitimate interest (Art. 6(1)(f)) | Aggregated/anonymized - indefinite |
| Usage analytics with a stored identifier, and session replay (Section 3.8) | Consent (Art. 6(1)(a)); ePrivacy Art. 5(3) for the storage on your device | Replays: 30 days. Identifier: until you withdraw consent or delete your account |
| Advertising measurement: pixels and sign-up / subscription events sent to Meta, TikTok and Google (Section 3.9) | Consent (Art. 6(1)(a)) and explicit consent (Art. 9(2)(a)) to the extent the fact of using Mouve could reveal health information; ePrivacy Art. 5(3) for the scripts and cookies | Click identifiers and ad cookies we keep: 90 days. Send log: 13 months |
| Complying with legal obligations | Legal obligation (Art. 6(1)(c)) | As required by applicable law |

<a id="how-use"></a>

## 7. How We Use Your Data

We use your personal data to:

- Create and maintain your Mouve account
- Enable you to track workouts, nutrition, and fitness progress
- Show locally-relevant food results — on mobile, we use your device's region setting (for example, your phone's Language & Region) to rank foods sold in your country first. This is a device setting, not GPS or IP-based location, and we do not store it.
- If you switch on “Share location with assistants”, keep your latest position for up to 24 hours so an AI assistant you connected can plan a route from where you are (Section 13)
- Analyze food images to estimate nutritional content
- Suggest ingredients for a dish you are turning into ingredients, using the dish, your market, and — unless you turn personalisation off in Settings → Privacy — your own previous food logs and scans
- Provide social features (following, likes, comments, direct messaging)
- Process premium subscription payments
- Send push notifications (when enabled)
- Email you about Mouve itself (product updates, and a short question if you stop using the app) unless you opt out — see “Product emails” in Section 6
- Display your public profile to other users
- Provide personalized content in your feed
- Respond to your support inquiries
- Ensure the security and integrity of our Service
- Understand how the Service is used so we can improve it (Section 3.8)
- Comply with legal obligations

<a id="data-sharing"></a>

## 8. Data Sharing and Third Parties

We share your data with the following categories of recipients:

### 8.1 Infrastructure and Hosting

- **Hetzner** (EU hosting): Our application, database and backend services are hosted on Hetzner servers in the EU.
- **Our own servers in the EU**: Mouve runs its own servers at our office. They hold our self-hosted product analytics (Section 3), backups of the production database and of other systems, and the training set for food recognition, which is built only from photos of users who opted in to model improvement. No processor other than ourselves is involved.
- **Cloudflare** (media storage and CDN): Your uploaded media (photos, videos) is stored securely in Cloudflare's R2 storage service with private access controls. Cloudflare's edge network also relays requests to our services and delivers media, and can handle that traffic outside the EU (Section 9).

### 8.2 Payment Processing

- **Stripe**: Handles all payment processing for premium subscriptions. Stripe is PCI-DSS compliant and GDPR compliant. See [Stripe's Privacy Policy](https://stripe.com/privacy).

### 8.3 AI Features and AI Providers

Some Mouve features use AI models. Each AI feature runs either on a model we host on our own infrastructure (Section 8.1), in which case your request does not leave our systems, or with an AI provider that processes the request on our behalf as our processor under a data processing agreement. Today every AI feature listed below uses an AI provider. The providers, and which features each one serves, are listed in the table at the end of this section.

The following commitments apply to every AI provider we use:

- **No training.** The provider may not use your requests or the results to train or improve its AI models.
- **No account identifiers.** We do not send your name, email address, username or account ID. The provider receives only the content described for each feature below; for a photo, that includes anything else visible in the image.
- **Limited retention.** The provider keeps the request and the result only for the abuse-monitoring period set by its terms, and uses them in that period only to detect and prevent misuse of its service. The period for each provider is in the table below.
- **Transfers.** Where a provider processes data outside the European Economic Area, the transfer is protected by the safeguards listed in the table below and in Section 9.

Food Scanner (Photos and Described Meals)

- **Data sent:** The food photo you take or upload, close-up crops of parts of that photo, any description you add, or — when you describe a meal in words instead of taking a photo — that description, together with our instructions to the model. Anything else visible in the photo is sent with it.
- **Purpose:** To identify the food and estimate its portions; nutritional values are then calculated from our own food database
- **Portion measurement (iPhone):** On an iPhone that supports augmented reality, the live scanner may measure a meal for about a second and a half with Apple ARKit, using the camera (and the LiDAR depth sensor where the phone has one). This runs on your phone. Only the resulting measurements (the area the food covers, its height and volume, and how sure the measurement is) are sent to Mouve with the scan, to work out the portion. No depth image, 3D scan or AR camera frame leaves your phone, and the measurements are never sent to an AI provider. They are kept and deleted with the scan
- **Retention by Mouve:** A photo scan you do not log stays in your History, marked “Not logged”, for 30 days, so you can still log it or delete it; deleting it removes the photo straight away, and after 30 days we delete its photo and crops. A described meal you do not log, or a scan that found no food, is deleted within 24 hours. If you save a scan, the photo is kept with the log entry until you delete the entry or your account
- **Improving food recognition (optional):** When you correct a scan or log a scanned item, we keep a record of what the scan suggested, what you ended on (product, barcode, pack size, nutrients, amount) and what the scan read on the pack. The record has no account identifier and is kept for 365 days (legal basis: our legitimate interest in improving the food scanner, Art. 6(1)(f)). Only if you turn on **Settings → Privacy → Help improve food recognition** (your consent, Art. 6(1)(a); we ask once, after a correction, and you can say no) do we also keep one copy of the scan photo, with location and other metadata removed, for up to 180 days, and a small cropped picture of each food or product in the scan together with what the scan said it was and what you confirmed. We use these to test food recognition and to train Mouve's own food recognition model; they are never given to anyone to train theirs. We have no face detector, so we do not blur faces; instead we do not copy a photo where a hand or a person may fill much of the frame. Turning the setting off stops new copies and deletes the photos, crops and records already copied under it (a model already trained on them is not recalled). The photo copy is never shared with anyone outside Mouve and is not used for advertising.

Food Log Text Parsing

- **Data sent:** A food description you dictate with voice food logging, or type in an older version of the app (e.g. “2 eggs and toast with butter”). Dictation is converted to text by your device's or browser's built-in speech recognition; Mouve never receives the audio. No images are sent.
- **Purpose:** To turn the description into structured nutritional data (calories, protein, carbohydrates, fats)

AI Meal Planning

- **Data sent:** The meal type or day you are planning, and the ingredients and calorie or macronutrient targets you enter for the request. No images are sent.
- **Purpose:** To generate meal suggestions or a day's meal plan

AI Workout and Program Generation

- **Data sent:** The description of the workout or training program you want (typed or dictated), the options you select (such as target muscles, equipment, duration, training days and number of weeks), and our exercise catalogue. Dictation is converted to text on your device or in your browser; Mouve never receives the audio.
- **Purpose:** To generate a workout or multi-week program that matches your request
- **Retention:** Generated workouts and programs are stored in your account until you delete them or your account

AI Progress Insights

- **Data sent:** For the period you choose: the date, duration and calories burned of up to 20 recent workouts, the date and type of up to 20 recent food log entries, up to 10 body-weight entries with their dates, and the number of workouts, food log entries and weight entries in the period.
- **Purpose:** To generate a summary of your progress and recommendations
- **Retention:** Insights are generated each time you request them and are not saved to your account

**Apps and AI agents you connect.** The food scanner, food log text parsing and meal planning features are also available to apps and AI agents you authorize (Section 8.8). When such an app uses one of them on your behalf, we process the request in the same way and with the same AI providers as when you use the feature in Mouve.

AI providers

| Provider | Features | Where data is processed | Transfer safeguard | Abuse-monitoring retention | Provider terms |
| --- | --- | --- | --- | --- | --- |
| OpenAI | Food log text parsing, meal planning, workout and program generation, progress insights; the food scanner (food photos and described meals) and the equipment suggestion for a World gym photo when Google's service is unavailable | United States | Standard Contractual Clauses (SCCs) | Up to 30 days, then deleted | [OpenAI API data controls](https://developers.openai.com/api/docs/guides/your-data), [OpenAI Privacy Policy](https://openai.com/policies/privacy-policy) |
| Google LLC (Gemini API, paid service) | Food scanner (food photos and described meals); the optional equipment suggestion for a World gym photo, when you ask for it | Google's global infrastructure, which includes the United States | EU-US Data Privacy Framework (DPF) + SCCs | 55 days, then deleted | [Gemini API Additional Terms](https://ai.google.dev/gemini-api/terms), [Gemini API abuse monitoring](https://ai.google.dev/gemini-api/docs/usage-policies) |

We keep this table up to date. Before a new AI provider receives any of your data, we add it here and notify you as described in Section 20.

**Right to opt out:** All AI features on Mouve are optional. You can use Mouve without ever using AI food scanning, food log text parsing, meal planning, workout generation or progress insights. No data is sent to an AI provider unless you actively start an AI feature, or an app you have connected starts one for you.

### 8.4 Food Data

- **Open Food Facts**: When you scan food barcodes, we query the Open Food Facts database to retrieve nutritional information. This is a collaborative, free, and open food products database.

### 8.5 Authentication Providers

- **Google** and **Apple**: If you choose to sign in with these providers, they share basic profile information with us according to their respective privacy policies.

### 8.6 Other Users

Certain information is visible to other Mouve users:

- Your public profile (username, bio, avatar, public posts)
- Workouts and content you share publicly
- Meals and days you share from your food diary, to the audience you chose for each one (Section 4.4), together with the likes and comments other people leave on them
- Your community memberships
- Your followers and who you follow

If another user uses “Log this” on a meal you shared, the foods and portions are copied into that user's own diary. That copy becomes their data, is not linked to your account, and is not deleted when you delete the share or your account. We tell you how many times a share was logged, never who logged it. Comments and likes other people leave on your shares stop being shown when the share is deleted, and are deleted when the author's account is deleted.

### 8.7 Data Processors and Other Recipients Summary

Hetzner, Cloudflare, Stripe, OpenAI and Google LLC process data on our behalf. Meta, TikTok and Google Ireland (last three rows) are not our processors: they receive data only if you opt in to Advertising measurement, and are controllers in their own right (Section 3.9).

| Processor | Purpose | Location |
| --- | --- | --- |
| Hetzner | Backend hosting | EU |
| Cloudflare | Media storage (R2), CDN | EU (storage); worldwide edge network (CDN) |
| Stripe | Payment processing | US (DPF + SCCs) |
| OpenAI | AI features: food log text parsing, meal planning, workout and program generation, progress insights, and the AI food scanner when Google's service is unavailable (Section 8.3) | US (SCCs) |
| Google LLC | AI food scanner: food photos and described meals (Section 8.3) | US and other countries (DPF + SCCs) |
| Meta Platforms Ireland Limited | Advertising measurement, only with your consent: that you visited our public pages, created an account or subscribed on the web, a hashed email, ad click identifier and cookie values (Section 3.9). Joint controller for the pixel, independent controller afterwards | Ireland; onward transfers to the US (DPF + SCCs) |
| TikTok Technology Limited | Advertising measurement, only with your consent: as for Meta (Section 3.9) | Ireland; onward transfers outside the EEA (SCCs) |
| Google Ireland Limited | Advertising measurement (Google Ads), only with your consent: as for Meta (Section 3.9) | Ireland; onward transfers to the US (DPF + SCCs) |

### 8.8 Third-Party Applications You Connect

You can authorize third-party applications and AI agents (for example, an MCP-compatible assistant, or apps built on the Mouve API as we open it to developers) to access parts of your Mouve account. These apps are **recipients** of your data in the sense of Art. 13(1)(e) GDPR — but only the apps you choose, and only with the access you approve.

- **What an app can access.** Nothing until you approve it. The authorization screen lists exactly what the app is requesting (for example “See your workouts” or “Create posts as you”), and the app receives only what those permissions cover. Where the request includes workout, nutrition, or body data, your explicit consent is asked separately (Section 4.2). Your latest location, if you chose to share it, is shared only with an app you approved “See where you are right now” for.
- **Who is responsible.** A connected app is an independent controller of the data it receives — it is not Mouve's processor and does not act under our instructions. Its own privacy policy governs what it does with your data, so review it before connecting.
- **What binds the developer.** Developers must accept the [Mouve Developer Terms](/legal/developer-terms), which contractually restrict them to the purpose you authorized and prohibit selling your data, using it for advertising, eligibility decisions, surveillance, or AI training, and require deletion within 30 days after you disconnect. Honesty requires saying plainly: these are contractual obligations we enforce through suspension and takedown — we cannot technically reach inside a third-party's systems to verify or force deletion there.
- **Your controls.** Review every connected app and what it can access, and disconnect any of them, at any time in Settings → Connected apps. Disconnecting revokes the app's credentials; short-lived tokens it already holds expire within one hour at most (Section 4.3). Apps that violate their obligations can be reported and are subject to suspension and removal from the platform.

Connected apps appear in this policy as a category of recipients because we cannot list them individually — which apps (if any) receive your data is entirely your choice. We never connect an app to your account ourselves, and we are not paid by apps for access to your data.

<a id="international"></a>

## 9. International Data Transfers

Some of our service providers are located outside the European Economic Area (EEA). When we transfer your data outside the EEA, we ensure appropriate safeguards are in place.

### 9.1 Transfers to the United States

| Processor | Purpose | Transfer Mechanism |
| --- | --- | --- |
| OpenAI | AI food log text parsing, meal planning, workout and program generation, progress insights, AI food scanner when Google's service is unavailable | Standard Contractual Clauses (SCCs) |
| Google LLC | AI food scanner: food photos and described meals | EU-US Data Privacy Framework (DPF) + SCCs |
| Stripe | Payment processing | EU-US Data Privacy Framework (DPF) + SCCs |
| Meta Platforms, Inc. (via Meta Platforms Ireland Limited) | Advertising measurement, only with your consent (Section 3.9) | EU-US Data Privacy Framework (DPF) + SCCs |
| Google LLC (via Google Ireland Limited) | Advertising measurement, only with your consent (Section 3.9) | EU-US Data Privacy Framework (DPF) + SCCs |
| TikTok group companies outside the EEA (via TikTok Technology Limited) | Advertising measurement, only with your consent (Section 3.9) | Standard Contractual Clauses (SCCs) |

### 9.2 Data Processed Within the EU

| Processor | Purpose | Location |
| --- | --- | --- |
| Hetzner | Backend services hosting | EU |
| Cloudflare (EU region) | Media storage (R2) | EU data centers |
| Mouve Technology OÜ (our own servers) | Self-hosted analytics, backups, food-recognition training set | EU |

Hetzner and our own servers are both in the EU, so no transfer safeguard is needed for them. Cloudflare also delivers content through its edge network, which can handle your requests outside the EU; Cloudflare relies on the EU-US Data Privacy Framework and Standard Contractual Clauses for that.

You may request a copy of the safeguards in place by contacting us at [privacy@mouve.it](mailto:privacy@mouve.it).

<a id="automated"></a>

## 10. Automated Processing and GDPR Article 22

Mouve uses AI-powered automated processing in the following features:

### 10.1 AI Food Image Analysis

- **Purpose:** To estimate the nutritional content of food from photographs
- **Logic involved:** An AI vision model identifies the food items in the image and estimates their portion sizes; calories and macronutrients are then calculated from our food database. Section 8.3 lists the AI providers involved
- **Significance and consequences:** The nutritional estimates influence your daily nutrition log and calorie/macro tracking. These are approximations and may be inaccurate. No health, medical, or dietary decisions should be based solely on these estimates.

### 10.2 AI Meal Planning

- **Purpose:** To generate meal plan suggestions based on your dietary preferences and nutritional goals
- **Logic involved:** An AI language model generates meal suggestions from the meal type, ingredients and targets you enter. Section 8.3 lists the AI providers involved
- **Significance and consequences:** Meal plans are suggestions only. They do not account for medical conditions, allergies not explicitly stated, or individual metabolic needs. You should consult a healthcare professional for personalized dietary advice.

### 10.3 Ingredient Suggestions From Your History

- **Purpose:** To pre-fill the ingredient picker with likely ingredients, and typical amounts, when you turn a dish into ingredients
- **Logic involved:** A dish prior (a checked-in list of typical ingredients for the dish) is ranked together with your own previous food logs and scans, so foods you actually buy and eat appear first. The product match uses your chosen market. No AI model is called to build the suggestions, and no history is sent to a model.
- **Your control:** Personalisation is on by default and can be turned off in Settings → Privacy. With it off, suggestions come only from the dish prior and never read your diary or scans. You can delete any suggestion before logging it, and deleting a diary entry or scan removes it from future personalisation.
- **Significance and consequences:** Suggestions are a starting point, not a dietary or medical decision, and never change or hide entries in your diary.

### 10.4 Applicability of Article 22

Although these features involve automated processing, they do not constitute automated decision-making within the meaning of GDPR Article 22. All AI outputs and ingredient suggestions are advisory only - they do not produce legal or similarly significant effects on users.

You may contact us if you believe an AI output is incorrect or if you have concerns about how automated processing is used:

- **Edit or delete** any AI-generated data from your logs at any time
- **Opt out** of AI features entirely - all AI features are optional and require your active initiation
- **Report concerns** by contacting [privacy@mouve.it](mailto:privacy@mouve.it)

<a id="ai-role"></a>

## 11. Role of AI Systems in the Service

Mouve uses artificial intelligence systems to assist with certain features such as food image analysis, meal planning, and workout generation. These systems generate estimates and suggestions based on the information you provide.

AI systems used by Mouve operate as assistive tools and do not independently make decisions that affect your rights, access to the Service, or the operation of your account. Where applicable, we aim to comply with requirements of the EU AI Act.

AI-generated outputs are provided for informational purposes only and may contain inaccuracies. Every AI result in the app is shown with a notice to that effect — “AI results are estimates and can be inaccurate. Check the numbers before logging.” Users remain responsible for reviewing and deciding whether to use the information generated by AI systems. For full details, see our [AI Transparency Notice](/ai-transparency).

<a id="cookies"></a>

## 12. Cookies and Similar Technologies

Mouve uses cookies and similar technologies. Strictly necessary ones (they keep you signed in and remember this choice) are exempt from consent under ePrivacy Article 5(3). Everything else needs your consent: **Analytics** (our own analytics, Section 3.8) and **Advertising measurement** (Meta, TikTok and Google, Section 3.9) are off until you accept them in the cookie banner, and you can change your mind at any time in *Cookie settings* (link at the bottom of our pages) or Settings → Privacy. Nothing but the strictly necessary storage is used before you choose.

### 12.1 Cookie Table

| Name | Purpose | Party | Type | Duration | Category |
| --- | --- | --- | --- | --- | --- |
| mouve\_session\_v2 | Keeps you signed in (opaque session id) | First-party | Cookie, HttpOnly | Up to 7 days, refreshed while active | Strictly necessary |
| mouve\_consent\_v1 | Remembers your cookie choice | First-party | Cookie | 12 months | Strictly necessary |
| ph\_<token>\_posthog, \_\_ph\_opt\_in\_out\_<token> | Our own analytics: analytics identifier (also in local storage) and opt-out marker | First-party (PostHog, hosted by us in the EU) | Cookie and local storage | Up to 12 months | Analytics (your consent) |
| mouve\_attr\_v1 | Which campaign brought you (UTM tags, referrer domain, landing path; ad click identifiers only with Advertising) | First-party | Cookie | 90 days | Analytics or Advertising (your consent) |
| \_fbp, \_fbc | Meta Pixel: browser and ad-click identifiers | Set on our domain by Meta's script | Cookie | 90 days | Advertising (your consent) |
| \_ttp, \_tt\_enable\_cookie | TikTok Pixel: browser identifier and cookie marker | Set on our domain by TikTok's script | Cookie | About 13 months | Advertising (your consent) |
| \_gcl\_au, \_gcl\_aw, \_gcl\_gb, \_gcl\_dc | Google Ads conversion linker and ad-click identifiers | Set on our domain by Google's script | Cookie | 90 days | Advertising (your consent) |
| fr, IDE, test\_cookie and similar | The platforms' own cookies on facebook.com, tiktok.com, doubleclick.net and google.com, when their scripts run | Third-party | Cookie | Set by the platform; see its policy | Advertising (your consent) |

### 12.2 Local and Session Storage

The web app stores a few settings on your device (for example whether the sidebar is pinned, and short-lived navigation state such as your feed scroll position) and, with Analytics consent, the analytics identifier and a per-tab window id. They are listed in full in the [Cookie Policy](/cookie-policy).

For full details, including security attributes and every storage entry, see our [Cookie Policy](/cookie-policy).

<a id="retention"></a>

## 13. Data Retention

We retain your personal data for as long as necessary to provide our Service and fulfill the purposes described in this Privacy Policy:

- **Account data:** Retained until you delete your account. When you confirm, your account is closed at once (you are signed out everywhere, nobody else can see it, a subscription bought on mouve.it is cancelled) and it is deleted for good 7 days later. Until then you can restore it with the link in the email we send, or by writing to support@mouve.it.
- **Accounts refused as under 16:** If the date of birth you enter shows you are under 16, we do not save it and we record only the time of the refusal. The account is deleted 7 days later, through the same full deletion as above (including your analytics profile), unless a date of birth showing you are 16 or older is entered first. We do not email you about it.
- **Product emails:** Your choice (subscribed or not, when and how you made it, and which of these emails we sent you) and your answer to the “why did you stop” question are kept until you delete your account, and are then deleted.
- **Workout and nutrition data:** Retained until you delete your account or specific entries; hard-deleted on account deletion
- **Health and fitness metrics:** Body measurements, weight history, and fitness-tracker data are hard-deleted on account deletion
- **Shared meals:** Kept until you delete the share, withdraw your meal sharing consent or delete your account, and then the shared meal is hard-deleted and its post is removed from view. On account deletion the post, its comments and its likes are deleted as well. A meal that another user copied into their own diary with “Log this” stays in that user's diary.
- **Food labels:** A label you make from a food, meal or recipe (its name, nutrition values, ingredients, allergens and dates, and a Mouve code) is kept until you delete it or delete your account, and then it is deleted and its QR code stops working. A label is private to you unless you share it. A label you printed and gave to someone stays as paper in their hands, and a meal they logged from it stays in their diary.
- **World (outdoor gyms):** A photo you add to a gym is deleted when you delete it or your account. The name of a gym you add and the equipment notes you write describe a public place, so they stay when you delete your account, with your name removed from them. Photos, gym names and equipment notes are checked by our moderation tools, and a moderator can remove them.
- **World (ratings, problem reports, prompts):** A rating you give a gym (stars, tags and an optional comment) and a problem you report on a gym or its equipment (a kind, an optional comment and an optional photo only our moderators and administrators can see) are kept until you delete them or your account, and are then deleted. A rating leaves the gym's score when you delete it. We also keep one small record per gym saying we have already asked you to add photos or rate it, so we never ask twice; it is deleted with your account. To decide whether you are at a gym, the app sends your position when you open the app near it; we use it for that answer and do not store it. A photo you add can show people who happened to be there: we look for faces in it on our own servers and pixelate them before the photo is shown to anyone (we keep no face data, and if the check cannot run the photo is not published), but aim at the equipment anyway, and use Report on any photo to have it reviewed and removed.
- **World (routes to a gym):** When you ask for a route, your position is sent to our server and to the routing software we run ourselves, only to work out the route and the calories. We do not store it and do not write it to our logs, and the answer is not kept. If you connect an AI assistant to Mouve and it sends you a planned route, we keep that route (where it starts, where it goes and how you travel) in your account for 7 days, so it shows in the app, and then delete it. You can delete it earlier, and it is deleted if you delete your account.
- **World (sharing your location with your AI assistants):** This is optional and off until you switch on “Share location with assistants” in the Mouve app. While it is on, the app sends your phone's precise position to our server now and then, also when Mouve is in the background, so an AI assistant you have connected to Mouve can plan a route from where you are. We keep only the latest point (never a history of where you have been) with how accurate it is, when it was taken and whether the app was open. It is replaced by each new one, deleted automatically 24 hours after it was taken, and deleted at once when you switch sharing off or delete your account. Only an assistant you connected, and only if you approved “See where you are right now” for it, can read it; we do not use it for anything else, do not show it to other users and do not write it to our logs.
- **World (search):** When you search for a gym, an address or a place, what you type, your position (or the centre of the map) and your phone's language are sent to our server and to the geocoding software we run ourselves, only to find and sort the results. We do not store them and do not write them to our logs. Your recent searches are kept on your phone only; you can clear them in the search box. The step count the app shows next to a route is read from Apple Health or Health Connect on your phone and is not sent to us.
- **World (while you navigate):** Mouve keeps reading your position on your phone for as long as a navigation runs, also when the screen is locked or Mouve is in the background (iPhone shows a location indicator, Android shows a notification), to guide you, count your calories and steps and keep the Lock Screen, Dynamic Island and Apple Watch display up to date. It stops when you arrive or end the navigation. This position is used on your phone only; we do not store it. It leaves your phone only when a new route is needed because you left the route, exactly as described above.
- **Messages you sent:** Retained until you delete them or delete your account. Messages other people sent to you remain part of their conversation data and are not deleted by your erasure request.
- **Payment records:** Retained for 7 years after the transaction to meet EU tax and bookkeeping obligations (GDPR Art. 6(1)(c) + Art. 17(3)(b)) — kept even after account deletion
- **Media files:** Retained until you delete them or your account; removed from object storage on account deletion
- **Food scanner photos and descriptions:** A photo scan you do not log: 30 days, shown in your History as “Not logged” and deletable there at any time. Other scans and descriptions you do not save: 24 hours. A saved scan: kept with the log entry until you delete it or your account (Section 8.3). Photo copies kept for improving food recognition and item crops (only with your optional consent): up to 180 days, or until you turn the setting off or delete your account
- **Content moderation records:** Retained for 6 months after the moderation action to meet our Digital Services Act obligations (GDPR Art. 6(1)(c) + Art. 17(3)(e)) — kept even after account deletion. A record is kept longer only while it is still needed: while an appeal against the decision is pending or can still be made, while the decision still applies to the content or account it concerns, and while the record is needed to establish, exercise or defend a legal claim or to comply with a legal order (GDPR Art. 17(3)(e)). When records are deleted, we keep only anonymous counts (for example, how many reports of each type we handled in a month) for our transparency reporting
- **Session replays:** Deleted 30 days after they were recorded (Section 3.8). Usage analytics events are pseudonymous (internal user ID only) and are kept for as long as we need them to produce aggregate statistics.
- **Advertising measurement (Section 3.9):** the advertising click identifiers and platform cookie values we store are kept for 90 days (the same as the cookies themselves). The log of what we sent to Meta, TikTok and Google (event, time, platform, outcome — never the email itself) is kept for 13 months. Which campaign brought you (UTM tags, referrer domain, landing page) is kept on your account until you delete it. Your cookie choice is kept in the consent cookie for 12 months and, if you are signed in, on your consent record until you delete your account.

**Things other members still use.** When you delete your account, a few things you made that other people depend on are kept without your name or any other way to identify you: a community you created passes to its longest-standing admin or member (or is archived if nobody else is left), a conversation you started (the other person's messages live in it, yours are deleted), a workout you published that another member has trained (hidden and no longer public, so their training history still shows it), a custom food another member has logged, and custom exercises or foods you added to the shared library that others have used. Anything of this kind that nobody else uses is deleted.

After account deletion, the only data we keep is the payment and content-moderation records described above (for their fixed legal retention periods), the shared items in the previous paragraph, and anonymized, aggregated statistics that can no longer identify you. Everything else is erased at the end of the 7 days. See our [Account Deletion page](/account-deletion) for the full list.

<a id="your-rights"></a>

## 14. Your Rights Under GDPR

As a data subject in the European Union, you have the following rights:

- **Right of Access (Art. 15):** Request a copy of your personal data. This includes knowing the recipients of your data (Art. 15(1)(c)): the third-party apps you have authorized are listed, with their access, in Settings → Connected apps
- **Right to Rectification (Art. 16):** Correct inaccurate or incomplete data
- **Right to Erasure (Art. 17):** Request deletion of your personal data (“right to be forgotten”)
- **Right to Restrict Processing (Art. 18):** Request limitation of how we use your data
- **Right to Data Portability (Art. 20):** Receive your data in a structured, machine-readable format (see “Your data export” below)
- **Right to Object (Art. 21):** Object to processing based on legitimate interests. To stop product emails use the unsubscribe link in any of them, or Settings → Notifications; it takes effect at once
- **Right to Withdraw Consent (Art. 7):** Withdraw consent at any time for processing based on consent
- **Automated Decision-Making (Art. 22):** Mouve's AI features do not constitute automated decision-making under Art. 22 (see Section 10). You may contact us with any concerns about automated processing.
- **Right to Lodge a Complaint:** File a complaint with your local data protection authority (see Section 17)

To exercise your rights, contact us at [privacy@mouve.it](mailto:privacy@mouve.it). We will respond within one month, subject to any extension permitted under applicable law.

**Your data export:** you can download a copy of your data yourself, at any time: in the app under Settings → Download your data, and on the web under Settings → Data Management → Export Data. You get one ZIP file, prepared on the spot and sent straight to you; we do not keep a copy of it. It contains everything we hold about you: your account and profile, consents, workouts with their sets, programs, body measurements, Apple Health or Health Connect data, food diary, custom foods, recipes, meal plans and shared meals, food scans, your posts, comments, likes, saved items, follows, blocks and communities, your conversations, your notifications, conversations with Mouve's AI and what it remembers about you, subscriptions and referrals, the apps you connected, support tickets, moderation decisions about your content, and product-analytics events. The data is a JSON file in a documented, versioned format, and your own photos and files are included as files. We leave out, and list in the file, only what would let someone sign in as you (passwords, tokens), notes written by our staff, and one-way hashes. Reports other people filed about you are not included because they identify the reporter; the decisions taken on them are. You can export up to six times an hour.

**Account Deletion:** You can delete your account at any time through the Settings page in the app. This immediately and permanently erases your profile, posts, comments, workouts, nutrition logs, health and fitness metrics, the messages you sent, social connections, notifications, and uploaded media. Payment records (7 years) and content-moderation records (6 months) are retained for their legal periods as described in Section 13. Or visit our public [Account Deletion page](/account-deletion) for full instructions, including how to request deletion by email if you no longer have access to your account.

**Deletion and connected apps:** deleting your account removes your data from Mouve, but a copy that a third-party app received while you had it connected is held by that app as an independent controller (Section 8.8). The Mouve Developer Terms oblige the app to delete your data within 30 days of your account deletion; to exercise your erasure right directly against an app, contact the app's developer. Disconnecting apps before deleting your account (Settings → Connected apps) revokes their credentials as described in Section 4.3.

<a id="california-rights"></a>

## 15. Your California Privacy Rights (CCPA / CPRA)

Notice at Collection — California Civil Code § 1798.100(b)

We collect the categories of personal information listed in Section 15.2 below. That information is used to provide and improve the Service, manage your account, process payments, prevent fraud, and operate AI features. We retain it for the periods described in [Section 13](#retention). We do not sell your personal information. If you opt in to Advertising measurement (Section 3.9) we share limited data with advertising platforms, described in Section 15.6.

### 15.1 Who This Applies To

This section applies to residents of the State of California and supplements the rest of this Privacy Policy. It is provided in accordance with the California Consumer Privacy Act of 2018 (CCPA) as amended by the California Privacy Rights Act of 2020 (CPRA), Cal. Civ. Code § 1798.100 et seq.

### 15.2 Categories of Personal Information Collected

In the preceding 12 months, we have collected the following categories of personal information as defined under Cal. Civ. Code § 1798.140:

| Category | Examples | Collected |
| --- | --- | --- |
| Identifiers | Name, email address, username, IP address, device identifiers | Yes |
| Customer records (Cal. Civ. Code § 1798.80(e)) | Profile information (name, bio, location), account details | Yes |
| Commercial information | Subscription tier, subscription history, Stripe customer ID | Yes |
| Internet or other electronic network activity | In-app interactions (likes, comments, follows), browser type, session data | Yes |
| Geolocation data | Coarse location derived from IP address only; no precise GPS location is collected | Yes |
| Professional or employment information | N/A | No |
| Inferences drawn from personal information | Workout and nutrition habits, fitness patterns derived from usage of the Service | Yes |
| Sensitive personal information | Health and fitness data (workout logs, nutrition logs, body measurements) — collected with your explicit consent under both GDPR Art. 9(2)(a) and the CCPA sensitive PI provisions. Not used to infer characteristics such as race, ethnicity, religion, or sexual orientation. | Yes |

### 15.3 Sources of Personal Information

- **Directly from you** — when you create an account, complete your profile, log workouts or nutrition, upload media, or communicate with other users.
- **From your device** — technical data (IP address, browser type, device identifiers) collected automatically when you access the Service.
- **From authentication providers** — basic profile information (name, email) when you choose to sign in with Apple or Google.

### 15.4 Business and Commercial Purposes for Collection

- Providing and operating the Service
- Creating and managing your account
- Fraud prevention and security
- Processing premium subscription payments
- Analytics for service improvement (aggregated and anonymized)
- Operating AI features (food image analysis, text parsing, meal planning, workout and program generation, progress insights) through the AI providers listed in Section 8.3, acting as our processors — each keeps request data only for the abuse-monitoring period listed there and may not use it to train its models
- Complying with legal obligations

### 15.5 Categories of Third Parties to Whom We Disclose Personal Information

- **OpenAI** — AI processing (food log text parsing, meal planning, workout and program generation, progress insights; the food scanner when Google's service is unavailable)
- **Google** — AI processing (food scanner: food photos and described meals)
- **Stripe** — payment processing for premium subscriptions
- **Cloudflare R2** — media storage (photos, videos)
- **Hetzner** — backend application hosting

### 15.6 Sale or “Sharing” of Personal Information

**We do not sell your personal information.** **Sharing for cross-context behavioral advertising happens only if you opt in.** If you choose “Accept all” or switch on Advertising measurement (Section 3.9), the pixels of Meta, TikTok and Google run on our public pages and, when you sign up or subscribe on the web, we send those platforms a hashed email, advertising identifiers and the fact of the sign-up or purchase. California law may treat that as “sharing” (§ 1798.140). The categories involved are identifiers, internet or network activity (pages viewed) and commercial information (that you subscribed); never health, nutrition, body or workout data. You can opt out at any time in Cookie settings or Settings → Privacy, and nothing is shared until you opt in. We do not knowingly share the personal information of anyone under 16.

### 15.7 Retention

Retention periods for each category of personal information are set out in [Section 13 (Data Retention)](#retention).

### 15.8 Your California Privacy Rights

As a California resident, you have the following rights under CCPA/CPRA:

- **Right to Know (§ 1798.100):** Request disclosure of the categories and specific pieces of personal information we have collected about you, the sources, the business purposes, and the categories of third parties with whom we share it.
- **Right to Access / Portability (§ 1798.100):** Receive a copy of your personal information in a portable, readily usable format.
- **Right to Delete (§ 1798.105):** Request deletion of personal information we hold about you, subject to limited exceptions under § 1798.105(d) (e.g., completing a transaction, security, legal obligations).
- **Right to Correct (§ 1798.106):** Request correction of inaccurate personal information.
- **Right to Opt Out of Sale / Sharing (§ 1798.120):** We do not sell personal information. Sharing for cross-context behavioral advertising happens only after you opt in (Section 3.9); turn Advertising measurement off in Cookie settings or Settings → Privacy to opt out, or contact us.
- **Right to Limit Use of Sensitive Personal Information (§ 1798.121):** You may direct us to use your sensitive personal information (health and fitness data) only as necessary to provide the Service. Because health data is already gated behind explicit consent — which you may withdraw at any time in Settings — this right is exercised through the existing consent mechanism.
- **Right to Non-Discrimination (§ 1798.125):** We will not discriminate against you for exercising any of these rights. Exercising your rights will not result in denial of services, different prices, or reduced quality.
- **Right to Designate an Authorized Agent:** You may designate an authorized agent to make a request on your behalf. We will require the agent to provide written permission from you and may verify your identity directly.

### 15.9 How to Exercise Your California Rights

To submit a verifiable consumer request, contact us at [privacy@mouve.it](mailto:privacy@mouve.it) from the email address associated with your Mouve account. This allows us to verify your identity. We will respond within **45 days**. If we need additional time, we will notify you within that initial period and may extend the response window by an additional 45 days.

You may submit up to two verifiable requests in a 12-month period. We will not charge a fee unless requests are manifestly unfounded or excessive.

<a id="dpo"></a>

## 16. Data Protection Officer

We are not currently required to appoint a Data Protection Officer under GDPR Article 37. We will reassess this obligation as our processing activities evolve.

All privacy-related inquiries, data subject access requests, and concerns can be directed to:

**Privacy Contact**
Mouve Technology OÜ
Sõpruse pst 8-31, Kristiine linnaosa, 10615 Tallinn, Estonia
Email: [privacy@mouve.it](mailto:privacy@mouve.it)

<a id="supervisory"></a>

## 17. Supervisory Authority

If you believe that our processing of your personal data infringes the GDPR, you have the right to lodge a complaint with the supervisory authority in your EU Member State of habitual residence, place of work, or place of the alleged infringement.

A list of EU data protection authorities is available at the [European Data Protection Board website](https://edpb.europa.eu/about-edpb/about-edpb/members_en).

<a id="security"></a>

## 18. Data Security

We implement appropriate technical and organizational measures to protect your personal data:

- Encryption of data in transit using TLS/HTTPS
- Secure authentication with session management
- Row-level security policies in our database ensuring users can only access their own data
- Private media storage with time-limited signed URLs (expiring after 24 hours)
- Regular security assessments and updates

While we strive to protect your personal data, no method of transmission or storage is 100% secure. If you become aware of any security vulnerabilities, please contact us immediately at privacy@mouve.it.

<a id="children"></a>

## 19. Children's Privacy

Mouve is not intended for children under the age of 16. We do not knowingly collect personal data from children under 16. If you are a parent or guardian and believe your child has provided us with personal data, please contact us at privacy@mouve.it, and we will delete such information.

When an account is opened with Google, Apple or an email code, we ask for the date of birth right after sign-in. If it shows the person is under 16, we refuse it and do not store it; we keep only the time of the refusal. The account, and the analytics profile linked to it, is then deleted automatically 7 days later, unless a date of birth showing the person is 16 or older is entered first.

<a id="changes"></a>

## 20. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or legal requirements. We will notify you of any material changes by:

- Posting the updated policy on this page with a new “Last updated” date
- Sending you an email notification for significant changes
- Displaying a notice in the app

We encourage you to review this Privacy Policy periodically.

<a id="contact-us"></a>

## 21. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact us:

**Mouve Technology OÜ**
Sõpruse pst 8-31, Kristiine linnaosa, 10615 Tallinn, Estonia
**Email:** [privacy@mouve.it](mailto:privacy@mouve.it)

<a id="changelog"></a>

## Changelog

| Version | Date | Changes |
| --- | --- | --- |
| v1.0 | January 24, 2026 | Initial version |
| v2.0 | February 27, 2026 | Added health data consent details (Section 4). Expanded AI disclosure with specific models and data policies (Section 8.3). Added retention periods to legal basis table (Section 6). Added Data Protection Officer info. Added supervisory authority. Expanded international transfer details with per-processor mechanisms (Section 9). Added cookie table (Section 12). Added automated decision-making disclosure (Section 10). Added DSA-aligned content moderation references. Versioning added. |
| v2.1 | March 7, 2026 | Corrected cookie names to reflect the chunked SSR format in use at the time. Fixed legal basis table heading and consolidated health data processing under Art. 6(1)(b) + Art. 9(2)(a). Clarified Article 22 does not apply to AI features. Added AI Workout Generation to Section 8.3. Replaced PII terminology with GDPR-aligned wording. Updated DPO section. Removed specific supervisory authority reference. Added data processors summary table (Section 8.7). Added Role of AI Systems section (Section 11). Added cookie policy cross-reference. Softened DSA scope. Updated rights response timing. Added user identification transparency. Improved third-party database transfer wording. |
| v2.2 | March 7, 2026 | Added Food Log Text Parsing to AI features (Section 8.3). Updated OpenAI purpose in data processors table (Section 8.7) and international transfers table (Section 9.1) to include text parsing, workout generation, and progress insights. Updated consent withdrawal scope to list all AI features. Made privacy@mouve.it a clickable link in Section 9. |
| v2.3 | May 1, 2026 | Added CCPA/CPRA disclosures (Section 15): categories of personal information, sources, business purposes, third-party recipients, no-sale/no-sharing statement, California consumer rights (right to know, access, delete, correct, opt-out, limit sensitive PI, non-discrimination, authorized agent), and verifiable request process (45-day response). Added California residents notice at top of policy. Renumbered subsequent sections 15–20 to 16–21. |
| v2.4 | August 5, 2026 | Corrected the description of AI features to match the app. AI features are no longer placed behind a separate consent step; they run only when you start them and every AI result now carries an in-app accuracy notice. Section 4.1 clarifies how AI features relate to health data consent. Section 4.3 no longer states that withdrawing health data consent disables AI features. Section 6 separates AI features from health and fitness tracking in the legal basis table and describes them as processing carried out to deliver a feature you actively request. Section 11 quotes the in-app AI accuracy notice. Health data consent under Art. 9(2)(a) is unchanged. |
| v2.5 | August 30, 2026 | Added Section 8.8 (Third-Party Applications You Connect): apps and AI agents you authorize are disclosed as recipients (Art. 13(1)(e)), acting as independent controllers, bound by the Mouve Developer Terms, with an honest statement that deletion inside their systems cannot be technically enforced by Mouve. Section 4.2 describes the explicit consent asked when a connected app requests health data; Section 4.3 explains withdrawal by disconnecting (Settings → Connected apps) and credential revocation timing. Section 14 documents which-apps-had-access under Art. 15(1)(c) and how account deletion interacts with data already received by connected apps. |
| v2.6 | September 17, 2026 | Added Section 3.8 (Usage Analytics and Session Replay): self-hosted analytics, what is recorded before and after analytics consent, how session replays are masked (all text and inputs, all images and charts; messages, body measurements and the food scanner excluded), the consent basis and the 30-day retention. Added the matching row to the legal basis table (Section 6), a purpose in Section 7, the analytics storage note in Section 12 and the replay retention period in Section 13. |
| v2.7 | September 27, 2026 | Section 8.3 rewritten around AI providers instead of named models: the commitments that apply to every AI provider (no training, no account identifiers, abuse-monitoring retention only, transfer safeguards), a table of AI providers with the features each serves, where data is processed, the transfer safeguard and the retention period, and a commitment to update the table before a new provider receives data. The food scanner (food photos and described meals) now uses Google LLC (Gemini API) instead of OpenAI, and its photos, crops and descriptions are deleted within 24 hours unless you save the scan. Corrected what is sent for meal planning and progress insights, added AI program generation, and stated that the same features are available to apps you connect. Sections 5, 6, 8.7, 9.1, 10 and 15 updated to match. |
| v2.8 | September 30, 2026 | A food photo scan you do not log is now kept for 30 days instead of 24 hours, shown in your History as “Not logged” so you can log it later or delete it (deleting removes the photo straight away); after 30 days its photo and crops are deleted. Described meals and scans that found no food are still deleted within 24 hours. Sections 6, 8.3 and 13 updated. |
| v2.9 | October 1, 2026 | The food scanner can now also use OpenAI, already one of our AI providers, when Google's service is unavailable, so a scan still works during an outage. The same commitments apply (no training, no account identifiers, OpenAI's up-to-30-day abuse-monitoring retention). Sections 8.3, 8.7, 9.1 and 15.5 updated. |
| v2.10 | October 2, 2026 | New optional consent, “Help improve food recognition”: a copy of a corrected scan photo (metadata removed, hands and people skipped) may be kept for up to 180 days to test and improve food recognition; turning it off deletes the copies. A record of what you corrected, without an account identifier, is kept for 365 days. Sections 8.3 and 13 updated. |
| v2.11 | October 10, 2026 | With that same optional consent we now also keep a small cropped picture of each food or product in a scan, with what the scan said it was and what you confirmed, for up to 180 days, to train Mouve's own food recognition model. Whether you accepted the scan as it was or corrected it is recorded. Turning the setting off deletes them. Sections 8.3 and 13 updated. |
| v2.12 | October 10, 2026 | Section 8.3: on an iPhone that supports augmented reality, the live scanner may measure a meal on the phone with Apple ARKit (and LiDAR where present). Only the measurements (area, height, volume and how sure they are) reach Mouve, with the scan; no depth image, 3D scan or camera frame leaves the phone, and nothing of it goes to an AI provider. |
| v2.13 | October 14, 2026 | New feature: you can share a meal or a day from your food diary with your approved followers or with everyone, one share at a time. It needs a separate explicit consent (Art. 9(2)(a)), which you can withdraw at any time; withdrawing deletes what you shared. New Section 4.4; Sections 3.4, 3.5, 6, 8.6 and 13 updated. |
| v2.14 | October 23, 2026 | Section 13 now says what happens on account deletion to things other members still use (a community or conversation you started, a workout they trained, a food they logged): kept without anything that identifies you. Everything else is deleted, as before. |
| v2.15 | October 24, 2026 | Cookie banner with separate choices for Analytics and Advertising measurement. Section 3.8 rewritten: our analytics now start in your browser only after you accept them; public pages are counted by our server with no cookie and no identifier; signed-in product events can be objected to by refusing Analytics. New Section 3.9 (Advertising measurement): with your consent only, pixels of Meta Platforms Ireland, TikTok Technology Limited and Google Ireland on our public pages, and sign-up and web-subscription events with a hashed email sent to them; joint and independent controllership; never health data. Sections 6, 8.7, 9.1, 12, 13 and 15 updated, including California “sharing”. Cookie Policy updated to 2.0. |
| v2.16 | October 24, 2026 | Section 14: you can now download all your data yourself in the app and on the web, as one ZIP file (JSON plus your photos), with what it contains and what it leaves out. |
| v2.17 | October 24, 2026 | Deleting your account now has a 7-day grace period: the account is closed at once and deleted 7 days later, and you can restore it until then. Section 13 updated. |
| v2.18 | October 25, 2026 | Section 13: content moderation records are deleted 6 months after the moderation action. The section now says when one is kept longer (a pending or still possible appeal, a decision still in effect, a legal claim or order) and that only anonymous counts are kept after deletion. |
| v2.19 | October 25, 2026 | An account whose date of birth is refused as under 16 is deleted 7 days later unless a valid date of birth is entered first; the refused date is not stored. Sections 13 and 19 updated. |

---

<!-- document: tos | version: 3.2 | effective: 2026-03-07 -->
Document: tos
Version: 3.2
Effective: 2026-03-07
Canonical: https://mouve.it/tos
Markdown: https://mouve.it/tos.md

# Terms of Service

Version 3.2 | Last updated: August 30, 2026 | Effective: March 7, 2026

<a id="introduction"></a>

## 1. Introduction and Acceptance

Welcome to Mouve. These Terms of Service (“Terms”) constitute a legally binding agreement between you (“you,” “your,” or “User”) and Mouve (“we,” “our,” or “us”) governing your access to and use of the Mouve website at mouve.it, our progressive web application, and all related services (collectively, the “Service”).

By creating an account, accessing, or using Mouve, you agree to be bound by these Terms, our [Privacy Policy](/privacy-policy), and all applicable laws and regulations. If you do not agree to these Terms, you must not access or use the Service.

We reserve the right to modify these Terms at any time. Material changes will be notified at least 30 days in advance (see Section 17). Your continued use of Mouve after such modifications constitutes your acceptance of the updated Terms.

<a id="description"></a>

## 2. Description of Service

Mouve is a social fitness network that enables users to:

- Track workouts including exercises, sets, repetitions, and weights
- Log nutrition and track calories and macronutrients
- Scan food using barcode scanning and AI-powered image analysis
- Generate AI-powered meal plans based on dietary preferences
- Monitor fitness progress with statistics and progress photos
- Connect with other users through social features (following, likes, comments, direct messaging)
- Join fitness communities
- Share workouts and fitness content
- Access premium features through paid subscriptions

Mouve is provided as a progressive web application (PWA) that can be installed on various devices and used offline for certain features.

<a id="eligibility"></a>

## 3. Eligibility

To use Mouve, you must:

- Be at least 16 years of age, or the minimum age required under applicable data protection law in your country
- Have the legal capacity to enter into a binding agreement
- Not be prohibited from using the Service under applicable laws
- Not have been previously banned from Mouve

By using Mouve, you represent and warrant that you meet all eligibility requirements. If you are between 16 and 18 years old, you confirm that your parent or legal guardian has reviewed and agrees to these Terms on your behalf.

<a id="account"></a>

## 4. Account Registration and Security

### 4.1 Account Creation

To access most features of Mouve, you must create an account by providing a valid email address or by authenticating through Google or Apple. You agree to provide accurate, current, and complete information during registration.

### 4.2 Account Security

You are responsible for:

- Maintaining the confidentiality of your account credentials
- All activities that occur under your account
- Notifying us immediately of any unauthorized access or security breach

We are not liable for any loss or damage arising from your failure to protect your account credentials.

### 4.3 Username Policy

Your username must not:

- Impersonate another person or entity
- Contain offensive, vulgar, or inappropriate language
- Violate any trademark or intellectual property rights
- Be misleading or deceptive

We reserve the right to reclaim or change usernames that violate these guidelines or are inactive for extended periods.

<a id="user-content"></a>

## 5. User Content

### 5.1 Your Content

“User Content” means any content you create, upload, post, or share through Mouve, including but not limited to workout data, nutrition logs, progress photos, videos, comments, messages, and profile information.

You retain ownership of your User Content. However, by posting User Content on Mouve, you grant us a worldwide, non-exclusive, royalty-free, sublicensable, and transferable license to use, reproduce, modify, adapt, publish, translate, distribute, and display such content solely for the purpose of operating, improving, and promoting the Service.

You are solely responsible for the User Content you upload, post, transmit, or otherwise make available through Mouve. This includes ensuring that you have all necessary rights, licenses, consents, and permissions to use and share that content.

**There is no tolerance for objectionable content or abusive users on Mouve.** By using the Service you agree not to post objectionable content - including any of the categories listed in section 5.2 - and not to harass, threaten, impersonate, or otherwise abuse other users. Objectionable content is removed and the accounts responsible for it are suspended or terminated. We act on reports of objectionable content within 24 hours, and we may remove content and terminate an account without prior notice where the content or behaviour is clearly abusive.

Every user can report content or another user from within the app, and can block any user, which immediately removes that user's content from their view and prevents further interaction. While automated screening runs on uploads and reports are actioned within 24 hours, no moderation system detects every violation before it is seen - which is why reporting and blocking are available on every surface where content appears.

### 5.2 Prohibited Content (DSA Compliance)

In accordance with the Digital Services Act (Regulation (EU) 2022/2065), the following categories of content are prohibited on Mouve:

- **Illegal content under EU or Member State law:** Any content that constitutes a criminal offense or infringes applicable laws
- **Child sexual abuse material (CSAM):** Any sexual or exploitative content involving minors - reported immediately to law enforcement
- **Terrorist content:** Content that incites, glorifies, or supports terrorism as defined under Regulation (EU) 2021/784
- **Hate speech:** Content that incites violence or hatred against individuals or groups based on protected characteristics (race, ethnicity, religion, gender, sexual orientation, disability)
- **Intellectual property infringement:** Content that infringes third-party copyright, trademark, publicity, privacy, or other intellectual property or proprietary rights
- **Harassment and bullying:** Targeted harassment, threats, doxxing, or coordinated abuse of other users
- **Explicit sexual content:** Pornographic, sexually explicit, or sexually exploitative content that is not appropriate for a general fitness and wellness platform
- **Dangerous health misinformation:** Content promoting eating disorders, dangerous supplements, or unproven health treatments
- **Fraudulent or deceptive content:** Content intended to scam, mislead, or defraud other users, including impersonation, phishing, or deceptive promotions
- **Spam and manipulation:** Unsolicited commercial messages, coordinated inauthentic behavior, or engagement manipulation

### 5.3 Content Moderation

In compliance with the Digital Services Act, Mouve moderates content as follows:

- Content is reviewed through a combination of automated tools and human review
- When content is removed or restricted, you will receive a **statement of reasons** explaining: the specific rule violated, the facts and circumstances, and the legal basis for the action
- You have the right to appeal any moderation decision (see Section 6)
- We may publish transparency information or reports regarding content moderation as required by applicable law or at our discretion

We may remove, restrict, or disable access to any content that we reasonably believe violates these Terms, applicable law, or poses a risk to the safety of users or the integrity of the Service. Automated systems may assist moderation, but final enforcement decisions may involve human review.

Mouve is not subject to any general obligation to monitor information that users transmit or store through the Service, nor to actively seek facts or circumstances indicating illegal activity. However, we may carry out voluntary investigations and take reasonable measures to detect, identify, remove, or restrict illegal content or content that violates these Terms, in accordance with applicable law.

<a id="photo-licence"></a>

### 5.4 Content You Contribute (Photos)

This section applies in particular to photos you add to Mouve, such as photos of outdoor gyms and equipment in Mouve World, and adds detail to Section 5.1.

- **You keep ownership.** Mouve does not claim ownership of your photos. You keep your copyright.
- **Licence to Mouve.** You grant Mouve a worldwide, non-exclusive, royalty-free, transferable and sublicensable licence to host, store, reproduce, modify for display (for example resize, crop, or blur faces and licence plates), publish and display the photo in Mouve's services and in the promotion of those services. The licence is non-exclusive: you remain free to use your photo anywhere else and to license it to others.
- **How long.** The licence lasts while the photo is on Mouve, plus the reasonable period needed for backups and caches to expire, and any period we are legally required to keep it.
- **Your confirmations.** By uploading you confirm that you took the photo or otherwise have the right to upload it and to grant this licence, and that any identifiable person in it has agreed to its publication.
- **Credit.** Photos are shown with a copyright line naming you (“© @username”), or “© Mouve user” if your profile is private.
- **No reuse by others without permission.** Photos on Mouve belong to the people who took them. Other users and third parties may not copy, download for reuse, republish or otherwise use them without the owner's permission, except as these Terms or the law allow.
- **Deleting.** You can delete your photo from the photo view in the app at any time, or delete your account (Section 16). Once deleted, we stop showing it and remove it from our systems, subject to the backup and legal periods above. Copies others made lawfully before deletion are outside our control.
- **Removal by Mouve.** We may remove a photo that we reasonably believe breaks these Terms, infringes rights or the law, or may harm others, as described in Section 5.3. To report a photo that infringes your copyright, see Section 11.3.

<a id="content-reporting"></a>

## 6. Content Reporting and Appeals (DSA)

In accordance with the Digital Services Act (DSA), Mouve provides mechanisms for reporting illegal content and appealing moderation decisions. Users may submit notices regarding illegal content under EU or Member State law using the reporting mechanisms described below.

### 6.1 Reporting Content

- You can report any content you believe violates these Terms or applicable law using the in-app reporting mechanism (available on every post, comment, and profile)
- Reports can also be submitted via email to [reports@mouve.it](mailto:reports@mouve.it)
- Reports should include: a description of the issue, a link or reference to the content, and the reason you believe it violates our policies or the law

### 6.2 Report Processing

- You will receive an acknowledgment of your report without undue delay
- Reports are reviewed in a timely, non-arbitrary, and objective manner
- Submission of a report does not guarantee removal of the reported content where we determine that it does not violate applicable law or these Terms
- We aim to resolve reports within 7 business days, though complex cases may take longer
- You will be notified of the outcome of your report and the action taken (if any)

### 6.3 Statement of Reasons

When we take action against content or an account (removal, restriction, suspension), we provide a clear statement of reasons that includes:

- The specific term or rule that was violated
- The facts and circumstances leading to the decision
- Whether automated tools were used in the decision
- Information about the right to appeal

### 6.4 Appeals Process

- You may appeal any moderation decision within 6 months of receiving the statement of reasons
- Appeals can be submitted through the in-app appeals mechanism or via email to [appeals@mouve.it](mailto:appeals@mouve.it)
- Appeals are free of charge and are reviewed by a qualified human moderator who was not involved in the original decision
- You will be notified of the appeal outcome without undue delay

### 6.5 Out-of-Court Dispute Settlement

If you are not satisfied with the outcome of an appeal, you may refer the dispute to a certified out-of-court dispute settlement body under DSA Article 21. You may also lodge a complaint with your national Digital Services Coordinator. More information about available dispute settlement bodies will be provided in the statement of reasons.

<a id="acceptable-use"></a>

## 7. Acceptable Use Policy

When using Mouve, you agree not to:

- Use the Service for any illegal purpose or to violate any laws
- Harass, bully, intimidate, or threaten other users
- Impersonate any person or entity
- Access or interact with the Service by any automated means — including bots, scripts, scrapers, or crawlers — except through the authorized Mouve API as described in Section 7.1
- Attempt to gain unauthorized access to our systems or other users' accounts
- Interfere with or disrupt the Service or servers
- Collect or harvest user information without consent
- Use the Service to send unsolicited messages or advertisements
- Circumvent, disable, or interfere with security features
- Reverse engineer, decompile, or disassemble any part of the Service
- Use the Service in any way that could damage our reputation
- Abuse reporting or moderation systems by submitting knowingly false or malicious reports
- Encourage or enable any other person to do any of the above

### 7.1 Authorized API Access

Automated access to the Service is permitted solely through the official Mouve API, using credentials issued by Mouve: either an application you have authorized through Mouve's OAuth consent flow, or a personal access token you created for your own account. Such access must stay within the scopes you (or the account holder) granted and within the rate limits Mouve publishes, and is subject to the following:

- If you build or operate an application, agent, or integration that accesses the Mouve API, you are additionally bound by the [Mouve Developer Terms](/legal/developer-terms). If you connect a third-party application or AI agent to your own account, that connection is governed by the [connected-app terms](/legal/mcp-terms) in addition to these Terms.
- API credentials are personal to the account or application they were issued to. You may not share, sell, or transfer access tokens, ask other users for their tokens, or use credentials issued to someone else.
- Scraping, harvesting, or bulk collection of content or user information by any means other than the authorized API remains prohibited — including for content that is publicly viewable without an account.
- Content created through the API is User Content under Sections 5 and 6 of these Terms: the same content rules, moderation processes, and appeal rights apply, and you remain responsible for content an application posts with your authorization.
- Mouve may throttle, suspend, or revoke automated access at any time to protect the Service and its users, and may change or withdraw the API as described in the Mouve Developer Terms.

<a id="ai-features"></a>

## 8. AI Features

IMPORTANT: AI Features Are Not Medical Advice

All AI-generated content on Mouve is provided “as-is” and is approximate. AI features do not constitute medical, nutritional, or dietary advice. AI-generated outputs may be produced by automated systems without human review. Always consult a qualified healthcare professional for personalized guidance.

Certain features of Mouve use artificial intelligence systems to generate or analyze content. When you use these features, you are interacting with automated AI systems rather than human experts. These systems may produce inaccurate or incomplete results and should not be relied upon as professional advice.

### 8.1 Available AI Features

- **Food Image Scanning:** Uses GPT-4o Vision (OpenAI) to analyze photographs of food and estimate nutritional content including calories, protein, carbohydrates, and fats
- **Food Log Text Parsing:** Uses GPT-4o-mini (OpenAI) to parse natural language food descriptions into structured nutritional data
- **AI Meal Planning:** Uses GPT-4o-mini (OpenAI) to generate meal plan suggestions based on your stated dietary preferences and nutritional goals
- **AI Workout Generation:** Uses GPT-4o-mini (OpenAI) to generate structured workout routines from natural language descriptions of your training goals
- **Progress Insights:** Uses GPT-4o-mini (OpenAI) to analyze your workout and nutrition history and generate personalized progress summaries and recommendations

### 8.2 Data Sent to AI Providers

- **Food scanning:** The food image you capture and a text prompt requesting analysis. No name, email, or account data is included.
- **Food log parsing:** The text description of food you enter. No images or identifying account data is included.
- **Meal planning:** Text prompts containing your calorie targets, macro goals, and food preferences. No images or identifying account data is included.
- **Workout generation:** Your natural language description of training goals. No identifying account data is included.
- **Progress insights:** Aggregated workout and nutrition history data for the selected time period. No identifying account data is included.

For full details on AI data processing, see our [Privacy Policy](/privacy-policy) (Sections 8.3 and 10).

### 8.3 Accuracy Limitations

- Nutritional estimates from food scanning are **approximations** and may vary significantly from actual values
- AI models may misidentify foods, misjudge portion sizes, or fail to detect all ingredients
- Meal plans do not account for medical conditions, medication interactions, or allergies not explicitly stated by you
- Generated workouts may not be suitable for your fitness level, physical limitations, or injury history — always consult a qualified professional before starting a new exercise routine
- Progress insights are based on the data you have logged and may not reflect your complete fitness picture
- AI outputs may be incomplete, misleading, or unsuitable for your health, fitness level, or dietary needs
- AI outputs may reflect biases present in training data, including regional food biases
- Progress insights are generated automatically based solely on the data you choose to log and do not involve automated decisions affecting your rights or account

### 8.4 User Responsibility

- You must verify AI-generated nutritional information independently, especially for medical or dietary needs
- You should not rely solely on AI-generated meal plans for dietary decisions
- AI-generated workouts are not a substitute for professional training advice — you exercise at your own risk and should assess whether any suggested routine is appropriate for your ability
- You are responsible for ensuring exercises are performed safely and with appropriate supervision where necessary
- If you have food allergies, intolerances, or medical conditions, consult a healthcare professional

### 8.5 Opt-In Nature

All AI features on Mouve are **opt-in**. You are never required to use AI food scanning, meal planning, workout generation, or progress insights. You can log nutrition manually, use barcode scanning, search our food database, and build workouts from our exercise library without interacting with any AI features. If you choose not to use AI features, no data is sent to AI providers.

### 8.6 Service Evolution

Mouve is an evolving service. Features, including AI functionality, may change, improve, or be discontinued over time. We will notify you of material changes in accordance with Section 15 of these Terms.

<a id="premium"></a>

## 9. Premium Subscriptions and Payments

### 9.1 Premium Features

Mouve offers premium subscription plans that provide access to additional features. The specific features and pricing are described on our pricing page and may change from time to time.

### 9.2 Payment Processing

All payments are processed securely through Stripe. By subscribing to a premium plan, you agree to Stripe's terms of service. We do not store your payment card details directly.

### 9.3 Subscription Terms

- Subscriptions are billed in advance on a recurring basis (monthly or annually)
- Your subscription will automatically renew unless you cancel before the renewal date
- Prices are displayed inclusive of applicable taxes (VAT) for EU customers
- We reserve the right to change subscription prices with 30 days' notice

### 9.4 Cancellation, Withdrawal, and Refunds

You may cancel your subscription at any time through your account settings or the Stripe customer portal. Upon cancellation:

- You will retain access to premium features until the end of your current billing period
- No refunds will be provided for partial billing periods
- You will not be charged for subsequent billing periods

EU Consumer Right of Withdrawal (Directive 2011/83/EU)

If you are a consumer in the European Union, you have the right to withdraw from your subscription purchase within **14 days** without giving any reason, in accordance with Directive 2011/83/EU on consumer rights.

To exercise this right, contact us at [support@mouve.it](mailto:support@mouve.it) with a clear statement of your decision to withdraw.

**Digital content exception:** If you have expressly consented to the provision of digital content (premium features) during the withdrawal period and acknowledged that you lose your right of withdrawal once the digital content delivery has begun, the withdrawal right may not apply. This consent is collected separately at the point of purchase.

If withdrawal applies and you have used premium features during the withdrawal period, we may deduct a proportionate amount from your refund corresponding to the services provided.

### 9.5 Feature Limitations

Certain features may have usage limits (e.g., food scanning limits). These limits reset periodically and are described within the Service.

<a id="third-party"></a>

## 10. Third-Party Services

### 10.1 OpenAI

Several features use OpenAI's API, including food image scanning (GPT-4o Vision), food log text parsing, meal planning, workout generation, and progress insights (all GPT-4o-mini). All AI-generated outputs are approximate and should not be relied upon for medical purposes. You acknowledge that:

- AI-generated nutritional information and workout routines may not be 100% accurate or suitable for your individual circumstances
- Data you submit (food images, text descriptions, training goals, and aggregated activity history) is processed by OpenAI according to their terms
- You should verify nutritional information for medical or dietary needs and consult a qualified professional before following AI-generated workout routines

AI services used by Mouve rely on third-party providers. Mouve is not responsible for errors, omissions, or limitations of these external systems.

### 10.2 Open Food Facts

Barcode scanning retrieves product information from Open Food Facts, a collaborative database. We do not guarantee the accuracy or completeness of this data.

### 10.3 Third-Party Links

The Service may contain links to third-party websites or services. We are not responsible for the content, privacy practices, or availability of these external sites.

<a id="intellectual-property"></a>

## 11. Intellectual Property

### 11.1 Our Intellectual Property

The Service, including its design, features, code, graphics, logos, and trademarks (“Mouve Materials”), is owned by Mouve and protected by intellectual property laws. You may not copy, modify, distribute, sell, or lease any part of Mouve Materials without our express written permission.

### 11.2 Limited License

We grant you a limited, non-exclusive, non-transferable, revocable license to access and use the Service for your personal, non-commercial purposes in accordance with these Terms.

### 11.3 Copyright Responsibility

Mouve does not claim ownership of third-party copyrighted materials uploaded by users and is not responsible for copyrighted content uploaded, posted, or shared by users through the Service. The user who uploads or shares such content is solely responsible for ensuring they have the legal right to do so and may be held liable for any infringement or other violation of law.

We reserve the right to remove or disable access to content alleged or reasonably believed to infringe intellectual property rights, and to suspend or terminate repeat infringers' accounts.

### 11.4 Feedback

If you provide us with feedback, suggestions, or ideas about the Service, you grant us the right to use such feedback without any restriction or compensation to you.

<a id="health-disclaimer"></a>

## 12. Health and Fitness Disclaimer

IMPORTANT NOTICE:

Mouve is a fitness tracking and social platform, not a medical service. The information provided through Mouve, including workout suggestions, AI-generated workout routines, nutritional information, AI-generated meal plans, progress insights, and progress tracking, is for general informational purposes only and is not intended as medical advice.

- Always consult a qualified healthcare professional before starting any new exercise or nutrition program
- Mouve does not provide medical diagnoses, treatment recommendations, or professional health advice
- Mouve does not monitor your health status and cannot guarantee that workouts or nutrition recommendations are safe for your individual circumstances
- Nutritional calculations, calorie estimates, and AI-generated workout routines are approximations and suggestions that may not be accurate or appropriate for your specific needs
- You are solely responsible for your health decisions and physical activities
- Stop any exercise immediately if you experience pain, dizziness, or discomfort
- If you have any medical conditions, injuries, or concerns, consult your doctor before using fitness tracking features

By using Mouve, you acknowledge that you are participating in fitness activities at your own risk.

<a id="disclaimers"></a>

## 13. Disclaimers

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW:

We may modify, suspend, or discontinue features or functionality of the Service at any time, including for maintenance, security, or product improvements.

- THE SERVICE IS PROVIDED “AS IS” AND “AS AVAILABLE” WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE
- WE DISCLAIM ALL WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT
- WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, SECURE, OR ERROR-FREE
- WE DO NOT WARRANT THE ACCURACY, RELIABILITY, OR COMPLETENESS OF ANY INFORMATION PROVIDED THROUGH THE SERVICE, INCLUDING AI-GENERATED CONTENT

These disclaimers do not affect your statutory rights as a consumer under EU law, which cannot be waived or limited by contract.

<a id="liability"></a>

## 14. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW:

- WE SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING LOSS OF PROFITS, DATA, GOODWILL, OR OTHER INTANGIBLE LOSSES
- OUR TOTAL LIABILITY FOR ANY CLAIMS ARISING FROM OR RELATED TO THE SERVICE SHALL, TO THE MAXIMUM EXTENT PERMITTED BY LAW, NOT EXCEED THE AMOUNT YOU PAID US IN THE 12 MONTHS PRECEDING THE CLAIM, OR €100, WHICHEVER IS GREATER
- WE ARE NOT LIABLE FOR ANY DAMAGE OR LOSS RESULTING FROM YOUR USE OF THIRD-PARTY SERVICES OR CONTENT, INCLUDING AI-GENERATED CONTENT

Nothing in these Terms excludes or limits our liability for death or personal injury caused by our negligence, fraud, or fraudulent misrepresentation, or any other liability that cannot be excluded or limited by law.

<a id="indemnification"></a>

## 15. Indemnification

You agree to indemnify, defend, and hold harmless Mouve, its officers, directors, employees, and agents from and against any claims, liabilities, damages, losses, and expenses (including reasonable legal fees) arising out of or in any way connected with: (a) your access to or use of the Service; (b) your User Content, including any allegation that such content infringes copyright, trademark, privacy, publicity, or other rights of a third party; (c) your violation of these Terms; or (d) your violation of any third-party rights.

<a id="termination"></a>

## 16. Termination

### 16.1 Termination by You

You may terminate your account at any time by deleting your account through the Settings page in the app. Upon deletion, your profile, workout data, nutrition logs, messages, and uploaded media will be deleted or anonymized, except where retention is required by law.

### 16.2 Termination by Us

We may suspend or terminate your account and access to the Service where we reasonably believe these Terms have been violated, where required by law, or where necessary to protect the integrity or security of the Service, including but not limited to:

- Violation of these Terms
- Conduct that we determine is harmful to other users or our business
- Extended periods of inactivity, where permitted by applicable law and following reasonable notice to you
- Suspected fraud, abuse, or security threats affecting the Service
- Request by law enforcement or government agencies

In all cases, you will receive a statement of reasons explaining the basis for suspension or termination, and information about how to appeal the decision, in accordance with the Digital Services Act.

### 16.3 Effect of Termination

Upon termination, your right to use the Service will immediately cease. Sections of these Terms that by their nature should survive termination will survive, including intellectual property provisions, disclaimers, limitations of liability, and dispute resolution provisions.

<a id="material-changes"></a>

## 17. Material Changes to Terms

We will notify you at least **30 days before** any material changes to these Terms take effect. Notification will be provided through:

- Email to the address associated with your account
- In-app notification
- A prominent notice on the Service

If you do not agree with the updated Terms, you may delete your account before the changes take effect. Your continued use of Mouve after the 30-day notice period constitutes acceptance of the updated Terms.

Non-material changes (e.g., corrections, formatting) may be made without advance notice but will be reflected in the updated version number and changelog below.

<a id="governing-law"></a>

## 18. Governing Law and Dispute Resolution

### 18.1 Governing Law

These Terms shall be governed by and construed in accordance with the laws of Estonia, without prejudice to mandatory consumer protection laws in the country where you reside. If you are a consumer in the European Union, you may bring legal proceedings in the courts of your country of residence and will benefit from any mandatory provisions of the law of that country.

### 18.2 Dispute Resolution

We encourage you to contact us first at support@mouve.it to resolve any disputes amicably. If we cannot resolve a dispute informally:

- **For EU Consumers:** You may seek redress through any available consumer dispute resolution mechanism under applicable EU or Member State law. You may also bring legal proceedings in the courts of your country of residence.
- **For Other Users:** Any disputes shall be submitted to the exclusive jurisdiction of the courts of Estonia, unless applicable law provides otherwise.

### 18.3 Class Action Waiver

To the extent permitted by applicable law, you agree to resolve any disputes on an individual basis and waive your right to participate in class action lawsuits or class-wide arbitration. This waiver does not affect your rights under the Representative Actions Directive (EU) 2020/1828, which allows qualified entities to bring representative actions on behalf of consumers.

<a id="general-provisions"></a>

## 19. General Provisions

### 19.1 Entire Agreement

These Terms, together with our Privacy Policy, constitute the entire agreement between you and Mouve regarding the Service and supersede all prior agreements and understandings.

### 19.2 Severability

If any provision of these Terms is found to be invalid or unenforceable, that provision shall be limited or eliminated to the minimum extent necessary, and the remaining provisions shall remain in full force and effect.

### 19.3 Waiver

Our failure to enforce any right or provision of these Terms shall not constitute a waiver of such right or provision.

### 19.4 Assignment

You may not assign or transfer your rights or obligations under these Terms without our prior written consent. We may assign our rights and obligations without restriction.

### 19.5 Force Majeure

We shall not be liable for any failure or delay in performing our obligations due to circumstances beyond our reasonable control, including natural disasters, acts of government, pandemics, or technical failures.

<a id="contact"></a>

## 20. Contact Information

If you have any questions about these Terms of Service, please contact us:

**General Support:** [support@mouve.it](mailto:support@mouve.it)
**Privacy Inquiries:** [privacy@mouve.it](mailto:privacy@mouve.it)
**Content Reports:** [reports@mouve.it](mailto:reports@mouve.it)
**Appeals:** [appeals@mouve.it](mailto:appeals@mouve.it)

<a id="dsa-contact"></a>

## 21. Digital Services Act Contact Point

In accordance with Articles 11 and 12 of the Digital Services Act (Regulation (EU) 2022/2065), Mouve designates the following single point of contact for users and authorities regarding matters related to the Digital Services Act.

**DSA Contact Email:** [dsa@mouve.it](mailto:dsa@mouve.it)

<a id="service-provider"></a>

## 22. Service Provider

Mouve is operated by Mouve Technology OÜ, a company registered in Estonia.

**Registered Address:** Sõpruse pst 8-31, Kristiine linnaosa, 10615 Tallinn, Harju maakond
**Country:** Estonia
**Contact:** [support@mouve.it](mailto:support@mouve.it)

<a id="changelog"></a>

## Changelog

| Version | Date | Changes |
| --- | --- | --- |
| v1.0 | January 24, 2026 | Initial version |
| v2.0 | February 27, 2026 | Added DSA-compliant prohibited content categories and content moderation procedures (Section 5.2, 5.3). Added content reporting and appeals process (Section 6). Added AI features section with model details, accuracy limitations, and opt-in disclosure (Section 8). Strengthened EU consumer withdrawal rights with Directive 2011/83/EU reference (Section 9.4). Added 30-day notice requirement for material changes (Section 17). Added DSA statement of reasons to termination (Section 16.2). Versioning added. |
| v3.0 | March 7, 2026 | Broadened eligibility age wording for multi-jurisdiction compliance (Section 3). Added uploader responsibility, no-guarantee disclaimer, and no general monitoring obligation (Section 5.1, 5.3). Added explicit sexual content and fraudulent content to prohibited categories (Section 5.2). Added discretionary content removal and DSA no-monitoring clause (Section 5.3). Added no-guarantee-of-removal to report processing (Section 6.2). Added false reporting abuse to acceptable use (Section 7). Added AI automated output transparency notice (Section 8). Added service availability clause (Section 13). Added health monitoring disclaimer (Section 12). Strengthened liability cap with “to the maximum extent permitted by law” (Section 14). Expanded indemnification to cover IP infringement claims (Section 15). Safer account deletion wording with anonymization (Section 16.1). Scoped termination to reasonable belief of violation, added fraud/security ground, softened inactivity clause (Section 16.2). Estonian governing law with consumer protection carve-out, replaced outdated ODR reference, specified Estonian courts for non-EU users (Section 18). Added Section 11.3 Copyright Responsibility, renumbered 11.3 Feedback to 11.4. Added DSA Contact Point (Section 21). Added Service Provider with registered address (Section 22). Two-column layout with sidebar navigation. |
| v3.1 | March 7, 2026 | Added Food Log Text Parsing, AI Workout Generation, and Progress Insights to AI features list (Section 8.1). Updated data sent to AI providers (Section 8.2). Added “outputs may be unsuitable” and profiling clarification for progress insights to accuracy limitations (Section 8.3). Added exercise safety responsibility (Section 8.4). Added service evolution clause (Section 8.6). Added provider liability separation (Section 10.1). Narrowed user content license to purpose-limited use (Section 5.1). Added automated tools and human review to moderation (Section 5.3). Updated health disclaimer to include AI-generated workouts and progress insights (Section 12). |
| v3.2 | August 30, 2026 | Replaced the blanket ban on automated access with an authorized-API exception and added Section 7.1 (Authorized API Access): automation is permitted only through the official Mouve API with issued credentials, within granted scopes and published rate limits, under the Mouve Developer Terms and the connected-app terms. Scraping outside the API remains prohibited, including for publicly viewable content. API-created content is User Content under Sections 5–6. |

---

<!-- document: cookie-policy | version: 2.0 | effective: 2026-10-14 -->
Document: cookie-policy
Version: 2.0
Effective: 2026-10-14
Canonical: https://mouve.it/cookie-policy
Markdown: https://mouve.it/cookie-policy.md

# Cookie Policy

Version 2.0 | Last updated: October 14, 2026 | Effective: October 14, 2026

<a id="introduction"></a>

## 1. Introduction

This Cookie Policy explains how Mouve (“we,” “our,” or “us”) uses cookies and similar technologies when you visit our website at mouve.it or use the Mouve web application on our domains (the “Service”).

This policy should be read alongside our [Privacy Policy](/privacy-policy), which provides further details on how we process your personal data.

<a id="what-are-cookies"></a>

## 2. What Are Cookies?

Cookies are small text files that are stored on your device (computer, tablet, or mobile) when you visit a website. They are widely used to make websites work efficiently and to provide information to site owners.

Similar technologies include local storage and session storage, which allow websites to store data locally on your device. Under EU law, the same rules that apply to cookies also apply to these technologies (ePrivacy Directive Article 5(3)).

<a id="our-approach"></a>

## 3. Our Approach

We sort everything we store on your device into three groups, and treat them differently:

- **Strictly necessary** — always on. They keep you signed in, keep the service secure and remember your choices, and fall within the exemption in Article 5(3) of the ePrivacy Directive, so they do not need your consent.
- **Analytics** — only if you opt in. Our own analytics (PostHog, run by us in the EU): an identifier stored on your device, which clicks and form fields are used (never the text), and masked session replays. Nothing is shared with anyone. See Privacy Policy Section 3.8.
- **Advertising measurement**— only if you opt in. Scripts and cookies of Meta, TikTok and Google on our public pages, so we can measure our ads. See Privacy Policy Section 3.9.

**Before you choose, nothing optional runs** in your browser and nothing optional is stored on your device. When you first visit, a banner offers three equally prominent buttons: *Reject all*, *Choose* and*Accept all*. Both optional groups start switched off. Closing the page without answering is not consent.

One thing happens without a cookie: when you open any of our public pages, our server counts the visit anonymously (page, campaign tags, referring website, country, kind of device, and a one-way code that changes every 24 hours so we can estimate how many different people visited that day). No script runs in your browser, nothing is stored on your device and the count cannot be linked to you (Privacy Policy Section 3.8). The same goes for a tap on an App Store or Google Play button: the link passes through our server, which counts the tap and sends you on to the store, and nothing is stored on your device.

**Changing your mind** is as easy as choosing: use *Cookie settings* in the footer of our pages, or Settings → Privacy in the app. Withdrawing Analytics stops recording and resets the identifier. Withdrawing Advertising measurement deletes the platform cookies and, if a platform script had already loaded, reloads the page so that it is gone.

Your choice is remembered for 12 months and recorded together with the version of this policy that you saw; when this policy changes in substance we ask again. If you are signed in, your choice is also recorded on your account, so a new device does not ask a second time.

<a id="cookies-we-use"></a>

## 4. Cookies We Use

Every cookie that Mouve or the services you opt in to set on mouve.it is listed here:

| Name | Purpose | Party | Type | Duration | Category |
| --- | --- | --- | --- | --- | --- |
| `mouve_session_v2` | Keeps you signed in: an opaque session identifier (not your name or email). Set when you sign in. | First-party | Cookie, HttpOnly, Secure, SameSite=Lax | Up to 30 days, extended while you use the app | Strictly necessary |
| `pkce_code_verifier`, `oauth_state` | Protect the “Sign in with Google / Apple” flow against forgery. Deleted when the sign-in completes. | First-party | Cookie, HttpOnly, Secure, SameSite=Lax | 10 minutes | Strictly necessary |
| `mouve_ref` | Remembers the invitation or referral code of the link you opened, so the person who invited you is credited when you sign up. Set only if you open such a link. | First-party | Cookie, SameSite=Lax | 7 days | Strictly necessary (for the invitation link you opened) |
| `mouve_consent_v1` | Remembers your choice in the cookie banner (analytics, advertising, the version of this policy you saw, the time). | First-party | Cookie, SameSite=Lax, Secure | 12 months, then we ask again | Strictly necessary |
| `mouve_attr_v1` | Remembers which campaign or link first and last brought you here: the UTM tags, referral code, referring website (domain only) and landing page. Advertising click identifiers are included only if you accepted Advertising measurement. Written only if you accepted Analytics or Advertising; never read before. | First-party | Cookie, SameSite=Lax, Secure | 90 days | Analytics or Advertising (your consent) |
| `ph_<token>_posthog`, `__ph_opt_in_out_<token>` | Our own analytics (PostHog, run by us in the EU): an identifier so we can recognise returning visits, and a marker of your analytics choice. Set only if you accepted Analytics. | First-party | Cookie (the identifier is also kept in local storage, below) | Up to 12 months | Analytics (your consent) |
| `_fbp`, `_fbc` | Meta Pixel: a browser identifier and, if you arrived from a Meta ad, the ad click. Set on our domain by Meta's script, which runs only on our public pages, only while you are signed out, and only if you accepted Advertising measurement. | First-party cookie set by Meta Platforms Ireland Limited's script | Cookie, SameSite=Lax | 90 days | Advertising (your consent) |
| `_ttp`, `_tt_enable_cookie` | TikTok Pixel: a browser identifier and a marker that cookies are enabled. Same conditions as Meta's. | First-party cookie set by TikTok Technology Limited's script | Cookie, SameSite=Lax | About 13 months (`_ttp`); about 13 months (`_tt_enable_cookie`) | Advertising (your consent) |
| `_gcl_au`, `_gcl_aw`, `_gcl_gb`, `_gcl_dc` | Google Ads conversion linker: ad-click identifiers and the information needed to attribute a sign-up to the ad. Same conditions as Meta's. We do not use Google Analytics. | First-party cookie set by Google Ireland Limited's script | Cookie, SameSite=Lax | 90 days | Advertising (your consent) |

The session cookie is set with the`HttpOnly`,`Secure` and`SameSite=Lax` attributes. It is scoped to our domain so that our API (api.mouve.it) can read it; it is never sent to any other party.

### 4.1 Cookies set by the advertising platforms themselves

If you accept Advertising measurement, the platforms' scripts contact their own servers, which may set cookies on their own domains. We do not control these cookies; their duration and purpose are set by each platform (see their policies, linked from the Privacy Policy). They appear only on our public pages, while you are signed out.

| Name | Purpose | Party | Type | Duration | Category |
| --- | --- | --- | --- | --- | --- |
| `fr` and similar | Meta's advertising cookie on facebook.com, set when the Meta script contacts Meta. | Third-party (Meta Platforms Ireland Limited) | Cookie on facebook.com | Set by Meta, up to 90 days; see Meta's policy | Advertising (your consent) |
| TikTok cookies | TikTok's own cookies on tiktok.com, set when the TikTok script contacts TikTok. | Third-party (TikTok Technology Limited) | Cookie on tiktok.com | Set by TikTok; see TikTok's policy | Advertising (your consent) |
| `IDE`, `test_cookie` and similar | Google's advertising cookies on doubleclick.net and google.com, set when the Google tag contacts Google. | Third-party (Google Ireland Limited) | Cookie on doubleclick.net / google.com | Set by Google, up to 13 months; see Google's policy | Advertising (your consent) |

<a id="local-storage"></a>

## 5. Local Storage

In addition to cookies, Mouve uses browser local and session storage for the following purposes:

| Key | Purpose | Category |
| --- | --- | --- |
| localStorage: `ph_<token>_posthog` | The analytics identifier and its settings (same data as the cookie of that name). Only if you accepted Analytics. | Analytics (your consent) |
| sessionStorage: `ph_<token>_window_id` | A per-tab window identifier for analytics. Cleared when the tab closes. Only if you accepted Analytics. | Analytics (your consent) |
| localStorage: `sidebar-visibility`, `theme`, `mouve:lastConversationId` | Remembers whether the sidebar is pinned and which conversation you last had open. | Strictly necessary (a setting you chose) |
| sessionStorage: `mouve:feedScroll`, `mouve:skipRestore`, `mouve_pending_subscription`, `auth_pending`, `mouve:stale-deployment-reload-at` | Short-lived navigation and sign-in state: your scroll position, an in-progress checkout or sign-in, and a one-time reload after an update. Cleared when the tab closes. | Strictly necessary |
| PWA offline data (service worker cache) | Caches the app's own files for faster, offline-capable loading. | Strictly necessary |

<a id="managing-cookies"></a>

## 6. Managing Cookies

**In Mouve:** open*Cookie settings* (the link in the footer of our pages) or Settings → Privacy to switch Analytics and Advertising measurement on or off at any time. Reject all stores your refusal and we do not ask again for 12 months.

**In your browser:** you can also control and delete cookies through your browser settings. Most browsers allow you to:

- View what cookies are stored and delete them individually
- Block third-party cookies (the platform cookies in Section 4.1)
- Block all cookies from specific or all sites
- Delete all cookies when you close your browser

Please note that if you block or delete our strictly necessary cookies, the Service may not function correctly — you will not be able to stay logged in, and we will have to ask for your cookie choice again.

<a id="changes"></a>

## 7. Changes to This Policy

We may update this Cookie Policy from time to time. If we make material changes, we will notify you by updating the date at the top of this page. A change in substance also asks for your cookie choice again, because your consent is tied to the version you saw.

| Version | Date | Changes |
| --- | --- | --- |
| 1.0 | March 2, 2026 | Initial cookie policy published |
| 1.1 | March 7, 2026 | Corrected authentication cookie names to reflect chunked cookie format; added security attributes disclosure; improved ePrivacy exemption wording; added first-party column to cookie table |
| 2.0 | October 14, 2026 | Cookie banner with separate choices for Analytics and Advertising measurement, and a Cookie settings link. Nothing optional runs before a choice. Our own analytics may store an identifier and record masked replays after opt-in. Meta, TikTok and Google Ads pixels on our public pages after opt-in. Cookie table now lists every cookie and storage entry, with the correct session cookie name and duration (replacing the earlier sb-<project-ref> entries) and the third-party cookies the platforms set. Anonymous server-side visit count described. |

<a id="contact-us"></a>

## 8. Contact Us

If you have questions about this Cookie Policy, please contact us:

**Mouve**
Email: [privacy@mouve.it](mailto:privacy@mouve.it)

---

<!-- document: community-guidelines | version: 1.0 | effective: 2026-04-17 -->
Document: community-guidelines
Version: 1.0
Effective: 2026-04-17
Canonical: https://mouve.it/community-guidelines
Markdown: https://mouve.it/community-guidelines.md

# Community Guidelines

Version 1.0 | Last updated: April 17, 2026 | Effective: April 17, 2026

<a id="introduction"></a>

Mouve is a fitness and nutrition social network. These guidelines describe what is welcome here and what is not, in enough detail that our reviewers and our automated moderation system can apply them consistently. The anchor IDs on the sections below (`#nudity`, `#eating-disorders`, and so on) are stable identifiers used in statement-of-reasons notices and appeal flows — you may receive a link to one of them explaining a decision on your content.

Our posture is to act gently on first marginal violations (interstitial, reach limit, content warning) so users can learn. We escalate for repeat offenders and act without warning on illegal content.

<a id="nudity"></a>

## Nudity and sexual content

Do not post sexual, pornographic, or sexually suggestive content. Progress photos showing a body in athletic wear (swimsuit, compression shorts, crop top, posing trunks, stage bikini for physique athletes) are allowed because this is a fitness network — you need to show body composition to discuss training.

Not allowed: genitals, nipples for female-presenting users outside of medical or educational context, simulated sex acts, any content that sexualises a minor, and framing that clearly aims for arousal rather than athletic documentation (close-ups of bulges, explicit captions, solicitation). When a post straddles the line we weigh context heavily — a full-body bodybuilding stage photo is fine, the same cropped to the genital region is not.

Repeated violations lead to account-level reach limits. Content that sexualises a minor is always removed and reported to the appropriate authority.

<a id="eating-disorders"></a>

## Eating disorders

Do not promote anorexia, bulimia, extreme fasting, laxative or diuretic abuse, purging, or any behaviour that treats severe caloric restriction or unhealthy weight loss as aspirational. Recovery content, medically supervised cuts, and honest discussion of disordered-eating history are welcome — the line is between sharing a struggle and encouraging others to enter one.

Banned: pro-ana imagery, “thinspiration” captions, body-check posts explicitly praising visible ribs or hipbones as a goal state, step-by-step guides to hiding disordered eating from loved ones.

We prefer soft actions here: age or consent warnings, crisis resource links shown before the post renders. Repeat or severe cases are removed. If a post also contains self-harm content we apply the self-harm policy in addition.

<a id="performance-enhancers"></a>

## Performance-enhancing drugs

Do not promote, sell, or give dosing or source advice for anabolic steroids, SARMs, prescription-only peptides (HGH, IGF-1), clenbuterol, DNP, insulin for non-diabetic body-composition use, or any substance requiring a prescription you do not lawfully hold.

Natural supplements (protein, creatine, caffeine, legal pre-workouts) are fine. Honest disclosure that you personally use PEDs is also fine — we do not force users to lie about their own bodies.

Removal is swift for links to grey-market suppliers, coaching services built around prescribing PEDs, cycle calculators presented as beginner guides, and anything of this kind targeted at minors. The physical harm to readers is high and latent, so we do not wait for a second strike.

<a id="coach-promotion"></a>

## Coach promotion

Coaches and trainers are welcome. Misleading, unqualified, or harmful coaching promotion is not. Do not claim certifications you do not hold, do not guarantee clinical outcomes (“lose 10 kg in 30 days”), do not post before-and-after photos that are staged or borrowed, and do not advertise meal plans or programming to users who have disclosed a medical condition (pregnancy, ED history, cardiac condition) that would contraindicate it.

Paid promotion of your own coaching is allowed up to a reasonable frequency; spam limits apply when promotional volume crowds out genuine engagement. Practising nutrition or medicine without a licence, where local law requires one, is a removal offence rather than a warning.

<a id="harassment"></a>

## Harassment

Do not target another user with repeated insults, slurs, sexual comments, threats, body-shaming, or coordinated negativity. This applies whether the target is on Mouve or off-platform. One sharp disagreement is not harassment; following someone from post to post to tell them they are fat, weak, or a cheater is.

Slurs based on race, ethnicity, religion, sex, sexual orientation, gender identity, disability, or medical condition are never acceptable even if the target is nominally a public figure.

Standard response: removal plus warning on first offence, escalating to account limits and eventual suspension for repeat offenders. Coordinated harassment (pile-ons, brigading) is treated as the severity sum of all participants combined.

<a id="minor-safety"></a>

## Minor safety

Mouve is for users aged 16 and over. If we learn a user is under 16 their account is removed.

Content that sexualises a minor — drawn, photographed, AI-generated, or implied — is removed on sight and reported to NCMEC or the appropriate local authority. Adults contacting minors for romantic or sexual purposes, soliciting images, or sending explicit material to an under-18 account results in immediate permanent ban and referral.

Posts featuring minors in athletic context — a 14-year-old gymnast warming up in a gym — are allowed when posted by the minor's parent, guardian, or coach with clear identifying context. We remove uploads that appear to lack consent or that are framed predatorily. When in doubt we act to protect the minor.

<a id="spam"></a>

## Spam

Do not post the same content repeatedly, do not mass-tag unrelated users, do not sell followers or likes, do not run unattributed affiliate schemes, and do not use the DM system for unsolicited commercial pitches.

Legitimate promotion of your own fitness business is fine; buying a bot farm to amplify it is not. Automated engagement via unauthorised scripts violates both this policy and our Terms of Service.

First-time spam is usually soft-actioned (rate limits, reach limits). Persistent or organised spam, especially spam that impersonates Mouve or another user, is removed and the account is banned.

<a id="copyright"></a>

## Copyright

Do not upload content you do not have the rights to — other people's workout videos, paid programmes republished in full, copyrighted music on long-form video, unlicensed stock photos passed off as your own. Short quotes, clips with commentary, and ordinary fair-use transformations are allowed to the extent local law permits.

Rightsholders can file a formal takedown notice via our [DMCA page](/dmca). We honour valid DMCA and EU copyright takedowns and accept counter-notices from users. Repeated infringement triggers the three-strike repeat-infringer policy described in the Terms of Service.

<a id="self-harm"></a>

## Self-harm

Do not post content that depicts, encourages, or provides detailed how-to information for self-harm or suicide. Discussing a past struggle, posting recovery progress, or asking for help is absolutely welcome — we never want to penalise someone for reaching out.

The line is instrumental encouragement: praising a specific method, posting instructional content, directly telling another user to hurt themselves, or sharing imagery designed to shock rather than to inform.

We may show a safety interstitial with resources before a post renders; severe cases are removed and the author receives an outreach message with contact information for a crisis line appropriate to their region.

<a id="violence"></a>

## Violence

Do not post graphic real-world violence (fights, beatings, injuries, gore) for entertainment, and do not celebrate or incite violence against any person or group.

Combat sports content (boxing, MMA, grappling, strongman competition) is allowed because it is the point of those sports; the same content becomes policy-violating when paired with captions targeting an individual or when it crosses from sport into real-world assault footage.

Threats of violence — specific or general — are removed and the author is warned or suspended depending on severity. Terrorist content, including praise, glorification, or recruitment, is removed on sight and reported.

<a id="misinformation"></a>

## Health misinformation

Do not post content that presents harmful health misinformation as fact. Within fitness and nutrition this most often means claims that a specific supplement cures disease, that resistance training is dangerous for cardiovascular health, that a particular diet cures cancer, or that vaccines cause a listed training injury pattern.

We do not penalise honest uncertainty — sports science is evolving and disagreement is normal — but we will remove definitive claims that contradict the current consensus of reputable health bodies when those claims could lead a reader to forego treatment. Political and lifestyle misinformation outside the health domain is generally off-scope.

<a id="impersonation"></a>

## Impersonation

Do not pose as another person, brand, coach, or athlete without a clearly labelled parody or fan-account disclaimer. Using someone else's name, profile photo, or biography to deceive followers is removed and the account is banned.

Athletes and coaches who control their own accounts can request verification via [support@mouve.it](mailto:support@mouve.it). Parody accounts must declare themselves in the bio (“fan account”, “parody”, “unofficial”) and may not solicit money or DMs as though they were the genuine person.

Reporting an impersonation account is a priority-queue action — we try to resolve it inside 24 hours of receipt of a verifiable identity claim.

<a id="enforcement"></a>

## Enforcement

- Our default action on a first marginal violation is a soft action — interstitial, reach limit, or content warning — so users can learn.
- Decisions include a policy reference anchor (e.g. `guidelines#nudity`) so the user can see which section informed the decision, as required by DSA Article 17.
- For illegal content — CSAM, terrorist content, severe intellectual-property infringement — we act without waiting for the marginal-first-strike ladder.

<a id="appeals"></a>

## Appeals

Users can appeal any decision within six months via the in-app appeals flow. Appeal outcomes either uphold, reverse, or narrow the original decision.

If you disagree with an appeal outcome you may submit the dispute to a certified out-of-court dispute-settlement body under DSA Article 21. Contact details are provided in the appeal-result notice.

<a id="changelog"></a>

## Changelog

| Version | Date | Changes |
| --- | --- | --- |
| v1.0 | April 17, 2026 | Initial community guidelines. |

---

<!-- document: ai-transparency | version: 2.1 | effective: 2026-03-07 -->
Document: ai-transparency
Version: 2.1
Effective: 2026-03-07
Canonical: https://mouve.it/ai-transparency
Markdown: https://mouve.it/ai-transparency.md

# AI Transparency

Version 2.1 | Last updated: March 7, 2026 | Effective: March 7, 2026 | EU AI Act Article 50 Disclosure

<a id="ai-notice"></a>

## 1. AI Notice

Mouve's food scanning, meal planning, and workout generation features use artificial intelligence to generate results. These outputs are produced by AI models, not by human professionals.

AI features in Mouve do not make automated decisions that produce legal or similarly significant effects on users. All AI outputs are suggestions only - you decide whether to use them.

AI-generated results are clearly labeled as “AI-generated” in the user interface where they are displayed.

<a id="ai-systems"></a>

## 2. What AI Systems We Use

Mouve uses five AI systems, all provided by OpenAI through their API. All systems listed below are subject to transparency obligations under Article 50 of the EU AI Act.

Food Image Scanning

- **Model:** GPT-4o Vision (OpenAI)
- **Purpose:** Analyzes photographs of food to estimate nutritional content including calories, protein, carbohydrates, and fats

Food Log Text Parsing

- **Model:** GPT-4o-mini (OpenAI)
- **Purpose:** Parses natural language food descriptions (e.g. “2 eggs and toast with butter”) into structured nutritional data including calories, protein, carbohydrates, and fats

AI Meal Planning

- **Model:** GPT-4o-mini (OpenAI)
- **Purpose:** Generates personalized meal plan suggestions based on your dietary preferences, calorie targets, and macro goals

AI Workout Generation

- **Model:** GPT-4o-mini (OpenAI)
- **Purpose:** Generates personalized workout routines based on a natural language description of your training goals, available equipment, and preferences

AI Progress Insights

- **Model:** GPT-4o-mini (OpenAI)
- **Purpose:** Generates personalized progress insights and recommendations based on your aggregated workout and nutrition history

Mouve may introduce additional AI-powered features in the future. When new features are added, this transparency notice will be updated to describe their functionality, data processing, and limitations. AI-generated outputs from these features will also be labeled in the user interface.

<a id="data-processed"></a>

## 3. What Data Is Processed

We do not intentionally include personal identifiers such as name or email in requests sent to the AI provider. The specific data sent for each feature is listed below.

### Food Image Scanning

- The food image you photograph or upload
- A text prompt requesting nutritional estimation

### Food Log Text Parsing

- The natural language food description you type
- No images or personal identifiers are sent

### AI Meal Planning

- Your stated dietary preferences and food restrictions
- Calorie and macronutrient targets

### AI Workout Generation

- Your natural language description of the workout you want (text or voice input, max 500 characters)
- Voice input is processed using your device or browser's speech recognition system. Mouve does not store audio recordings or send them to OpenAI.

### AI Progress Insights

- Aggregated workout statistics (exercise counts, volume trends, frequency)
- Aggregated nutrition statistics (calorie and macronutrient averages)
- No personal identifiers such as name or email are sent

**Data retention by OpenAI:** We use the OpenAI API (not consumer products). Under OpenAI's API Terms, data sent through the API is **not used to train OpenAI's models**. OpenAI retains API inputs and outputs for up to 30 days for abuse monitoring, after which they are deleted.

**Training data:** OpenAI states that its models are trained on a mixture of licensed data, data created by human trainers, and publicly available data. The AI models were not trained specifically for nutrition analysis, food log parsing, meal planning, or exercise programming. Results should therefore be considered approximate suggestions rather than professional guidance. Mouve's user data is not used to train these models.

<a id="how-generated"></a>

## 4. How AI Outputs Are Generated

When you use an AI feature on Mouve, this is what happens:

1. You initiate the feature (scan a food photo, request a meal plan, or generate a workout)
2. Mouve sends the relevant data to OpenAI's API along with a structured prompt
3. OpenAI's model processes the input and returns a structured response
4. Mouve parses the response and presents it to you with an “AI-generated” label

The AI system generates responses based on patterns learned from large datasets. Mouve does not manually review each output and does not guarantee the accuracy of the results.

AI features are only activated when you initiate them.

AI outputs are generated automatically and are not reviewed by a human before being shown to you.

<a id="limitations"></a>

## 5. Limitations and Accuracy

Important: AI outputs are estimates, not facts

All AI-generated content on Mouve is approximate and should not be relied upon for medical, health, or dietary decisions without independent verification.

- **Food scanning accuracy:** Nutritional estimates may vary significantly from actual values. The AI may misidentify foods, misjudge portion sizes, or miss hidden ingredients.
- **Meal plan limitations:** Generated plans do not account for medical conditions, medication interactions, allergies not explicitly stated, or individual metabolic needs.
- **Workout generation limitations:** AI-generated workouts may contain errors or unsafe exercise combinations and should be reviewed before performing. Generated routines do not account for injuries, physical limitations, or medical conditions. Always use proper form and consult a qualified professional if unsure.
- **Progress insights limitations:** AI-generated insights are based on aggregated historical data and may not reflect your current fitness level, recovery status, or changing goals. Insights are general observations, not professional coaching advice.
- **Regional bias:** AI models may have limited knowledge of regional or culturally specific foods due to training data composition.
- **Not medical advice:** Mouve is a fitness tracking tool, not a healthcare provider. Always consult a qualified professional for personalized dietary guidance.
- **Exercise safety:** Always perform exercises within your physical limits. Stop immediately if you experience pain or discomfort.

<a id="human-oversight"></a>

## 6. Human Oversight

Mouve does not rely on AI systems to make decisions that significantly affect users. Users review AI-generated outputs before saving them, and no actions are taken automatically based on AI outputs.

- **User control:** You can edit any AI-generated nutritional data or workout before saving it, and you can delete AI-generated entries at any time.
- **Report incorrect results:** If you believe an AI-generated result is incorrect, you may contact us at [privacy@mouve.it](mailto:privacy@mouve.it) to report the issue.

<a id="your-rights"></a>

## 7. Your Rights and Controls

You have full control over AI features on Mouve:

AI features are optional and run only when you choose to use them. You can use Mouve for workout tracking, nutrition logging, and social features without ever using AI.

- **User-initiated only:** AI processing occurs only when you explicitly request it (e.g., scanning a food photo, generating a meal plan, or creating a workout). No AI processing happens in the background.
- **Data deletion:** You can delete any AI-generated nutrition entries from your logs at any time.
- **Request information:** You can request details about how a specific AI output was generated by contacting [privacy@mouve.it](mailto:privacy@mouve.it).

<a id="provider-info"></a>

## 8. Provider Information

Mouve deploys AI models provided by OpenAI. OpenAI is the model provider; Mouve is the deployer responsible for how these models are used within the service.

**Model provider:** OpenAI, L.L.C.
**Website:** [openai.com](https://openai.com)
**Privacy Policy:** [OpenAI Privacy Policy](https://openai.com/policies/privacy-policy)
**API Data Usage:** [OpenAI API Data Usage Policies](https://openai.com/policies/api-data-usage-policies)

<a id="legal-basis"></a>

## 9. Legal Basis & Compliance

This page is provided in compliance with the EU AI Act (Regulation (EU) 2024/1689) Article 50 transparency obligations for deployers of AI systems.

- **Applicable obligations:** Transparency obligations under Article 50 of the EU AI Act apply to the AI systems described in this notice. These systems do not fall into categories requiring conformity assessment.
- **Obligations met:** Transparency, labeling, and user awareness as required under Article 50.
- **Legal basis for processing:** AI features operate when users request them as part of the Mouve service. Processing required to generate meal plans, workout routines, and nutrition estimates is carried out for the performance of a contract (GDPR Article 6(1)(b)). Certain supporting processing necessary to operate, monitor, and secure AI features may rely on legitimate interests (GDPR Article 6(1)(f)).
- **GDPR alignment:** AI features do not involve automated decision-making within the meaning of GDPR Article 22. All outputs are advisory and non-binding.

For questions about our AI practices, contact [privacy@mouve.it](mailto:privacy@mouve.it).

<a id="changes"></a>

## 10. Changes to This Notice

We may update this AI Transparency Notice as our AI features evolve or as regulatory requirements change. Material changes will be reflected in the version number and date at the top of this page.

| Version | Date | Changes |
| --- | --- | --- |
| 1.0 | March 2, 2026 | Initial AI transparency notice published |
| 2.0 | March 7, 2026 | Added AI disclosure labeling across all AI output surfaces; clarified legal basis under GDPR Article 6(1)(b) and 6(1)(f); updated user rights section to reflect that AI features are user-initiated and optional; added AI Progress Insights as fourth AI system; added version history |
| 2.1 | March 7, 2026 | Added Food Log Text Parsing as fifth AI system; updated system count and data processing details; added text parsing to training data scope |

---

<!-- document: account-deletion | version: 1.0 | effective: 2026-10-25 -->
Document: account-deletion
Version: 1.0
Effective: 2026-10-25
Canonical: https://mouve.it/account-deletion
Markdown: https://mouve.it/account-deletion.md

# Delete your Mouve account

Your account is closed as soon as you confirm and deleted for good 7 days later. This page explains how to delete your account, how to change your mind during those 7 days, and what happens to your data.

<a id="in-app"></a>

## 1. Delete in the app (preferred)

The fastest way to delete your account is directly inside Mouve. When you confirm, your account is closed at once (you are signed out everywhere, nobody else can see it, a subscription bought on mouve.it is cancelled) and it is deleted for good 7 days later. Until then you can restore it with the link in the email we send, or by writing to support@mouve.it.

### On the Mouve mobile app

1. Open the Mouve app and sign in.
2. Tap the menu icon to open the drawer, then go to **Settings**.
3. Scroll to **Data & account** at the bottom (older app versions: the **Account** section at the top).
4. Tap **Delete account**. The screen tells you about any subscription and links to your data download.
5. Tap **Email me a code**, enter the code from the email, tick the box and tap **Delete my account permanently**. Older app versions delete after a confirmation without the code.

### On the Mouve web app (mouve.it)

1. Sign in at [mouve.it](https://mouve.it).
2. Navigate to **Settings** (profile menu, top right).
3. Open **Data & account**.
4. Click **Delete account**. You can download a copy of your data from the same screen first.
5. We email a code to the address on your account. Enter it, tick the box to confirm, and click **Delete my account permanently**.

### If you pay for Mouve+

- **Bought on mouve.it:** deleting your account cancels the subscription. If we cannot reach our payment provider, nothing is deleted and you can try again.
- **Bought in the iPhone or Android app:** Apple or Google bills you, and deleting your Mouve account does **not** cancel it. Cancel it first: on iPhone in Settings → your name → Subscriptions; on Android in the Google Play Store → Payments & subscriptions → Subscriptions.

Important

After the 7 days, deletion is permanent and cannot be undone. All your data is then removed from our systems (subject to the limited legal-hold categories described in Section 3 below). During the 7 days you cannot sign in or download your data yourself; write to support@mouve.it if you need a copy.

<a id="what-deleted"></a>

## 2. What gets deleted

When you delete your account, the following personal data is permanently and irreversibly removed:

- **Profile** — your username, display name, bio, avatar, and cover image.
- **Posts and content** — all posts, photos, and videos you have shared.
- **Comments** — all comments you have left on other content.
- **Workout data** — all workout sessions, exercise logs, templates, and progress history.
- **Nutrition logs** — all meals, food entries, and calorie/macro history.
- **Messages you sent** — the direct messages you sent are deleted. Messages other people sent to you remain part of *their* conversation data and are not deleted by your request — just as your sent messages remain in your own copy until you delete your account.
- **Health metrics** — body measurements, weight history, fitness-tracker metrics, and any other health data you entered are hard-deleted.
- **Social connections** — your follower and following lists, likes, reposts, blocks, mutes, and community memberships.
- **Notifications and devices** — your notifications and registered push-notification devices.
- **AI coach memory and AI results** — what the coach remembered about you, AI-generated meal suggestions and recipes, and your scan history.
- **Training programs and shares** — your programs, the workouts you shared with people or communities, and your challenge progress.

Anonymized or aggregated statistics derived from your activity (for example, platform-level usage counts) may be retained for fraud prevention and service improvement purposes, in line with our [Privacy Policy](/privacy-policy) and Terms of Service. These aggregates cannot be used to identify you.

<a id="what-retained"></a>

## 3. What is kept, and why

A small set of records is kept: some because the law requires it, and some because other members' own data depends on them:

| Data category | Retention period | Legal basis |
| --- | --- | --- |
| Subscription and payment records (Stripe customer ID, subscription tier, billing dates) | 7 years | EU bookkeeping law, tax obligations — GDPR Art. 6(1)(c) |
| Content moderation records (reports, enforcement actions) | 6 months after the moderation action | Digital Services Act (DSA) obligation — GDPR Art. 6(1)(c) |
| Things other members still use: a community you created (it passes to its longest-standing admin or member, or is archived if nobody is left), a conversation you started, a workout you published that someone has trained, a custom food or exercise someone has used. Kept without your name or anything else that identifies you; your own messages, posts and memberships in them are deleted. If nobody else uses it, it is deleted. | As long as the other members use it | The other members' own data depends on it — GDPR Art. 6(1)(f), Art. 17(1) does not reach other people's records |
| Anonymized usage aggregates | Indefinite (no longer personal data) | Legitimate interest — GDPR Art. 6(1)(f) |

These retention periods are consistent with Section 13 of our [Privacy Policy](/privacy-policy).

<a id="no-app"></a>

## 4. No longer have app access?

If you have lost access to your account or device and cannot sign in to delete your account through the app, you can request deletion by email:

**Email:** [privacy@mouve.it](mailto:privacy@mouve.it)

**Subject line:** Account deletion request

**Include in your message:** Your Mouve username and the email address associated with the account. Send from that email address if possible — it helps us verify ownership.

- We will respond to your request within **7 days**.
- Once we have verified that the account is yours, your personal account is closed at once and erased 7 days later, in accordance with GDPR Article 17 (right to erasure). The only delay is the identity-verification step — there is no fixed retention window after deletion.
- The legal-hold categories in Section 3 above still apply.

<a id="your-rights"></a>

## 5. Your rights

The right to delete your account is grounded in the following regulations:

- **GDPR Article 17 — Right to erasure** (“right to be forgotten”): If you are located in the European Economic Area, you have the right to request that we erase your personal data without undue delay when you withdraw consent, when the data is no longer necessary for the purposes for which it was collected, or when you object to processing under Article 21.
- **CCPA / CPRA — Right to deletion (California residents)**: If you are a California resident, you have the right to request that we delete personal information we have collected from you, subject to certain exceptions.

For a full list of your privacy rights and how to exercise them, see Section 14 of our [Privacy Policy](/privacy-policy).

If you have a complaint about how we handle your data, you may lodge one with your local data protection authority. EU authorities are listed at the [European Data Protection Board website](https://edpb.europa.eu/about-edpb/about-edpb/members_en).

---

<!-- document: notice-and-action | version: v2 | effective: 2026-05-01 -->
Document: notice-and-action
Version: v2
Effective: 2026-05-01
Canonical: https://mouve.it/notice-and-action
Markdown: https://mouve.it/notice-and-action.md

# Notice & Action Procedure

Version v2 · Last updated: 2026-05-01. This page implements our obligations under Article 16 of the EU Digital Services Act (Regulation (EU) 2022/2065) and is enforced internally by our moderation SLA escalation worker (15-minute scan cadence).

<a id="purpose"></a>

## 1. Purpose

Mouve provides this notice-and-action mechanism so that any person or entity can notify us of content hosted on Mouve that they consider to be illegal under EU law or the law of an EU Member State. When we receive a valid notice, we review the content and take any action we consider appropriate under our Terms of Service, the [Community Guidelines](/community-guidelines), and applicable law.

This is in addition to the in-product “Report” flows available from every post, comment, profile, and message on Mouve, which you should use for violations of our Community Guidelines (whether or not illegal).

<a id="who-can-notify"></a>

## 2. Who Can Submit a Notice

Any person or entity may submit a notice, whether or not they are a Mouve user. Notices may be submitted by the person or entity affected by the allegedly illegal content, by their authorised representative, or by any third party with knowledge of the content.

<a id="how-to-notify"></a>

## 3. How to Notify Us

You can submit a notice by any of the following methods:

- **In-product reporting.** Use the “Report” button on the post, comment, profile, or message concerned. This is the fastest route for most reports.
- **Email.** Send a structured notice to [legal@mouve.it](mailto:legal@mouve.it).
- **Copyright notices** go through the separate form at [/copyright](/copyright) so we can process them under the DMCA / InfoSoc Directive.

<a id="what-to-include"></a>

## 4. Required Information

To allow us to assess a notice under Art.16(2) DSA, please include all of the following:

- A sufficiently substantiated explanation of why you consider the content illegal (which provision of law, which element of the offence).
- A clear indication of the exact electronic location of the content (one or more URLs, or post IDs, in-product).
- The name and a contact email address of the person or entity submitting the notice (except where the content falls into a restricted category such as CSAM or terrorism, where anonymous reports are accepted).
- A statement confirming the good faith of the notifier that the information in the notice is accurate and complete.

A complete notice creates a presumption of our “actual knowledge” under Art.6(1)(b) DSA for the content specifically referenced in the notice.

<a id="trusted-flaggers"></a>

## 5. Trusted Flaggers

We process notices from entities designated as trusted flaggers by the Digital Services Coordinator of an EU Member State with priority, in accordance with Art.22 DSA. Trusted flaggers wishing to submit batched or API-based notices should contact [trusted-flagger@mouve.it](mailto:trusted-flagger@mouve.it) to set up a dedicated intake channel.

<a id="how-we-act"></a>

## 6. How We Act on Notices

We review every notice. Each report is automatically classified into one of three severity tiers on intake; an escalation worker runs every 15 minutes and pages on-call when the tier’s SLA is breached. The committed response times are:

- **Manifestly illegal content (CSAM, terrorism, imminent threats):** reviewed and removed within 1 hour of escalation. We page on-call automatically and notify the competent authorities under Art.18 DSA where applicable (NCMEC for CSAM, Europol IRU for terrorism, national law enforcement for direct threats to life).
- **Severe abuse, harassment, hate speech, or minor-safety risk:** reviewed within 24 hours of report. The internal SLA is 12 hours, with hard takedown by hour 24 to comply with Apple App Store Review Guideline 1.2(e).
- **All other reports** (spam, misinformation, impersonation, generic Community Guidelines breaches): within 48 hours. Complex cases that require legal review or coordination with a competent authority may take up to 7 days — when this happens we record the reason for the extended review on the report.

We apply the action proportionate to the violation: content removal, de-ranking or reach limitation, account suspension, or, for minor or good-faith issues, a warning. Every decision is logged with a statement of reasons (Art.17 DSA) and can be audited against the SLA timeline.

<a id="statement-of-reasons"></a>

## 7. Statement of Reasons

When we take a moderation action against a user's content, we provide the user with a clear statement of reasons under Art.17 DSA, including:

- What action was taken (remove, limit, suspend, etc.);
- The facts and circumstances on which the decision was based;
- The legal ground and/or the specific provision of our Community Guidelines that was infringed;
- Whether automated means were used in detection or decision;
- The redress routes available to the user.

Statements of reasons are published to the Transparency DB as required by Art.24(5) DSA, with personal data removed.

<a id="appeals"></a>

## 8. Appeals (Art.20)

Users whose content has been restricted can appeal the decision through the in-product appeal form for up to 6 months from the decision. Appeals are handled by a human reviewer who was not involved in the original decision. Outside of our internal complaint-handling, users retain the right to take the matter to a certified out-of-court dispute settlement body (Art.21 DSA) or to a court of competent jurisdiction.

<a id="misuse"></a>

## 9. Misuse of the Procedure

Submitting notices in bad faith, fraudulent notices, or repeat manifestly unfounded notices constitutes misuse under Art.23 DSA. We may rate-limit, suspend, or terminate intake from a notifier following a warning.

<a id="copyright-notices"></a>

## 10. Copyright Notices

Copyright infringement notices are handled through a separate intake. See our [Copyright / DMCA page](/copyright) for the required information and counter-notice procedure.

<a id="urgent-content"></a>

## 11. CSAM and Urgent Threats to Life

Suspected child sexual abuse material, content depicting credible threats to life, or imminent terrorism content must be reported immediately to the emergency mailbox [urgent@mouve.it](mailto:urgent@mouve.it) so we can act within the hours required by Art.18 DSA and coordinate with the relevant authorities (NCMEC, Europol IRU, national law enforcement). Please include the URL or post ID only — do not re-distribute the underlying content.

<a id="contact"></a>

## 12. Contact

**Legal / Notice & Action:** [legal@mouve.it](mailto:legal@mouve.it)

**DSA single point of contact:** [dsa@mouve.it](mailto:dsa@mouve.it)

For general questions see the [Contact page](/contact).

---

<!-- document: copyright | version: 1.0 | effective: 2026-04-17 -->
Document: copyright
Version: 1.0
Effective: 2026-04-17
Canonical: https://mouve.it/copyright
Markdown: https://mouve.it/copyright.md

# Copyright Policy

Last updated: 2026-04-17. This policy covers both DMCA (17 U.S.C. § 512) takedown notices and EU Copyright Directive (2019/790, Art.17) takedown requests.

<a id="policy"></a>

## 1. Copyright Policy

Mouve respects the intellectual-property rights of others and expects users to do the same. Content that infringes a valid copyright will be removed, and repeat infringers may be suspended or banned in accordance with our [Terms of Service](/tos) and [Community Guidelines](/community-guidelines#copyright).

<a id="submit-notice"></a>

## 2. Submitting a Takedown Notice

Rightsholders (or their authorised agents) may submit a takedown notice by emailing [copyright@mouve.it](mailto:copyright@mouve.it) with the information listed below, or by using the in-product [Copyright Submission form](/copyright/submit).

We verify each notice before acting. Knowingly false takedowns expose the sender to liability under 17 U.S.C. § 512(f).

<a id="required-info"></a>

## 3. Required Information (DMCA § 512)

A valid notice must include:

- A physical or electronic signature of the copyright owner or their authorised agent.
- Identification of the copyrighted work claimed to have been infringed (title, registration number if any, URL of the original work).
- Identification of the infringing material and information reasonably sufficient to permit us to locate it (Mouve post URL or post ID).
- Your name, postal address, telephone number, and email address.
- A statement that you have a good-faith belief that the disputed use is not authorised by the copyright owner, its agent, or the law.
- A statement, made under penalty of perjury, that the information in the notice is accurate and that you are the copyright owner or authorised to act on behalf of the owner.

Notices missing any of these elements will be returned and may be rejected until complete.

<a id="counter-notice"></a>

## 4. Counter-Notice

If your content was removed and you believe it was removed by mistake or misidentification, you can submit a counter-notice using the in-product [Counter-Notice form](/copyright/counter-notice), or by emailing [copyright@mouve.it](mailto:copyright@mouve.it) with the following information (per 17 U.S.C. § 512(g)):

- Your physical or electronic signature.
- Identification of the material that has been removed and the location at which it appeared before removal (URL or post ID).
- A statement under penalty of perjury that you have a good-faith belief that the material was removed as a result of mistake or misidentification.
- Your name, postal address, telephone number, and a statement consenting to the jurisdiction of the Federal District Court for the judicial district in which your address is located (or, if outside the US, the judicial district of our registered office in the EU).
- A statement that you will accept service of process from the party who filed the original notice.

On receipt of a valid counter-notice we will forward it to the original claimant. If the claimant does not initiate a lawsuit against you within 10 to 14 business days, we will restore the content.

<a id="repeat-infringers"></a>

## 5. Repeat-Infringer Policy

We terminate, in appropriate circumstances, the accounts of users who are repeat infringers. A “strike” is logged for each sustained takedown. Three strikes within a rolling 12-month window trigger permanent account termination. Strikes can be contested through the in-product appeal flow.

<a id="eu-takedowns"></a>

## 6. EU Copyright Takedowns

For rightsholders operating under Directive (EU) 2019/790, we accept takedowns in the same form as DMCA notices, with the following adjustments:

- A statement of accuracy under your Member State's applicable civil code, in lieu of the US “perjury” statement.
- Identification of the relevant exclusive right (reproduction, communication to the public, etc.) and, where applicable, any collective management organisation licence.
- We apply the exceptions of Art.17(7) of the Directive (quotation, criticism, review, caricature, parody, pastiche) before acting.

<a id="transparency"></a>

## 7. Transparency

Sustained copyright takedowns are counted in our half-yearly DSA transparency report and in the EU Transparency Database per Art.24(5) DSA (redacted of personal data).

<a id="contact"></a>

## 8. Contact

**Copyright agent:** [copyright@mouve.it](mailto:copyright@mouve.it)

Non-copyright complaints belong on the [Notice & Action page](/notice-and-action).

---

<!-- document: developer-terms | version: 1.0 | effective: 2026-08-30 -->
Document: developer-terms
Version: 1.0
Effective: 2026-08-30
Canonical: https://mouve.it/legal/developer-terms
Markdown: https://mouve.it/legal/developer-terms.md

# Mouve Developer Terms

Version 1.0 | Last updated: August 30, 2026 | Effective: August 30, 2026

<a id="scope"></a>

## 1. Who These Terms Bind

These Developer Terms (“Terms”) are a legally binding agreement between Mouve Technology OÜ (“Mouve,” “we,” “us”) and you, the developer, if you do any of the following:

- Register an application or client (through the developer portal or dynamic client registration) that authenticates against the Mouve API;
- Build, operate, or distribute any application, AI agent, bot, integration, or service (each an “Application”) that accesses the Mouve API or acts on a Mouve user's behalf; or
- Access the Mouve API programmatically in any way beyond personal use of your own account with your own credentials.

“User Data” means any data about a Mouve user that your Application receives from the Mouve API or derives from data it received — profile data, posts and social activity, and where authorized, workout, nutrition, and body-measurement data.

These Terms supplement the [Mouve Terms of Service](/tos), which also apply to you as an account holder. End users who connect your Application to their account are covered by the [connected-app terms](/legal/mcp-terms) and the [Mouve Privacy Policy](/privacy-policy). If these Terms conflict with the main Terms of Service, these Terms control as to API access and Application operation.

<a id="acceptance"></a>

## 2. Acceptance

You accept these Terms by:

- Checking the acceptance box when creating an application in the developer portal (your acceptance is recorded with the version of these Terms shown above);
- Registering a client via dynamic client registration, which constitutes acceptance without a separate signature; or
- Accessing the Mouve API with any issued credential.

If you accept on behalf of a company or other legal entity, you represent that you are authorized to bind that entity, and “you” means that entity. If you do not agree to these Terms, do not register an Application and do not access the API.

<a id="registration"></a>

## 3. Registration and Credentials

- Provide accurate, current registration information (name, description, website, redirect URIs, contact addresses) and keep it up to date. Contact addresses must reach a person who can act on security and legal notices.
- Keep client secrets and access, refresh, and personal access tokens confidential. Never embed a client secret in code distributed to end users, commit credentials to a repository, or transmit them over unencrypted channels.
- Credentials are issued per Application and are non-transferable. You may not sell, lease, share, or broker API access, tokens, or quota — including operating a proxy that resells access to your credentials.
- Never ask a user for their Mouve password, session cookie, or a personal access token. The only permitted way to act on a user's behalf is the authorization flow described in Section 4.
- Rotate any credential you believe may be compromised and notify us per Section 14 where User Data may be affected.

<a id="authorization"></a>

## 4. Scopes and User Authorization

- Your Application receives access only through scopes an individual user has granted on Mouve's consent screen. Scopes are exact-match: a write scope does not imply the corresponding read scope, and no scope implies another.
- Request the minimum scopes your Application needs to function (least privilege). Do not request scopes “for later” or condition unrelated functionality on unrelated scopes.
- A user may revoke your Application's access at any time, and Mouve may revoke any credential at any time (Section 11). Design your Application to handle revocation gracefully: treat 401/403 responses as loss of authorization, not as an error to retry.
- Act only within the granted authorization and only at the user's direction. Do not take actions the user did not ask for, and do not attempt to access data belonging to users who have not authorized your Application.

<a id="user-data"></a>

## 5. User Data

### 5.1 Purpose Limitation

Use User Data solely to provide the functionality of your Application that the authorizing user requested, as described to that user. Any other use requires that user's separate, informed consent collected by you. Without such consent, you must not use User Data for — and must never in any case sell or broker User Data for:

- Sale, licensing, or brokerage of User Data to any party;
- Advertising, ad targeting, ad measurement, or audience building;
- Eligibility determinations of any kind — including insurance, credit, housing, employment, or benefits;
- Surveillance, tracking, or monitoring of users, including on behalf of governments or employers;
- Training, fine-tuning, or evaluating machine-learning or AI models.

### 5.2 Retention and Deletion

- Retain User Data only as long as needed for the purpose the user authorized. Cache minimally; prefer fetching fresh data over storing copies.
- Delete a user's User Data within **30 days** after any of the following: the user revokes your Application's access; the user deletes their Mouve account; Mouve notifies you of a deletion or erasure request; or the user asks you directly. Deletion covers backups on their normal expiry cycle.
- You may retain data where retention is required by law that applies to you, limited to what that law requires, and you must tell the user so in your privacy policy.

### 5.3 Onward Transfer

Do not disclose User Data to third parties except service providers processing it on your behalf under a written agreement at least as protective as this Section 5, or where disclosure is required by law. You remain responsible for your service providers.

<a id="health-data"></a>

## 6. Health Data

Workout, nutrition, and body-measurement data is health data — special-category personal data under GDPR Article 9. If your Application requests any health-designated scope, all of Section 5 applies plus the following stricter floor:

- Access requires the user's explicit consent, which Mouve collects and records at grant time. You must not attempt to obtain health-scoped access any other way.
- You must publish a privacy policy at a working URL and register it with your Application before requesting health scopes.
- Use health data only for the health feature the user is actively using. Do not derive, infer, or score health conditions, and do not combine health data with data from other sources to build a health profile.
- Never disclose health data to any third party other than a Section 5.3 service provider. The separate-consent carve-outs of Section 5.1 do not permit sale or brokerage of health data under any circumstances.
- When a user withdraws health consent or disconnects, delete health data per Section 5.2 — the 30-day clock applies from withdrawal.

<a id="prohibited"></a>

## 7. Prohibited Conduct

You must not:

- Scrape, crawl, or bulk-collect content or user information outside the API, or use the API to reconstruct a substantial portion of Mouve's content or social graph;
- Circumvent or attempt to circumvent rate limits, scopes, authentication, moderation, or any technical control — including by rotating credentials, coordinating multiple Applications, or automating account creation;
- Use the API to spam, mass-follow, mass-message, artificially amplify content, or generate engagement a user did not individually direct;
- Post or facilitate content that violates the [Community Guidelines](/community-guidelines) or the content rules in the Terms of Service;
- Introduce malware, probe or test the vulnerability of Mouve's systems without written permission, or interfere with the Service's operation;
- Misrepresent your Application's identity, functionality, or data practices to users or to Mouve;
- Use the API to build a service whose primary purpose is republishing Mouve user content without added functionality for the authorizing user; or
- Encourage or enable any third party to do any of the above.

<a id="rate-limits"></a>

## 8. Rate Limits and Quotas

API access is subject to published rate limits and quota tiers. The authoritative, most current limits are published in the Mouve developer documentation; the tables below are rendered from the same configuration the platform enforces and reflect the current values at the date of this document. Where the documentation and this page ever differ, the documentation controls.

### 8.1 Application Tiers (OAuth apps)

| Tier | Reads / min / user | Writes / min / user | Writes / day / user | App-wide reads / min | App-wide writes / min |
| --- | --- | --- | --- | --- | --- |
| **Restricted** anonymous / dynamic registration | 30 | 5 | 50 | 300 | 30 |
| **Standard** default for portal-registered apps | 60 | 10 | 200 | 600 | 60 |
| **Elevated** granted by Mouve on request | 300 | 30 | 1000 | 6000 | 600 |
| **Partner** by written agreement | 900 | 60 | By agreement | 30000 | 6000 |
| **Personal access tokens** per token | 300 | 30 | 1000 | — | — |

### 8.2 Ceilings and Enforcement

- Across all Applications and tokens combined, writes on behalf of one user are capped at 60 per minute and 500 per day. Connecting more Applications does not multiply one account's write throughput.
- Unauthenticated requests (discovery documents, API specification, health checks) are limited to 60 per minute per IP address.
- Requests over a limit receive HTTP 429 with standard `RateLimit-*` headers. Back off and retry after the indicated reset; treating 429 as a signal to retry immediately is circumvention under Section 7.
- Mouve may temporarily reduce an Application's effective limits in response to abusive or anomalous traffic, may adjust tiers and limits over time per Section 12, and assigns and changes an Application's tier at its discretion.

<a id="attribution"></a>

## 9. Attribution and Labeling

- Content and actions created through the API are attributed to the authorizing user together with the credential that created them. Mouve records this attribution server-side and may display an indication that content was created via an Application; you must not attempt to forge, strip, or spoof it.
- If your Application generates content with AI, do not present that content to users, on or off Mouve, as human-authored where law applicable to you requires disclosure.
- Do not misattribute actions to a user that the user did not direct, and do not post on a user's behalf outside the functionality they connected your Application for.

<a id="branding"></a>

## 10. Branding and Naming

- Your Application's name and presentation must not state or imply that it is made, endorsed, or verified by Mouve. Application names containing “Mouve” or reserved terms such as “official,” “verified,” “support,” “admin,” “staff,” or “team” are rejected at registration — including lookalike spellings using substituted or visually confusable characters. Attempting to evade this screening is a material breach.
- You may state factually that your Application “works with Mouve” or “connects to the Mouve API.” Any other use of Mouve's name, logo, or brand assets requires prior written permission.
- Unverified Applications are presented to users with an “unverified” notice on the consent screen and do not display a developer-supplied logo until it is reviewed. Do not describe your Application as verified unless Mouve has granted it verified status.

<a id="suspension"></a>

## 11. Suspension, Takedown, and Cure

- Mouve may suspend or terminate your Application's access, throttle its traffic, or revoke any or all of its tokens and secrets **at any time, effective immediately**, where Mouve reasonably believes this is needed to protect users, the Service, or third parties — including for breach of these Terms, user reports, security incidents, unlawful content, or abnormal traffic. Users' existing authorizations for a suspended Application stop working and are re-requested from users if access is restored.
- For breaches that do not require immediate action, Mouve will make reasonable efforts to notify you at your registered contact address and give you an opportunity to cure within a stated period before terminating.
- You may appeal a suspension or takedown by replying to the notice or contacting [support@mouve.it](mailto:support@mouve.it). Appeals are reviewed by a human.
- On termination, all credentials are invalidated, and Sections 5.2 (deletion), 6, 17, 18, and 19 survive. You may stop using the API and delete your Application at any time; deletion revokes its credentials and user grants.

<a id="changes"></a>

## 12. Changes to the API and These Terms

- The API evolves. Mouve may add, change, deprecate, or withdraw endpoints, scopes, tiers, and limits. For changes that break documented behavior your Application reasonably relies on, Mouve will give at least **30 days' notice** via the developer documentation changelog and/or your registered contact address, except where a shorter period is required for security, legal compliance, or abuse response.
- Mouve may modify these Terms with 30 days' notice given the same way; continued API access after the effective date constitutes acceptance. Changes required by law or needed to address security or abuse may take effect immediately.
- Mouve may discontinue the API program as a whole with reasonable notice. No provision of these Terms obliges Mouve to keep any API available.

<a id="security"></a>

## 13. Security Obligations

- Protect User Data and credentials with technical and organisational measures appropriate to the risk (GDPR Art. 32 where it applies to you): encrypted transport everywhere, encrypted storage of tokens and health data, least-privilege access within your organisation.
- Do not log access tokens, refresh tokens, or client secrets. Store only hashes where verification is needed.
- Keep your software dependencies patched, and maintain a way for security researchers to reach you.
- Report suspected vulnerabilities in the Mouve platform to [security@mouve.it](mailto:security@mouve.it) rather than exploiting or publicising them.

<a id="breach"></a>

## 14. Breach Notification

If you become aware of unauthorized access to, or loss or disclosure of, User Data or credentials in your custody, you must:

- Notify Mouve at [security@mouve.it](mailto:security@mouve.it) **within 72 hours** of becoming aware, describing the nature of the incident, the data and users affected, and the measures taken;
- Revoke or rotate affected credentials immediately and cooperate with Mouve's investigation; and
- Comply with your own legal notification duties towards users and authorities (e.g. GDPR Arts. 33–34) — notifying Mouve does not discharge them.

<a id="your-users"></a>

## 15. Your Users: Transparency and Support

- Maintain a clear, accurate privacy policy describing what User Data your Application collects, how it is used and retained, and how users can reach you and exercise their rights. The registered privacy policy URL must stay working.
- Provide users of your Application a working support channel. Mouve supports the Mouve platform, not your Application, and may refer your users to you.
- Honor data-subject rights addressed to you (access, rectification, erasure, portability, objection) for the data you hold, within statutory deadlines.

<a id="fees"></a>

## 16. Fees

API access is currently provided free of charge. Mouve may introduce paid tiers or fees for elevated access in the future; any fees will apply only after notice per Section 12 and will never apply retroactively. Continuing to use a newly paid tier after its effective date constitutes acceptance of its fees; declining means your Application reverts to a free tier or terminates per Section 11.

<a id="relationship"></a>

## 17. Relationship of the Parties

When a user authorizes your Application, Mouve discloses User Data to you **at that user's direction**. From the moment you receive it, you process it for your own Application's purposes, which you determine. Accordingly:

- You are an **independent controller** (GDPR Art. 4(7)) of the User Data your Application receives — not Mouve's processor, and Mouve is not yours. No GDPR Art. 28 data processing agreement exists between us, and these Terms are not one.
- You are solely responsible for your own lawful basis, transparency, security, transfers, and data-subject rights for the data you hold, under GDPR and any other law that applies to you or your users worldwide.
- Sections 5 and 6 are contractual data-use commitments to Mouve (and for the benefit of users), not processing instructions.
- Nothing in these Terms creates a partnership, joint controllership, agency, or employment relationship between you and Mouve.

<a id="liability"></a>

## 18. Disclaimers, Liability, Indemnification

### 18.1 No Warranty

The API is provided **“as is”** and “as available,” without warranties of any kind, express or implied — including merchantability, fitness for a particular purpose, non-infringement, availability, or that the API will be uninterrupted or error-free. No service-level agreement is offered. Fitness and nutrition data exposed by the API is user-entered or AI-estimated and is not medical advice.

### 18.2 Limitation of Liability

To the maximum extent permitted by law, Mouve is not liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, data, or goodwill, arising from or related to the API or these Terms. Mouve's total aggregate liability under these Terms is limited to the greater of the fees you paid Mouve for API access in the 12 months preceding the claim and €100. Nothing in these Terms excludes liability that cannot be excluded by law, including for intent or gross negligence.

### 18.3 Indemnification

You will defend, indemnify, and hold harmless Mouve, its officers, and employees from claims, damages, fines, and reasonable costs (including legal fees) arising from your Application, your use of the API or User Data, or your breach of these Terms or of applicable law — including data-protection claims brought by users or authorities relating to your processing.

<a id="governing-law"></a>

## 19. Governing Law and Venue

These Terms are governed by the laws of the Republic of Estonia, excluding its conflict-of-law rules. Disputes arising from these Terms that cannot be resolved amicably are subject to the exclusive jurisdiction of Harju County Court (Harju Maakohus), Tallinn, Estonia. If you are a consumer, mandatory consumer-protection provisions of your country of residence remain unaffected.

<a id="general"></a>

## 20. General Provisions and Contact

- These Terms, together with the documents they reference, are the entire agreement between you and Mouve regarding the API and supersede prior discussions.
- You may not assign these Terms without Mouve's written consent; Mouve may assign them to a successor of the Service.
- If a provision is held unenforceable, the remainder stays in effect. A failure to enforce a provision is not a waiver.
- Notices to you go to your registered contact address; notices to Mouve go to the address below.

**Mouve Technology OÜ**
Sõpruse pst 8-31, Kristiine linnaosa, 10615 Tallinn, Harju maakond, Estonia
Developer contact: [support@mouve.it](mailto:support@mouve.it)
Security: [security@mouve.it](mailto:security@mouve.it)
Privacy: [privacy@mouve.it](mailto:privacy@mouve.it)

---

<!-- document: mcp-privacy | version: 1.1 | effective: 2026-04-23 -->
Document: mcp-privacy
Version: 1.1
Effective: 2026-04-23
Canonical: https://mouve.it/legal/mcp-privacy
Markdown: https://mouve.it/legal/mcp-privacy.md

# MCP Connector Privacy Policy

Version 1.1 | Last updated: August 30, 2026 | Effective: April 23, 2026

<a id="introduction"></a>

## 1. Introduction

The Mouve Model Context Protocol (“MCP”) connector is a server that exposes a subset of your Mouve account data to AI agents you have authorized (for example Claude, ChatGPT, or other MCP-compatible clients). Access is granted through the OAuth 2.1 authorization flow; you review and confirm the requested scopes on the Mouve consent screen before any data leaves your account.

This notice describes what the MCP connector processes, which third parties are involved, how long data is retained, and how you can exercise control. It supplements the main [Mouve Privacy Policy](/privacy-policy), which continues to govern the underlying data held in your Mouve account.

<a id="controller"></a>

## 2. Data Controller

Mouve is the data controller for the processing described on this page. Controller contact details, establishment, and supervisory authority information are listed in the [main Privacy Policy](/privacy-policy). For connector-specific questions, write to [privacy@mouve.it](mailto:privacy@mouve.it).

<a id="what-accessed"></a>

## 3. What Data Is Accessed

An AI agent can only access data covered by the OAuth scopes you approved during consent. Each scope is tied to a specific data category:

| Scope | Data exposed to the AI agent |
| --- | --- |
| `profile.read` | Read the profile of the authorizing user and the public, viewer-projected profiles of other users: username, display name, bio, avatar, and follower counts. Never includes body measurements — those are behind body.read. |
| `profile.write` | Update the authorizing user’s public profile fields: display name, bio, location, website, and avatar. Identity fields (username, date of birth, sex) and body measurements are excluded — body metrics require body.write. |
| `body.read`Health data (GDPR Art. 9) | Read the authorizing user’s body measurements: height, current weight, body-fat percentage, and their history. Health data (GDPR Article 9) — requires explicit consent. |
| `body.write`Health data (GDPR Art. 9) | Record body measurements (height, weight, body-fat percentage) on the authorizing user’s behalf. Health data (GDPR Article 9) — requires explicit consent. |
| `follows.write` | Follow and unfollow other users on the authorizing user’s behalf (social-graph mutations). |
| `posts.read` | Read the authorizing user’s feed and any posts, replies, likes, and attached media their account can see. Visibility is always viewer-projected — the token sees no more than the user would. |
| `posts.write` | Create posts and replies (including media upload/attach), like and comment, and delete the authorizing user’s own posts, acting as that user. Agent-authored content is provenance-stamped. |
| `workouts.read`Health data (GDPR Art. 9) | Read the authorizing user’s workouts, training sessions and history, and search the exercise library. Health data (GDPR Article 9) — requires explicit consent. |
| `workouts.write`Health data (GDPR Art. 9) | Create workout templates and log completed training sessions on the authorizing user’s behalf. Health data (GDPR Article 9) — requires explicit consent. |
| `nutrition.read`Health data (GDPR Art. 9) | Read the authorizing user’s nutrition data and use food search, food-description parsing, AI food-image analysis, and meal-plan generation. Health data (GDPR Article 9) — requires explicit consent. |
| `nutrition.write`Health data (GDPR Art. 9) | Log meals and nutrition diary entries on the authorizing user’s behalf. Health data (GDPR Article 9) — requires explicit consent. |
| `notifications.read` | Read the authorizing user’s notifications and recent account activity (new likes, comments, follows) so a connected assistant can react to it. |
| `memory.read` | Read the per-user memory notes connected assistants have stored for conversational continuity. |
| `memory.write` | Store per-user memory notes for conversational continuity across sessions of connected assistants. |
| `world.read` | Search the World map of outdoor gyms around coordinates you give the assistant and estimate walking, running and cycling routes (time, distance, calories, steps). Positions are used for the request only and are not stored. |
| `world.write` | Save a planned route (start position, destination and mode) to the authorizing user’s account so it appears in the Mouve app as "Planned by your assistant". The start position is personal location data and is deleted after 7 days. |
| `location.read` | Read the authorizing user’s latest precise location, only while they have switched on "Share location with assistants" in the Mouve app. One point, at most 24 hours old, deleted when they turn sharing off. Used to plan routes from where they are. |

The connector never exposes passwords, payment details, Stripe identifiers, or other users’ private data. Requests are scoped to your account only.

<a id="third-parties"></a>

## 4. Third-Party Processors

Some nutrition tools invoked through the MCP connector rely on OpenAI to interpret free-form text or images. When you (via an AI agent) call one of the tools listed below, the relevant input is forwarded to OpenAI for processing:

- `parse_food_description` — the natural-language food description you submit is sent to OpenAI text models.
- `analyze_food_image` — any food photograph you submit is sent to OpenAI Vision for recognition and portion estimation.
- `generate_meal_suggestion` and `generate_daily_meal_plan` — your stated preferences, calorie and macro targets are sent to OpenAI text models.

OpenAI is used under its API Terms. Data submitted through the OpenAI API is not used to train OpenAI models and is retained for up to 30 days for abuse monitoring before deletion. The AI agent you use (Anthropic’s Claude, OpenAI’s ChatGPT, or any other MCP client) is an independent controller for the conversation between you and that agent; its data handling is governed by its own privacy policy.

Further detail on Mouve’s AI processing is available in the [AI Transparency notice](/ai-transparency).

<a id="retention"></a>

## 5. Retention

- **OAuth access tokens** expire one hour after issuance.
- **OAuth refresh tokens** expire after 30 days of inactivity and are rotated on every use.
- **Authorization and audit logs** (token issuance, revocation, tool invocation metadata) are retained for **90 days** for security and abuse detection, then deleted.
- **Tool outputs** are not persisted by the MCP server itself. Retention of any data the AI agent caches locally is governed by that agent’s provider.
- **Underlying app data** (your workouts, meals, posts) follows the retention schedule described in the main [Privacy Policy](/privacy-policy).

<a id="user-control"></a>

## 6. User Control and Revocation

You can revoke an AI agent’s access at any time. Revocation prevents the agent from obtaining any new access tokens immediately; an access token it already holds expires on its own within one hour at most.

- **In-app:** visit [Settings](/settings) and remove the authorized connector from the connected applications list.
- **Programmatic:** send an authenticated `POST` to `https://api.mouve.it/oauth/revoke` with the token to revoke.
- **On the client side:** disconnecting the connector from within Claude, ChatGPT, or another MCP client instructs that client to stop using the token, but does not remove it from Mouve’s records — use one of the two options above to retire the grant itself.

<a id="lawful-basis"></a>

## 7. Lawful Basis (GDPR)

Processing associated with the MCP connector relies on your consent (GDPR Article 6(1)(a)), provided by approving the Mouve OAuth consent screen for the specific scopes you selected. Withdrawing consent by revoking the grant stops further processing; it does not affect the lawfulness of processing performed before withdrawal.

<a id="rights"></a>

## 8. Data Subject Rights

You have the right to access, rectify, erase, port, restrict, and object to processing of your personal data. These rights are exercised against Mouve as controller; to submit a request, email [support@mouve.it](mailto:support@mouve.it) or [privacy@mouve.it](mailto:privacy@mouve.it). Rights exercisable against third-party AI providers (Anthropic, OpenAI, or another MCP client you chose) are governed by their respective privacy policies.

<a id="related-documents"></a>

## 9. Related Documents

- [Mouve Privacy Policy](/privacy-policy) — governs your underlying account data.
- [MCP Connector Terms of Service](/legal/mcp-terms) — rules of use for the connector.
- [AI Transparency](/ai-transparency) — details of the AI systems Mouve deploys.
- [Mouve Terms of Service](/tos).

<a id="contact"></a>

## 10. Contact

**Privacy questions:** [privacy@mouve.it](mailto:privacy@mouve.it)

**User support:** [support@mouve.it](mailto:support@mouve.it)

**Security reports:** [security@mouve.it](mailto:security@mouve.it)

---

<!-- document: mcp-terms | version: 1.1 | effective: 2026-04-23 -->
Document: mcp-terms
Version: 1.1
Effective: 2026-04-23
Canonical: https://mouve.it/legal/mcp-terms
Markdown: https://mouve.it/legal/mcp-terms.md

# MCP Connector Terms of Service

Version 1.1 | Last updated: August 30, 2026 | Effective: April 23, 2026

<a id="purpose"></a>

## 1. Purpose

These terms govern your use of the Mouve Model Context Protocol (“MCP”) connector: a server that lets you expose a subset of your Mouve account data to AI agents such as Claude, ChatGPT, or any other MCP-compatible client through the OAuth 2.1 authorization flow.

These terms are supplemental to the main [Mouve Terms of Service](/tos). In the event of a conflict between the main Terms and this document, this document controls solely as to use of the MCP connector.

<a id="acceptance"></a>

## 2. Acceptance

You accept these terms by approving the Mouve OAuth consent screen for any MCP connector client. If you do not accept these terms, cancel the consent flow and do not grant access. Continuing to use the connector after changes to these terms constitutes acceptance of the revised version.

<a id="user-responsibilities"></a>

## 3. User Responsibilities

- Use the connector only for lawful purposes and in accordance with the main Mouve Terms of Service.
- Do not share, transfer, or otherwise distribute your OAuth access or refresh tokens. Authorizations are per user; each device or AI client that needs access should run its own authorization flow.
- Do not attempt to circumvent rate limits, scope restrictions, authentication, or other security controls.
- Do not instruct AI agents to request, exfiltrate, or attempt to infer data belonging to other Mouve users.
- Review the outputs of AI agents before acting on them. The connector can surface fitness and nutrition data to agents that will then generate suggestions; those suggestions are not medical advice.
- Revoke access promptly if a device or agent is lost, compromised, or no longer in use (see the MCP Privacy Policy for revocation options).

<a id="mouve-responsibilities"></a>

## 4. Mouve Responsibilities

- Provide the connector on a best-effort basis. No service-level agreement, uptime guarantee, or support response time is offered for the free tier.
- Apply rate limits to protect service stability. Current default for connector tool calls: 60 requests per 60 seconds, per user and per tool (this number is rendered from the same constant the connector enforces). Limits may change at any time and may be reduced without notice for abusive traffic.
- Process data in accordance with the [MCP Connector Privacy Policy](/legal/mcp-privacy) and the main [Mouve Privacy Policy](/privacy-policy).
- Suspend or restrict access that violates these terms, the main Terms of Service, applicable law, or that poses a security or stability risk.

<a id="ip"></a>

## 5. Intellectual Property

Mouve’s service, software, and branding remain the property of Mouve. Your account content remains yours, subject to the license grants set out in the main Terms of Service.

Content generated by a third-party AI agent in response to data obtained via the connector is subject to the intellectual-property provisions of that AI provider (for example, Anthropic or OpenAI) and any applicable law. Mouve makes no claim over content produced by a third-party AI agent. You are responsible for complying with the AI provider’s terms regarding reuse of such content.

<a id="third-party-ai"></a>

## 6. Third-Party AI Agents

Your interaction with a third-party AI agent is governed by that provider’s own terms and privacy policy. Mouve does not control the AI agent’s behavior, retention, or further use of data the connector returns. Developers and operators of applications and agents that access the Mouve API are additionally bound by the [Mouve Developer Terms](/legal/developer-terms), which restrict what they may do with data received from your account.

- Anthropic (Claude): [Commercial Terms](https://www.anthropic.com/legal/commercial-terms) / [Consumer Terms](https://www.anthropic.com/legal/consumer-terms)
- OpenAI (ChatGPT and API): [Terms of Use](https://openai.com/policies/terms-of-use)
- Any other MCP client: refer to that client’s published terms and privacy policy.

In addition, certain nutrition tools invoked through the connector internally call OpenAI on Mouve’s behalf; those calls are governed by the OpenAI API Terms and are described in the MCP Privacy Policy and the [AI Transparency notice](/ai-transparency).

<a id="termination"></a>

## 7. Termination

- **By you:** revoke consent at any time from your Mouve settings or through the `/oauth/revoke` endpoint. Revocation takes effect within minutes.
- **By Mouve:** we may suspend or terminate connector access with or without notice for violation of these terms, abuse, security incidents, legal requirements, or the discontinuation of the connector itself.

Termination of the connector does not terminate your Mouve account. Termination of your Mouve account under the main Terms automatically revokes all active connector grants.

<a id="disclaimers"></a>

## 8. Disclaimer of Warranties

To the maximum extent permitted by applicable law, the connector is provided “as is” and “as available”, without warranties of any kind, whether express, implied, or statutory, including without limitation warranties of merchantability, fitness for a particular purpose, non-infringement, uninterrupted availability, accuracy, or compatibility with any third-party AI agent.

Nothing in this section excludes or limits liability that cannot be excluded or limited under mandatory law, including consumer protection laws in the country where you reside.

<a id="liability"></a>

## 9. Limitation of Liability

To the maximum extent permitted by applicable law, Mouve will not be liable for indirect, incidental, special, consequential, punitive, or exemplary damages, or for loss of profits, revenue, data, or goodwill arising out of or related to the connector, even if Mouve has been advised of the possibility of such damages.

Mouve’s aggregate liability arising from or related to the connector is limited to the greater of (a) the amount you have paid to Mouve for the connector in the twelve months preceding the event giving rise to liability (zero for the free tier) and (b) EUR 50. Mandatory consumer rights are not affected.

<a id="governing-law"></a>

## 10. Governing Law

These terms are governed by the laws of Estonia, without prejudice to mandatory consumer protection laws in the country where you reside. Disputes are subject to the jurisdiction provisions set out in Section 18 of the main [Mouve Terms of Service](/tos).

<a id="changes"></a>

## 11. Changes to These Terms

We may update these terms as the connector evolves or to reflect legal or regulatory requirements. Material changes will be reflected in the version number and effective date at the top of this page. Continued use after the effective date of a new version constitutes acceptance of that version. If you do not accept the change, revoke your connector authorization.

<a id="contact"></a>

## 12. Contact

**Support:** [support@mouve.it](mailto:support@mouve.it)

**Privacy:** [privacy@mouve.it](mailto:privacy@mouve.it)

**Security:** [security@mouve.it](mailto:security@mouve.it)

---

<!-- document: venue-terms | version: venue-terms-1.0 | effective: 2026-10-25 -->
Document: venue-terms
Version: venue-terms-1.0
Effective: 2026-10-25
Canonical: https://mouve.it/legal/venue-terms
Markdown: https://mouve.it/legal/venue-terms.md

Version venue-terms-1.0

Draft, not yet in force.

---

<!-- document: venue-dpa | version: venue-dpa-1.0 | effective: 2026-10-25 -->
Document: venue-dpa
Version: venue-dpa-1.0
Effective: 2026-10-25
Canonical: https://mouve.it/legal/venue-dpa
Markdown: https://mouve.it/legal/venue-dpa.md

Version venue-dpa-1.0

Draft, not yet in force.

---

<!-- document: data-sources | version: 1.0 | effective: 2026-10-02 -->
Document: data-sources
Version: 1.0
Effective: 2026-10-02
Canonical: https://mouve.it/legal/data-sources
Markdown: https://mouve.it/legal/data-sources.md

# Nutrition Data Sources

Last updated: October 2, 2026

<a id="summary"></a>

## 1. Summary

The calories and nutrients Mouve shows for everyday foods come from public food composition databases maintained by government food agencies, and from OpenFoodFacts for packaged products. We are grateful to the people who build them. Where a licence asks for credit, this page is where we give it.

<a id="usda"></a>

## 2. USDA FoodData Central

U.S. Department of Agriculture, Agricultural Research Service. [FoodData Central](https://fdc.nal.usda.gov/) (SR Legacy and Foundation Foods). Public domain (CC0 1.0).

<a id="ciqual"></a>

## 3. ANSES Ciqual

ANSES. 2025. Ciqual French food composition table. [doi:10.5281/zenodo.17550133](https://doi.org/10.5281/zenodo.17550133). Licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) (also published under the [Etalab Open Licence 2.0](https://www.etalab.gouv.fr/licence-ouverte-open-licence/)). Mouve converts units and derives vitamin A as retinol activity equivalents from the published retinol and beta-carotene values.

<a id="cnf"></a>

## 4. Canadian Nutrient File

Health Canada. [Canadian Nutrient File](https://www.canada.ca/en/health-canada/services/food-nutrition/healthy-eating/nutrient-data.html) (2015). Contains information licensed under the [Open Government Licence – Canada](https://open.canada.ca/en/open-government-licence-canada).

<a id="cofid"></a>

## 5. UK CoFID (McCance and Widdowson)

Office for Health Improvement and Disparities. [McCance and Widdowson’s Composition of Foods Integrated Dataset](https://www.gov.uk/government/publications/composition-of-foods-integrated-dataset-cofid) (CoFID, 2021). Contains public sector information licensed under the [Open Government Licence v3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/). Mouve converts carbohydrate from monosaccharide equivalents to grams and derives vitamin A as retinol activity equivalents.

<a id="fineli"></a>

## 6. Finnish Fineli

Finnish Institute for Health and Welfare (THL). [Fineli food composition database](https://fineli.fi/fineli/en/avoin-data), Basic package 2. Licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Fineli publishes energy in kilojoules only; Mouve converts to kilocalories using the standard 4.184 kJ/kcal factor.

<a id="slv"></a>

## 7. Swedish Livsmedelsdatabasen

Livsmedelsverket (Swedish Food Agency). [Livsmedelsdatabasen](https://dataportal.livsmedelsverket.se/livsmedel/api/v1) open-data API. Licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Mouve derives vitamin A as retinol activity equivalents from the published retinol and beta-carotene values, the same conversion applied to Ciqual and CoFID.

<a id="matvaretabellen"></a>

## 8. Norwegian Matvaretabellen

Norwegian Food Safety Authority, Directorate of Health and University of Oslo. [Matvaretabellen (the Norwegian Food Composition Table)](https://www.matvaretabellen.no/). Published under the [Norwegian Licence for Open Government Data (NLOD) 2.0](https://data.norge.no/nlod/en/2.0), treated as equivalent to CC BY 4.0 (attribution only).

<a id="bls"></a>

## 9. German BLS 4.0

Max Rubner-Institut. 2025. [Bundeslebensmittelschlüssel (BLS), version 4.0](https://blsdb.de/download). Licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) since the 4.0 release (2025-12-16); earlier versions were restricted and are not used by Mouve. Mouve converts vitamin B6 from micrograms to milligrams to match the rest of this collection.

<a id="openfoodfacts"></a>

## 10. OpenFoodFacts

Packaged-product data from [OpenFoodFacts](https://world.openfoodfacts.org), available under the [Open Database License](https://opendatacommons.org/licenses/odbl/1-0/).

<a id="recipes"></a>

## 11. Mouve Standard Recipes

Sauces and home-cooked dishes that no public database covers (chimichurri, for example) use Mouve standard recipes: a typical formulation with explicit ingredient weights. Their nutrients are calculated from the USDA values of those ingredients, adjusted for water lost in cooking and fat poured off — never estimated by hand. A dish you cook yourself will differ from the typical recipe; adjust the entry if you know what went into it.

---

<!-- document: photo-credits | version: 1.0 | effective: 2026-09-26 -->
Document: photo-credits
Version: 1.0
Effective: 2026-09-26
Canonical: https://mouve.it/legal/photo-credits
Markdown: https://mouve.it/legal/photo-credits.md

# Photo Credits

Last updated: September 26, 2026

<a id="summary"></a>

## 1. Summary

Product photographs in Mouve come from three places, and every one of them is either openly licensed or given to us directly. We store the source and the licence alongside each individual picture, which is what lets us credit it correctly and remove it precisely if it is ever contested.

We host copies of these images on our own infrastructure rather than loading them from someone else’s servers. That is partly reliability — a photo does not disappear because a third party reorganised their site — and partly courtesy: the largest source is a volunteer-run non-profit, and we would rather not send them our traffic.

<a id="openfoodfacts"></a>

## 2. OpenFoodFacts

Most branded product photographs in Mouve come from [OpenFoodFacts](https://world.openfoodfacts.org), a collaborative, free and open database of food products built by volunteers around the world.

Photographs contributed to OpenFoodFacts are published under the [Creative Commons Attribution-ShareAlike 3.0](https://creativecommons.org/licenses/by-sa/3.0/) licence. Credit goes to the OpenFoodFacts contributors who took and uploaded them. Each photo in Mouve links back to its product page on OpenFoodFacts, where you can see the original and its history.

Note that the OpenFoodFacts *database* is licensed separately, under the [Open Database License](https://opendatacommons.org/licenses/odbl/1-0/). The two are different licences covering different things.

If you would like more products to have photographs — and in some countries, including Estonia, most still do not — the most direct way to help is to contribute one to OpenFoodFacts. It benefits every app built on the database, not only this one.

<a id="wikimedia"></a>

## 3. Wikimedia Commons

Some generic ingredient images come from [Wikimedia Commons](https://commons.wikimedia.org). Commons files are licensed individually rather than under one blanket licence, so we record the specific licence for each file we use and never assume one. The credit line under the image names it, and links to both the file page and the licence text.

<a id="brands"></a>

## 4. Brand-Supplied Images

Producers and brands can supply their own product imagery for the SKUs they own. These are used with the brand’s permission under our producer terms, and are marked as brand-supplied.

If you represent a brand and want your own photography used for your products, get in touch — see [Contact](/contact).

<a id="ai-illustrations"></a>

## 5. AI-Generated Illustrations

Pictures of generic foods — an apple, cooked rice, a boiled egg — are illustrations that Mouve generated with an AI image model (FLUX.2 \[klein\]). They are not photographs, and they do not show any particular product or the food you ate. Where one is shown at size, it is labelled “AI image”. Nobody else’s work is involved, so they carry no credit line.

<a id="your-photos"></a>

## 6. Your Own Photos

When you photograph a meal to log it, that photo is yours. It stays private to your account, it is not published to any of the sources above, and it carries no credit line because none is needed. Where a food you logged shows your own photo, that is what you are seeing — not a catalogue picture.

<a id="what-we-dont"></a>

## 7. What We Do Not Do

We do not take product photographs from manufacturer or retailer websites. Those images are copyrighted, and finding one on the web is not permission to redistribute it in a commercial product.

This is enforced in the software rather than left to judgement: our image pipeline will only fetch from an explicit list of approved sources, and it refuses to store any image without a recorded licence. A picture with no known terms cannot enter Mouve at all.

<a id="contest"></a>

## 8. Contesting an Image

If you believe a photograph in Mouve is used without the right to do so — because you hold the rights, because the licence was misrecorded, or for any other reason — tell us and we will remove it.

Because we store the source and licence for each individual image, we can remove exactly the pictures a complaint covers, and our system records the removal so the same image is not re-fetched later. You do not need to identify a product ID; the product name or barcode, or a link to the original photograph, is enough.

For formal copyright notices, see our [Copyright policy](/copyright) and [Notice & Action](/notice-and-action) procedure.

<a id="contact"></a>

## 9. Contact

Questions about image sourcing, licensing or attribution: [hello@mouve.it](mailto:hello@mouve.it).

---

<!-- document: help | version: 1.0 | effective: 2026-09-13 -->
Document: help
Version: 1.0
Effective: 2026-09-13
Canonical: https://mouve.it/help
Markdown: https://mouve.it/help.md

# Hey, how can I help?

<a id="getting-started"></a>

## Getting Started

New to Mouve? Start here.

<a id="getting-started-how-do-i-create-an-account"></a>

How do I create an account?

Download Mouve from the App Store or visit mouve.it. You can sign up with your email address or use Google sign-in. After creating your account, you'll go through a quick onboarding to set up your profile and fitness goals.

<a id="getting-started-is-mouve-free-to-use"></a>

Is Mouve free to use?

Mouve offers a free tier with core features including workout tracking, basic nutrition logging, and community access. Mouve Pro unlocks advanced features like AI-powered meal plans, detailed analytics, body scanning, and more.

<a id="getting-started-how-do-i-set-up-my-profile"></a>

How do I set up my profile?

After signing up, the onboarding flow will guide you through setting your fitness goals, body metrics, and dietary preferences. You can update these anytime from Settings in the app.

<a id="getting-started-is-mouve-available-on-both-ios-and-web"></a>

Is Mouve available on both iOS and web?

Yes! Mouve is available as a native iOS app and as a web app at mouve.it. Your data syncs seamlessly across both platforms.

<a id="workouts"></a>

## Workouts

Tracking, templates, and programs.

<a id="workouts-how-do-i-log-a-workout"></a>

How do I log a workout?

Tap the "+" button or go to Workouts to start a new session. You can choose from your saved templates, browse exercises, or create a custom workout. Log sets, reps, and weight as you go, then complete the session when you're done.

<a id="workouts-what-are-workout-templates"></a>

What are workout templates?

Templates are saved workout routines you can reuse. Create a template with your favorite exercises, set/rep schemes, and notes. Next time you train, just start the template instead of building from scratch.

<a id="workouts-how-do-workout-programs-work"></a>

How do workout programs work?

Programs are structured training plans spanning multiple weeks. Each program contains scheduled workouts organized by day. You can create your own programs or follow ones shared by the community.

<a id="workouts-can-i-share-my-workouts"></a>

Can I share my workouts?

Yes! After completing a workout, you can share it as a post to your feed or generate a shareable link. Other users can view your workout details and even save your template.

<a id="workouts-how-do-i-view-my-workout-history"></a>

How do I view my workout history?

Go to Workouts > History to see all your past sessions. You can filter by date, view weekly stats, and tap any session to see full details including exercises, sets, and personal records.

<a id="nutrition"></a>

## Nutrition

Food logging, scanning, and meal plans.

<a id="nutrition-how-do-i-log-food"></a>

How do I log food?

Go to Nutrition and tap "Add Food" for any meal (breakfast, lunch, dinner, snacks). You can search our database of thousands of foods, scan a barcode, or create custom entries. Nutritional info is calculated automatically.

<a id="nutrition-how-does-barcode-scanning-work"></a>

How does barcode scanning work?

Tap the scan icon when adding food to open the camera. Point it at any product barcode and Mouve will look up the nutritional information from our database. If a product isn't found, you can add it manually.

<a id="nutrition-what-are-ai-meal-plans"></a>

What are AI meal plans?

Mouve Pro subscribers can generate personalized meal plans powered by AI. Based on your goals, dietary preferences, and calorie targets, the AI creates balanced daily meal suggestions with recipes and nutritional breakdowns.

<a id="nutrition-how-do-i-track-micronutrients"></a>

How do I track micronutrients?

Mouve Pro includes detailed micronutrient tracking. Go to Nutrition > Micronutrients to see your daily intake of vitamins and minerals. This helps ensure you're meeting all your nutritional needs beyond just calories and macros.

<a id="nutrition-can-i-save-recipes"></a>

Can I save recipes?

Yes! Use the Cookbook feature to save and organize your recipes. You can create recipes from scratch with ingredients and instructions, and easily log them as meals.

<a id="subscription"></a>

## Subscription & Billing

Plans, payments, and invoices.

<a id="subscription-what-does-mouve-pro-include"></a>

What does Mouve Pro include?

Mouve Pro unlocks AI-powered meal plans, advanced analytics and charts, body composition scanning, micronutrient tracking, workout programs, and priority support. Check our pricing page for the latest features.

<a id="subscription-how-do-i-upgrade-to-pro"></a>

How do I upgrade to Pro?

Go to Settings > Subscription or visit the Pricing page. Choose between monthly or yearly plans. Payment is processed securely through Stripe.

<a id="subscription-how-do-i-cancel-my-subscription"></a>

How do I cancel my subscription?

Go to Settings > Subscription and click "Manage Subscription." You can cancel anytime and will retain Pro access until the end of your current billing period. No cancellation fees apply.

<a id="subscription-can-i-get-a-refund"></a>

Can I get a refund?

If you're not satisfied within the first 7 days of your subscription, contact us at support@mouve.it for a full refund. After 7 days, refunds are handled on a case-by-case basis.

<a id="subscription-how-do-i-update-my-payment-method"></a>

How do I update my payment method?

Go to Settings > Subscription > Manage Subscription. You'll be directed to your Stripe billing portal where you can update your card, view invoices, and manage your payment details.

<a id="account"></a>

## Account & Privacy

Settings, security, and your data.

<a id="account-how-do-i-change-my-email-or-password"></a>

How do I change my email or password?

Go to Settings > Account to update your email address or password. You'll receive a confirmation email when changing your email. If you signed up with Google, you can add a password from the same screen.

<a id="account-how-do-i-delete-my-account"></a>

How do I delete my account?

Go to Settings > Account > Delete Account. This permanently removes all your data including workouts, nutrition logs, and profile information. This action cannot be undone.

<a id="account-what-data-does-mouve-collect"></a>

What data does Mouve collect?

Mouve collects the data you provide (profile info, workouts, nutrition logs) and basic usage analytics to improve the app. We never sell your personal data. For full details, see our Privacy Policy.

<a id="account-how-does-mouve-use-ai"></a>

How does Mouve use AI?

Mouve uses AI for features like meal plan generation, food image analysis, and workout suggestions. Your data is processed securely and not used to train third-party AI models. See our AI Transparency page for more details.

<a id="account-can-i-export-my-data"></a>

Can I export my data?

Yes, and you can do it yourself. In the app go to Settings, then Download your data. On the web go to Settings, then Data Management, then Export Data. You get one ZIP file with your data as JSON plus your own photos and files. Questions: privacy@mouve.it.

### Still need help?

Can't find what you're looking for? Our team is here to help.

[Contact Support](/contact)

---

<!-- document: contact | version: 1.0 | effective: 2026-09-13 -->
Document: contact
Version: 1.0
Effective: 2026-09-13
Canonical: https://mouve.it/contact
Markdown: https://mouve.it/contact.md

# Contact Us

Have a question, feedback, or need help? Reach out through any of the channels below.

## General Support

Questions about your account, features, or anything else.

[support@mouve.it](mailto:support@mouve.it)

## Feedback

Ideas, suggestions, or feature requests — we'd love to hear from you.

[feedback@mouve.it](mailto:feedback@mouve.it)

## Privacy & Data

Data requests, privacy concerns, or GDPR inquiries.

[privacy@mouve.it](mailto:privacy@mouve.it)

We aim to respond to all inquiries within 48 hours. For urgent matters related to account security, please include “URGENT” in your email subject line.