Create a Privacy Policy for iOS and Android Apps

Tested prompts for privacy policy generator for mobile apps compared across 5 leading AI models.

BEST BY JUDGE SCORE Claude Haiku 4.5 8/10

If you're building an iOS or Android app and collecting any user data, you're legally required to publish a privacy policy before you can list on the App Store or Google Play. Apple explicitly rejects apps that lack one, and Google flags missing or inadequate policies during review. This isn't optional paperwork — it's a hard gate between your app and your users.

The challenge is that privacy policies for mobile apps have specific requirements that generic document generators miss. You need to cover mobile-specific data points: device identifiers, push notification tokens, location permissions, camera and microphone access, and third-party SDKs like Firebase, Admob, or Facebook Login. A policy built for a SaaS website won't satisfy App Store reviewers or GDPR/CCPA compliance standards when applied to a native app.

This page shows you how to use an AI prompt to generate a complete, accurate privacy policy for your mobile app in minutes. You'll see the exact prompt structure that works, four model outputs compared side by side, and practical guidance on how to customize the result for your specific app's data practices. Whether you're a solo developer shipping your first app or a startup preparing for launch, this workflow gets you to a usable first draft fast.

When to use this

This approach works best when you need a legally structured starting draft quickly and plan to review it with a lawyer or compliance tool before publishing. It fits indie developers, small teams, and early-stage startups who collect standard mobile data and use common third-party services.

  • Launching a new iOS or Android app and need a privacy policy before App Store or Google Play submission
  • Using common third-party SDKs (Firebase, AdMob, Stripe, Facebook SDK) and need those disclosed in plain language
  • Building an app that requests device permissions like location, camera, microphone, or contacts
  • Updating an existing privacy policy after adding new features or data collection practices
  • Creating a privacy policy for a client app as a freelance developer or agency

When this format breaks down

  • Your app handles health data (HealthKit, HIPAA-adjacent), financial records, or data from children under 13 (COPPA) — these require specialized legal counsel, not a generated draft
  • You're in a heavily regulated industry like telemedicine, fintech, or edtech targeting minors, where boilerplate language creates real legal liability
  • You plan to publish the AI output without any human review — privacy policies are legal documents and jurisdiction-specific nuances require verification
  • Your app operates across the EU and you need a full GDPR-compliant Data Processing Agreement in addition to a user-facing policy — that's a separate, more complex document

The prompt we tested

You are a privacy policy generator specialized in mobile applications for iOS and Android. Generate a comprehensive, legally-structured privacy policy based on the app details provided below.

Rules and formatting requirements:
Output a complete, ready-to-publish privacy policy in clean Markdown with clear H2 section headings and concise bullet points under each section. Use plain, user-friendly legal language that complies with GDPR, CCPA, COPPA, Apple App Store, and Google Play requirements, and explicitly reference the mobile platforms (iOS/Android), SDKs, and permissions mentioned by the user. Keep the total length between 900 and 1500 words and do not include any commentary outside the policy itself.

App details provided by the user:
App Name: FitPulse. Platforms: iOS and Android. The app is a fitness tracking app that collects user email, name, age, weight, GPS location during workouts, and health data from Apple HealthKit and Google Fit. We use Firebase Analytics, Crashlytics, RevenueCat for subscriptions, and Meta Ads SDK. Company: FitPulse Inc., based in California, contact support@fitpulse.app. Users must be 13+.

Produce the complete privacy policy now, tailored to the app details above. Include all standard sections: Introduction, Information We Collect (personal data, device data, usage data), How We Use Your Information, Third-Party Services and SDKs, Data Sharing and Disclosure, Data Retention, Data Security, Children's Privacy (COPPA), Your Privacy Rights (GDPR, CCPA), International Data Transfers, Permissions Requested (camera, location, contacts, notifications, etc.), Push Notifications and Analytics, Changes to This Policy, and Contact Information. Use placeholders like [Effective Date] and [Contact Email] where the user did not provide specifics.

Model comparison

ModelQualityCostLatencyTokens
Claude Opus 4.7 7 $0.1631 26.6s 633 / 2048
Claude Haiku 4.5 8 $0.0107 18.5s 420 / 2048
GPT-5.4 6 $0.0316 41.7s 367 / 2048
Gemini 2.5 Pro 2 $0.0017 17.8s 371 / 254
Grok 4.1 Fast Reasoning 8 $0.0009 19.3s 512 / 1606

Outputs

Claude Opus 4.7 7/10
# FitPulse Privacy Policy

**Effective Date:** [Effective Date]
**Last Updated:** [Effective Date]

## Introduction

FitPulse Inc. ("FitPulse," "we," "us," or "our") respects your privacy and is committed to protecting the personal information you share with us through the FitPulse mobile application (the "App") available on iOS and Android. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use FitPulse.

- This policy applies to all users of the FitPulse App on iOS (via the Apple App Store) and Android (via Google Play).
- By downloading, accessing, or using FitPulse, you agree to the terms of this Privacy Policy.
- If you do not agree, please do not install or use the App.

## Information We Collect

### Personal Data
- **Account information:** name, email address, age, and password.
- **Health and fitness profile:** weight, height, fitness goals, workout history.
- **Subscription data:** billing identifiers managed through Apple App Store, Google Play, and RevenueCat (we do not store full payment card details).

