GAMHON Profile – OpenACAI

GAMHON profile

A GAMHON profile card is a small preference card for future games and group activities. It is not a public profile, friend list, message inbox, or social feed.

Edit account preferences Play current games Safety rules

Current use

A card for comfort and play preferences.

Use it to remember a display name, avatar color, play style, comfort boundaries, and contact boundary. Keep private details, medical history, emergency needs, passwords, benefit case numbers, and full Social Security numbers out of profile fields.

Open account page App readiness

Launch gates

What stays closed until the safeguards are real.

Future Android, iOS, and web clients should treat unknown profile or social readiness as disabled. A missing gate is not a soft launch.

Public profiles

Off until profile review, reporting, blocking, visibility audit logs, and privacy review are in place.

Friend graph

Off until consent, abuse prevention, account recovery, and youth-safety rules are written and tested.

Direct messages

Off until moderation, report handling, evidence preservation, blocking, and emergency guidance are ready.

Online rooms

Off until room rules, facilitator controls, reports, pause tools, and escalation paths exist.

Social sign-in

Hidden until provider setup, PKCE/state checks, privacy copy, and app redirect rules are verified.

Signed-in sync

Held until sessions, no-store responses, device storage, and deletion/export paths are tested.

Developer handoff

Contracts future app clients must read.

These public documents are safe to cache and do not contain user profiles, emails, messages, secrets, OAuth client secrets, or case details.

Public contractAccount data rulesWhat account/profile actions can appear in web or native clients.openacai.ong Public contractSocial readinessWhich social features are supported now and which must stay hidden.openacai.ong Public contractIdentity readinessOAuth, session, PKCE, redirect, and Cloudflare Access boundaries.openacai.ong Public contractCommunity safetyModeration, reporting, blocking, youth-safety, and launch gate rules.openacai.ong Public contractSync mapPublic datasets a mobile app can cache, refresh, and verify by hash.openacai.ong Public contractMobile packageApp-facing manifest for public contracts and offline-ready data.openacai.ong

What someone can do today

Use public GAMHON games without an account
Sign in to save private GAMHON profile preferences
Export a full profile preference JSON for personal records
Export a safer GAMHON card without account identifiers or free-text notes

What the share card leaves out

Email address
User login
private account identifiers
free-text profile notes
case data
messages
private files

What future apps should do

Read account, social, identity, safety, sync, and mobile package contracts at startup. If a contract is missing, stale, or says a feature is gated, hide that feature and keep the public help tools usable without sign-in.

Why this is public

People should be able to see the safety boundary before signing in. Partners and future app reviewers should also be able to confirm that OpenACAI is not quietly launching social features before the safeguards exist.