Full KYC & 2257 Compliance
Complete identity verification with video, ID document, liveness detection, face matching, and automatic 2257 performer record creation.
Client-Side Automated Checks
The following checks run in the user's browser during the verification session using local AI models. No biometric data is sent to third-party servers.
| Check | Description |
|---|---|
| Document detection | Edge detection, aspect ratio validation, coverage analysis |
| Document OCR | Keyword detection (100+ terms, 15+ languages) for ID fields: name, DOB, expiry, document number |
| Face detection | Single face, centering, size, frontal pose |
| Liveness challenges | Randomized blink detection and head turn (left/right) |
| Anti-spoofing | Detects printed photos, video replay, and masks |
| Screen fraud detection | Detects if an ID is displayed on a screen rather than a physical document |
| Face descriptor extraction | 1024-dimensional embedding for face matching between liveness and ID photo |
Admin Manual Review
After client-side checks pass and the verification is submitted, an admin reviews the evidence and performs the following checks:
| Check | Description |
|---|---|
| DOB extraction | Admin extracts date of birth from the ID document |
| Age threshold | Subject must be at least 18 years old based on extracted DOB |
| Legal name extraction | Required for 2257 performer records (full_kyc level) |
| Document authenticity | Visual inspection for tampering, forgery, and expiration |
| Face matching | Compare liveness face vs ID photo using cosine similarity of face embeddings |
2257 Performer Records
When a full_kyc verification is approved, a 2257 performer record is automatically created. These records support US regulatory compliance for adult content platforms.
- Auto-created on approval — no separate API call required
- Legal name and DOB — extracted by admin during review
- Alias support — stage names and companion names can be registered via the API
- Document details — document type, hashed document number, and archived document images
- 7-year retention — records are retained for 7 years from creation as required by 18 U.S.C. 2257
- Immutable access audit trail — every view, download, review, and export event is logged with actor, IP, timestamp, and access reason
- JSON export — full record export for compliance audits
Retention Policy
| Data | Retention | Basis |
|---|---|---|
| Performer records | 7 years minimum | 18 U.S.C. 2257 compliance |
| Verification data (full_kyc) | 7 years | Matches performer record retention |
| Verification data (full_age) | 1 year after expiry | GDPR data minimization |
| Access audit logs | 7 years | Compliance audit trail |
Verification Status Flow
Every verification follows a defined status progression:
pending→under_review→approved|rejected|resubmit_required
On approval of a full_kyc verification, the performer record is created automatically and linked to the verification. The platform is notified via the status polling API.
Frequently Asked Questions
- What document types are accepted for full KYC?
- AgeEvidence accepts passports, driver's licenses, and national ID cards. The system performs document edge detection, aspect ratio validation, and coverage analysis during capture. For passports, only the front is required. For driver's licenses and national IDs, both front and back are captured.
- How does face matching work between the liveness video and the ID photo?
- The system extracts 1024-dimensional face embeddings from both the liveness capture and the ID document photo. An admin reviews the cosine similarity score during manual review to confirm the person in the video matches the person on the document.
- What happens to 2257 records after a performer leaves a platform?
- Records are retained for a minimum of 7 years from creation, regardless of whether the performer remains active on the platform. This retention period is a legal requirement under 18 U.S.C. 2257. Records include an immutable access audit trail showing every access event.
- Can performers register stage names or aliases?
- Yes. The 2257 record system supports alias registration so that stage names and companion names can be linked to the legal identity on file. Aliases are registered through the API and stored alongside the performer record.