Google Play Privacy Policy Generator: What Play Console Checks Before Review

Published November 20, 2026 · Updated November 20, 2026

Every app on Google Play needs a privacy policy, even one that collects no data. Google requires the URL in the Privacy policy declaration on the Play Console App content page plus a link or the text inside the app. The policy must name your app or the developer on your store listing and agree with your Data safety answers, your manifest permissions and the data your SDKs send.

To build one, open the free privacy policy generator, choose Android - Google Play, tick your libraries under Third-party SDKs / services and your permissions under Device permissions, and add an Account deletion URL if users can create accounts. You get a hosted URL to paste into Play Console.

Where Play Console Asks for the URL, and What It Rejects

Play Console Help says you must link a privacy policy "on your store listing and within your app," even if the app touches no personal data. The field sits with your other policy declarations:

  1. Select your app and go to Monitor and improve > Policy and programs > App content.
  2. Under Privacy policy, click Start declaration (or Manage to change a saved URL).
  3. Enter the URL and save. Then link the same page from the app's Settings or About screen.

Google sets four conditions for the URL, and each maps to a common rejection:

  • Active and public, with a valid SSL certificate. A 404, an expired certificate or a staging domain fails.
  • Reachable worldwide, with no geofencing or login. A sign-in screen or a country block fails.
  • A standard, non-editable web page. No PDF, no download, no shared document visitors can edit.
  • Specific to the app. A company website policy that never mentions the app does not count.

The User Data policy lists what the text must contain: developer information and a privacy contact, the personal and sensitive data accessed, collected, used and shared, the parties it is shared with, secure handling procedures, your retention and deletion policy, and a clear "Privacy Policy" title.

Matching the Policy to Your Data Safety Answers

The Data safety form, also on the App content page, builds the Data safety card on your listing. Google says the policy must cover your practices "not limited by the data disclosed in the Data safety section," so the form summarizes the policy, not the reverse. The policy should answer each question in words:

Data safety questionGoogle's optionsWhat the policy must say
Data typesLocation, Personal info, Financial info, Health and fitness, Messages, Photos and videos, Audio files, Files and docs, Calendar, Contacts, App activity, Web browsing, App info and performance, Device or other IDsThe same types. If the form lists Approximate location and Crash logs, so does the policy. IP-inferred location counts.
Collected or sharedCollected / Shared (transfers to service providers, for legal reasons or of anonymized data are not "sharing")The types of recipients, including service providers the form leaves out.
Processed ephemerally?Yes / No (held in memory only to serve the request)Data used briefly off the device, such as a location to fetch weather, and that you do not store it.
Required or optionalRequired / Users can chooseWhich data users can decline, and what stops working.
PurposesApp functionality, Analytics, Developer communications, Advertising or marketing, Fraud prevention, security, and compliance, Personalization, Account managementEach purpose, attached to its data type. "To improve our services" covers none of them.
Security practicesIs all data encrypted in transit? Can users request deletion?Encryption in transit, and how to request deletion, matching the Delete account URL.

Google's review does not verify declarations, but it may take enforcement action when app behavior and the form disagree, and a policy that contradicts the form is the easiest mismatch to spot. The Data safety answer builder walks through all 14 categories.

Permissions, Families and Account Deletion

Three parts of the Developer Program Policy catch indie developers more often than the URL field itself.

Sensitive permissions

These need a Play Console declaration justifying the core feature, and the policy should describe the same use:

  • READ_SMS, READ_CALL_LOG and related permissions: only for the default SMS, Phone or Assistant handler.
  • ACCESS_BACKGROUND_LOCATION: critical features only, never ads or analytics alone. From January 27, 2027, apps targeting API 37 must use the Android location button for one-time requests.
  • READ_MEDIA_IMAGES and READ_MEDIA_VIDEO (API 33+): only when the system photo picker cannot do the job.
  • MANAGE_EXTERNAL_STORAGE and QUERY_ALL_PACKAGES: only when targeted alternatives fall short.

If collection would surprise users, such as location gathered while the app is closed, the Prominent Disclosure & Consent requirement adds an in-app notice before the runtime prompt and an affirmative user action. The privacy policy alone does not satisfy it.

Families policy

Your Target audience and content answers decide whether it applies. If children are in the audience, disclose all personal and sensitive data collected from them, including through SDKs. Apps solely for children must not transmit the AAID, IMEI, IMSI, MAC, SSID, BSSID, SIM serial or build serial, may not request location permission, and should not request AD_ID on API 33+. Ads to children or users of unknown age must come from a Families Self-Certified Ads SDK, with no interest-based ads or remarketing. See the COPPA privacy policy guide for parental consent.

Account deletion

If users can create an account, they must be able to request deletion in the app and on a web page that works without the app. That page goes in the Delete account URL field of the Data safety form. Freezing an account does not count, and any data you keep for security or legal reasons must be disclosed in the policy. The account deletion page generator hosts that page for free.

