Legal generators

Privacy Policy Generator for Apps (iOS and Android)

Create the privacy policy Apple and Google require for every app, with your SDKs disclosed and checklists for Apple's App Privacy details and Google Play's Data safety form.

  • Free foreverNo trial, no paywall, no usage limits.
  • No sign-upOpen the page and start. We never ask for an email to use a tool.
  • PrivateEverything runs in your browser. Your input is never uploaded or stored on our servers.
  • Works offlineOnce the page has loaded, the tool keeps working without a connection.

A template, not legal advice. Laws differ by country and change often. Check the result against your product and have a lawyer review it before you rely on it.

Your product

Tell us what you publish and where. Each choice adds the clauses that product type needs.

What are you publishing?

Pick everything this document should cover. Each choice adds the clauses that product type needs, such as cookies for websites or device permissions for apps.

Where is it distributed?

Store rules change what the documents must say: Apple requires specific EULA terms, Google Play needs account deletion links, and the Chrome Web Store needs a Limited Use statement.
Adds Apple's required EULA terms and the App Privacy checklist.Adds Google Play terms and the Data safety checklist.

About the product

The name people know it by. It appears in the title and throughout the document.
Optional. The product's home page or store listing, so readers know which product the document is for.
One or two plain sentences. The terms quote it so readers know what they are agreeing to use.

Your answers will be saved in this browser only as you type.

Your privacy policy

Updates as you answer. Copy or download it as HTML for your site, Markdown for docs and GitHub, or plain text for store forms.
Copy HTMLDownload privacy-policy.html

15 sections · built in your browser. 3 items need your attention in Review.

Want an app this simple to use? Talk to our team

Quick answer

Every app on the App Store and Google Play needs a privacy policy linked in the store listing and inside the app, even one that collects no data. Playxoft's free privacy policy generator for apps asks which data your iOS or Android app collects and which SDKs it uses, such as analytics, ads and crash reporting, then writes matching clauses and gives you checklists for Apple's App Privacy details and Google Play's Data safety form. It is a template, not legal advice.

  • App Store and Google Play rules
  • SDK catalog with vendor links
  • App Privacy checklist
  • Data safety checklist
  • Device permissions
  • Account deletion clause

How to use the Privacy Policy Generator for Apps

  1. 1In Product, choose where you publish (the App Store, Google Play or both) and describe your app in a line.
  2. 2In Publisher and Audience, add your developer name and support email, where your users are and whether children use the app.
  3. 3In Features, turn on accounts and payments, and select the device permissions your app asks for, such as camera, location or notifications.
  4. 4In Services, add every SDK in your build: analytics, crash reporting, ads, attribution, sign-in and payments.
  5. 5Copy the policy and publish it at a public URL, then open the Store checklist tab to fill in App Privacy in App Store Connect and Data safety in Play Console.

Does my app need a privacy policy?

Yes, on both stores, with no exception for small, free or offline apps:

  • Apple requires every app to include a link to its privacy policy in App Store Connect and within the app, in an easily accessible place (App Review Guideline 5.1.1).
  • Google Play requires every app to post a privacy policy link in Play Console and a link or the policy text within the app (User Data policy). Every app must also complete the Data safety form, even one that collects no user data (Data safety).

The in-app link is the one developers forget. A Privacy policy row in your settings or about screen that opens the same URL covers it on both platforms.

What do the App Store and Google Play require in a privacy policy?

Both stores list what the policy must say, and they overlap more than they differ:

RequirementApp Store (Guideline 5.1.1)Google Play (User Data policy)
Data collectedWhat data, how it is collected and all its usesTypes of personal and sensitive data accessed, collected, used and shared
Third partiesConfirm that SDKs, analytics and ad networks give the same or equal protectionEvery party personal or sensitive data is shared with
Retention and deletionRetention and deletion policy, and how to revoke consent or request deletionData retention and deletion policy
Contact and securityNot listed in 5.1.1A privacy point of contact and secure data handling procedures
FormatLink in App Store Connect and in the appActive, public, non-geofenced URL; no PDFs; not editable
Account deletionIn-app deletion if users can create an account (5.1.1(v))In-app path plus a web link for deletion requests (details)

Privacy laws add more: GDPR rights and lawful bases for users in Europe, and the CCPA's categories and opt-out for California. The generator adds those clauses when you have users there.

How do I fill in Apple's App Privacy details and Google's Data safety form?

