Every adult site has some kind of age gate, and the range between the weakest and the strongest is enormous. At one end is a button saying you are over eighteen, which stops nobody. At the other is document or payment verification, which works and introduces a set of problems of its own. Both exist for reasons and they are not interchangeable.

It is worth being clear-eyed about what each accomplishes, because a great deal of public argument about this treats the weakest option as though it were the strongest, or dismisses the strongest as though it did nothing.

What a click-through gate does

A self-declaration gate does three things. It states clearly what is on the other side, so nobody arrives by accident. It creates a deliberate act, which changes the character of the visit. And it satisfies a requirement in some jurisdictions and some payment arrangements, which is frequently the actual reason it exists.

What it does not do is verify anything, and pretending otherwise is dishonest. Treating it as an interface courtesy and a legal formality is the accurate description, and designing it in that spirit produces something more useful than a stern warning that everybody clicks past in half a second.

What real verification does

Document checks, payment card checks and third-party verification services genuinely restrict access. They also collect identity data about adults who wanted to look at drawings, and that data becomes a target. Breaches of such systems are not hypothetical, and the consequences fall on readers rather than on the service that collected it.

There are approaches that reduce the exposure, including third parties that confirm an attribute without passing identity to the site. These are better and they still create a record somewhere. Anybody implementing verification should be able to say plainly what is stored, by whom, and for how long.

Requirements differ by jurisdiction

Some jurisdictions require nothing beyond labelling, some require meaningful verification, and the map changes regularly. A site available internationally is therefore subject to several regimes at once, which is the layered rule problem described in the piece on why publishability varies.

Geographic detection is the common response, applying stricter checks where they are required. It is imperfect, since detection is approximate and readers travel, but it is the practical middle between blocking large regions and ignoring their law entirely.

The cost in reach

Every additional step loses readers. A verification flow that requires uploading a document loses the large majority of casual visitors, including many who would have become paying supporters. That is a genuine cost and it should be counted honestly rather than treated as somebody else's problem.

It also pushes readers toward services that do not verify, which are frequently the ones with the worst practices on everything else. Strict requirements applied unevenly tend to advantage operators who ignore them, which is an outcome worth noticing when arguing about policy.

Designing a gate honestly

Whatever the mechanism, the gate should say plainly what the site contains, what it is asking, and why. Vague warnings and dark patterns that hurry people through both undermine the purpose, and readers are entitled to know what they are agreeing to, which is the position set out in our reader agreement.

Uniquely worded, specific language beats a boilerplate warning copied from elsewhere. It reads as somebody having thought about it, which is also the impression a reader should be given, because it should be true.

There is a design question underneath all of this that gets very little attention. A gate is the first thing a reader meets, and it sets the tone for everything after it. A page that is clear, calm and specific about what the site is suggests a publisher who has thought about their readers; a flashing warning with three exclamation marks suggests the opposite, and readers draw conclusions from it immediately. The gate is part of the publication, not an obstacle placed in front of one.

Choosing a gate that matches what you claim

Decide what the gate is for, implement the level your jurisdictions actually require, be honest about what verification collects and retains, count the reach cost rather than ignoring it, and write the wording yourself. That is a defensible position at any level of strictness.

Our own data handling is described in the data page, and account-level controls for creation stay with the source platform at adult character safety.