Safety at Agyata
Who we are trying to protect
Everyone using Agyata is 18+. That gate is strict and binding. Within that population, we pay the most attention to users being harassed, users receiving sexual content they did not ask for, and users being targeted for their identity.
How the 18+ gate works
A single-screen confirmation on first visit. Persisted locally and server-side. If you are under 18, do not use this site. Any report that surfaces a minor triggers immediate escalation — frame evidence via perceptual hash (not the frame itself), and where applicable, escalation to NCMEC-partner channels on our post-launch track.
Reporting
Every confession has a Report button. Every chat room — text or video — has a Report button. Reports are triaged by real humans through an ops CLI (the full web ops dashboard is a v1.1 item). Three distinct reporters on a confession auto-soft-hide it pending review.
Abuse detection
Text: every chat message and every confession passes a Workers AI classifier. Three flags in a single room auto-ends the room. Video: Cloudflare CSAM Scanning Tool runs at the zone level. On a report, your browser computes a perceptual hash of the flagged frame — only the hash reaches our moderation pipeline; the frame itself never leaves your device.
Bans and evasion
Bans apply at the session fingerprint layer. Clearing cookies does not defeat them. Evasion attempts are shadow-queued — the offender appears to be in the queue but will not be paired.
What we keep and what we do not
Confession text is persisted in our database until removed. Chat messages (text or video) are never saved. Reports keep evidence — up to the last fifteen text messages in a reported chat, and perceptual hashes of reported video frames. Hashed IPs + timestamps are kept for 18+ compliance. No emails, no phone numbers, no behavioral logs.