Privacy Policy Generator
Generate a free, Google Play compliant privacy policy for your Android app. Covers Data Safety disclosures, AdMob, Firebase, analytics and children’s privacy. Download as HTML or plain text.
Free · No signup · Runs entirely in your browser
Your app
These details appear throughout the policy.
What does your app use?
Tick every SDK and permission in your build. The data types in the policy are derived from these.
Your privacy policy
PRIVACY POLICY FOR [YOUR APP NAME]
Effective date: 23 September 2026
[Your Name or Company] ("we", "us", or "our") operates the mobile application [Your App Name] (the "App"). This page explains what information the App collects, how it is used, and the choices you have. By using the App you agree to this policy.
1. INFORMATION WE COLLECT
The App, or the third-party services it uses, may collect the following types of data:
- App interactions
- Device identifiers
- Diagnostics
- Crash logs
Some of this data is collected automatically by the software development kits listed below, even when you do not actively provide it.
2. THIRD-PARTY SERVICES
The App uses the following third-party services, each governed by its own privacy policy:
- Firebase Analytics (collects: App interactions, Device identifiers, Diagnostics)
- Firebase Crashlytics (collects: Crash logs, Diagnostics, Device identifiers)
3. HOW WE USE YOUR INFORMATION
We use the information described above to:
- Provide, operate, and maintain the App
- Diagnose crashes and improve stability and performance
- Understand how features are used so we can improve them
- Comply with applicable legal obligations
4. SHARING OF DATA
We do not sell your personal information and we do not share it with third parties for their own marketing purposes. Data may be disclosed only where required by law or to protect our legal rights.
5. DATA RETENTION AND DELETION
Data collected for analytics and diagnostics is retained only as long as necessary for the purposes described in this policy. You may request deletion of any data associated with you by writing to [your@email.com].
6. SECURITY
All data transmitted by the App is encrypted in transit using industry-standard TLS. While we take reasonable measures to protect your information, no method of transmission or electronic storage is completely secure, and we cannot guarantee absolute security.
7. CHILDREN'S PRIVACY
The App is not directed at children under the age of 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us at [your@email.com] and we will delete it.
8. YOUR RIGHTS
Depending on where you live, you may have the right to access, correct, export, or delete the personal information we hold about you, and to object to or restrict certain processing. To exercise any of these rights, contact us at [your@email.com].
9. GOVERNING LAW
This policy is governed by the laws of India, without regard to its conflict of law provisions.
10. CHANGES TO THIS POLICY
We may update this privacy policy from time to time. Changes are effective as soon as the revised policy is posted at this URL, and the effective date above will be updated accordingly. Material changes will additionally be notified in the App.
11. CONTACT US
If you have questions about this privacy policy, contact:
[Your Name or Company]
Email: [your@email.com]
Generated in your browser — nothing you typed was sent anywhere. This is a template, not legal advice.
Why Google Play requires a privacy policy
Every app on Google Play must link to a privacy policy, even apps that collect nothing. Play checks that the URL is public, that the document is not editable by visitors, and that what it says matches your Data Safety declaration. A mismatch between those two is one of the most common causes of a User Data policy rejection.
How this generator works
Rather than asking you to guess which data types to disclose, it asks which SDKs are in your build and derives the data types from them. AdMob implies the advertising ID and approximate location. Crashlytics implies diagnostics and device identifiers. Firebase Auth implies email and user IDs. The generated policy lists exactly those types, so when you fill in the Data Safety form you can copy straight from section 1.
After you generate it
- Download the HTML file and upload it to a public URL on your own domain.
- Open that URL in a private window on mobile data to confirm it loads for a stranger.
- Paste the URL into Play Console under Store listing, and link it inside the app too.
- Reconcile every answer in the Data Safety form against section 1 of the policy.
Frequently asked questions
- Is this privacy policy accepted by Google Play?
- It is written to satisfy Play’s structural requirements: it names your app, lists the data types you collect and share, explains retention and deletion, and gives a contact address. You still need to host it at a public URL and make sure it matches your Data Safety form answers.
- Do I need a privacy policy if my app collects nothing?
- Yes. Google Play requires a privacy policy URL for every app, regardless of what it collects. Most apps also collect more than their developer assumes — AdMob and Firebase both collect device identifiers.
- Where should I host the policy?
- Any public URL that loads without a login works: your own domain, GitHub Pages, or a static host. Avoid editable Google Docs and Notion pages in edit mode — Play rejects those.
- Is this legal advice?
- No. It is a well-structured template generated from your inputs. If your app handles health, financial or children’s data, have a lawyer review it before you publish.
- Does my data get uploaded anywhere?
- No. The policy is assembled in your browser with JavaScript. Nothing you type is sent to a server.