### Health and Location Data
- **Apple HealthKit (iOS):** steps, heart rate, workouts, calories, and other metrics you authorize.
- **Google Fit (Android):** activity data, heart rate, step count, and other fitness metrics you authorize.
- **GPS location:** precise location collected during active workouts to map routes, distance, and pace.

### Device Data
- Device model, operating system version (iOS/Android), unique device identifiers (IDFA on iOS, AAID on Android), language, time zone, mobile carrier, and app version.

### Usage Data
- In-app interactions, features used, session duration, workout frequency, screens viewed, crash reports, and diagnostic logs.

> **Note on HealthKit:** Data received from Apple HealthKit is never used for advertising, shared with third parties for marketing, or sold, in compliance with Apple's HealthKit requirements.

## How We Use Your Information

We use the information we collect to:

- Create and manage your FitPulse account.
- Provide core fitness tracking, workout mapping, and progress analytics.
- Process subscriptions and in-app purchases via RevenueCat.
- Personalize your experience, recommendations, and training plans.
- Send transactional emails, push notifications, and service announcements.
- Monitor app performance, diagnose crashes, and improve stability.
- Display relevant advertising outside the App (excluding HealthKit/Google Fit data).
- Comply with legal obligations and enforce our Terms of Service.

## Third-Party Services and SDKs

FitPulse integrates the following third-party SDKs and services, each governed by its own privacy policy:

- **Firebase Analytics (Google):** usage analytics and user engagement metrics.
- **Firebase Crashlytics (Google):** crash reporting and stability diagnostics.
- **RevenueCat:** subscription management and receipt validation.
- **Meta Ads SDK (Facebook):** advertising attribution and measurement of ad campaigns.
- **Apple HealthKit (iOS):** access to health metrics with your explicit authorization.
- **Google Fit (Android):** access to fitness data with your explicit authorization.

These providers may collect device identifiers, IP address, and usage events as described in their own privacy notices.

## Data Sharing and Disclosure

We do **not** sell your personal information. We may share data with:

- **Service providers** (e.g., cloud hosting, analytics, crash reporting, subscription processors) acting under written data-processing agreements.
- **Advertising partners** (e.g., Meta) for non-health, non-HealthKit data used in attribution and measurement.
- **Legal and regulatory authorities** when required to comply with applicable law, subpoena, or court order.
- **Business transfers**, such as in the case of a merger, acquisition, or sale of assets, with continued protection of your data.

We never share HealthKit or Google Fit data with advertisers or data brokers.

## Data Retention

- Account and profile data are retained while your account is active.
- Workout, GPS, and health data are retained until you delete them or close your account.
- Crash logs and analytics data are retained for up to 24 months.
- Subscription records are retained as required by tax and accounting laws.
- You may request deletion of your account and associated data at any time.

## Data Security

We implement technical and organizational measures to protect your information, including:

- TLS/HTTPS encryption in transit.
- Encryption at rest for sensitive data.
- Access controls, authentication, and least-privilege principles.
- Regular security reviews and vendor assessments.

No method of electronic transmission or storage is 100% secure, and we cannot guarantee absolute security.

## Children's Privacy (COPPA)

- FitPulse is not intended for children under **13 years old**.
- We do not knowingly collect personal information from children under 13.
- If we learn that we have collected data from a child under 13, we will delete it promptly.
- Parents or guardians who believe their child has provided us information may contact support@fitpulse.app.

## Your Privacy Rights

### GDPR (European Economic Area, UK, Switzerland)
You have the right to:
- Access, correct, or delete your personal data.
- Object to or restrict processing.
- Withdraw consent at any time.
- Port your data to another service.
- Lodge a complaint with your local Data Protection Authority.

Legal bases for processing include consent, contract performance, legitimate interests, and legal obligations.

### CCPA/CPRA (California Residents)
You have the right to:
- Know what personal information we collect, use, and disclose.
- Request deletion or correction of your personal information.
- Opt out of the "sale" or "sharing" of personal information (we do not sell personal information as defined by law).
- Non-discrimination for exercising your rights.
- Limit the use of sensitive personal information.

To exercise any rights, contact us at support@fitpulse.app. We will verify your identity before fulfilling requests.

## International Data Transfers

- FitP
Judge notes: The output is cut off mid-section ("FitP") before completing International Data Transfers, Permissions Requested, Push Notifications and Analytics, Changes to This Policy, and Contact Information sections, making it incomplete and not production-ready.
Claude Haiku 4.5 8/10
# Privacy Policy for FitPulse

**Effective Date:** [Effective Date]

**Last Updated:** [Last Updated Date]

## 1. Introduction

FitPulse Inc. ("**Company**," "**we**," "**us**," or "**our**") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application, FitPulse (the "**App**"), available on iOS and Android platforms, and our related services (collectively, the "**Service**").

Please read this Privacy Policy carefully. By accessing or using FitPulse, you acknowledge that you have read, understood, and agree to be bound by all the terms of this Privacy Policy. If you do not agree with our policies and practices, please do not use our App.

**Minimum Age Requirement:** FitPulse is intended for users aged 13 years or older. By using this App, you represent and warrant that you meet this age requirement.

---

## 2. Information We Collect

### Personal Information
We collect the following personal information you voluntarily provide:

