Do I need to disclose MyFitnessPal API in my privacy policy?

Yes. MyFitnessPal API collects health-related data including food logs, calorie tracking, weight measurements, and exercise information. Under GDPR, nutrition and weight data qualify as special category health data requiring explicit disclosure. You must inform users that MyFitnessPal LLC processes this data in the United States and explain their rights regarding health information.

What specific information does MyFitnessPal API collect?

MyFitnessPal API collects food diary entries and meal logs, calorie and macronutrient tracking data, exercise and activity logs, weight and body measurements, and dietary goals and food preferences. All of this data is transmitted to MyFitnessPal's servers for processing and storage.

Do I need a cookie consent banner for MyFitnessPal API?

No cookie consent banner is specifically required for MyFitnessPal API itself, as no cookies are documented as part of the API integration. However, your website may use cookies for other purposes, requiring separate consent management. Always verify your implementation for any cookies your website independently deploys.

Who processes MyFitnessPal API data and where is it stored?

MyFitnessPal LLC, a United States-based company, acts as the data processor. User data is transferred to and stored on MyFitnessPal's servers in the US. Under GDPR, this international transfer requires appropriate safeguards. Review MyFitnessPal's privacy policy at https://www.myfitnesspal.com/privacy-policy for their data handling practices and security measures.

Health & Fitness

Privacy policy clauses for MyFitnessPal API

MyFitnessPal API is a nutrition and fitness tracking integration that allows websites to collect and log users' food intake, exercise activity, body measurements, and dietary goals. Websites implement it to enable users to track nutritional data and fitness metrics directly through their platform.

Scan my site free →Copy sample clause ↓

Free scan · No signup · Results in 60 seconds

What data MyFitnessPal API collects

Your privacy policy must disclose each of the following data types when you use MyFitnessPal API.

Food diary and meal logs

Calorie and macro tracking

Exercise logging

Weight and body measurements

Dietary goals and preferences

When does MyFitnessPal API trigger privacy obligations?

Activation Point

Integrating MyFitnessPal API triggers compliance obligations the moment your application begins collecting or transmitting user health data (food logs, weight, exercise, macros, dietary goals) to MyFitnessPal LLC's servers. This is not a deferred obligation—data flows begin immediately upon API initialization.

Applicable Regulations

GDPR (if users are in EU/EEA):

Privacy policy clauses for MyFitnessPal API

What data MyFitnessPal API collects

When does MyFitnessPal API trigger privacy obligations?

Activation Point

Applicable Regulations

First Concrete Step

Where data goes

Common compliance pitfalls

Pitfall 1: Treating Health Data as Standard Analytics

Pitfall 2: Missing DPA or Incomplete Processor Terms

Pitfall 3: Inadequate Transatlantic Data Transfer Mechanism

Legal note

Sample privacy policy clause

What regulators look for

DPA Audit Priorities

Frequently asked questions

Do I need to disclose MyFitnessPal API in my privacy policy?

What specific information does MyFitnessPal API collect?

Do I need a cookie consent banner for MyFitnessPal API?

Who processes MyFitnessPal API data and where is it stored?

Don't ship without Bandit.