App development Article

What every Android app privacy policy must include

A plain-language checklist for developers: what to disclose, how to describe ads and third-party SDKs, and how to keep your policy consistent with the Play Console Data safety form.

Arefin Khaled · 8 min read

Why it matters

To publish an app on Google Play you must link to an active privacy policy. It is more than a rule: it is how users decide whether to trust you. For apps that show ads or use third-party SDKs, a missing or inaccurate policy can block a release.

The usual problem is a policy copied from a generator that does not match what the app actually does. The checklist below is meant to close that gap.

Start by mapping your app’s data flow

Before writing a word of the policy, write down what the app collects, where it goes and how long it is kept. You will end up with four buckets.

  • What you collect yourself: accounts, email, location, photos, files, anything you ask for.
  • What SDKs collect: AdMob, Firebase, Crashlytics and so on. Each has its own data collection.
  • What stays on the device: user calculations or settings that never reach a server.
  • Nothing at all: if truly nothing is collected, say so plainly.

What every policy should contain

If a policy has these parts, both users and reviewers can find the answers they need.

  • Identity and contact: the developer or business name and a working email address.
  • What is collected: by type, for example advertising ID, device information, crash logs.
  • Why it is collected: app functionality, advertising, analytics, security.
  • Who it is shared with: the names or categories of ad networks and other service providers.
  • Retention and deletion: how long data is kept and where to send a deletion request.
  • Children: whether the app is for children and whether data is collected from them.
  • User rights: access, correction, deletion and ad opt-out.
  • Dates: effective date and last updated date.

Ads and third-party SDKs

If you use AdMob, say that Google may use the device advertising ID and other information to serve and measure ads, and link to Google’s own policy. Add one line on how users can reset the advertising ID or turn off personalised ads in device settings.

Listing each SDK by name is good practice. When an update adds a new SDK, update the policy in the same release.

Keep the Data safety form and the policy consistent. Declaring “no data collected” in the form while the policy mentions an advertising ID is a mismatch reviewers notice.

What to check on the Play Console side

The policy URL should open for everyone, with no login and no geo-blocking. A normal web page is safer than a PDF. Name the app or developer on the page, and make sure the developer website in Play Console and the domain of the policy match.

If your app lets people create an account, you must also provide a way to delete the account and data, both inside the app and on the web. Check the current wording of that rule on Google’s Play Console help pages.

If you publish many apps

With many apps, one URL per app is the cleanest approach, for example arefinkhaled.com/privacy/app-name. Generating the pages from one master template keeps the language consistent, and only the data section changes from app to app.

A final checklist before you publish

Open the policy link in a private browser window. Add the link inside the app too. Compare every answer in the Data safety form with the policy. And remember to update the policy whenever you add an SDK.

This article is general information, not legal advice. Platform rules change, so check the official pages before you act.

Share this article Facebook LinkedIn X WhatsApp
Arefin Khaled

A lawyer in Bangladesh who builds Android apps and websites, and researches environment, climate and human rights.

More about me →

Keep reading