Safety & Community Playbook
How bounded design, moderation, reports, and blocks reduce risk.
1. Core Philosophy: Why Mythic Match Exists
Mythic Match supports imaginative connection through creature personas and bounded interaction. Moderation reduces risk; it cannot guarantee safety.
Anti-Tinder by Design
Unlike typical dating apps that focus on real-world photos, rapid swiping, validation loops, and hookup culture, Mythic Match is built as a creative sanctuary. It is a space where real people can connect through mythological personas, roleplay, and narrative resonance.
Adult-only controlled beta: invited participants must be 18 or older and acknowledge eligibility before entering. We do not collect birth dates or identity documents, and do not claim verified age. A signed browser cookie grants access for up to 12 hours. Do not share access. Existing accounts can export, delete or appeal without entering the beta.
- Sexual innuendos, hookup requests, or sexually explicit lore.
- Harassment, bullying, or stalking.
- Predatory behavior, grooming, or child exploitation of any kind.
- Bad actors, trolls, and perverts looking to abuse open chat features.
To enforce this, we have engineered out the primary vector for online harassment and grooming: unrestricted free-text private messaging.
2. Bounded Communication Protocols
To maintain a fun, respectful, and safe space, all communication in Mythic Match is strictly structured and symbolic. There is no way for a user to type and send free-text messages to another user.
A. Pre-Written Symbolic Cards
Once a match (or 'resonance') is established, entities can communicate only through a curated deck of pre-written cards. These cards are crafted in a high-fantasy, atmospheric style. They allow users to express interest, set boundaries, invite collaboration, or slow things down.
- “The mist remembers you.”
- “Our realms may align.”
- “A ritual alliance seems possible.”
- “The omens are favorable.”
- “Your storms do not frighten me.”
- “Your signal feels steady.”
- “I would share a quiet omen.”
- “May your path stay protected.”
- “I welcome a slow ritual.”
- “Your lore deserves patience.”
- “I honor your boundary.”
- “I will keep respectful distance.”
- “This signal thread can rest.”
B. Free-Form Emoji Messages
- The Rule: Emoji messages must contain only valid emoji characters (e.g., 🦄🌈🌈⭐🕧).
- The Filter: Any standard alphanumeric text, punctuation, or hidden characters will be rejected automatically by the client and server.
- Emoji limits reduce ordinary text abuse but cannot prevent coded messages or all misuse. Report concerns and use Block for personal protection.
C. Card Reactions
Users can tap a sent card in their thread to toggle subtle, positive emoji reactions (e.g., 👍, ❤️, 😮, 😢) to show acknowledgement or delight without starting a new conversation thread.
3. The AI Moderation Engine
Profile and report text uses local filters and, when configured, Gemini review. Operators review submitted reports and custom labels. Filters can make mistakes.
A. Safety Thresholds
Our Gemini prompts are configured with zero-tolerance safety settings across four primary harm categories:
- Harassment: Block insults, aggressive language, and targeted intimidation.
- Hate Speech: Block derogatory statements, slurs, and discriminatory language.
- Sexually Explicit: Block physical/sexual descriptors, innuendos, and references to hookups or dating apps.
- Dangerous Content: Block self-harm, violence, doxxing, and illegal activities.
B. Fail-Closed Design
Configured AI moderation rejects the submission when review is unavailable. Rejection does not automatically delete an existing profile. There is no dedicated appeal workflow yet.
C. Custom Taxonomy Moderation
When players enter custom realms (e.g., 'Nebula Sprite') or custom affinities, these strings are saved to a separate queue for review by app operators. They do not appear in the global dropdown lists for other players until they have been audited, preventing offensive words from leaking into the shared taxonomy.
4. Reporting & Operator Protocols
If an entity generates a profile that bypasses automated safety checks (e.g., highly stylized roleplay that borders on harassment or includes hidden patterns), players have immediate recourse.
A. Reporting a Profile
From the Discover deck, players can report any candidate. The reporting UI requires selecting a reason:
- Harassment or Bullying
- Sexually Explicit / Dating Focus
- Real-World PII (Names, Phone Numbers, Social Media links)
- Inappropriate generated image (Borders, watermarks, text, or multiple faces)
- Off-topic / Non-fantasy theme (Trolling)
B. Report Containment & Deck Advancement
- Reporting requests operator review. It does not automatically block or quarantine the profile.
- Use the separate Block action to stop discovery and match interactions with that creature. Public profile pages remain publicly accessible.
- Operator Review Queue: Reports are logged directly to the operator dashboard, where the admin can view the creature's full profile details and take remediation actions.
C. Current operator limits
- Operators can review reports and set their review status. Changing a report status does not hide or block its target.
- Operators can restrict accounts after human review. A restricted account cannot interact or reactivate itself. Credential-authenticated appeals are available on Account safety. Lifting a restriction leaves the profile hidden until its owner recovers it. Custom-label review remains separate.
- One appeal is accepted per restriction. Check Account safety for the human decision; review time is not guaranteed. AI does not permanently delete accounts. No real-identity tracking or persistent re-registration fingerprint is implemented.