Moderation Policy
Effective date: May 18, 2026. Safety, abuse, moderation, and App Review questions are received at support@appxora.xyz.
Summary
XORA is an invite-based secure messenger. This policy explains reports, blocking, invite abuse controls, rate limits, escalation, and E2EE moderation limits.
Report content or users
Use in-app report controls when available or contact support@appxora.xyz. Do not send passwords, recovery phrases, verification codes, private keys, or unrelated personal data. If you voluntarily submit evidence, include only what is necessary for review.
Block users
Blocking is intended to reduce unwanted interaction. Depending on the current build and surface, blocking may limit contact, visibility, notifications, messaging, or profile interaction with the blocked user.
After a report
XORA may review account, invite, device, rate-limit, abuse, entitlement, and metadata signals. Because XORA is designed as a secure messenger, operators may not be able to view message plaintext unless a user voluntarily submits client-side evidence.
Enforcement
XORA may remove content where technically possible, restrict features, disable invites, apply rate limits, suspend accounts, preserve relevant records, escalate urgent safety issues, or take other action needed for user safety and legal compliance.
Prohibited abuse
XORA has no tolerance for CSAM, child exploitation, credible threats, trafficking, terrorism, non-consensual intimate content, malware, account takeover, harassment, spam, fraud, or illegal activity.
Invite and rate controls
XORA may use invite-only access, invite validation, reservation controls, email verification, rate limits, session checks, and abuse throttles to reduce spam, fraud, and coordinated abuse.
Appeals and contact
If you believe an enforcement action was incorrect, contact support@appxora.xyz with concise account context. Do not include verification codes, recovery phrases, passwords, private keys, or unrelated personal data.
Production queue status
This public policy is App Review-ready. Full production moderation queue and server-backed enforcement workflows remain release-gated until production HTTPS API readiness is proven.