SDKs That Create Disclosure Duties Android Developers Miss

Data safety answers must include what your SDKs collect, so the policy must too. Google's SDK Index links to providers' own Data safety guidance. These libraries are the ones most often left out:

SDKWhat it sendsData safety types and policy line
firebase-crashlyticsStack traces, app state, device metadata, a Crashlytics installation UUIDCrash logs, Diagnostics, Device or other IDs. Name Google.
firebase-analyticsApp instance ID, automatic events and screen views; advertising ID if AD_ID is declaredApp interactions, Device or other IDs. Say if linked to Google Ads.
firebase-auth / Google Sign-InIP address for abuse prevention; email, name, phone or user ID by sign-in methodEmail address, Name, User IDs. Purposes: Account management, Fraud prevention.
firebase-messaging / OneSignalPush token, app version, installation ID; OneSignal also email or SMS if usedDevice or other IDs. Name the push provider.
Google Mobile Ads (AdMob)Advertising ID or app set ID, IP-derived location, ad interactions, diagnosticsDevice or other IDs, Approximate location, App interactions; shared for Advertising. Also complete the Advertising ID declaration.
Play Billing LibraryPurchase tokens and order IDs if you verify on your server; card details stay with GooglePurchase history. Do not claim you collect payment card data.
Meta (Facebook) SDKAutomatic install and launch App Events unless com.facebook.sdk.AutoLogAppEventsEnabled is false; advertising IDApp interactions, Device or other IDs. Name Meta and any ad measurement.
AppsFlyer / Adjust / BranchAdvertising ID, install referrer, attribution eventsDevice or other IDs, App interactions. Name the partner.
RevenueCat / SentryApp user ID and subscriptions (RevenueCat); crash data, plus IP and user details if Sentry's sendDefaultPii is onPurchase history, User IDs; Crash logs, Diagnostics.

Ads and analytics SDKs can add AD_ID or other permissions through the merged manifest, so check it before answering the form. The SDK disclosure generator turns an SDK list into policy paragraphs.

Copy-Ready Google Play Clauses

Add these to a full app policy (see writing a privacy policy for a mobile app), replace the brackets and drop what does not apply.

Google Play clauses — ready to copy

Privacy Policy for [App Name]

This policy applies to the [App Name] Android app published on Google Play by [developer name as shown on the store listing]. Contact us about privacy at [privacy@example.com].

Information we collect

[App Name] collects [e.g. email address and user ID when you create an account; crash logs; approximate location from your IP address] for [account management / analytics].

Device permissions

The app requests [Camera] to [scan documents you choose] and [Notifications] to [send reminders you set]. It does not access [location / contacts / SMS]. You can revoke permissions at any time in your device's Settings > Apps.

Advertising ID

[We and our advertising partner Google AdMob use your device's advertising ID to show and measure ads.] You can reset or delete your advertising ID in your device's Settings > Privacy > Ads. [OR: The app does not use the advertising ID.]

Third-party SDKs

The app includes third-party software that processes data on our behalf: [Firebase Crashlytics (Google): crash reports; Firebase Cloud Messaging (Google): push tokens; RevenueCat: purchase history]. Data is encrypted in transit.

Account deletion and retention

Delete your account in the app under [Settings > Account > Delete account] or at [https://example.com/delete-account]. We delete account data within [30] days, except [transaction records], kept [7 years] for legal reasons.

Rather not edit a template? The generator on our homepage writes these sections from your answers.

Frequently Asked Questions

How to generate a privacy policy for an Android app?

List the data your app and its SDKs collect, its permissions and how users delete data, then enter them into a generator that supports Google Play. Host the result on a public page and paste the URL under App content > Privacy policy.

What is a privacy policy generator?

A tool that builds a privacy policy from your answers about data practices. A good one for Android asks about SDKs, permissions, children and account deletion.

Which privacy policy generator is the best?

For a Play app, one whose questions match the Data safety form and that hosts the policy on a public, non-PDF page. Check the output against your app whichever tool you use.

Can I create my own privacy policy?

Yes. Google does not require a lawyer, only the required contents and a clear "Privacy Policy" label. Consider legal advice if you handle children's, health or financial data.

Can ChatGPT create a privacy policy?

It can draft one, but it does not know which SDKs or permissions are in your build. Check every statement against your Data safety answers and merged manifest.

Where can I get a free privacy policy?

Free generators, including this site's, create and host one at no cost. You can also host it on GitHub Pages or your website, as a normal web page rather than a PDF.

This page summarizes Google Play's requirements as of the date above; it is not legal advice. Sources: Prepare your app for review (Play Console Help), User Data policy, Data safety section, Families policies, Firebase data disclosure.