Skip to content

Policing Content

AeroBeat is an open platform, but it is not a lawless one. The locked v1 moderation posture is mod.io curation plus human review, with automation used as advisory support rather than as an AI-first public gate.

V1 moderation posture

For launch:

  • all public UGC must pass review before release
  • the operational gate is mod.io Full Curation
  • human reviewers remain responsible for approval decisions
  • automation may help surface risks, but it should not be treated as the only authority

This means v1 moderation is intentionally lower-scope than a custom AeroBeat-owned review platform.

What review is trying to catch

Review is meant to catch:

  • malformed or broken packages
  • missing required assets
  • misleading metadata, thumbnails, or storefront claims
  • free/premium lane rule violations
  • clone or near-duplicate abuse
  • rights / licensing self-attestation problems
  • illegal, abusive, unsafe, deceptive, or otherwise disallowed content

Review should not be framed as a vague aesthetic-quality gate.

Creators must self-attest that they hold the necessary rights for all included content and assets.

The v1 posture is:

  • no proof-of-rights documentation required in the normal submission path
  • the current operational route for copyright / DMCA / takedown handling is mod.io's reporting and moderation system
  • repeat or severe abuse may still lead to creator sanctions or removal from trusted lanes

This describes the current review/takedown workflow, not a final legal conclusion that the full DMCA / safe-harbor posture is settled. Depending on final provider/legal guidance, AeroBeat may still need additional escalation or response duties when likely infringement is reported or independently discovered.

Suspensions and post-publication action

The v1 policy vocabulary still needs a conceptual suspended state for high-risk cases after release.

Examples include:

  • DMCA / rights complaints
  • fraud or bait-and-switch behavior
  • serious safety or trust concerns
  • severe clone / abuse concerns

In v1, that concept maps to mod.io deactivated rather than a separate AeroBeat-owned moderation state machine.

Reporting content

Athletes should be able to report content from the in-game browser or from the mod.io-facing listing/reporting flows.

Human review remains the durable decision layer for escalations, ambiguous policy calls, and repeat-offender handling.

Streamer mode note

Streamer-mode and copyright-safe playback ideas may still be useful product features, but they are separate from the locked v1 moderation gate. They should not be confused with the public submission/review policy.