Free tool

Privacy policy generator for apps

Tick what your iOS or Android app collects and which SDKs it uses. You get the privacy policy, plus the answers for Apple's App Privacy label and Google Play's Data safety form, all built from the same answers.

Free, no sign-up. What you type stays in your browser.

1. Your app
2. Accounts
3. What your app itself collects

Only what leaves the phone: data your app sends to your server or keeps in your cloud. Data that stays on the device doesn't count.

4. SDKs in your app

Each one adds the data its maker says it collects, with a link to their own page.

5. People and places
Nothing ticked yetSee results ↓

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.

RuleApp StoreGoogle Play
Who needs a policyEvery app (Guideline 5.1.1)Every app, even one that collects no personal data
Where the link goesApp Store Connect's Privacy Policy field, and inside the appPlay Console's privacy policy field, and inside the app
What the page must beA public URLA 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 sayWhat 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 consentWho 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 formApp Privacy: each data type, whether it's linked to the person, whether it's used for tracking, and whyData safety: each data type, whether it's collected or shared, and why; encryption in transit; deletion requests
SDKsYour answers must include what third-party code in your app collectsSame: data an SDK collects counts as your app's
Account deletionIf people can create an account, they must be able to delete it inside the appDeletion 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.

SDKWhat its maker says it collectsSource
HailbellSupport 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 webhookHailbell docs
Google Analytics for FirebaseApp instance ID (and the Android advertising ID), approximate location from IP, in-app purchases, screens and sessionssupport.google.com
Firebase CrashlyticsCrash stack traces, device and OS details, an installation IDfirebase.google.com
Firebase Cloud MessagingPush token tied to an installation ID, app version, device model, language, time zonefirebase.google.com
Google AdMobAdvertising and device IDs, approximate location from IP, ad views and taps, performance and crash data; shared to show adsdevelopers.google.com
RevenueCatPurchase history; a user ID if you set onerevenuecat.com
SuperwallPurchase 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 pagesuperwall.com
SentryCrash reports, performance data and device details; random install IDs, no advertising IDdocs.sentry.io
MixpanelCity, 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 pagemixpanel.com
PostHogHow the app is used (product interaction and other usage data); from its iOS privacy manifest, since it publishes no store guidancegithub.com
Meta (Facebook) SDKDevice IDs, app events such as installs, launches and purchases, crash data; used for ads, so it counts as trackingdevelopers.facebook.com
AppsFlyerAdvertising and device IDs, approximate location from IP, app launches and events, performance data for fraud checkssupport.appsflyer.com
OneSignalA OneSignal ID, sessions and notification taps, in-app purchase eventsdocumentation.onesignal.com

How to use it

  1. 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.
  2. Tick every SDK, including ones you forgot. Check your Podfile, Package.swift or build.gradle. Crash reporting and analytics SDKs collect device IDs even when you never call them.
  3. 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.
  4. 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.
  5. 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.