Every app needs a privacy policy, even if it collects no data. Apple's App Store Review Guideline 5.1.1 requires a link to it in App Store Connect and inside the app, and Google Play requires one for every app, along with a completed Data safety form. Beyond the policy itself, Apple also asks for App Privacy details, a privacy manifest for apps and SDKs that use certain APIs, App Tracking Transparency permission before tracking, and in-app account deletion. This guide covers each requirement, what to put in your policy, and how to write one.
A missing or broken privacy policy link is one of the most common reasons apps get rejected, and it's one of the easiest to avoid. If you're getting ready to submit, use our app store publishing checklist alongside this guide.
Key takeaways
Apple and Google both require a privacy policy for every app, whether or not it collects data.
Your policy has to match what you declare in Apple's App Privacy details and Google Play's Data safety form, including data collected by SDKs.
If people can create an account in your app, Apple requires a way to delete it from inside the app.
Webview apps usually collect more than the website does, like push notification tokens and device identifiers, so the website's policy may need updating.
Does my app need a privacy policy?
Yes. Apple's Guideline 5.1.1(i) says all apps must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible place. Google Play also requires a privacy policy for every app, including apps that don't collect any user data. (Sources: Apple, App Store Review Guidelines 5.1.1, Google Play Console Help, Data safety)
Privacy laws can require one too. In the US, California's Online Privacy Protection Act (CalOPPA) requires apps that collect personal information from California residents to post a privacy policy, and Europe's GDPR sets rules for what the policy has to explain.
Apple app privacy policy requirements
Apple's requirements go beyond the policy document. Here's what you need for an iOS app in 2026.
1. A privacy policy link in App Store Connect and in the app
Add the URL in App Store Connect under App Privacy, and put a link somewhere easy to find inside the app, like a settings or account screen. Open both links in a private browser window before you submit to make sure they load.
2. App Privacy details (the "privacy nutrition label")
In App Store Connect, you answer questions about every type of data your app and its third-party SDKs collect, how it's used, and whether it's linked to the user or used for tracking. Apple shows the answers on your App Store listing. They have to match your privacy policy. (Source: Apple, App privacy details)
3. A privacy manifest
Since May 2024, apps and the third-party SDKs they include must ship a privacy manifest file that lists the data they collect and explains why they use certain "required reason" APIs. Uploads without one can be rejected. (Source: Apple, Privacy manifest files)
4. App Tracking Transparency permission
If your app tracks users across other companies' apps or websites, for example for targeted ads, you must ask permission through Apple's App Tracking Transparency prompt first. Read our guide to App Tracking Transparency.
5. In-app account deletion
If people can create an account in your app, Guideline 5.1.1(v) requires a way to start deleting it from inside the app. A link to an email address or a support form isn't enough. This catches a lot of webview apps whose delete option only exists on the website.
What counts as data your app collects
The purpose of the privacy policy is to explain what types of user data the app gathers, which may include:
Contact details
Geographic location
Financial information
Browsing history
Device usage patterns
In-app purchase records
Apple uses "collect" to mean any time data is sent from the user's device somewhere it can be accessed for longer than it takes to handle the request. Data that's processed only on the device and never sent anywhere doesn't count as collected. Keep in mind that a webview app loads your website, so anything your website sends to your servers counts as collected.
Google Play privacy policy requirements
A privacy policy link in Play Console and inside the app, on a public, working URL. It can't be a PDF.
A completed Data safety form that declares what data the app and its SDKs collect and share, whether it's encrypted in transit, and whether users can ask to delete it.
Account deletion. If users can create an account, Google requires a way to request deletion both in the app and through a web link you add in Play Console.
Prominent disclosure before collecting sensitive data, like location in the background, under Google's User Data policy.
For the rest of Google's review checks, see will Google Play approve my webview app. (Source: Google Play Console Help, Data safety)
What to include in an app privacy policy
Your privacy policy should cover:
The types of personal data gathered
Techniques used for gathering this information
The purposes behind collecting such data
Who you share it with, including third-party SDKs, and whether you sell it
How long you keep it
Options available to users for managing their personal data, including how to request access, correction and deletion
How users can contact you about privacy
When the policy was last updated
Update the policy whenever your app starts collecting new data, adds an SDK or a new law applies.
Legal frameworks to consider
When you write a privacy policy for an app, you need to account for the privacy laws that apply to your users. These include Europe's General Data Protection Regulation (GDPR), with its rules on data erasure and withdrawing consent, the California Consumer Privacy Act (CCPA), and other local laws.
Apps aimed at children have to follow stricter rules, like the Children's Online Privacy Protection Act (COPPA) in the United States.
California's CalOPPA also requires any app that collects personal information from California residents to post a privacy policy, wherever the developer is based.
How to write a privacy policy for an app
List every piece of data your app touches. Include what users type in, what your website collects, and what every SDK collects, like push notification, analytics and crash reporting tools.
Note why you collect each one and who receives it.
Check which laws apply based on where your users are, such as GDPR, CalOPPA, CCPA or COPPA for children's apps.
Write the policy using the checklist above. A template or generator is a fine starting point, but edit it to match your real data. Have a lawyer review it if you handle sensitive data like health or financial information.
Publish it on a public URL and link it in App Store Connect, Play Console and inside the app.
Match your store forms. Fill in Apple's App Privacy details and Google Play's Data safety form so they say the same thing as the policy.
Privacy policies for webview apps
If your app is built from your website, start with your website's privacy policy, then check what the app adds on top. A webview app can collect data the website never did:
Push notification tokens and the push provider you use
Device identifiers and the device's operating system version
Data from native features such as the camera, location, contacts or biometric login
Data from any SDKs added through native plugins, such as analytics or in-app purchases
Each of these needs to appear in your privacy policy and in your App Privacy details and Data safety form. With Median, your app loads your own website, and you choose which native plugins to turn on, so you know exactly which SDKs to declare. See will Apple approve my webview app for the full list of App Review checks.
Third-party SDKs and your privacy policy
External services like advertising networks, analytics tools, and third-party software development kits (SDKs) can collect data inside your app, and you're responsible for disclosing it. Tell users what data these components gather and how it's used for advertising.
Apps made for children can't include third-party advertising or analytics, which gives young users stronger protection.
If your app processes payments, disclose any user data the third-party payment processor collects.
Disclosing third-party partnerships
Disclose any user data collected through third-party components like SDKs. That means listing the types of data gathered, how they're used, and whether they're used for tracking.
Set up a data sharing agreement with each third party that spells out how user data is shared, and make sure it matches your own privacy policy.
Ensuring third-party compliance
Make sure your third-party partners follow Apple's App Store rules and data collection standards, and that what you declare about their data in App Store Connect is accurate and up to date. Check that each SDK you use includes its own privacy manifest. Apple lists commonly used SDKs that must.
User control over personal data
Your app should let users control their personal data, including:
Adjusting privacy settings
Accessing their own information
Requesting removal of their personal data through in-app tools or by contacting you directly
Be clear about whether the data you collect can be linked to a user's identity and whether it's used to track them. A consent management platform can make it easier for users to change their tracking and location preferences.
Access and management options
Give users tools to manage their privacy settings and see their personal information. On iOS, deleting an app removes its local data, and some apps also offer an in-app option to wipe the user's data.
Revoking consent and requesting data deletion
Tell users clearly that they can withdraw consent for data collection, and explain how. That includes how to get a copy of their data, correct mistakes, or deactivate and delete their account. If users can create an account, both Apple and Google require a way to request deletion in the app.
Under the GDPR in the European Union, users also have the "right to be forgotten," which lets them ask you to erase their personal data.
Updating and communicating privacy policy changes
Privacy policies need to change as laws, your app's features and user expectations change. When you update yours, tell your users. Skipping that step can cost you their trust and create legal risk.
Common ways to let users know include:
Email alerts
Website pop-up messages
In-app push notifications
Blog posts
Social media announcements
Whichever channel you use, keep the message short and easy to understand. An update email should include the date the changes take effect, a summary of what changed, a link to the full policy, and what users can do if they don't agree. Direct channels such as email and push notifications work best.
For significant changes, ask users to accept the new terms before they keep using the app, for example with a clickwrap agreement where they tap a button or check a box to agree.
Get your privacy setup right before you submit
Most privacy rejections come from a broken link, store forms that don't match the policy, or a missing account deletion option. Fix those three and you've covered most of what App Review and Google Play check. Median builds your iOS and Android apps from your website, and our Publishing Service can handle submission and reviewer questions for you.
App privacy policy FAQs
Do I need a privacy policy for my app?
Even if your app does not gather any data, a privacy policy is mandatory on the Apple App Store and Google Play. Apple requires the link in App Store Connect and inside the app.
How do I draft a privacy policy for an app?
List the data your app and its SDKs collect, why you collect it and who receives it. Then check which laws apply, write the policy, publish it on a public URL and match it to Apple's App Privacy details and Google Play's Data safety form.
What does Apple Guideline 5.1.1 require?
Guideline 5.1.1 covers data collection and storage. It requires a privacy policy link in App Store Connect and in the app, consent before collecting data, collecting only what the app needs, and in-app account deletion for apps that support account creation.
Where do I add my privacy policy URL in App Store Connect?
In App Store Connect, open your app, go to App Privacy, and enter the URL in the Privacy Policy URL field. It has to be a public page that loads without a login.
Does a webview app need its own privacy policy?
It can use your website's policy, as long as that policy also covers what the app adds, like push notification tokens, device identifiers and any SDKs from native plugins.
Are there federal laws for mobile app privacy?
The US has no single federal privacy law. The Federal Trade Commission can act against apps that mislead users about their data, and COPPA covers apps aimed at children under 13. Several states also have their own laws, and California's CalOPPA requires a privacy policy for any app that collects personal information from California residents.
What does 'collect' mean in the context of an iOS app privacy policy?
"Collect" means sending data off the device somewhere it can be accessed for longer than it takes to handle a request. Data processed only on the device doesn't count. For webview apps, anything your website sends to your servers counts as collected.
What are the requirements for notifying users of updates to privacy policies?
Tell users clearly and promptly through email, website pop-ups, in-app push notifications, blog posts or social media. An update email should include the effective date, the main changes, a link to the policy, and what users can do if they don't accept the changes.
*DISCLAIMER: This content is provided solely for informational purposes. It is not exhaustive and may not be relevant for your requirements. While we have obtained and compiled this information from sources we believe to be reliable, we cannot and do not guarantee its accuracy. This content is not to be considered professional advice and does not form a professional relationship of any kind between you and GoNative.io LLC or its affiliates. Median.co is the industry-leading end-to-end solution for developing, publishing, and maintaining native mobile apps for iOS and Android powered by web content. When considering any technology vendor we recommend that you conduct detailed research and "read the fine print" before using their services.*