Creator Verification, Consent, and 2257-Style Recordkeeping Policy

Noodi maintains a compliance workflow for adult creator verification, consent confirmation, performer approval, audit logging, and 2257-style recordkeeping support.

Creators must complete identity verification, government ID review, age verification, liveness/selfie review, duplicate-identity screening, creator agreement acceptance, adult-content consent acceptance, no-AI/no-synthetic-impersonation certification, tax form completion where required, payout setup, and admin approval before creator features unlock.

Jumio or another verification provider may handle ID, selfie, liveness, document authenticity, fraud, duplicate, and age checks. Noodi may still require admin review and may override or reject if platform risk remains.

Every performer or identifiable person in content must be separately verified and approved. A creator may not upload content of a spouse, partner, friend, co-creator, guest, or other person until that person has a completed performer record linked to the creator profile and content item.

Noodi maintains performer records with legal name, stage name where applicable, date of birth, verification reference, approval status, consent/release acceptance, linked creator profile, linked content references, timestamps, and reviewer/audit history.

Creators must obtain and maintain voluntary, informed, specific consent from every person in content for creation, upload, sale, distribution, teasers, paid messages, subscriptions, marketing teasers where applicable, and retention of records.

If consent is disputed, revoked, unclear, incomplete, expired, or missing, Noodi may remove or restrict content and hold payouts while reviewing the issue.

For sexually explicit visual content, creators may have legal obligations to maintain age and identity records for each performer, production dates, custodian-of-records information, and related content records. Noodi may require creators to provide or confirm records before publication or payout.

Noodi keeps secure internal records to support platform safety, verification, consent, audit, payment, and legal response workflows. Noodi's technical workflow does not replace a creator's independent legal obligations.

Sensitive verification records are admin-only, private, and auditable. Noodi logs every view, download, approval, rejection, status change, resubmission request, note, export, and access to verification or performer records.

Verification records may not be deleted except through a super-admin or legal retention workflow that preserves required audit history and complies with retention obligations.