- Section 4.3 of Meta’s Developer Data Use Policy bars selling or licensing User Data, or letting a third party do it.
- User Data includes Device User Data: headset position, sensor data and data calculated about hands, body, face and eyes.
- Meta says raw hand and body images are processed on the headset and not stored on its servers.
- What a studio can license: code, engine project, assets, levels and new capture recorded outside Quest’s platform data flows with each player’s written consent.
What does Meta’s policy say about selling or licensing Quest user data?
This page is general information, not legal advice. The rules below are quoted from Meta’s own pages, read on 19 November 2026, with what each means in plain words. If Meta changes the wording, the live text wins. Checked 19 November 2026.
| Platform or source | Stated rule | Records it covers | Date checked |
|---|---|---|---|
| Meta Developer Data Use Policy, section 4.3 | Bars "Selling, licensing, purchasing, renting, or lending User Data" | All User Data from a Quest app | 19 Nov 2026 |
| Same policy, glossary (Device User Data) | Includes "the position of a user’s headset" and data calculated about hands and body | Head pose, controller and sensor data, hand and body tracking | 19 Nov 2026 |
| Same policy, glossary (Developer User Data) | Data "you independently collect or process from an end user" is not User Data | The studio’s own accounts and inputs, still under privacy law | 19 Nov 2026 |
| Same policy, section 4.7 | Bars combining User Data with other data, except as section 3 allows | Joins of platform data with your own logs | 19 Nov 2026 |
| Meta Hand and Body Privacy Notice (effective 24 Feb 2025) | Raw images and key points: "We do not collect or store this data on Meta servers" | Hand and body tracking | 19 Nov 2026 |
| Roblox Terms of Use, as quoted by a developer | Restricts "using Virtual Content in connection with machine learning models" | Content made and used on Roblox | 19 Nov 2026 |
| Matterport generative AI guidelines | AI features may not be used to train AI or ML models | Outputs of Matterport AI features | 19 Nov 2026 |
| COPPA Rule, 16 CFR Part 312 | A child is "an individual under the age of 13" | Personal information from children | 19 Nov 2026 |
Does Meta allow Quest developers to sell hand tracking or gameplay data from their VR apps for AI training?
No. Section 4.3 of the Developer Data Use Policy lists among prohibited practices "Selling, licensing, purchasing, renting, or lending User Data or similar actions, or permitting a third party to do so." Plain meaning: a studio may not sell or license User Data, and may not let a data company do it on its behalf.
Hand tracking and head pose are inside that rule. The glossary says Device User Data "includes data from sensors such as a microphone or camera and the position of a user’s headset" and "data calculated about a user’s hands and body". User Data is "the combination of Meta Horizon User Data and Device User Data."
Two more rules close the side doors. Section 4.7 bars "Combining User Data with any other data, including with data separately collected by you or received from a third party", except where section 3 allows it. Section 4.6 bars using User Data to work out who a person is. And Meta may enforce by "permanently removing your Content and account". For a studio whose income comes from the Quest store, that risk outweighs any data fee.
Does Meta store hand tracking data, and could a studio get it?
Meta’s Hand and Body Privacy Notice, effective 24 February 2025 and still the live version on 19 November 2026, says the headset analyzes camera images to estimate key points on the hands and body, and the images and points are deleted in real time. "We do not collect or store this data on Meta servers."
Abstracted data is handled differently. For users outside Illinois and Texas, estimated body scale and hand and body pose "will also be stored on our servers to diagnose and fix issues with hand and body tracking", separated from the account after 45 days and kept for up to a year. That is Meta’s data for Meta’s purpose. A studio cannot get it, and cannot license it.
Apps that support hand tracking receive the abstracted data while they run. The notice says "App developers are permitted to use this data only for purposes outlined in the Developer Data Use Policy". So whatever an app logs of it falls under the policy above.
What can a Quest studio license to AI companies instead?
Everything it owns that did not come from Meta’s platform:
- Source code with its commit history, and the Unity or Unreal project.
- 3D assets, animation, levels and design documents, where the studio made them or holds the rights.
- A hosted build that AI labs can run agents in, as described in the game environment guide.
- Staff playtests and new sessions recorded with paid testers who agreed in writing, outside the platform’s data flows.
- Engine replays and bot traces that hold no personal data.
The policy’s definitions draw a fine line. Developer User Data, which is outside User Data, is defined to include "inputs from the end user through the Meta Quest device", while headset position is Device User Data. Whether a particular log of player inputs falls on the studio’s side of that line is a question for the studio’s lawyer, and for Meta in writing, before anything is licensed.
Can a game developer license player gameplay data to AI companies, or do the players or the platform own it?
No single party owns all of it. The studio owns the game, the code and the records it creates. The platform sets the rules for data that flows through it, and Meta’s rules bar licensing User Data. The players have privacy rights in recordings of what they did.
Motion is personal data. Researchers showed that "a user can be uniquely identified amongst the entire pool of 50,000+ with 94.33% accuracy from 100 seconds of motion." EgoGaming, a VR data vendor, treats every file that way: "Because VR movement data can reveal someone’s identity, all files must be treated as personal data."
Children raise the bar further. If a game is directed to children, the COPPA Rule applies: "It shall be unlawful for any operator of a website or online service directed to children" to collect a child’s personal information except as the rule allows. Leave all data from players who may be under 13 out of any license.
The safe pattern is consent recorded at capture. EgoGaming says its players are adults who "sign up, pass a review and agree in writing" before anything is captured. A studio that wants to license session data should record new sessions the same way, for that purpose, outside Quest’s platform data flows, for example in a PC VR build or on its own capture rig.
Do AI companies pay for VR gameplay data with head and hand tracking from Quest games?
Origin’s own conversations in this market point to real demand for VR gameplay data held by game studios. No buyer has published a price for it, so any figure is set in negotiation.
In public, the market is early. A VR telemetry vendor said on 16 October that it held 1,500 hours over 28 titles and was "awaiting our first partner"; the CEO of a humanoid-data marketplace replied that he was happy to be that partner (post and reply). A capture vendor charges $30 to $49 per accepted hour for custom VR capture with exclusive rights. Origin Lab, a game data company unrelated to Origin Data Partners, offers VR capture as a premium option recorded per order.
What labs pay for most clearly is the game itself: licensed games, engine projects and gameplay with inputs and engine state. The VR game studio data guide lists the buyers seen in public.
No headset-data offer appears from General Intuition either: the gameplay-model lab publishes no buying program, as our General Intuition review sets out.
Is headset and controller pose data valuable for AI and robotics training?
For some buyers, yes. Pose from a headset is measured on every frame rather than estimated from video afterwards. EgoGaming’s format puts "Position and orientation (6DoF) for the head and both controllers for each video frame, on the same capture clock as the video". World-model and robotics teams value that link between what a person saw and how they moved.
Others doubt it. Nvidia’s world-model lead told WIRED he would be "more conservative on using video game data for manipulation." Value depends on the buyer’s task, on variety across many situations, and on whether inputs and game state are recorded alongside the pose.
Do other platforms limit AI training on what developers make there?
Yes, and the limits differ. A developer on the Roblox forum wrote that the Roblox Terms of Use contain a clause that "restricts using Virtual Content in connection with machine learning models", and asked how to request an exception (forum post). Matterport’s guidelines say users of its AI features must use them "not to train artificial intelligence or machine learning models" (guidelines).
The pattern is the same as Meta’s. A platform can limit what you do with data or content that passes through it, even where you own the game. Read each platform’s current terms before a license, and keep a dated copy with the deal file.
What should a Quest studio check before licensing its games and source code for AI training?
Work through the list before you share anything, even a sample:
- Which records came through Meta’s platform. Keep all User Data out of the license.
- Who owns the game: studio, publisher or both. Get the publisher’s signature if it owns the IP.
- Engine and store terms, store-bought assets, licensed music and performers, as the game studio data guide explains.
- Player consent for any recording, recorded at capture, with withdrawal and deletion handled.
- Players under 13: leave them out entirely.
- The license itself: scope, exclusivity, no resale, no training to recreate the game, deletion and audit.
Meta keeps audit rights. Under section 7 it may review a developer’s systems where it suspects a breach or where the developer goes through a change of control. A studio being sold should expect that diligence, and the guide to licensing data when selling a business covers the order of steps.
Where should a Quest studio start?
Split the archive in two: what came from Meta’s platform, which stays out, and what the studio made or recorded itself, which may be licensable. Then value the second half as game studio data.
Origin is an independent data partner. We help you license your data. For a Quest studio that means sorting the records, checking them against Meta’s policy and the studio’s contracts, and working out terms for what can be licensed. See what your studio’s data is worth.
Origin Data Partners works with companies that own data and helps get it bought. We are independent of the services on this page, and a buyer may pay us when a deal closes (how Origin is paid). See what your data is worth.
Common questions
I am the M&A adviser on the sale of a Quest studio. Can the buyer license its gameplay and motion data to AI companies?
Only the parts the studio owns outside Meta’s platform. Head, controller and hand data from Quest players is User Data under Meta’s Developer Data Use Policy, which bars selling or licensing it, and Meta keeps audit rights on a change of control. Code, the engine project, assets, levels and consented playtests can transfer and be licensed, subject to publisher and engine contracts.
A data company offered to buy our Quest players’ hand tracking logs. What should we check before we sign?
Check Meta’s policy first: section 4.3 of the Developer Data Use Policy bars selling or licensing User Data, which includes data calculated about users’ hands and body. Signing such a deal risks removal of your apps and account. Ask the company instead about licensing your code, assets or new sessions recorded outside Quest’s platform data flows with players’ written consent.
Is the position of a user’s headset User Data under Meta’s developer policy?
Yes. The policy defines Device User Data to include data from sensors such as a microphone or camera and the position of a user’s headset, plus data calculated about hands, body, face and eyes. User Data is Meta Horizon User Data plus Device User Data, so headset pose logged by a Quest app is covered by the ban on selling or licensing.
Can we license Quest session recordings if players accepted our privacy policy?
Not if the recordings contain User Data, such as headset or hand pose, because Meta’s policy bars licensing it whatever your privacy policy says. For recordings outside that definition, a general privacy policy rarely amounts to consent to AI training. Record new sessions outside Quest’s platform data flows, with written consent for that purpose, instead.
Does Meta’s Developer Data Use Policy stop a studio licensing its own game code and assets?
No. The policy governs user data collected or processed through the Meta Horizon platform, not the studio’s own code, engine project, art or levels. Those can be licensed if the studio owns them and its publisher, engine and asset store terms allow it. Unity and the asset stores have their own AI training limits.
Are VR players under 13 a problem for licensing session data to AI companies?
Yes. Under the COPPA Rule a child is anyone under 13, and operators of services directed to children, or that know they are collecting a child’s data, must follow its notice and parental consent rules. Leave any data from players who may be under 13 out of a license, and record new sessions only with adults.
Sources and further reading
- Meta: Developer Data Use Policy (Meta Horizon platform)
- Meta: Hand and Body Privacy Notice (effective 24 February 2025)
- EgoGaming: VR gameplay dataset with head and controller poses
- EgoGaming president on LinkedIn: 1,500 hours of VR telemetry (16 October 2026), with replies
- Exylos: VR egocentric dataset pricing, rates per accepted hour (18 September 2026)
- Origin Lab: FAQ
- Roblox Developer Forum: request for an exception to the ML restriction in the Terms of Use
- Matterport: Generative AI user guidelines
- Nair et al., Unique Identification of 50,000+ Virtual Reality Users from Head and Hand Motion Data (USENIX Security 2023)
- eCFR: 16 CFR Part 312, Children’s Online Privacy Protection Rule
- WIRED: The next evolution of AI is learning from your gaming skills (28 September 2026)