- **Account Information:** Email address, name, age, and weight
- **Health and Fitness Data:** Workout duration, distance, calories burned, heart rate, and other health metrics integrated from Apple HealthKit (iOS) and Google Fit (Android)
- **Location Data:** GPS coordinates and location history during workouts (collected only when you enable location services and start a workout)

### Device and Technical Information
We automatically collect:

- **Device Identifiers:** Device type, operating system version, unique device identifiers, and device settings
- **App Usage Data:** Features accessed, workout frequency, session duration, crash reports, and performance analytics
- **Network Information:** IP address and mobile network provider information

### Information from Third-Party Sources
We receive information from:

- **Apple HealthKit (iOS):** Health and fitness data you authorize to sync with FitPulse
- **Google Fit (Android):** Health and fitness data you authorize to sync with FitPulse
- **Analytics and Advertising Providers:** Usage patterns, device information, and advertising interaction data (see Section 5 for details)

---

## 3. How We Use Your Information

We use collected information for the following purposes:

- **Service Delivery:** Creating and maintaining your account, providing fitness tracking features, and delivering personalized workout recommendations
- **Analytics and Improvement:** Understanding user behavior, improving App functionality, and optimizing user experience through Firebase Analytics and Crashlytics
- **Subscription Management:** Processing payments, managing subscription tiers, and billing inquiries through RevenueCat
- **Advertising and Marketing:** Displaying personalized advertisements via Meta Ads SDK and sending promotional content (with your consent where required)
- **Communication:** Responding to support requests, sending service updates, and notifying you of policy changes
- **Legal Compliance:** Fulfilling legal obligations, enforcing Terms of Service, and protecting against fraud or security threats
- **Location-Based Features:** Providing map visualizations, route tracking, and location-specific performance analytics during workouts

---

## 4. Third-Party Services and SDKs

FitPulse integrates the following third-party services and software development kits (SDKs):

### Firebase (Google Analytics and Crashlytics)
- **Purpose:** App analytics, crash reporting, and performance monitoring
- **Data Shared:** Device information, app usage events, crash logs, and anonymous identifiers
- **Privacy Policy:** https://policies.google.com/privacy

### RevenueCat
- **Purpose:** Subscription management, in-app purchase processing, and billing
- **Data Shared:** Email, subscription status, purchase history, and device identifiers
- **Privacy Policy:** https://www.revenuecat.com/privacy

### Meta Ads SDK
- **Purpose:** Serving personalized advertisements and measuring ad performance
- **Data Shared:** Device identifiers, app usage patterns, and anonymized user behavior
- **Privacy Policy:** https://www.facebook.com/about/privacy

