Create a complete privacy policy for your Android or iOS app or game in under two minutes. Select the data you collect and the SDKs you use (AdMob, Unity Ads, Firebase and more), then copy or download your policy.
A privacy policy is no longer optional for mobile apps and games. Both major app stores require one, advertising networks require one and data protection laws in many countries require one. Publishing without a valid privacy policy is one of the most common reasons apps are rejected, removed or limited on Google Play and the App Store.
Even a simple offline game usually includes third-party SDKs for ads, analytics or crash reporting. Those SDKs collect data such as device identifiers and IP addresses, which means you need to disclose them in your policy.
List the categories of information your app and its SDKs collect, such as device identifiers, usage statistics, crash logs, location or account details.
Explain the purposes: running the app, saving progress, showing ads, measuring performance, fixing bugs, processing purchases and preventing fraud.
Name the third-party services that receive data and link to their privacy policies. Stores and regulators expect this transparency.
If you show ads, explain whether ads may be personalized, how users can opt out (for example through device ad settings) and how consent is handled where required.
Describe how long you keep data and the reasonable measures you take to protect it.
State whether your app is directed at children and how you comply with rules such as COPPA and the Google Play Families policy.
Explain how users can access, correct or delete their data, and include specific sections for GDPR and CCPA where relevant.
Provide a working contact email and explain how you will notify users of changes to the policy.
Your privacy policy is a full legal document. The Google Play Data safety form and Apple's App Privacy labels are short structured summaries shown on your store listing. They must be consistent with each other. If your Data safety form says you collect no data while your policy lists AdMob and Firebase, reviewers may flag the mismatch. After generating your policy, use the same list of data types and SDKs to fill in both store forms.
The stores need a public, accessible URL that does not require login and does not open a PDF download. Good options include a page on your own website, a simple page on a free website builder or a public document page. Make sure the URL stays live as long as the app is published, because broken privacy policy links can lead to warnings or removal. Also add a link to the policy inside your app, for example in the settings or about screen.
If your game targets children, the rules are stricter. In the United States, COPPA restricts collecting personal information from children under 13 without verifiable parental consent. Google Play's Families policy requires that apps for children only use ad SDKs certified for families and do not use personalized advertising for children. Apple requires apps in the Kids category to avoid third-party analytics and advertising in most cases. Choose your SDKs carefully, configure them for child-directed treatment and select "Yes" or "Mixed" in the audience option of this generator.
If you monetize with Google AdMob or another ad network, your privacy policy must disclose that third parties may collect data, use cookies or device identifiers and show personalized ads. Google also requires publishers to obtain consent from users in the EEA, the UK and Switzerland using a certified consent management platform, such as Google's User Messaging Platform (UMP). On iOS, you must show Apple's App Tracking Transparency prompt before accessing the IDFA. Selecting your ad SDKs in this generator adds the relevant advertising disclosures, but you still need to implement consent correctly inside your app.
Yes. You can generate, copy and download as many policies as you need, for free, with no sign-up. The policy is created in your browser and is not stored on our servers.
Yes. The stores still require a privacy policy link, and most games use SDKs that collect device data. If your app truly collects nothing, the policy should clearly say so.
Generate a separate policy for each app, because each app may use different SDKs, permissions and data types.
No. It is a well-structured template based on common requirements. Laws vary by country and change over time, so review it carefully and consult a qualified lawyer if you need legal certainty.
Start from a ready-to-publish Unity or Buildbox source code, then use our free tools to name it, write the listing and create the privacy policy.
Browse Source Codes