Updated
For studios with shipped games
Sell Game Studio Data to AI Companies
Short answer
Yes, if you shipped a game that earns revenue and you own the records. AI data programs license copies of a studio's chat, tickets, game code and gameplay footage. You keep ownership. Publisher contracts, engine terms and player privacy decide what can go in.
You can sell game studio data to AI companies through a paid license on the records behind your shipped games. A program pays to use a copy, under a contract, while your studio stays the owner. No game, build or asset changes hands.
Below, you'll see the records programs want from a studio and who is not a fit. It also covers the three things that can block you: your publisher, your engine and your players. A studio owes DillisData nothing. Programs are the ones who pay us, as a referral fee.
- Shipped games only
- Publisher terms checked first
- Player data handled with care
What programs ask for
What do AI companies look for in game studios?
Rules differ by program and change often. Studios get screened on the first four rows. The others can add interest. Larger studios that bring full company records tend to draw the most. Some programs welcome studios outside the US.
| What some programs ask for | Where it usually lives | Why they want it |
|---|---|---|
| At least one shipped title that earns revenue | Store dashboards such as Steamworks | It shows a real game reached real players |
| A team of 10+ people working together, not mainly short-term contractors | Payroll and your org chart | A steady team leaves a long record of shared choices |
| Company records the studio owns: chat, tickets, code and shared drives | Slack, Discord, Jira, shared drives | They show how a game really gets made, bugs and arguments included |
| A studio of about 10 to 500 employees | Your payroll | A common size rule for studios. Other programs differ |
| Game and engine code with commit history | Perforce P4, GitHub, Git LFS | History shows how a system grew and changed from build to build |
| Gameplay video synced with keyboard, mouse or controller input | Capture rigs, test builds, QA recordings | It ties what a player saw to what the player pressed |
| Full-length gameplay videos and trailers of your own games | Video archives and marketing drives | Long footage you own is cleaner to license than clips from elsewhere |
| Player analytics, playtest data and support tickets | GameAnalytics, Zendesk, your own telemetry | They show what players did, and what went wrong for them |
| Design documents and 3D assets | Wikis, shared drives, your art repo | They explain the reasons behind a game, and the parts it was built from |
An honest filter
Which studios are not a fit?
These are the usual reasons a studio gets turned down. We would rather say so plainly.
No shipped game earning revenue
A long prototype, an unreleased game or a title that never earned money does not meet this rule.
Footage of other studios' games
Let's-play channels and capture of someone else's game don't count. That footage isn't yours to license.
Asset-store or template code
A game built mainly from bought kits and templates shows little of your own work.
Crypto and play-to-earn token projects
Some programs rule these out, even when the game itself shipped.
Mostly short-term contractors
Programs want a team that works together. Rotating outside hires leave a thin record, and their rights can be unclear.
Smaller studios in general programs
Some general programs ask for about 50 office staff. Only desk roles count there, so artists and testers on contract may not. They may also want 5 systems in daily use and 3 years of records.
Check your studio in two minutes
A short quiz covers team size, years open, tools and location. You send no builds, no code and no player data.
Rights
Does your publisher or engine stop you?
Start with the publisher deal. Some contracts give the publisher the game's IP, its code or its marketing footage. Some limit how you use records from the project. If you worked on someone else's IP under license, that may be out as well. Have your lawyer read each contract before a title goes in.
Next, check your engine. The Unreal Engine EULA limits who can get engine source code from you. The other party must hold its own Epic license for the same version. So copies of the engine in your repos likely stay out, even if your own game code can go. It also says assets from marketplaces like Fab are not licensed under it, so check their terms separately.
The Unity Asset Store EULA goes further. It bars using store assets to train an AI model without consent from the provider or Unity. So strip those assets from any export. Godot is under the MIT license, which is more relaxed, but your lawyer should still look at it.
Then look at people. Composers, voice actors and outside artists may have contracts that limit reuse. Some performer deals have their own AI terms. Leave out any work you can't clear. This is general information and not legal advice, so ask your lawyer.
Player privacy
Can you include player data?
Treat player data as the riskiest part of the archive. Many studios may choose to leave most of it out.
Children's data
The FTC's COPPA rule covers services aimed at kids under 13, and others that know they collect from them. It says to keep a child's data only as long as needed for the reason it was collected. If kids play your game, get legal advice first.
Your privacy policy
The FTC has warned against quietly rewriting your terms to allow AI training. It says that may be unfair or deceptive. Read what your policy told players at the time.
Players in Europe and California
Laws such as the GDPR and the California Consumer Privacy Act can apply. California residents may opt out of a sale of their personal information.
Support tickets and in-game chat
These hold names, emails, payment talk and sometimes private details. Programs say they remove personal details. No method catches everything, so ask to review sample tickets.
Keys and server secrets
Game repos can hold store keys, server logins and anti-cheat code. Swap those keys and keep live anti-cheat code out, because it shows how to beat your systems.
How it works
How does a studio go from quiz to license?
We match studios with programs and never hold any records. To see how other kinds of companies do this, read how businesses sell data to AI companies.
Answer the quiz
Tell us your team size, years in business and the tools you use.
2 minutesGet an estimate and your top 3 matches
We line up your studio's answers with what each program publishes, and explain each fit. The number is a guide. It is no offer.
Clear your titles
Your lawyer reads the publisher, engine and talent terms. You list which games, tools and years are in or out.
Sign with the program
You choose and sign up directly. For some programs, one of its representatives contacts you.
Send the export yourself
Your team moves the copy straight to the program. It never passes through us.
Public evidence
What public reports show
None of these is a DillisData deal or a game studio deal. We found no public price for a game studio's records. These are signs from nearby markets.
A wind-down firm says 47% of its deals now include code or work data. Those sellers are closed startups, not game studios.
MIT Technology Review, Oct 2026A shut-down software firm's former CEO says this many dollars came in. It covered every Slack message, internal email and Jira ticket.
Slashdot citing Fast Company, Apr 2026What four big US tech firms planned for capital spending in 2026. Most goes to chips and data centers, not to data.
Sherwood News, Apr 2026Timing
Why sort out your studio's archive soon?
No one knows how long programs will keep looking for game records. Here is what a studio loses by waiting.
Old builds stop working
Engines update, and old projects stop opening. Footage and input capture are easiest to pull while a build still runs.
Teams scatter after launch
When a project ends, people leave and chat accounts get shut down. The staff who know what is safe to include leave with them.
Storage gets cleaned out
Studios wipe old capture drives and depots to save money. What is deleted can't be licensed.
Unusual data stands out
Input-synced footage is hard to find elsewhere. Interest in a type of data can fall once a rival program holds plenty of it.
Publisher contacts fade
Asking a publisher to agree is easier while you still know someone there.
See what your shipped games could bring in
Get a rough figure first. Then decide if a contract review makes sense for your studio.
Questions
Questions owners ask
We self-published on Steam. Does that make this simpler?
Often, yes, since no publisher contract stands in the way. You still need to check your engine, asset store terms, music and any contractors.
Our publisher owns the IP. Is anything left?
Maybe. Your internal chat, tickets and studio tools may still belong to you, along with your own tech. Your contract decides. Ask your lawyer, and consider asking the publisher.
Can we license footage without code?
Some programs ask for company records as well, and treat footage as an add-on. Tell the program what you hold. Make sure you own the game shown, and check any music or licensed content in it.
Why does input data matter?
It ties what a player pressed to what happened on screen. Some programs name synced keyboard, mouse or controller capture as a plus. If you have QA tools that record it, say so.
How much could a studio get?
The range programs typically pay across industries runs $100K to $5M+, largely depending on studio size. It is not a promise. Run the estimate for a number based on your answers.
Our team is remote and outside the US. Does that matter?
Not always. Some programs welcome international studios. Some general programs ask that you be based in Australia, Canada, the EU or the US. English-language records are usually required.
Do we lose rights to our own game?
No. It is a license to use a copy, and your studio keeps its game, code and brand. The contract sets the limits. Your lawyer should read it closely.
Will DillisData see our builds or code?
No. We take your quiz answers only. The studio signs with its chosen program, and files go straight from your team to it.
Free estimate
Find out what your studio's records could earn
Two minutes, one careful number, three top matches. Your builds stay on your servers.
No code, builds or player data needed.