EN

Privacy Policy

 To publish games on platforms like Google Play and the Apple App Store, you need a public Privacy Policy page. It must be accessible online, at a stable URL on your domain, so you can put it in the platform forms (see Apple / Google Play links).

In the privacy policy you explain what data you collect from users, why and how you use it. For games, a lot of data is collected by SDKs you add (analytics, ads, crash reporting), not necessarily directly by you.

The template below is for a free-to-play (F2P) mobile game. It covers analytics, accounts, purchases, virtual currency, cosmetics, sometimes ads. If your game is different, adapt it. And in any case, a template is not a final legal document: for games with multiplayer, accounts, analytics, ads, IAP, personal data or international users, it should be reviewed by someone with legal experience.

What it should cover

  • who the company operating the game is (legal name, contact details);
  • what data you collect and through which SDKs / services;
  • whether there are accounts, guest profiles, analytics, crash reports or device identifiers;
  • whether there are purchases, premium currency, battle pass or cosmetics;
  • whether there is chat, usernames, social features or moderation;
  • whether there are ads, rewarded ads or ad measurement;
  • who you share data with (analytics, ads, payment providers);
  • how a user can request information or data deletion;
  • whether the game targets children and which regions your users come from (EU, US, etc.).

A useful generator as a starting point

For a basic structure, you can use app-privacy-policy-generator.firebaseapp.com. It's useful for your first game, but it doesn't know how your game works, check the SDKs, accounts, payments, ads and the rest manually. More on consistency with Google Play Data Safety and Apple App Privacy in Apple / Google Play links.

Template (F2P)

A starting point for a free-to-play mobile game. Adapt it to your actual game (company name, SDKs, features) before publishing:

What's next

Write clearly and honestly what happens to users' data, put the page at a public, stable URL on your domain, then also prepare the Terms & Conditions. Save the final link in My Own Company Details.