21+ confirmation

Confirm your age before entering the protected product flow.

Ask for a direct user confirmation that they meet the current 21+ adult-entry threshold before onboarding, billing, or protected runtime entry begins.

Keep the step short. Explain the current policy posture, note that unresolved region handling stays fail-closed on the stricter default, and keep policy links close to the action instead of burying them elsewhere.

Return to landing page

Continuing keeps the protected 21+ route tied to the linked Terms, Privacy, and Billing Policy instead of hiding consent posture in a distant footer.

What this unlocks

  • Protected app entry stays behind a real server-side confirmation seam.
  • Confirmation persists cleanly for downstream onboarding and premium entry.
  • Future region-aware policy can replace the default without redesigning every page.