Can a game studio sell its data to AI companies?
Part of it. A studio writes down how a game breaks, how players describe the break and how a team decides what to fix. Those internal records can be licensed. The players themselves, especially children, and the content a platform owns are a different matter, and they decide how much of a studio archive can leave the building.
What a game studio has that is licensable
| Bug reports with reproduction steps | A tester or player describes what happened, a developer asks follow-up questions, and the fix is noted. The path from a vague report to a located cause is the useful part. |
| QA notes and test plans | Checklists for each build, the failures found, and how severity was argued over before a release date. |
| Design documents and balance notes | Why a weapon was weakened, why a level was cut, and the memo that records the argument. Reasoning that rarely appears in public. |
| Player support tickets | A refund request, a lost-progress complaint or a ban appeal, with the agent reply. Usable only after player details are removed. |
| Play and telemetry logs | Event streams showing where players stall or quit. These are the riskiest records in the archive, and are handled last. |
Where the records live
Bugs and design notes usually sit in an issue tracker and a wiki. Support conversations live in a help desk tool. Telemetry sits in an analytics warehouse that the engineering team controls, often with a different retention rule from everything else.
Tell us which tools hold them, how far back each goes and who administers it. A studio with a decade of tracker history and a clean wiki is easier to assess than one with a large warehouse and no written notes next to it.
Players are not employees
A game collects data from the public, and some of that public is under 13 or under 18. In the United States, a children's privacy law called COPPA sets rules for collecting personal information online from children under 13, and other countries have their own age rules. A studio that cannot say which accounts belonged to minors should assume the player-facing records are off the table until that is settled.
The player terms of service and privacy notice also matter. They state what the studio said it would do with play data. If they never mention reuse for model training, the safe reading is to ask counsel first. Treat this as general background, not legal advice.
Platform and middleware terms
A game ships on console stores, a PC launcher or a mobile store, and each has a developer agreement. Some limit what can be done with player data that came through the platform. Engines, voice tools and anti-cheat services carry their own licenses too. The studio's own writing is generally its to offer; what flowed through a platform or a vendor needs a separate check.
What stays out for a game studio
| Player names, emails and account identifiers | Replaced consistently or dropped. Gamer tags and chat names count, because people recognise them. |
| Anything from accounts of children | Records tied to players under the age limits, or where age is unknown, are left out. |
| In-game chat and voice between players | The studio does not hold the right to what players said to each other, so it is not licensed. |
| Platform-owned data and licensed assets | Store analytics, music, voice acting and art that the studio licensed from others are not the studio's to pass on. |
More on this: how personal details are removed, who carries the risk and how you get paid.
A sample, step by step
An independent studio with forty staff has nine years of tracker history, a design wiki and a help desk archive. The first package pairs each resolved bug with its report and the developer follow-up, plus the matching design memos, with every player name and account number removed. Telemetry and player chat are not included. Leadership reviews the sample before choosing to continue.
Questions owners ask about this
Can we include bug reports that players submitted?
Often, once the reporter details are removed and the terms they agreed to are checked. Reports that came from a minor, or that quote another player, are left out.
Does a shut-down game change the answer?
It does not change who owns the records, but it can change who is left to give approval. A closed studio should first confirm who holds the rights to the code, the player data and the archive.
Are game assets such as levels and character art part of this?
Those are creative works, often with contractor or licensor claims on them. They are handled as separate rights questions and are not part of the written-record packages described here.
What about mods and community content?
Content made by players belongs to its makers under the terms they accepted. It is not offered unless the studio can show it holds the right to do so.
Do we need to remove staff names from design memos?
Staff names are usually replaced with roles. The reasoning in the memo stays, and the person who wrote it does not need to be named.
Didn't find your question? Ask us directly.
Keep reading
Records to look at first
- Support tickets: The whole thread, wrong guesses included, with customers replaced by stand-ins.
- Project and task history: Jira, Asana, Linear, Monday, Trello, ClickUp and Airtable comments and status changes, not task titles.
- SOPs and knowledge bases: Procedures with their edit history and comments; published help articles add nothing.
- Jira data export: How to get issues with their comments and links out of Jira, and the secrets to remove first.
- Zendesk data export: How to get tickets with every reply and internal note out of Zendesk, and what customers’ details need first.
- Slack data export: Channels, threads and the settings that decide how much of your chat history can leave.
Other industries
- Software companies: Tickets, postmortems and renewal threads; customers appear everywhere and code is a separate deal.