VibeSense Community Standards

Content and behavior we do not allow

These rules cover visible and hidden content, code paths, assets, metadata, store media, links, and game behavior. A game must not contain or facilitate:

• Nudity, pornography, sexual activity, sexual exploitation, fetish content, or sexualization of minors.
• Hate, racism, dehumanization, or discrimination targeting protected or vulnerable people.
• Harassment, toxicity, threats, stalking, humiliation, or bullying, including systems designed to encourage it.
• Praise, propaganda, recruitment, fundraising, or operational support for extremist or terrorist organizations or ideology.
• Graphic gore, torture, sadistic cruelty, realistic mutilation, or cruelty to people or animals presented for shock or enjoyment.
• Encouragement, instruction, glorification, or coercion relating to suicide, self-harm, eating-disorder behavior, or dangerous challenges.
• Instructions or tooling that meaningfully enable illegal, violent, dangerous, or controlled activity.
• Scams, fraud, impersonation, deceptive monetization, manipulated consent, dark patterns, or misleading claims.
• Privacy abuse, stalking, surveillance without consent, credential collection, doxxing, or exposing personal or sensitive data.
• Malware, credential theft, destructive behavior, exploit delivery, malicious downloads, unsafe redirects, phishing, or deceptive or executable external content.
• Unsafe external commands, online interactions, chat, matchmaking, user-generated content, moderation gaps, or network-loaded content that can bypass these standards after approval.

Contextual teen-friendly content

Reasonable allowances may include non-graphic fantasy or cartoon violence, stylized combat, mild peril, non-targeted competitive banter, and age-appropriate themes when they are not hateful, sexual, cruel, instructional, or realistically graphic. Context matters, and these examples do not guarantee acceptance.

What review covers

Every immutable revision is reviewed against the exact policy version accepted by its creator. Review covers source code and reachable code paths; visible and hidden text, dialogue, and names; audio, music, and voice; images, video, animation, models, and fonts; metadata, manifests, and package text; screenshots, trailers, and store copy; external commands, links, and redirects; runtime or network-loaded content; analytics and data collection; and online, community, and user-generated-content features and moderation controls.

Where applicable, review also covers alternate states, errors, easter eggs, progression, unlocks, and platform-specific paths.

Unreviewable content

Encrypted, obfuscated, dynamically generated, remote, account-gated, region-gated, age-gated, unavailable, or otherwise unreachable content remains under review and cannot be published when it cannot be assessed. The creator must make it reviewable or remove it. An assertion that hidden content is safe is not evidence.

Creator attestation

For every submission and revision, the creator must attest that all in-scope content and behavior complies with the linked policy version, disclose every external, network, and user-generated-content surface, confirm the necessary rights and consents, and accept re-review, suspension or takedown, and record retention.

The acceptance is bound to that creator, revision, source checksum, policy version, and acceptance time. It never carries forward to a new revision.

Updates and policy changes

Any code, content, asset, metadata, store-media, link, network, external-command, moderation, or user-generated-content update requires a new immutable revision, a fresh attestation, and full re-review before publication. Material policy changes may require re-attestation and re-review on a documented transition schedule. Urgent safety changes may cause immediate suspension.

Review decisions and remediation

Review combines automated checks, AI-assisted analysis, and human judgment. AI is defense in depth and cannot approve a game on its own. Creators may receive actionable comments that cite these public standards and identify concrete content or code to remediate. Internal review methods, sequencing, coverage, reviewers, and security details are not disclosed.

Suspension, takedown, and appeals

Published content that no longer complies may be delisted or suspended, with checkout, installation, and downloads disabled while it is reviewed. VibeSense preserves customer treatment and relevant evidence under its retention policy.

Creators may request appeal or re-review from their dashboard and respond through actionable remediation comments. An appeal stays under review, does not restore acquisition automatically, and does not disclose the internal workflow. A revised game must complete a fresh review before publication.

Questions

Questions about these standards can be sent through the contact form. The current version is always available at this URL; accepted versions are retained for audit and support.