Both stores show a structured privacy summary on your store page, built from your answers, and both make you responsible for the SDKs in your app.

  • Apple App Privacy (App Store Connect): for each data type you collect, such as Contact Info, Location, Identifiers, Usage Data or Diagnostics, say whether it is linked to the user, whether it is used for tracking, and its purposes (App Functionality, Analytics, Third-Party Advertising and others). Apple counts data as collected when it leaves the device and is kept longer than needed to serve the request in real time; data processed only on the device is not collected (App Privacy details).
  • Google Play Data safety (Play Console): declare each data type collected or shared, whether it is encrypted in transit and whether users can request deletion. Collection means transmitting data off the device, including by SDKs and webviews; transfers to service providers, for legal reasons or at the user's request do not count as sharing (Data safety).

Apple also requires a privacy manifest for SDKs on its list of commonly used SDKs, such as Firebase and Unity, when you submit a new app or an update that adds one (SDK requirements). Answer both forms from the same inventory you used for the policy, so the label and the policy describe the same app.

Which SDKs do I need to list in my app's privacy policy?

Every SDK that sends data off the device. The usual suspects:

SDK typeData it typically sendsPurpose to disclose
AnalyticsApp events, device model, identifiersAnalytics
Crash reportingCrash logs, device and OS detailsApp functionality
Advertising and mediationAdvertising ID, IP address, ad interactionsThird-party advertising
AttributionInstall source, advertising IDAdvertising or marketing
Sign-inName, email, account IDApp functionality
Payments and subscriptionsPurchase historyApp functionality

Apple asks you to confirm that third parties protect user data as well as your policy does, and Google makes you reflect third-party code in your Data safety answers. On iOS, tracking users across other companies' apps and websites needs permission through App Tracking Transparency (Guideline 5.1.2). To serve personalized AdMob ads to users in the EEA, UK or Switzerland, Google also requires a Google-certified consent management platform (Google).

How do I get a privacy policy URL for my app?

Both stores want a link, not a file. Publish the HTML on your own website or a free static host such as GitHub Pages, at a permanent address like example.com/privacy, then:

  1. In App Store Connect, open your app, choose App privacy in the sidebar and edit Privacy Policy (Apple).
  2. In Play Console, open Policy and programs, then App content, and add the URL under Privacy policy.
  3. Link the same URL from your app's settings or about screen.

For the license to the app itself, see the EULA generator; for games, the game privacy policy generator adds clauses for online play, chat, anti-cheat and young players. Treat the result as a solid first draft rather than legal advice, and have a lawyer check it if your app handles health, financial or children's data.

Frequently asked questions

Yes. Apple requires a privacy policy link for every app in App Store Connect and inside the app, and Google Play requires every app to link one in Play Console and in the app, even if it collects no user data. A short policy that says exactly that, and names any SDKs, is enough.
In App Store Connect, open your app, select App privacy in the sidebar, click Edit next to Privacy Policy and enter the URL. Changes to the URL are released with your next app version. Link the same URL from inside your app as well.
Open your app in Play Console, go to Policy and programs, then App content, and enter the URL under Privacy policy. Google requires an active, publicly accessible, non-geofenced URL that is not a PDF. The same policy must also be linked or shown inside the app.
App Privacy details on the App Store and the Data safety section on Google Play are structured summaries you fill in through the store's form; they appear as labels on your store page. The privacy policy is your full written notice. Both must describe the same practices, including your SDKs, and you need both.
Yes. Ad SDKs usually collect the advertising ID, IP address and ad interactions, so you must disclose the ad network, the data and the purpose. On iOS, tracking across other companies' apps needs App Tracking Transparency permission, and to serve personalized AdMob ads to users in the EEA and UK, Google requires a certified consent management platform.
Yes, if users can create an account in your app. Apple requires account deletion inside the app, and Google Play requires an in-app path plus a web link where users can request deletion of their account and data. Say in your privacy policy what you delete and what you keep, for example for fraud prevention or legal reasons.
Yes, as long as it is accurate for both. If the versions use different SDKs, permissions or sign-in options, list each one, or note which platform it applies to. Using a single URL in both stores and inside both apps makes it easier to keep up to date.

Last updated by the Playxoft engineering team.

From the team that built this tool

Have an app idea you keep putting off?

We design and build iOS, Android and cross-platform apps people enjoy using, from the first sketch to store launch. Tell us about your idea and get a free, no-pressure consultation on how to build it well.