Skip to content

Free, no account needed

Free privacy policy generator for apps

Answer three questions about your app and get a privacy policy that matches what it actually does, ready for App Store Connect and Play Console. Copy the text for free, or host it with Pro at a URL that never changes.

  • Can people create an account?
  • Does it collect usage analytics?
  • Does it show ads?
Language of the page
Host it on AppTap with Pro

Get it at apptap.me/yourapp/privacy, ready to paste into App Store Connect and Play Console.

Preview

Privacy Policy

Introduction

This policy explains how Your app handles your data. It applies to the app on every platform it is published on.

Data we collect

Your app works entirely on your device and collects no personal data. The only information that exists is what the app needs to work:

  • Your preferences and settings
  • The content and history you create in the app

Where it is stored

All of it is stored on your device. None of it is sent to us, and we operate no server that could receive it.

How long it is kept

Data on your device is kept for as long as the app is installed. It is removed when you clear it in the app, clear the app's storage in your device settings, or uninstall the app.

Because nothing leaves your device, there is nothing for us to keep or delete on our side.

Sharing

We share nothing, because we receive nothing. No analytics service, advertising network or other third party gets your data from us.

Your rights

You are in control of your data. You can:

  • Clear the app's data from within the app
  • Reset your preferences
  • Uninstall the app, which removes everything stored on your device

Children

We do not knowingly collect personal data from children. If you think a child has shared personal data through Your app, contact us and we will delete it.

Changes to this policy

If this policy changes, the date at the top of this page changes with it.

Contact

For questions about this privacy policy, contact the developer through the app's store listing.

Why every app needs a privacy policy

Apple and Google both require a privacy policy for every app they publish. There is no exemption for free apps, offline apps or small games without accounts.

  • App Store, guideline 5.1.1(i): every app needs a privacy policy URL in App Store Connect and an easily accessible link inside the app.
  • Google Play, User Data policy: every app needs a privacy policy, linked in Play Console and inside the app, even if it accesses no personal or sensitive data.

That is why this privacy policy generator for apps starts from the simplest case. If your app keeps everything on the device, the policy says exactly that. It just has to be true: add one analytics SDK, crash reporter or ad network and your app does collect data, whether or not you ever open the dashboard.

What an app privacy policy has to say

Store reviewers don't expect a legal treatise. They expect a page that answers a few questions clearly and matches what the app does:

  • What data the app collects, how, and what it is used for.
  • Who else receives it: SDKs, ad networks, hosting or analytics providers. Name them, and link to their own policies.
  • How long it is kept, and how people can have it deleted or withdraw consent.
  • Who you are and how to reach you: the app or developer name shown on your store listing, and a contact address someone reads.
  • How you protect it. Google Play lists security among the things a policy must cover.

Google also wants the page clearly titled as a privacy policy. Keep it consistent with your App Privacy details in App Store Connect and your Data safety form in Play Console: if the form says you collect location and the policy never mentions it, one of them is wrong.

How your answers shape the policy

The generator above asks three questions because they cover what most indie apps do. Each answer adds or removes sections, so the policy never claims more, or less, than you told it.

Your answers What the policy says
No accounts, no analytics, no ads The app works on the device, collects no personal data, and shares nothing because nothing is sent
Accounts The email address and profile details people sign up with, kept while the account is open and deleted on request
Analytics Which screens are opened and which features are used, to see what to improve
Ads Advertising identifiers, used by advertising partners to select and measure ads

Every version also covers retention, sharing, the user's rights (clearing data, resetting preferences, uninstalling, and deleting the account if there is one), children, changes to the policy, and your contact email.

What the generator can't know is which services you use. If you rely on Firebase, AdMob, RevenueCat, a crash reporter or a payment provider, copy the generated text, add them by name, and publish that version as your own text.

Where to paste the URL, and why it should never change

Once the policy is live, its link goes in three places:

  1. App Store Connect: App Privacy, then Edit next to Privacy Policy.
  2. Play Console: the Privacy policy section of the App content page. Do it first, since Google needs it before you can complete the Data safety form.
  3. Inside the app: a "Privacy policy" row in settings or on the about screen, and on the sign-up screen if you have one.

The policy has to be a real web page. Google wants it public, not geofenced and not editable, and does not accept PDFs. A shared document anyone can edit, a file download or a page hidden behind a cookie wall all cause trouble.

Stability matters more than people expect. In App Store Connect, a change to the privacy policy URL only goes live with your next app version. If the address breaks, your store page links to a 404 until you ship an update. Pick a URL you can keep for the life of the app, and change the text behind it instead.

That is what hosting on AppTap gives you: the policy at apptap.me/yourapp/privacy, a URL that stays the same while you update the text as often as you need. The page opens in English or French depending on the visitor's language, and shows when it was last updated.

Before you publish

A generated policy is a starting point, not legal advice. Read it once with your app in mind:

  • List everything that leaves the device, including through each SDK, and check the policy covers all of it.
  • Check the children section. The generated text says the app doesn't knowingly collect data from children. If your app is aimed at kids, you need more than that.
  • Get advice for sensitive data: health, financial or children's data, or strict local rules such as GDPR for users in the EU.
  • Revisit it whenever you add an SDK, together with your App Privacy details and Data safety answers.

For everything each store expects, read the guide to the privacy policy URL for the App Store and Google Play. The other store pages work the same way: terms and conditions, an account deletion page if your app has accounts, and a support page for your Support URL. All four can live under one AppTap link, free for one app: get started.

Questions

Yes. Generating and copying the text is free. Hosting it on AppTap at apptap.me/yourapp/privacy is part of Pro, from $4 a month billed yearly.

Yes. The App Store and Google Play both require a privacy policy for every app. Without accounts, analytics or ads it can be short, but it has to exist and be accurate.

Yes, one policy at one URL is the norm. If the two versions collect different data, for example ads on Android only, the policy should say so.

Not on Google Play: the policy must be a public, non-editable web page, and PDFs are not accepted. A plain https page that loads without a login works for both stores.

It covers the basics, but GDPR asks for more, such as the legal basis for each use of data and the right to complain to a data protection authority. If you have users in the EU, complete it or get advice.

More free tools

Your app’s links, sorted before lunch.

Free for your first app. No card, no code, nothing to host.

Create your free link I already have an account