Quick answer
A game privacy policy explains what player data your game collects, such as accounts, gameplay, chat, device identifiers for ads and analytics, and purchases, and who receives it. Playxoft's free game privacy policy generator asks how your game works and which SDKs it ships with, covers online play, chat and anti-cheat, adds COPPA clauses if children may play, and gives you App Store and Google Play privacy checklists. It is a template, not legal advice.
- Player accounts and chat
- Online play and anti-cheat
- Ad and analytics SDKs
- Game SDKs from Unity to Steamworks
- Children's privacy
- App Store and Google Play checklists
How to use the Privacy Policy Generator for Games
- 1In Product, name the game and choose where you publish: the App Store, Google Play, Steam or your own site.
- 2In Publisher and Audience, add your studio name and contact email, then say whether children under 13 may play.
- 3In Features, turn on what your game has, such as accounts, purchases, online multiplayer, player chat, leaderboards and anti-cheat.
- 4In Services, add the SDKs in your build, such as Unity, Game Center, Google Play Games, Photon, ad networks and crash reporting.
- 5Copy or download the policy and publish it at a public URL; the Store checklist tab has your answers for App Privacy and Data safety.
What should a game's privacy policy cover?
Games collect more than most apps, often without the developer writing a line of tracking code. Work through this list:
| Data | Where it comes from | Disclose it as |
|---|---|---|
| Player account | Sign-in, platform accounts, email | Contact details, user ID |
| Gameplay | Progress, scores, leaderboards, matchmaking | Gameplay content, product interaction |
| Chat and voice | Multiplayer, clans, friend lists, reports | User content, communications |
| Purchases | In-app purchases, virtual currency | Purchase history |
| Device and ads | Advertising ID, IP address, device model | Identifiers, advertising data |
| Diagnostics | Crash and performance reports | Diagnostics |
| Anti-cheat | Device and gameplay signals | Security and fraud prevention |
Name each SDK that sends this data, such as your ad network and mediation partners, analytics, crash reporting, multiplayer backend and engine services, and link its privacy policy. On mobile, the same answers feed Apple's App Privacy details, which has its own Gameplay Content data type, and Google Play's Data safety form. The app privacy policy generator explains both forms in detail.
Does COPPA apply to my game?
COPPA applies if your game is directed to children under 13, or if you know you are collecting personal information from a child under 13 (FTC COPPA FAQ). To decide whether a service is directed to children, the FTC looks at things like its subject matter, visual content, animated characters, child-oriented activities and the age of models. Personal information includes persistent identifiers such as an advertising ID, so a kids' game with a standard ad SDK collects personal information even without sign-up.
If COPPA applies, you need a privacy notice, direct notice to parents and verifiable parental consent before you collect personal information. The FTC amended the COPPA Rule in 2025, with compliance required by April 22, 2026; the changes include separate parental consent before disclosing children's data to third parties such as ad networks, and a written data retention policy in your notice (Federal Register).
The stores add their own rules:
- Apple: apps in the Kids Category, and apps primarily for kids, should not include third-party analytics or advertising, with narrow exceptions (Guidelines 1.3 and 5.1.4).
- Google Play: apps that target children may show ads only through Families Self-Certified Ads SDKs, and must not transmit the advertising ID from children or users of unknown age (Families policy).
- Europe: where you rely on consent, GDPR Article 8 requires a parent's consent for children under 16, and countries may lower that age to 13.
Do I have to disclose loot box odds?
Yes, on both mobile stores, and the disclosure belongs in the game itself:
- App Store: apps offering loot boxes or other mechanisms that provide randomized virtual items for purchase must disclose the odds of receiving each type of item before purchase (Guideline 3.1.1).
- Google Play: apps and games offering randomized virtual items from a purchase must clearly disclose the odds in advance of, and in close and timely proximity to, that purchase (Payments policy).
Show the odds on the purchase screen and keep a full table on a support page. A loot box clause in your terms or policy should point players to that disclosure, not replace it.
Age ratings need the same honesty: answer Apple's age rating questions accurately (Guideline 2.3.6), and complete Google Play's IARC content rating questionnaire, because unrated apps may be removed (Content ratings).
Which game rules belong in the privacy policy, the terms or the EULA?
Put each rule in the document that does its job:
| Topic | Privacy policy | Terms or EULA |
|---|---|---|
| Chat, voice and player reports | What is recorded, who reviews it, how long it is kept | Conduct rules and what happens when players break them |
| Virtual currency and items | The purchase records you keep | Items are licensed, have no cash value and are refunded only where the law requires |
| Loot boxes | Not needed | Where the odds are published |
| Bans and anti-cheat | The signals you collect to detect cheating | What counts as cheating and the consequences |
| Leaderboards | That player names and scores are public | Not needed |
Use the EULA generator for the license to the game itself and the terms and conditions generator for accounts, online play and purchases. Both add virtual currency and loot box clauses when you turn those features on, and the EULA adds rules for online play and anti-cheat. All three are templates rather than legal advice; games for children, or with real-money features, are worth a lawyer's review before launch.
Frequently asked questions
Last updated by the Playxoft engineering team.