### Apple HealthKit (iOS) and Google Fit (Android)
- **Purpose:** Accessing authorized health and fitness data
- **Data Shared:** Only data you explicitly authorize and approve through OS-level permissions
- **Privacy Policy:** Apple (https://www.apple.com/privacy) and Google (https://policies.google.com/privacy)

These third parties may use your information according to their own privacy policies. We recommend reviewing their privacy policies directly.

---

## 5. Data Sharing and Disclosure

We do **not** sell your personal information to third parties for marketing purposes. However, we may share information in the following circumstances:

- **Service Providers:** With vendors and contractors who process data on our behalf under strict confidentiality obligations
- **Legal Requirements:** When required by law, court order, or government request, or to protect our legal rights
- **Business Transfers:** In the event of merger, acquisition, bankruptcy, or sale of assets, your information may be transferred as part of that transaction
- **Aggregated Data:** We may share anonymized and aggregated data that cannot identify you for research, marketing, and analytics purposes
- **With Your Consent:** When you explicitly authorize us to share information with third parties

---

## 6. Data Retention

We retain your personal information as follows:

- **Account Data:** Retained while your account is active and for 12 months after account deletion unless legally required to retain longer
- **Health and Fitness Data:** Retained for the duration of your subscription; deleted within 30 days of account termination
- **Location Data:** Retained for 90 days unless needed for legal, security, or fraud prevention purposes
- **Analytics Data:** Aggregated and anonymized analytics are retained indefinitely; individual event logs are retained for 12 months
- **Backup Data:** Backup copies may be retained for up to 30 days after deletion

---

## 7. Data Security

We implement reasonable technical, administrative, and physical safeguards to protect your information:

- **Encryption:** All data transmission between your device and our servers uses TLS/SSL encryption
- **Secure Storage:** Personal information is stored in encrypted databases with access controls
- **Access Restrictions:** Only authorized personnel with a legitimate business need can access sensitive data
- **Regular Audits:** We conduct periodic security assessments and vulnerability testing

**No security system is completely impenetrable.** While we strive to protect your information, we cannot guarantee absolute security. You are responsible for maintaining the confidentiality of your account credentials.

---

## 8. Children's Privacy (COPPA Compliance)

FitPulse is not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13.

**If you are a parent or guardian** and believe your child has provided information to FitPulse, please contact us immediately at support@fitpulse.app, and we will delete such information promptly.

For users aged 13–17, we provide additional privacy protections and limit data collection and marketing practices consistent with applicable child protection laws.

---

## 9. Your Privacy Rights

### GDPR (European Users)
If you are located in the European Union, you have the following rights:

- **Right of Access:** Request a copy of personal data we hold about you
- **Right to Rectification:** Correct inaccurate or incomplete information
- **Right to Erasure:** Request deletion of your personal data ("Right to be Forgotten")
- **Right to Restrict Processing:** Limit how we use your information
- **Right to Data Portability:** Receive your data in a structured, portable format
- **Right to Object:** Oppose processing of your information for marketing or profiling purposes
- **Right to Withdraw Consent:** Revoke consent for data collection at any time

### CCPA (California Users)
If you are a California resident, you have the right to:

- **Know** what personal information is collected, used, and shared
- **Delete** personal information collected from you (subject to certain exceptions)
- **Opt-Out** of the sale or sharing of your personal information
- **Correct** inaccurate personal information
- **Access** your personal information in a portable and readily useable format

**California Shine the Light:** You may request information about categories of personal information we share with third parties for their marketing purposes.

### Other U.S. State Privacy Laws
Similar privacy rights may apply if you reside in Colorado, Connecticut, Utah, Virginia, or other states with privacy legislation.

**To Exercise Your Rights:** Contact us at support@fitpulse.app with the subject line "Privacy Rights Request." Please include your name, email, and a detailed description of your request. We will respond within 30 days.

---

## 10. International Data Transfers

FitPulse Inc. is based in California, United States. Your personal information may be transferred to, stored in, and processed in the United States or other countries where we and our service providers operate.

**For European Users:**
Judge notes: The output is cut off mid-section (Section 10 ends abruptly with "For European Users:" and no content follows), and subsequent required sections—International Data Transfers completion, Permissions Requested, Push Notifications and Analytics, Changes to This Policy, and Contact Information—are entirely missing, making it not fully production-ready.
GPT-5.4 6/10
# Privacy Policy for FitPulse

## Introduction

- **FitPulse Inc.** (“**FitPulse**,” “**we**,” “**us**,” or “**our**”) provides the **FitPulse** mobile application on **iOS and Android**.
- This Privacy Policy explains how we collect, use, disclose, and protect personal information when you use the FitPulse app, related services, and features.
- FitPulse is a **fitness tracking app** that allows users to record workouts, monitor progress, and connect health information from **Apple HealthKit** and **Google Fit**.
- By using FitPulse, you agree to the practices described in this Privacy Policy.
- **Users must be at least 13 years old** to use the app.
- **Effective Date:** [Effective Date]

## Information We Collect

### Personal Information You Provide

- We collect information you provide directly when you create an account, update your profile, subscribe, or contact us, including:
  - **Name**
  - **Email address**
  - **Age**
  - **Weight**
- We may also collect any information you provide when communicating with customer support.

### Health and Fitness Information

- With your permission, FitPulse may access and process health and fitness data from:
  - **Apple HealthKit** on iOS
  - **Google Fit** on Android
- This may include workout-related and fitness data you choose to connect or share with the app.
- Health data is used only to provide and improve fitness tracking features and is handled in accordance with Apple and Google platform requirements.
- We do **not** use HealthKit or Google Fit data for advertising or marketing purposes.

### Location Information

- We collect **GPS location data during workouts** when you grant location permission.
- This information is used to:
  - Track workout routes
  - Measure distance and pace
  - Provide workout summaries and map-based activity history
- On some devices, location may be collected in the foreground while the app is in use, depending on your settings and workout activity.

### Device and Technical Information

- We may automatically collect certain device and app information, including:
  - Device model
  - Operating system and version
  - App version
  - Mobile platform (**iOS/Android**)
  - Device identifiers
  - IP address
  - Crash logs and diagnostic information
  - Language and time zone settings

### Usage Information

- We collect information about how you interact with the app, such as:
  - Features used
  - Screens viewed
  - Session duration
  - Workout activity within the app
  - Subscription events
  - App performance and engagement metrics

## How We Use Your Information

- We use personal information to:
  - Create and manage your account
  - Provide fitness tracking and workout features
  - Sync and display data from Apple HealthKit and Google Fit
  - Track routes, pace, and workout performance using location data
  - Personalize your app experience
  - Process and manage subscriptions
  - Respond to support requests and communicate with you
  - Monitor app performance, troubleshoot issues, and fix bugs
  - Analyze usage trends and improve the app
  - Maintain security, detect fraud, and enforce our terms
  - Comply with legal obligations

- We may use email addresses to send:
  - Account-related notices
  - Subscription and billing communications
  - Service announcements
  - Important policy or security updates

## Third-Party Services and SDKs

- FitPulse uses third-party service providers and software development kits (**SDKs**) to operate the app.

### Firebase Analytics

- We use **Firebase Analytics** to understand how users interact with FitPulse.
- Firebase Analytics may collect:
  - App usage events
  - Device and technical information
  - Approximate identifiers associated with your device or app instance
- This helps us improve performance, usability, and features.

### Firebase Crashlytics

- We use **Firebase Crashlytics** to monitor crashes and diagnose technical issues.
- Crashlytics may collect:
  - Crash reports
  - Device state information
  - Diagnostic data at the time of an error

### RevenueCat

- We use **RevenueCat** to manage in-app subscriptions and entitlement status.
- RevenueCat may process:
  - Subscription status
  - Purchase-related identifiers
  - App user identifiers
  - Transaction metadata
- Payment transactions themselves may be processed by **Apple App Store** or **Google Play**, subject to their own privacy policies.

### Meta Ads SDK

- We use the **Meta Ads SDK** to measure ad performance, attribution, and marketing effectiveness.
- The Meta Ads SDK may collect:
  - Device information
  - Advertising identifiers
  - App events
  - Interaction data for attribution and campaign analysis
- Where required by law, we will seek consent before using advertising-related tracking technologies.

### Apple HealthKit and Google Fit

- FitPulse integrates with:
  - **Apple HealthKit**
  - **Google Fit**
- We access health and fitness data only after you grant permission.
- Health data obtained through these services is used solely to provide health and fitness functionality and not for advertising, profiling, or unrelated marketing.

## Data Sharing and Disclosure

- We do **not sell** your personal information in the traditional sense.
- We may share information in the following circumstances:

### Service Providers

- With trusted vendors that help us operate the app, including:
  - Analytics providers
  - Crash reporting providers
  - Subscription management providers
  - Infrastructure and support providers

### Business and Advertising Partners

- We may share limited data with advertising and measurement partners, such as **Meta**, for attribution, campaign effectiveness, and analytics, subject to applicable law and consent requirements.

### Legal and Safety Reasons

- We may disclose information if required to:
  - Comply with applicable law, regulation, subpoena, or legal process
  - Enforce our agreements or policies
  - Protect the rights, property, or safety of FitPulse, our users, or others
  - Detect, prevent, or investigate fraud, abuse, or security issues

### Business Transfers

- If FitPulse is involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, your information may be transferred as part of that transaction.

## Data Retention

- We retain personal information for as long as necessary to:
  - Provide the app and requested services
  - Maintain your account
  - Fulfill subscription and transaction obligations
  - Resolve disputes
  - Enforce agreements
  - Meet legal, tax, accounting, and regulatory requirements
- Health, workout, and profile data may be retained while your account is active and for a reasonable period afterward unless deletion is required by law or requested by you.
- Crash, analytics, and technical logs may be retained for shorter periods as needed for diagnostics and service improvement.

## Data Security

- We use reasonable administrative, technical, and organizational safeguards to protect your information, including measures designed to prevent unauthorized access, disclosure, alteration, or destruction.
- These safeguards may include:
  - Encrypted transmission of data
  - Access controls
  - Authentication mechanisms
  - Monitoring and logging
- No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

## Children's Privacy (COPPA)

- FitPulse is **not intended for children under 13**.
- We do not knowingly collect personal information from children under 13.
- If we learn that we have collected personal information from a child under 13 without appropriate authorization, we will delete that information as required by applicable law.
- If you believe a child under 13 has provided personal information to us, please contact us at **support@fitpulse.app**.

## Your Privacy Rights (GDPR, CCPA, and Similar Laws)

### GDPR and Other International Privacy Rights

- Depending on your location, you may have the right to:
  - Access the personal information we hold about you
  - Request correction of inaccurate information
  - Request deletion of your information
  - Object to or restrict certain processing
  - Request portability of your data
  - Withdraw consent where processing is based on consent
  - Lodge a complaint with a supervisory authority

- Our legal bases for processing may include:
  - Performance of a contract with you
  - Your consent
  - Compliance with legal obligations
  - Our legitimate interests, such as improving and securing the app

### California Privacy Rights (CCPA/CPRA)

- If you are a California resident, you may have the right to:
  - Know what personal information we collect, use, disclose, and retain
  - Request deletion of personal information, subject to exceptions
  - Request correction of inaccurate personal information
  - Access specific pieces of personal information
  - Limit certain uses of sensitive personal information where applicable
  - Not be discriminated against for exercising your privacy rights

- We do not sell personal information for money.
- We may share certain identifiers or app event data with advertising partners for analytics or attribution, which may be considered “sharing” under California law.

### How to Exercise Your Rights

- To submit a privacy request, contact us at:
  - **support@fitpulse.app**
  - [Contact Email], if different
- We may need to verify your identity before fulfilling certain requests.
- You may also manage some data directly in your device settings, app settings, Apple HealthKit, or Google Fit permissions.

## International Data Transfers

- FitPulse is based in **California, United States**.
- If you use the app from outside the United States, your information may be transferred to and processed in the United States or other countries where our service providers operate.
- These countries may have data protection laws that differ from those in your jurisdiction.
- Where required, we use appropriate safeguards for international transfers, such as contractual protections or other legally recognized transfer mechanisms.

## Permissions
Judge notes: The output is cut off mid-section (the "Permissions" section is incomplete and missing), which disqualifies it from production use and is a critical failure given the explicit instruction to include a "Permissions Requested" section, and the remaining required sections (Push Notifications and Analytics, Changes to This Policy) are entirely absent.
Gemini 2.5 Pro 2/10
**Privacy Policy for FitPulse**

**Effective Date:** [Effective Date]
**Last Updated:** [Date of Last Update]

## Introduction

Welcome to FitPulse! This Privacy Policy explains how FitPulse Inc. ("we," "us," or "our") collects, uses, shares, and protects information in relation to our mobile application, FitPulse (the "Service"), available on iOS and Android.

This policy is designed to help you understand what information we collect, why we collect it, and how you can manage it. By using our Service, you agree to the collection and use of information in accordance with this policy. This policy complies with major privacy regulations, including the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and the Children's Online Privacy Protection Act (COPPA).

## Information We Collect

We collect several types of information to provide and improve our Service to you.

### Information You Provide Directly

*   **Account Information:** When you create an account, we collect personal information such as your name, email address, age, and weight. This information is necessary to set up your profile and personalize your fitness experience.
*   **Health and Fitness Data:** You may voluntarily
Judge notes: The output is critically incomplete — it cuts off mid-sentence in the second section and fails to deliver the vast majority of the required policy sections (missing ~12 of 14 required sections), making it entirely unusable as a production privacy policy.
Grok 4.1 Fast Reasoning 8/10
# FitPulse Privacy Policy

**Effective Date: [Effective Date]**

FitPulse Inc. ("we," "us," or "our") operates the FitPulse mobile application ("App") available on iOS and Android platforms. This Privacy Policy explains how we collect, use, disclose, and protect your information when you use the App, a fitness tracking app for monitoring workouts, health metrics, and progress. We are committed to protecting your privacy and complying with applicable laws, including GDPR, CCPA, COPPA, Apple App Store Guidelines, and Google Play policies.

By using the App, you consent to the practices described in this Policy. If you do not agree, please do not use the App. We collect data only as necessary to provide our services, and users must be 13 years or older.

## Information We Collect

We collect the following categories of information to deliver personalized fitness tracking, analyze usage, and improve the App.

### Personal Data
- **Account Information**: Email address, name, age, weight, and height provided during registration or profile setup.
- **Health and Fitness Data**: GPS location data during workouts (precise location on iOS/Android), steps, heart rate, calories burned, and other metrics imported from Apple HealthKit (iOS) or Google Fit (Android).
- **Payment Data**: Subscription details processed via RevenueCat (we do not store full payment card details).

### Device and Usage Data
- **Device Information**: Device ID, model, OS version (iOS or Android), IP address, and mobile carrier.
- **Usage Data**: Workout logs, session duration, app interactions, and crash reports via Firebase Crashlytics.
- **Analytics Data**: Anonymized events like screen views and feature usage via Firebase Analytics.

We do not collect sensitive data like racial/ethnic origin, political opinions, or biometric data beyond fitness metrics.

## How We Use Your Information

We use your information for the following purposes:
- Provide core App features, such as tracking workouts, syncing health data from Apple HealthKit/Google Fit, and generating progress reports.
- Personalize your experience, e.g., tailoring workout recommendations based on age, weight, and GPS-tracked activities.
- Process subscriptions and payments through RevenueCat.
- Improve the App via analytics (Firebase Analytics) and crash reporting (Firebase Crashlytics).
- Send push notifications for workout reminders, updates, or promotions (with opt-out options).
- Display targeted ads via Meta Ads SDK.
- Comply with legal obligations, prevent fraud, and enforce our terms.
- Aggregate anonymized data for research and product development.

## Third-Party Services and SDKs

The App integrates third-party services for enhanced functionality. These providers may collect data as described in their policies:

| Service | Purpose | Platforms | Data Shared |
|---------|---------|-----------|-------------|
| Firebase Analytics & Crashlytics | Usage analytics and error reporting | iOS/Android | Anonymized events, device info, crash logs |
| RevenueCat | Subscription management | iOS/Android | Purchase data, subscription status |
| Meta Ads SDK | Personalized advertising | iOS/Android | Device ID, usage events for ad targeting |
| Apple HealthKit | Health data import (iOS only) | iOS | Steps, heart rate, etc. (user-authorized) |
| Google Fit | Health data import (Android only) | Android | Steps, heart rate, etc. (user-authorized) |

We do not sell your personal data. Review these services' privacy policies for details.

## Data Sharing and Disclosure

We share information only as necessary:
- **Service Providers**: With vendors like Firebase, RevenueCat, and Meta for App operations (under strict agreements).
- **Business Transfers**: In mergers, acquisitions, or asset sales, with notice where required.
- **Legal Requirements**: To comply with laws, respond to subpoenas, or protect rights/safety.
- **With Consent**: For marketing partners or affiliates if you opt in.

Under CCPA, we do not "sell" or "share" personal information as defined. No sharing with third parties for their direct marketing without consent.

## Data Retention

We retain your data only as long as needed:
- **Account Data**: Until account deletion or 2 years of inactivity.
- **Health/Fitness Data**: As long as your account is active; deleted upon request.
- **Analytics Data**: Anonymized after 14 months (Firebase standard).
- **Logs/Crashes**: 90 days.

Deleted data is securely purged. Backups may retain data up to 30 additional days.

## Data Security

We implement reasonable security measures:
- Encryption in transit (HTTPS/TLS) and at rest for sensitive data.
- Access controls, regular audits, and Firebase/Google Cloud security for iOS/Android data.
- No absolute security guarantee; report suspected breaches to support@fitpulse.app.

## Children's Privacy (COPPA)

FitPulse is not directed to children under 13. We do not knowingly collect data from children under 13. If we learn of such collection, we delete it promptly. Parents/guardians: Contact us at support@fitpulse.app. COPPA-compliant for users 13+.

## Your Privacy Rights (GDPR, CCPA)

You have rights regarding your data. California residents (CCPA/CPRA): Rights to know, delete, correct, opt-out of "sale/sharing," limit sensitive data use, and non-discrimination.

EU/UK residents (GDPR): Rights to access, rectify, erase, restrict, portability, object, and withdraw consent.

**How to Exercise Rights**:
- Email support@fitpulse.app with your request, including verification (e.g., account email).
- Access/delete via App settings (profile data).
- Opt-out of analytics/ads: App settings or device-level (iOS App Tracking Transparency/Android ad ID reset).
- CCPA Opt-Out: Do Not Sell/Share toggle in App.
- Authorized agents: Provide proof.

We respond within 45 days (extendable). Appeals: Reply to our response email.

## International Data Transfers

FitPulse Inc. is based in California, USA. Data from EU/UK users may transfer to the US via Standard Contractual Clauses (SCCs) with processors like Google/Firebase. We ensure adequacy under GDPR (e.g., EU-US Data Privacy Framework where applicable). Australian users: Transfers comply with APPs.

## Permissions Requested

The App requests permissions essential for functionality (iOS/Android prompts):
- **Location (GPS)**: Precise location during workouts for route mapping and distance tracking (background/foreground).
- **Health Data Access**: Apple HealthKit (iOS) or Google Fit (Android) for importing steps, heart rate, etc. (user-initiated).
- **Notifications**: Push alerts for workout reminders, achievements, or updates (opt-out anytime).
- **Background App Refresh**: For seamless HealthKit/Google Fit syncing (iOS).
- No camera, microphone, contacts, or photos access required.

Grant/revoke via device settings. Denials may limit features.

## Push Notifications and Analytics

- **Push Notifications**: Sent via Apple Push Notification service (iOS) or Firebase Cloud Messaging (Android). Opt-out in App or device settings.
- **Analytics**: Firebase collects anonymized data to optimize performance. Opt-out via App settings or device ad privacy features.

## Changes to This Policy

We may update this Policy to reflect changes. Posted version controls, with notice via App/push/email for material changes. Continued use constitutes acceptance. Check periodically.

## Contact Information

FitPulse Inc.  
[Company Address, if available]  
Email: support@fitpulse.app  
For privacy requests: privacy@fitpulse.app (or use support@fitpulse.app)  

California residents: Data Processing Addendum available upon request. EU Representative: [TBD]. DPO: support@fitpulse.app.

*Word count: 1,248*
Judge notes: Production-ready and well-tailored to the app details, but the contact section introduces an unsolicited "privacy@fitpulse.app" address not provided by the user, and a few sections (Changes, Children's Privacy) feel slightly thin compared to the depth elsewhere.

What makes these work

  1. 01
    List every SDK and permission upfront

    The most common reason AI-generated privacy policies fail App Store review is missing third-party SDK disclosures. Before running the prompt, write out every SDK you've integrated and every iOS/Android permission your app requests. Feed that full list into the prompt explicitly. Vague inputs produce vague policies that won't satisfy reviewers.

  2. 02
    Specify your target jurisdictions

    GDPR, CCPA, PIPEDA, and LGPD each require different language and user rights sections. Tell the model exactly which regions your app serves. If you're launching globally, ask for GDPR and CCPA as a baseline since those are the most stringent and will cover most requirements elsewhere.

  3. 03
    Ask for plain language explanations alongside legal clauses

    App stores and users both respond better to policies that explain what data is collected and why in simple terms before presenting legal language. Prompt the model to include a plain-language summary at the top of each section. This also makes it easier for you to verify the output is accurate to your actual data practices.

  4. 04
    Use the output as a draft, not a final document

    AI-generated policies are accurate for common scenarios but cannot account for your specific business context, jurisdiction-specific edge cases, or recent regulatory changes. Run the draft through a compliance tool like Termly or iubenda, or have a privacy attorney review it before you publish. The AI gets you 80% of the way there in minutes; the last 20% needs human judgment.

More example scenarios

#01 · Simple fitness tracker with no account login
Input
Generate a privacy policy for a mobile app called StridePace. It is a fitness tracking app for iOS and Android. It collects step count and GPS location during workouts. There is no user account or login. Data is stored only on the user's device. We use no third-party analytics or advertising SDKs.
Expected output
The policy should state that StridePace collects GPS location and motion data solely to track workout activity, that all data remains on-device and is never transmitted to external servers, that no account creation is required so no personal identifiers are collected, and that no third-party services receive user data. Include a section on how users can delete data by uninstalling the app.
#02 · Free app with Google AdMob ads and Firebase Analytics
Input
Write a privacy policy for a mobile app called QuizBlast, a free trivia game on iOS and Android. We collect email at registration, use Firebase Analytics to track in-app events, and serve ads through Google AdMob. Users are adults only. We are based in the United States and want CCPA compliance language included.
Expected output
The policy should disclose email collection at registration and its use for account management, explain that Firebase Analytics collects device identifiers and usage data sent to Google servers, clarify that AdMob may serve personalized ads using device advertising IDs, include a CCPA section granting California residents the right to opt out of data sale and request deletion, and link to Google's privacy policy for third-party SDK data practices.
#03 · E-commerce app with payment processing
Input
Create a privacy policy for ShopNest, an iOS and Android shopping app. We collect name, email, shipping address, and payment info. Payments are processed by Stripe. We use Klaviyo for marketing emails and Firebase Crashlytics for crash reporting. We serve EU users and need GDPR compliance included.
Expected output
The policy should cover collection of personal and financial data for order fulfillment, clarify that payment card data is processed by Stripe and not stored on ShopNest servers, disclose Klaviyo's use for email marketing with an unsubscribe mechanism, note Crashlytics collects crash logs and device data for debugging, and include a GDPR section covering lawful basis for processing, data subject rights (access, deletion, portability), and the identity of the data controller.
#04 · Social app with user-generated content and camera access
Input
Write a privacy policy for Framely, a photo-sharing social app for iOS and Android. It requests camera and photo library access. Users create profiles with a username and profile photo. We store content on AWS servers. We use Mixpanel for analytics. Users can be any age above 18.
Expected output
The policy should explain that camera and photo library access is used solely for uploading user content, that profile information including username and photos are stored on AWS servers in the United States, that Mixpanel receives anonymized usage event data to improve the app experience, that user-generated content may be visible to other users per the app's default public setting, and include instructions for account deletion and content removal requests via in-app settings or email.
#05 · B2B productivity app for enterprise users
Input
Generate a privacy policy for TaskBridge, an iOS and Android task management app sold to enterprise companies. End users are employees. We collect work email, task data, and file attachments. Data is hosted on Google Cloud in the US. We integrate with Slack and Google Calendar. Our customers sign a separate DPA.
Expected output
The policy should clarify that TaskBridge acts as a data processor on behalf of the enterprise customer (the data controller), that work email and task data are processed solely to deliver the service under the customer's instructions, that Slack and Google Calendar integrations access only the scopes explicitly authorized by the user, that data is hosted on Google Cloud US infrastructure under Google's security certifications, and note that enterprise customers should refer to their signed Data Processing Agreement for GDPR and contractual obligations.

Common mistakes to avoid

  • Omitting third-party SDKs from the prompt

    If you don't tell the model which SDKs you use, it generates a policy that only covers your own data collection. Apple's App Store and Google Play specifically check that third-party data sharing is disclosed. Undisclosed SDKs are a leading cause of privacy policy rejection during app review.

  • Using a web-app template for a mobile app

    Privacy policies written for websites skip mobile-specific data types like advertising identifiers (IDFA, GAID), push notification tokens, and device sensor data. Applying a web template to a mobile app leaves legally required disclosures out and can result in app store rejection or regulatory fines.

  • Not updating the policy when you add features

    A privacy policy is only valid for the data practices it describes at the time it's published. If you add a new analytics SDK, enable in-app purchases, or request a new device permission in an update, your policy must be updated before that version ships. Outdated policies are a compliance liability, not a minor oversight.

  • Publishing without a contact method for data requests

    GDPR requires you to provide a way for users to submit data access, deletion, and portability requests. CCPA has similar requirements for California residents. Many generated policies include placeholder contact info that developers forget to replace. A policy with a broken or missing contact email fails compliance requirements in multiple jurisdictions.

  • Assuming one policy covers all platforms

    If your app has both a mobile app and a web dashboard that share a backend, users may assume one privacy policy covers both surfaces. Be explicit in your policy about which platforms and services it applies to. If data practices differ between iOS, Android, and web, call those differences out rather than using catch-all language.

Related queries

Frequently asked questions

Is a free privacy policy generator good enough for App Store submission?

It depends on what the generator produces and whether it accurately reflects your app's actual data practices. Apple does not require a lawyer-drafted document, but it does require the policy to be accurate, accessible via a public URL, and cover all data types your app collects. AI-generated policies work well as a starting point but need to be reviewed and customized before submission.

Do I need a separate privacy policy for iOS and Android?

No, a single policy can cover both platforms as long as it addresses any platform-specific data points, such as Apple's IDFA or Android's Advertising ID. Most developers host one policy at a public URL and link to it from both the App Store listing and the Play Store listing. Just make sure the policy's scope statement mentions both platforms explicitly.

Where do I host my privacy policy so I can link to it in the App Store?

You need a publicly accessible URL, meaning no login required. Common options include a page on your app's marketing website, a GitHub Pages URL, or a free hosting service like notion.site or carrd.co. The URL must remain live as long as your app is listed. Using a cloud document link (like a Google Doc) is technically possible but less professional and prone to link rot.

Does my privacy policy need to be written by a lawyer to be legally valid?

In most jurisdictions, no legal requirement specifies that a privacy policy must be attorney-drafted. What matters is that it accurately describes your data practices and complies with applicable regulations. That said, if you collect sensitive data categories or serve regulated industries, having a lawyer review the AI-generated draft is a worthwhile investment to avoid liability.

What happens if my mobile app doesn't have a privacy policy?

Apple will reject your app during review, and Google will flag or remove it from the Play Store if you collect any personal data without a disclosed policy. Beyond app store consequences, operating without a privacy policy in the EU (under GDPR) or in California (under CCPA) can result in regulatory fines and user complaints to data protection authorities.

How do I handle privacy policy requirements for an app with in-app purchases?

In-app purchases processed through Apple or Google's native payment systems use Apple's and Google's own payment infrastructure, so you typically don't collect payment card data directly. Your policy should note that payment processing is handled by the platform's native billing system and link to Apple's or Google's privacy policy for that data. If you use a third-party payment processor like Stripe for subscriptions outside the app stores, you must disclose Stripe's data collection separately.