Content Moderation
This page describes the live backend moderation behavior that happens after uploads are attached to products.
Moderation pipeline overview
The current backend uses a mixed moderation model:
- image moderation through SightEngine
- video uploads handled outside the SightEngine image flow
- internal/manual review states surfaced through admin workflows
Image moderation
Images are checked server-side by the moderation job pipeline.
The public API does not ask clients to call SightEngine directly. Fangate handles:
- building the media URL or payload for moderation
- dispatching the moderation job
- storing the resulting verification/moderation status
Video moderation
The live backend currently does not send video media to SightEngine.
Instead, video uploads enter the moderation state model without SightEngine image analysis. Depending on creator moderation settings, that can result in manual approval handling.
Statuses used by the backend
The moderation / verification enum exposed through media records includes labels such as:
UncheckedApprovedAI RemovalManual Approval
These statuses are reflected in admin tooling and can affect whether content becomes purchasable or visible.
Skip-moderation behavior
The backend supports creator-level skip-moderation logic in some flows.
Important current behavior:
- skip-moderation does not mean every asset skips all status handling
- videos for skip-moderation users can still be set to
Manual Approval
That means client teams should not treat "skip moderation" as a guarantee of immediate public availability.
Consent and moderation both matter
Purchasability depends on more than moderation alone.
A product may still be blocked from purchase if:
- moderation is not in an allowed state
- third-party consent is pending or declined
Manual approval notifications
When media transitions into manual-approval workflows, the backend can dispatch creator notifications. The exact admin action surface is internal, but the resulting creator-facing state is part of the live behavior and should be expected in product workflows.
What integrators should do
- rely on product/media status returned by Fangate APIs
- do not hardcode direct SightEngine assumptions in clients
- do not build against internal admin moderation panels
- handle delayed availability after upload
Common moderation-related symptoms
Examples:
- product exists, but media is not yet purchasable
- preview exists, but content is still under review
- consent is accepted, but moderation is still blocking purchase
- a video item is waiting on manual approval instead of automatic approval