After your app is submitted to the App Store, you must complete the App Privacy details before launching. These answers show on your App Store product page and must be kept accurate and up to date.
Who can complete App Privacy
Apple allows certain App Store Connect roles (commonly Account Holder, Admin, App Manager, and Marketing) to manage App Privacy details. Learn more
Where to find it
- Log into App Store Connect
- Select My Apps → choose your app
- In the left sidebar, select App Privacy
- Complete the sections and click Publish to apply changes
What you’ll complete
- Privacy Policy URL (required)
- Privacy Choices URL (optional, recommended if you have a “manage data / request deletion” page)
- Data collection: whether you collect data from the app
- Data Types: what categories of data you collect
- For each data type: Purpose, whether it’s Linked to the user, and whether it’s used for Tracking
Step 1: Add your privacy link(s)
Privacy Policy (required)
Add the URL to your publicly accessible privacy policy. Apple overview
Privacy Choices (optional, but helpful)
Add a URL where users can manage their privacy choices (for example: access data, request deletion, manage preferences). Learn more
Step 2: “Do you collect data from this app?”
For most Fliplet apps that have login, profiles, analytics, uploads, or notifications, the answer is usually: Yes.
Only choose No if you are confident the app does not collect any data at all.
Step 3: Data Types (If you have X, select Y)
Select the categories that match what your app uses. These are the most common for Fliplet apps, but your app may use other categories depending on what you’ve built. Apple expects you to include your practices and any third-party code you integrate. Reference
Most common Fliplet features
| If your Fliplet app has… | Apple Data Type you will usually select |
|---|---|
| Login | Contact Info (Email, Name) and/or Identifiers |
| User profiles | Contact Info (Name, Email, Phone number — only if collected) |
| Analytics / usage tracking | Usage Data (e.g., product interactions) and/or Identifiers |
| Push notifications | Identifiers |
| File uploads | User Content (Files/Documents) |
| Image uploads | User Content (Photos/Images) |
Other common data types to check (only if your app uses these)
| If your app includes… | Apple Data Type you may need |
|---|---|
| Maps / “near me” / check-in / location permission | Location |
| Crash reporting / diagnostics | Diagnostics (and sometimes Identifiers) |
| In-app messaging / chat / comments | User Content (Messages) |
| Purchases / subscriptions | Purchases (and/or Financial Info only if you collect payment details yourself) |
| Search feature where you store/log search terms | Search History |
When in doubt: start with the “Most common Fliplet features” table, then scan the rest of Apple’s list for anything that matches features you’ve added (especially Location, Diagnostics, User Content, and Purchases).
Step 4: For each Data Type, answer the 3 questions
When you select a data type, Apple will ask you to describe it using:
1. Purpose: “How is this data used?”
For Fliplet apps, the most common purposes are:
-
App Functionality (login, profiles, uploads, notifications)
-
Analytics (usage reporting, dashboards)
2. Linked to the user: “Is this linked to the user’s identity?”
If the data connects to a user account (email/login) or a device identifier, it’s commonly linked to the user.
3. Tracking: “Is this used for tracking?”
Apple’s definition of Tracking is about linking data with third-party data for targeted advertising or ad measurement, or sharing data with a data broker. Basic internal analytics is not automatically “tracking.”
Recommended defaults (common Fliplet business apps)
Use this as a starting point for apps with login + profiles + analytics + notifications + uploads, where you are not doing advertising or cross-app tracking.
| Data type (Apple category) | How is data used? | Linked to user identity? | Used for tracking? |
|---|---|---|---|
| Name (Contact Info) | App Functionality | Yes | No |
| Email address (Contact Info) | App Functionality, Analytics, Product Personalization | Yes | No |
| Phone number (Contact Info) | App Functionality | Yes | No |
| Device ID / Identifiers (Identifiers) | App Functionality, Analytics | Yes | No |
| Product interactions (Usage Data) | Analytics, App Functionality | Often yes | No |
Notes:
- Only include what your app actually collects (for example, if you don’t collect phone numbers, don’t add Phone number).
- “Tracking” is usually no unless you use targeted advertising, third-party ad measurement, or share data with a data broker.
Publish and review
Once you’ve answered all required questions for each data type, click Publish. You can review the product page preview in App Store Connect to see what users will see on the App Store. Learn more
Two common gotchas
- Don’t confuse “Tracking” with analytics. Tracking is specifically about linking to third-party data for ads/ad measurement or sharing with a data broker. Apple definition
- Update App Privacy when your app changes. If you add a feature like location, messaging, uploads, or a new SDK, update App Privacy so your product page stays accurate. Apple guidance