Plain-English explanation
Every platform that offers adult content needs some way to keep it away from minors, and "age verification" covers a wide spectrum of approaches. At the weakest end is a self-attestation click-through: a button that says "I am 18 or older," which confirms nothing beyond the user's willingness to click it. At the stronger end are systems that check a government-issued ID, run facial age-estimation, or rely on a third-party verification service that confirms age without the platform itself seeing the underlying ID.
Which approach a given platform uses is increasingly not just a product decision: a growing number of jurisdictions now require specific verification methods by law for sites hosting adult content, rather than leaving it to a site's discretion.
Adult-AI use
Age verification is one of the first gates a user encounters on an AI companion or image/video generation platform that offers explicit modes governed by an NSFW filter, often a click-through on first visit, sometimes a more substantial ID or payment-card check before explicit features unlock. Payment processors, app stores, and cloud infrastructure providers that adult AI platforms depend on frequently impose their own age-verification or content-moderation requirements as a condition of service, which is part of why verification methods vary so much between platforms and can change abruptly when an upstream provider updates its policy.
Common uses
- A self-attestation checkbox or birthdate field gating entry to a site's adult section.
- Government ID upload, often processed by a third-party verification vendor rather than stored by the platform itself.
- Facial age-estimation software that estimates whether a user appears to meet a minimum age from a live camera check.
- Credit card verification, used as a weak proxy for adult age in some regions.
Limitations and misconceptions
- A checkbox-style self-attestation verifies nothing on its own; it shifts stated responsibility to the user rather than confirming age.
- Stronger methods (ID upload, age estimation) raise their own privacy questions about how long identity data is retained and by whom, which is why reputable implementations increasingly use a third-party verifier that confirms only a yes/no age result to the platform rather than sharing the ID itself.
- Requirements differ significantly by jurisdiction and are actively changing; a method that satisfies one region's law may not satisfy another's.