Community safety
How OpenACAI is keeping GAMHON, profiles, group play, and future social features gated until the reporting, blocking, moderation, privacy, and youth-safety pieces are ready.
Call or text 988 in the United States. Call 911 for immediate danger. OpenACAI games, profiles, and contact forms are not monitored emergency services.
Current mode
What is available now, and what stays closed.
The site can be useful without opening public social spaces too early. This keeps the GAMHON work honest while the back-end and moderation tools are being built.
Shared-screen games
Breathing, grounding, mood weather, connection cards, and co-op prompts can be used without creating an account.
Open gamesPrivate profile preferences
Signed-in users can save GAMHON display preferences, accessibility notes, and local exports. Public profile directories are off.
View account pagePublic social features
Public profiles, direct messages, open rooms, online friend graphs, and open matchmaking are gated until safety controls are tested.
Launch gates
What must exist before wider social features open.
These are product requirements, not slogans. If a feature needs people to interact online, it needs a clear safety path first.
Report flow
People need a visible way to report messages, profiles, rooms, invitations, and behavior that breaks the rules.
Block and mute controls
Users need simple controls to stop unwanted contact without explaining themselves to the other person.
Moderator queue
Staff or approved moderators need a private queue for reports, review notes, decisions, and follow-up.
Youth-safety review
Any youth-facing or mixed-age space needs age-aware design, adult-supervision boundaries, and clear limits.
Audit trail
Profile visibility changes, report decisions, moderation actions, and role changes need private audit records.
Abuse limits
Invites, posts, messages, file links, and account creation need rate limits and abuse detection before public launch.
Privacy boundaries
What the public website should not expose.
Public pages should help people understand the program. Private safety work belongs behind access controls, no-store caching, and role checks.
No public social graph
The site should not publish who someone knows, talks to, plays with, or receives support from.
No public moderation records
Reports, reporter names, decisions, notes, and case details should not appear in public HTML, feeds, analytics, or cached pages.
No sensitive analytics
Analytics events should not send names, emails, phone numbers, message text, profile notes, report text, or search text.
Facilitators and partners
Use the current games as guided activities, not unsupervised public rooms.
For now, GAMHON fits best as shared-screen play, small group prompts, workshops, family-table activities, or professionally facilitated sessions. Public online spaces come later.
Why public rooms are not open yet
A room that lets people meet strangers, message each other, invite others, or create public identity needs safety controls before it is fair to users. OpenACAI is keeping those features closed until the basics are in place.
What a safe pilot can look like now
- A facilitator starts the activity
- People can pass on any prompt
- No one is pressured to share private history
- The group uses copied rules before play starts
- Immediate crisis needs leave the game and use 988 or 911
How this connects to accounts
Account profile preferences can help future games remember accessibility choices and comfort boundaries. They are not a public profile directory, message inbox, or social feed.
Machine-readable safety contract
Developers and future app builds can read the current safety gates at openacai.ong/.well-known/openacai-community-safety.json.