You are getting ready to launch, and somewhere on your to-do list sits a vague line item that just says “legal stuff.” So do I need a EULA and terms of service for my game? The honest answer is that it depends on what your game actually does, and most articles never tell you that part.
They explain what each document is, then stop.
Here is the short version before the detail. You almost never need a separate EULA and a terms of service, because a terms of service already contains the license a EULA gives. It is the bigger document, and the EULA is one part of it. So this really comes down to two things: your player agreement, which is a EULA or a terms of service depending on your game, and your privacy policy. I will show you the right shape for your game, and flag the one document you can genuinely get penalized for leaving out.
How a EULA and a terms of service actually relate
Before you can decide what you need, you have to know how these fit together, because this is where most guides get it wrong.
A EULA (end-user license agreement) is a license to use your game. It gives the player permission to run your software while you keep ownership of the code. On its own, that is the whole job of a EULA: the license. If you want the deeper version, I broke down the clauses in my guide to game EULAs.
A terms of service is the bigger document, and here is the key point most guides skip: it already includes that license. A terms of service (also called terms of use) grants the same permission to play, then adds the rules your service needs on top, like accounts, online play, purchases, user-generated content, and how players treat each other. So a terms of service is not a second document you bolt onto a EULA. It is the EULA plus everything a live game also has to cover.
That reframes the real question. It is not “a EULA or a terms of service?” It is how much service your game has. A simple offline game can live on a standalone EULA. The moment you add accounts, online play, or a community, you want a terms of service, and the license rides along inside it.
A privacy policy is the separate one. It covers data: what personal information you collect, why, and what you do with it. It sits alongside your player agreement, never inside it.
Most guides list these as a checklist and stop there, which is exactly why they leave you thinking you need one of everything.
Only one of these is actually required by law
Here is the part that surprises most developers: no US law requires you to have a EULA or a terms of service.
They are contracts you choose to put in place. They protect your intellectual property and cap your liability, and whether they even bind a player depends on how you present them. Smart? Absolutely. Legally mandatory? No.
The privacy policy is the exception, and it is a big one.
The moment your game collects personal data, a privacy policy stops being optional. California’s Online Privacy Protection Act requires one for any site or app that collects personal information from California residents. The GDPR applies if players in the EU can access your game. On top of that, both the Apple App Store and Google Play require a valid privacy policy before you can publish at all. This holds whether your game is free or paid.
So if you skip your privacy policy, you are exposed to real legal and platform consequences. Skip the EULA or terms of service, and you are simply unprotected in a dispute you could have won. For the full picture on the data side, start with the privacy laws that apply to game companies and the specific California online privacy policy requirements.
What you actually need, by game type
A straight answer beats a lecture here. Match your game to the closest scenario below.
Premium downloadable PC or console game
A standalone EULA to license the code is enough here, since players just install and run your software. Add a privacy policy if you collect any data, which you almost certainly do through the storefront, analytics, or crash reporting. If the game has accounts or online play, move up to a terms of service instead. It folds the license in and adds the service rules, so you are upgrading to the broader document, not stacking a second one.
Free-to-play mobile game
A privacy policy is required, full stop, by both the app stores and data-privacy law. For accounts and in-app purchases you want a terms of service, and since it carries the license, you do not also need a separate EULA. On iOS there is a wrinkle: Apple’s default EULA applies unless you supply your own, which I get to below.
Online multiplayer or live-service game
This is the terms-of-service game. One player agreement, your terms of service, carries the license and does the heavy lifting: accounts, matchmaking, voice chat, bans, and player-created content all live there. Put your privacy policy alongside it. That is two documents, not three, and this is the category where weak terms hurt you the most.
Purely offline physical board game
If there is no app, no website, and no data collection, you likely need none of these. Your board game gets its protection from copyright and trademark. A EULA licenses software, and a box of cardboard and tokens is not software.
Board game with a companion app or online play
The moment you add an app, an online account, or data collection, you become a software company too. Now the same privacy policy, app-store, and children’s-privacy rules that apply to video games apply to you.
The game-specific clauses generic templates miss
You can buy a terms-of-service template for the price of a coffee. The problem is that a template written for a SaaS dashboard has no idea how a game works.
Take virtual currency and items. The major studios all treat them as a revocable license with no ownership and no real-world value. Riot Games states that players have no ownership or property interest in virtual content. Ubisoft grants a limited, revocable license to virtual currency and says it has no value outside its services. Electronic Arts says the same about its in-game currency. If your game sells gems, skins, or a battle pass and your terms are silent on this, you have a gap.
User-generated content is the other big one. If players build levels, make mods, create art, or post in your community, you need a license from them to you. Without it, you have no clear legal right to host, feature, or ship what your players make.
Then there are the clauses no SaaS template thinks about. Account bans, codes of conduct, and anti-cheat enforcement all need a home, and so does a plan for the day you shut the servers down.
A generic template does not reflect how your game actually operates, and your terms are your first line of defense when a dispute lands. That coffee-priced template gets expensive fast.
If kids might play, COPPA changes everything
If children under 13 might play your game, one law towers over the rest, and the penalty for getting it wrong is enormous.
In 2022, the FTC hit Epic Games with a $275 million penalty for violating the Children’s Online Privacy Protection Act in Fortnite, the largest penalty ever for breaking an FTC rule. Epic had collected personal data from players under 13 without notifying parents or getting their consent. That was part of a $520 million package that also included $245 million in refunds to players.
COPPA is triggered when your game is directed at children under 13, or when you knowingly collect data from them. Once it applies, you need verifiable parental consent before collecting a child’s data, and you have to limit what you collect.
This catches more developers than you would think. Cartoonish art and a spot in an app store’s kids category both signal “child-directed” to a regulator.
One important detail: COPPA stacks on top of your privacy policy rather than replacing it. If under-13s could realistically end up playing, get this reviewed before launch rather than after the FTC comes knocking.
The app stores decide some of this for you
Before you draft anything, know that the platform you launch on has already made some decisions for you.
On the Apple App Store, there is a standard Licensed Application End User License Agreement that automatically applies to your users if you do not supply your own. Your iOS game already has a EULA whether you write one or not. You can provide a custom EULA instead, but it has to include Apple’s required minimum terms, such as stating that the agreement is between you and the player rather than Apple, and listing your name, address, and a contact for complaints.
Apple and Google both require a valid privacy policy before they will let you publish. No policy, no listing.
Steam runs distribution under its own Steam Subscriber Agreement, which governs Steam’s relationship with the player rather than yours. Your own terms still have to do the game-specific work.
The takeaway is simple. The storefront sets a baseline and forces the privacy policy, and it still will not write your terms of service or your game-specific clauses for you.
A document only protects you if players actually agree to it
You can have perfect documents and still lose, if you never get players to actually agree to them.
Courts draw a hard line between two ways of presenting terms. Browsewrap terms sit behind a link at the bottom of a page that nobody has to click. They get struck down often, failing in court roughly 86% of the time, because there is no proof the player ever saw or accepted them.
Clickwrap is the standard that holds up. That is the “I agree” checkbox or button at account creation or first launch, with the terms readable right next to it. It works because the player takes a clear action to accept.
Get the mechanics right. A pre-checked box or a “continue” button that never mentions the terms does not count as agreement, and neither does splash-screen text that says “by playing you accept.” Keep a record of who accepted which version and when, and prompt players to accept again when you make a material change. I go deeper on this in my piece on making your game’s terms enforceable.
Getting your game’s player agreement, with the EULA license built into a proper terms of service, and a privacy policy drafted and wired into a real clickwrap flow is a lot to hand a launching studio. That is what our Terms of Use/EULA and Privacy Policy bundle is built for: the documents your game actually needs, written to fit it and ready to hold up when it matters.
Frequently asked questions
What is the difference between a EULA and terms of service for a game?
A EULA is just the license: it gives players permission to use your game while you keep ownership. A terms of service is the broader agreement that includes that same license and then adds the service rules, like accounts, purchases, user content, and player conduct. A terms of service is a superset of a EULA, not a separate document you also need. A simple offline game can use a standalone EULA, while a game with any online or account layer wants a terms of service, which carries the license inside it.
Is a EULA legally required for my game?
No. No US law forces you to have a EULA or a terms of service. Both are strongly advisable because they protect your IP and set the rules, but the only document actually required by law is a privacy policy, and only once you collect personal data.
Do I need a separate EULA if I already have a terms of service?
Usually no. A terms of service already grants the same license a EULA does and then adds your service rules, so for most games it is your single player agreement. A standalone EULA makes sense only for a simple game with no accounts, online play, or community. What matters more than the label is that the document covers the license plus your rules and that players actually accept it.
What legal documents do I need to launch a game?
One player agreement, plus a privacy policy if you collect any data. The player agreement is a standalone EULA for a simple offline game, or a terms of service (which includes the license) once you have accounts, online play, or purchases. A privacy policy is required by both the app stores and privacy law the moment you collect personal data. If children under 13 might play, COPPA applies on top.
Are free game terms of service templates good enough?
They beat having nothing, but they are risky for a real game business. Generic and SaaS templates miss game-specific clauses like virtual currency, user content, and account bans, and your terms are your first line of defense in a dispute. Once money is on the line, tailored documents are worth it.