What Apple and Google ask of your privacy policy
Both stores refuse an app without a privacy policy link, and both read the policy against what you declare in their forms. Here is what each one asks for, from their own pages as of November 16, 2026.
| Rule | App Store | Google Play |
|---|---|---|
| Who needs a policy | Every app (Guideline 5.1.1) | Every app, even one that collects no personal data |
| Where the link goes | App Store Connect's Privacy Policy field, and inside the app | Play Console's privacy policy field, and inside the app |
| What the page must be | A public URL | A public web page that works in every country, can't be edited by visitors, labeled as a privacy policy, and not a PDF |
| What it must say | What you collect, how and why; that SDKs and other third parties protect it the same way; how long you keep it and how people delete it or withdraw consent | Who you are and a privacy contact; what you access, collect, use and share; how you keep it safe; how long you keep it and how people delete it |
| Store form | App Privacy: each data type, whether it's linked to the person, whether it's used for tracking, and why | Data safety: each data type, whether it's collected or shared, and why; encryption in transit; deletion requests |
| SDKs | Your answers must include what third-party code in your app collects | Same: data an SDK collects counts as your app's |
| Account deletion | If people can create an account, they must be able to delete it inside the app | Deletion inside the app and on a web page, with that page's link in Play Console |
Why the store answers come with the policy
Most privacy policy generators stop at the policy and tell you to fill in Apple's and Google's forms yourself. That's where apps slip: the policy says one thing, the App Privacy label another, and an SDK collects something neither mentions. Here the three come from the same ticks, so the policy names everything either form declares. Where an SDK maker's App Store and Google Play guidance differ, each tab follows that store's guidance.
The SDK list is where most of the work goes. Each SDK maker publishes what its code collects for Apple's and Google's forms, in their own docs. The generator uses those pages and links each one, so you can check them yourself. Where a maker publishes no store guidance, it uses the data list the maker ships inside its iOS SDK (the privacy manifest). Where the two disagree, it takes the stricter answer. AppsFlyer's help page says it doesn't track, but its own manifest marks the device ID as tracking, so the generator says tracking.
| SDK | What its maker says it collects | Source |
|---|---|---|
| Hailbell | Support chat messages and photos, user ID, install ID and push token, app and device details, chat signals; name and email only if the app passes them; purchase history if you connect the Superwall or RevenueCat webhook | Hailbell docs |
| Google Analytics for Firebase | App instance ID (and the Android advertising ID), approximate location from IP, in-app purchases, screens and sessions | support.google.com |
| Firebase Crashlytics | Crash stack traces, device and OS details, an installation ID | firebase.google.com |
| Firebase Cloud Messaging | Push token tied to an installation ID, app version, device model, language, time zone | firebase.google.com |
| Google AdMob | Advertising and device IDs, approximate location from IP, ad views and taps, performance and crash data; shared to show ads | developers.google.com |
| RevenueCat | Purchase history; a user ID if you set one | revenuecat.com |
| Superwall | Purchase history (its stated minimum), plus what its page lists as collected: paywall views, a device ID (IDFV), device details and approximate location from IP; no Play page, so the Play answer follows its App Store page | superwall.com |
| Sentry | Crash reports, performance data and device details; random install IDs, no advertising ID | docs.sentry.io |
| Mixpanel | City, region and country, a Mixpanel user ID and device identifiers, how the app is used; no Play page, so the Play answer follows its App Store page | mixpanel.com |
| PostHog | How the app is used (product interaction and other usage data); from its iOS privacy manifest, since it publishes no store guidance | github.com |
| Meta (Facebook) SDK | Device IDs, app events such as installs, launches and purchases, crash data; used for ads, so it counts as tracking | developers.facebook.com |
| AppsFlyer | Advertising and device IDs, approximate location from IP, app launches and events, performance data for fraud checks | support.appsflyer.com |
| OneSignal | A OneSignal ID, sessions and notification taps, in-app purchase events | documentation.onesignal.com |
How to use it
- Tick only what leaves the phone. Apple and Google both count data your app sends off the device. A to-do list stored only on the phone isn't collected.
- Tick every SDK, including ones you forgot. Check your
Podfile,Package.swiftorbuild.gradle. Crash reporting and analytics SDKs collect device IDs even when you never call them. - Put the policy on a web page you control. Download the HTML page and upload it to your site, or paste the text into a page on it. Copy the link into App Store Connect, Play Console and your app's Settings screen.
- Fill in both store forms from the tabs. The App Store tab lists every data type with the three questions Apple asks about it. The Google Play tab lists each type with collected, shared and the purposes.
- Come back when you add an SDK. Save the share link. It reopens the generator with your answers, so an update takes a minute.
Where Hailbell fits
A privacy policy is one of the dull jobs around shipping an app. Another is answering the people who leave at the paywall with a question. Hailbell is a support chat inside your app. The AI answers first from your docs and prices, and messages reach you in Discord, Telegram or the web dashboard. It also sends push notifications to iOS, Android and the web. It's in the SDK list above with the data it collects, so adding it to your policy takes one tick. It has a 14-day free trial, no card needed. See how Hailbell works.
Questions
Does my app need a privacy policy?
Yes, on both stores. Apple's App Review Guideline 5.1.1 says every app must link its privacy policy in App Store Connect and inside the app. Google Play's User Data policy asks every app for one, including apps that collect no personal data.
Where do I put my app's privacy policy URL?
In App Store Connect, it goes in the Privacy Policy field of the app's App Privacy page. In Play Console, it goes in the privacy policy field under App content. Both stores also want a link inside the app, such as in Settings. Google asks for a public web page that works in every country, can't be edited by visitors, and isn't a PDF.
Do SDKs count in my App Store privacy label?
Yes. Apple says your answers must include what the third-party code in your app collects, such as analytics, ads and crash reporting SDKs. Google's Data safety form works the same way. Tick each SDK you use in the generator and it adds the data types that SDK's own documentation lists.
Is a generated privacy policy enough?
For a typical app it's a solid start that covers what both stores ask a policy to say: what you collect, why, who gets it, how long you keep it and how people delete it. It isn't legal advice. If your app handles health data, is made for children, or you aren't sure which laws apply, have a lawyer read it.
Is what I type sent anywhere?
No. The policy and the store answers are built in your browser, and nothing you type is sent to Hailbell or anyone else. The share link keeps your answers in the part of the link after the # sign, which browsers don't send to servers.
Sources: Apple, App Review Guideline 5.1.1, App privacy details on the App Store and Offering account deletion in your app; Google, Provide information for Google Play's Data safety section and User Data policy. SDK sources are linked in the table above. All checked November 16, 2026.
More free tools for app developers: all free tools. Questions? Start a chat with us.