Age & Identity Verification

Closegram sells paid, creator-owned intimate content (exclusive posts, subscription chats, shop products, live streams), so two separate compliance concerns exist beyond the notability verification badge (which is about authenticity/notoriety, not age or identity): confirming a new account belongs to an adult, and confirming a creator's real-world identity before they can cash out real money.

Each property has its own checkbox marking whether that specific piece is fully implemented and functional end to end (frontend + backend) — update these yourself as work lands; this page won't overwrite them.

• Require a date of birth at signup and reject registrations under 18 — the registration form now collects it and the backend enforces a minimum age of 18 (previously: the field existed in the schema but was optional and the signup form never asked for it, so effectively no age check ever ran)
• Submit an identity verification request (a government ID photo + a selfie) from Settings
• View your own request status (not submitted / pending / approved / rejected, with the rejection reason if applicable) and resubmit after a rejection
• Admin review queue: view the submitted documents, approve, or reject with a reason
• Gate cashouts on identity verification — you can't request a Stripe or manual cashout until an admin has approved your identity verification
• Automated/third-party ID verification (e.g. Stripe Identity, Persona) — this is a fully manual, admin-reviewed flow today
• Age verification beyond the signup date-of-birth check (e.g. re-verifying age for specific content, ID-based age verification) — the platform relies on the signup-time date of birth

See the technical reference for GraphQL schemas, routes, source file links, and per-field wiring status.