Age verification for adult content producers: what good looks like

There is a version of age verification that most adult productions actually run, and it goes like this. Someone is recommended in a group chat. You look at their feed. They look like an adult. You ask, near the end of the booking conversation, whether they can send ID, and they send a photograph of a driving licence taken at an angle on a duvet. You screenshot it. The screenshot lives in the message thread until you change phones.

Every part of that is understandable and almost none of it survives contact with the question it is supposed to answer. This is a practical walk through what a check should establish, what record it should leave, how long that record needs to live, and the specific ways the common version fails.

What you are actually establishing

"Age verification" is shorthand for three separate propositions, and the confusion between them is where most processes go wrong.

• This document is genuine. The identity document has not been altered or fabricated.
• This document belongs to this person. The person in front of you is the person the document describes.
• That person is 18 or over. The date of birth on the genuine, matched document places them over the line.

A photograph of a licence sent over a messaging app addresses the third and only the third, and only if the first two happen to hold. It cannot show you that the document is real, because you are looking at a compressed image of it. It cannot show you it belongs to the sender, because anyone can photograph anyone's document. The check that feels most reassuring is doing the least work.

Why the match is the hard part

Document authenticity is a solved problem at a technical level: security features, machine-readable zones and optical checks are well understood. The genuinely difficult step is binding the document to a live human being at a specific moment. That is what a liveness capture does, and it is the reason a guided live capture is not interchangeable with a selfie. A selfie is a file. A file can come from anywhere.

If you take one thing from this article: a process that never required the person to do something live is not a match, however good the document was.

The record is the deliverable

Producers tend to think of verification as a gate, something you pass through and forget. In practice the gate matters much less than the receipt. Nobody is going to ask you, later, whether you felt satisfied. They are going to ask you to produce something.

A usable verification record has five properties:

• Contemporaneous. Created before the shoot, not assembled after a query.
• Specific. Tied to a named booking on a named date, not a general assurance about a person.
• Attributable. States what was checked, by what method, and when.
• Durable. Survives a phone upgrade, a staff departure and a platform shutting down.
• Retrievable. Findable in minutes by someone who was not there.

Score the message-thread screenshot against that list and it fails four of the five. It is contemporaneous and nothing else. This is why productions that felt careful at the time are unable to answer a compliance query eighteen months later: the caution was real and the record was not.

Who actually asks

The mental model of "what if this ends up in court" is not wrong but it is rare, and building a process around a rare event makes it feel optional. The frequent requests come from three places, and all three ask the same question in different words.

Distributors

A distributor's compliance team will not accept material without documentation of the performers, because their own downstream relationships depend on it. They typically want to see that a check existed, when it happened, and that it predates the material. Material submitted without it is not argued about. It is declined.

Payment processors

Processors carry direct liability for what they process and are correspondingly unforgiving. A processor review is usually triggered by volume, by a chargeback pattern, or by a complaint, and it arrives with a short deadline. Businesses lose processing over documentation they had, somewhere, but could not produce inside a week.

Advertising and hosting platforms

If any of the material is used in paid placements, the platform's policy team applies its own standard, and that standard has tightened steadily. The specific request is usually for the release and the licence rather than the identity check, but the three travel together and a gap in one invites questions about the others.

What good looks like in practice

A defensible process is not elaborate. It is four things done in the right order.

1. Check before you book, not before you shoot

Doing the check when the model arrives on set is the worst possible moment. You have paid for a studio, a crew is standing around, and everyone is under pressure to proceed. That pressure is exactly what makes people accept a document they would otherwise question. Move the check to the point where saying no costs nothing, which is before the booking is confirmed.

This is the single argument for verification happening at the platform level rather than the production level. If the check is a precondition of a profile being visible at all, the awkward conversation never occurs, and the pressure to wave something through never arises. That is how verification works on this platform: nothing publishes until the document, the liveness match and the date of birth have all passed.

2. Record what was checked, not what you concluded

"Verified, 18+" is a conclusion. A record states the method: document type, the check performed, the match performed, the date of birth read from the document rather than typed in by the subject, and the date and time. A conclusion cannot be re-examined. A record can.

3. Link the record to the booking

A verification floating free of a booking is only half an answer, because the question is always about specific material. The link is what turns two files into a chain: this person, checked on this date, booked for this shoot, under this release, licensed for this use. Assembling that chain retrospectively is the task that eats a week when a distributor asks.

4. Store it somewhere that is not a phone

Identity documents on a producer's laptop are a liability, not an asset. You are storing other people's sensitive data with no particular expertise in doing so, and if it leaks you have created a far worse problem than the one you were solving. The better arrangement is that the verifier holds the document and the producer holds proof that a verification exists, with an identifier and a date, and never the document itself. That is exactly what a booking-linked record-keeping entry is for.

The failure modes, named

The verified-by-vibes check

The person is clearly in their thirties, so nobody asks. This is fine right up until it is not, and the whole point of a process is to be identical for people about whom you have no doubt. A process only applied when someone looks young is a process that documents your suspicion rather than your diligence.

The reused check

You verified them eighteen months ago, so you do not check again. Age does not go backwards, so this is defensible on the age question and weak on the identity question: you are relying on an old match to a person you are booking today. Re-verification on a schedule and on document expiry costs almost nothing.

The delegated check with no record

An agency, a scout or another producer says they verified. Possibly they did. What you hold is a sentence. Delegation is fine, but delegate to someone who gives you a record with an identifier and a date, not an assurance in a message.

The check that dies with the platform

The record lived in a service that shut down, or an account that got deleted, or a person who left the company. Retention is a policy question and it needs an actual answer, in years. The record-keeping statement for this platform sets its answer at seven years from the last completed booking a record supports.

Where the release and the licence come in

Age verification answers who. The release answers what they consented to, and the licence answers what you may do with it. Compliance queries almost never ask for one in isolation, because a check without a release proves you booked a legal adult and nothing about consent to the use you made of the material. Our companion piece on model releases and usage rights goes through each clause.

The practical consequence is that all three should be generated at the same moment by the same event. When they are separate documents produced by separate people at separate times, the gaps are where the problems live. If you want to see the full document set a specific shoot needs, run it through the casting brief builder: the compliance checklist it produces is generated from the shoot type and the usage you pick.

A checklist you can actually apply

• Verification is a precondition of booking, applied identically to everyone.
• The check includes a live capture matched to a genuine document.
• The date of birth is read from the document, not entered by the subject.
• The record states the method and the date, not just the conclusion.
• The record is linked to the specific booking by identifier.
• You hold proof of the check; you do not hold copies of other people's identity documents.
• Retention has a stated number of years and somebody knows what it is.
• Somebody who was not there could retrieve the chain in under ten minutes.

None of this is legal advice and requirements differ by jurisdiction, particularly around what a producer is obliged to retain and for how long. But the shape of a good answer does not vary much: check before you book, record the method, link it to the shoot, and keep it somewhere that will still exist when someone asks.