Draft page - not yet linked from main navigation or sitemap.

Our position

Do not create consumer Meta accounts for students for classroom VR deployment. Consumer accounts are not designed for shared classroom use, they create COPPA and FERPA exposure for the district, and Meta enterprise program exists precisely to solve this.

Use Meta Horizon Managed Services (the enterprise program) or do not use Quest at all. Individual parent-managed accounts for 10-12 year olds do not scale to 25-kid classrooms and create real compliance headaches.

Other voices

Reputable sources worth reading before you decide. Labels reflect our honest read of each source's general stance, not direct quotes.

Meta's own policies separate consumer accounts (age 10+ with parent management) from enterprise deployments. Consumer accounts in classrooms are explicitly off the supported path.

Why trust it: Platform-provider rules.

FTC COPPA guidance puts responsibility on the service provider and the school for data collection on under-13 users. Consumer VR platforms are not designed to be COPPA-compliant by default.

Why trust it: Regulatory authority.

Some teachers run small pilots with a couple of headsets and consumer accounts linked to their own Meta login. Works at micro-scale, does not scale to a class set.

Why trust it: Real pilot-scale reality. Different risk profile at 2 headsets vs 25.
A note on honesty: We have no affiliate arrangement with any brand or publication linked here. Labels reflect our honest read of each source's general stance as of this writing; they are not quotes. Click through and form your own view.