SAFETY & COMPLIANCE

Meta Quest Store Policies for Kids

Meta has specific policies for apps that target or attract children. These are layered on top of COPPA — even if you're COPPA-compliant, Meta may reject your app for platform-specific policy violations. This page maps every requirement that applies to Eggscape and provides a pre-submission checklist.

10 years old
Quest Minimum Age
Meta requires users to be 10+ to create a Meta account. Users under 13 must use a supervised (parent-managed) account. Eggscape's 8-9 year old segment requires supervised accounts.
4 categories
Content Rating Tiers
IARC ratings: Everyone (E), Everyone 10+ (E10+), Teen (T), Mature (M). Eggscape should target E10+ to cover the 8-13 audience while allowing mild fantasy themes.
2-6 weeks
Avg Review Timeline
Initial submission review takes 2-6 weeks. Kids-focused apps often receive additional scrutiny, pushing toward the longer end. Updates typically review in 3-7 business days.
~30%
Rejection Rate (Kids Apps)
Estimated first-submission rejection rate for kids-targeted Quest apps. Most common reasons: inadequate parental controls, unclear data practices, IAP flow issues.

Meta Content Requirements for Kids Apps

Category Requirement Impact on Eggscape Status
Age Rating (IARC) All Quest apps must receive an IARC rating. Apps targeting children must receive E or E10+ rating. Content must match the rating — no violence, sexual content, or substance use beyond rating thresholds. Target E10+ rating. Eggscape rooms can include mild fantasy peril (traps, timed challenges) but no realistic violence, weapons, or blood. Spooky themes for Halloween must be "fun scary" not genuinely frightening. Pending — submit IARC questionnaire during pre-launch
Content Descriptors Must accurately declare content descriptors: mild fantasy violence, interactive elements (in-app purchases, users interact). Misrepresenting descriptors is grounds for removal. Declare: "Users Interact" (multiplayer), "In-App Purchases" (cosmetics/Battle Pass), "Mild Fantasy Violence" (if escape scenarios include peril). Be conservative — it's better to over-declare than under-declare. Pending — finalize at content lock
Parental Controls Apps targeting children must integrate with Meta's parental control systems. Supervised accounts must have restricted functionality by default with parent opt-in for additional features. Integrate with Meta Family Center API. Default supervised account to: quick-chat only, no friend requests without approval, spending limits active, play-time notifications to parent. Parent can unlock features through Family Center dashboard. Required — integrate early in development
Data Practices Must comply with Meta's data use policies AND COPPA. Must declare all data types collected in the store listing. Must have a privacy policy accessible from the store page. Minimize data collection. Declare only: gameplay analytics (aggregated), purchase history (via Meta), display name. Privacy policy URL must be active and accessible before submission. Required — complete privacy policy before submission
Advertising No personalized/targeted advertising to users under 13. No third-party ad SDKs that collect persistent identifiers from children. Contextual ads allowed with restrictions. Eggscape should avoid all advertising entirely — it's a F2P cosmetics model, not ad-supported. If ads are ever considered, use only contextual (non-targeted) ads with clear "AD" labeling and no tracking pixels. N/A — Eggscape uses IAP model, not ads
In-App Purchase Rules IAP must clearly display real-money prices (not just virtual currency equivalents). Purchase confirmations required. Refund policy must be accessible. No "bait and switch" pricing. Every IAP screen must show the real USD price alongside any virtual currency price. Two-step purchase confirmation ("Are you sure? This costs $4.99"). Link to Meta's refund policy from purchase screen. Never use "$" symbol for virtual currency to avoid confusion. Required — build into IAP flow from start

Age-Gating & Supervised Accounts

Quest Account Age Restrictions

  • Ages 10-12: Must use a supervised account managed by a parent through Meta Family Center. Parent must approve app downloads, friend requests, and can set play-time limits. The child cannot create an unsupervised account.
  • Ages 13+: Can create a standard Meta account without supervision (though parents can still link for oversight). Most social features unlock by default.
  • Under 10: Meta officially does not support Quest use for children under 10. However, Eggscape's target audience of 8-9 year olds CAN use Quest with a supervised account set up by a parent. The parent must acknowledge the age restriction during setup.
  • Implementation for Eggscape: At first launch, detect if the user is on a supervised account. If yes, apply child-safe defaults automatically. If the account is unsupervised but the user indicates they're under 13 (via age gate), restrict features to match supervised account settings and prompt parental setup.

In-App Purchase Rules for Kids

Price Display Requirements

  • All prices must be displayed in real currency (USD, EUR, etc.) — never show only virtual currency amounts
  • If using a virtual currency, show the conversion rate prominently: "100 Gems = $0.99"
  • Bundle prices must show the individual item values and the bundle discount percentage
  • No "first purchase discount" that creates urgency or pressure on children

Confirmation Flows

  • Two-step confirmation: Every purchase requires a confirmation dialog: "Buy [Item Name] for [$X.XX]? [Cancel] [Confirm Purchase]"
  • Parental authentication: For supervised accounts, Meta requires parental PIN or password entry for purchases. Integrate with Meta's purchase authentication API.
  • Spending notifications: Parents receive a notification after every purchase made on their child's supervised account. This is handled by Meta Family Center, but your app must properly tag transactions.
  • No one-click purchases: Even for small amounts, never allow a single tap to complete a transaction for children's accounts

Refund Policy

  • Meta handles refunds through their standard process (within 2 hours of purchase for auto-approval)
  • Your app must gracefully handle refunded items — remove the cosmetic/item without punishing the player
  • Link to Meta's refund policy from your in-app store page
  • Consider offering a more generous refund window for children's purchases (24 hours) as a goodwill measure that reduces parent complaints and chargebacks

Advertising Restrictions

What's Prohibited

  • No targeted advertising to users known to be under 13 — this includes behavioral targeting, interest-based targeting, and retargeting
  • No third-party advertising SDKs that collect persistent identifiers (most major ad networks violate this for under-13)
  • No ads that blend with game content (disguised ads, playable ads that look like gameplay)
  • No rewarded ads that pressure children ("Watch this ad to continue playing")
  • No ads for age-inappropriate products (alcohol, gambling, mature-rated games, etc.)

What's Permitted (If Applicable)

  • Contextual advertising based on the content being viewed (not user behavior) — e.g., showing an ad for a kids' movie in a kids' game
  • First-party promotions for your own content (cross-promoting your other games/products)
  • All ads must be clearly labeled as "Advertisement" or "Sponsored"
  • Eggscape recommendation: Avoid ads entirely. The cosmetics/Battle Pass model is more lucrative for kids games and avoids the regulatory complexity of children's advertising. Ads also degrade the VR experience and increase churn.

App Review Process

Timeline & Stages

  1. Pre-submission (2-4 weeks before): Complete IARC questionnaire, finalize privacy policy, prepare store assets (screenshots, description, trailer). Apply for Quest developer account if not already done.
  2. Initial submission: Upload build + store listing via Meta Quest Developer Hub. Include all required metadata, privacy policy URL, and content rating.
  3. Technical review (1-2 weeks): Meta tests for crashes, performance (must maintain 72fps on Quest 3, 60fps on Quest 2), comfort (no VR sickness-inducing design), and Quest platform guideline compliance.
  4. Content review (1-3 weeks): Manual review of all content for age-appropriateness, policy compliance, and accurate content descriptors. Kids apps receive additional scrutiny here.
  5. Decision: Approved, rejected with feedback, or requires changes. Average total time: 2-6 weeks for first submission. Subsequent updates: 3-7 business days.

Common Rejection Reasons (Kids Apps)

  • Inadequate parental controls: Social features not properly gated, IAP not properly authenticated, no integration with Meta Family Center
  • Privacy policy issues: Missing, inaccessible, or doesn't specifically address children's data practices
  • IAP flow violations: Missing price display, one-click purchases, unclear what's being bought, virtual currency confusion
  • Content rating mismatch: Declared E rating but content has T-level themes (too much peril, scary imagery, text chat enabled by default)
  • Performance issues: Drops below 72fps in key scenarios, loading times exceeding 30 seconds, crashes during common flows
  • Comfort violations: Camera movements that cause VR sickness, lack of comfort settings, forced locomotion without alternatives

Appeal & Re-submission

  • Rejections include specific feedback on what needs to change — address every item, not just some
  • Re-submissions go through an expedited review (typically 1-2 weeks)
  • If you disagree with a rejection, you can appeal through the Developer Hub. Appeals are reviewed by a different team. Include documentation supporting your position.
  • Multiple rejections do not penalize your account, but they do delay launch. Plan for at least one rejection cycle in your timeline.

Pre-Submission Compliance Checklist

Complete Before Submitting to Quest Store

  • IARC questionnaire completed and rating received (target E10+)
  • Privacy policy published at a public URL, specifically addresses children's data
  • Privacy policy link embedded in-app (Settings menu) and in store listing
  • Meta Family Center integration tested — supervised accounts detect correctly
  • Default settings for supervised accounts: quick-chat only, no unsolicited friend requests, parental purchase authentication
  • All IAP screens show real-money prices with two-step confirmation
  • No third-party SDKs that collect persistent identifiers from children
  • Content descriptors accurately declared (Users Interact, In-App Purchases, etc.)
  • Performance targets met: 72fps Quest 3 / 60fps Quest 2, <15s load times
  • VR comfort settings available: snap turn, vignette, seated mode
  • Reporting system functional and accessible from all game states
  • All user-generated content (names, chat) passes through content filter
  • Store listing assets prepared: 5+ screenshots, 30-60s trailer, description under 4000 chars
  • Refund policy link accessible from in-app store
  • Age gate implemented — does not coach users to enter a specific age

Steps to Ensure First-Time Approval

  1. Engage Meta Developer Relations early: Reach out through the Quest Developer Hub for a pre-submission consultation. Meta offers office hours and can flag issues before formal review.
  2. Study recent approvals: Look at kids apps that were recently approved (Horizon Worlds kids features, educational VR apps) and mirror their compliance patterns.
  3. Over-comply: When in doubt, be more restrictive than required. It's easier to unlock features post-approval than to fight a rejection. Launch with conservative defaults and loosen based on feedback.
  4. Internal QA checklist: Before submission, have someone unfamiliar with the project go through the entire app on a supervised account and document every friction point. Fix issues before Meta finds them.
  5. Budget 8 weeks: Plan for a 6-week review plus 2 weeks of buffer for a rejection/re-submission cycle. Do not announce a launch date until you have approval.