> ## Documentation Index
> Fetch the complete documentation index at: https://docs.waffo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AIGC Compliance

> Review requirements for AI image / video generation products — branding, model disclosure, content moderation, and content policy

If your product lets users generate images or videos from text prompts, account review checks it against every requirement on this page, on top of the general [account review](/mor/account-reviews) checklist. Fix everything here before you submit — these items decide whether an AI generation product is approved.

<Note>
  This page applies to products with AI **image or video generation** capability. If your product builds on top of an AI model (an "AI wrapper"), these requirements are how review distinguishes a legitimate product from a repackaged model.
</Note>

## What review checks

<CardGroup cols={2}>
  <Card title="Independent branding" icon="tag">
    **Required:** your own product name and identity. **Not allowed:** marketing yourself *as* an AI model brand (e.g., "the official GPT app") or using a model's name/logo as your own.
  </Card>

  <Card title="Honest marketing" icon="bullhorn">
    **Required:** describe what your product actually does. **Not allowed:** overstating capabilities, implying endorsement by a model provider, or hiding that output is AI-generated.
  </Card>

  <Card title="Moderation in place" icon="shield-check">
    **Required:** run a content-moderation step on prompts and outputs — your own, or [Prompt Sift](#moderation-api). **Not allowed:** shipping an unmoderated raw-model passthrough.
  </Card>

  <Card title="Published content policy" icon="file-shield">
    **Required:** a public AUP covering prohibited content, reporting, and enforcement — use the [AUP template](/mor/account-reviews/aup). **Not allowed:** no policy, or one that doesn't match your actual product.
  </Card>
</CardGroup>

<h2 id="model-disclosure">
  Underlying model disclosure
</h2>

You must clearly disclose the underlying AI models your platform actually uses. Either form of disclosure is accepted:

* **Document-based**: list the model names on your About, Pricing, or Terms page, or on a dedicated page;
* **Interface-based**: in the image/video generation UI, users can directly see and select different underlying models (e.g., a dropdown, model switcher, or model cards), with each option clearly labeled with the model name.

The disclosure must meet all of the following:

* Model names are **real and specific** — vague phrasing such as "AI technology," "advanced models," or "30+ models" is not acceptable;
* The models used are **industry-mainstream** (e.g., Flux, Seedream, Nano Banana/Gemini, GPT Image, Veo, Kling, Seedance, Wan);
* **No repackaging or misrepresentation**: no free-riding on official brands, no inflated version numbers, no models of unknown origin without safety guardrails;
* If multiple models are offered, **every selectable model must meet the requirements above**, and switching models must not bypass content-safety filtering.

<Note>
  Truthful model disclosure does not conflict with the independent-branding requirement: listing "images/videos on this product are generated with Flux and Kling" in your docs or UI is compliant disclosure; marketing yourself *as* the model's brand (e.g., "the official GPT app") is the violation.
</Note>

<h2 id="moderation-api">
  Content moderation API — Waffo Prompt Sift
</h2>

A platform-side moderation step is a hard requirement (see [content policy requirements](#content-policy-requirements) below). You can build your own, or integrate **Prompt Sift**, Waffo's content-safety check for AI generation.

<h3 id="moderation-setup">
  How to set up moderation
</h3>

**1. Deploy scanning at more than one stage.**

* **Before generation** — scan user prompts in real time (Prompt Sift covers this stage).
* **After generation, before display** — scan the AI output before showing it to the user.
* **After publication** — if your product has a public gallery or feed, scan published images/videos asynchronously.

Cover at least the first two; add the third whenever user works are publicly visible.

**2. Maintain an actively updated blocklist of prohibited terms and prompts.**
It should cover at minimum: pornography/NSFW terms; CSAM-related vocabulary; copyrighted characters, brands, and trademark names; violence, hate speech, and self-harm; deepfake / celebrity / political-figure terms. "Actively updated" is part of the requirement — a static list shipped once doesn't count.

**3. Keep moderation logs.**
Retain both the AI moderation model's outputs and human-review decisions. Review may ask you to produce them.

### What Prompt Sift is

Before you hand a user's text prompt to your generation model, send it to Waffo for a safety check. Prompt Sift primarily intercepts requests involving child-unsafe content — standard practice across the industry (OpenAI, Google, Civitai, and other major AI generation platforms run equivalent checks). It protects your users and your product, and helps you meet the compliance requirements on this page.

### How it works

<Steps>
  <Step title="Your user enters a generation prompt">
    Any text description the user submits for image or video generation.
  </Step>

  <Step title="Your product calls Prompt Sift before generating">
    Send the prompt to the check endpoint at `https://api.waffo.ai/v1/actions/verification/scan-prompt`.
  </Step>

  <Step title="Act on the verdict">
    * **Pass** → call your generation model as normal; the flow is unaffected.
    * **Block** → don't generate; show the user a friendly message (e.g., "This content doesn't meet our usage guidelines").
    * **Pending review** → hold briefly (usually resolved within 1 hour); our human review team makes the final call.
  </Step>
</Steps>

### What you get

A simple API: pass us the user's text prompt, and we return a clear verdict — with minimal impact on your product flow.

<Card title="Content safety API reference" icon="shield-check" href="/api-reference/endpoints/content-safety/scan-prompt">
  Endpoint reference, request/response format, and integration examples.
</Card>

Prefer an SDK? The official Waffo SDKs (TypeScript / Go) expose this as `client.contentSafety.scanPrompt(...)` — the fastest way to integrate.

<Card title="SDK integration guide" icon="cube" href="/integrate/sdks">
  Install and authenticate the TypeScript or Go SDK, then call content safety with a single method.
</Card>

<Tip>
  If users type a text prompt and your product generates an image or video from it, review expects a moderation step on that prompt — integrating Prompt Sift is the fastest way to have one.
</Tip>

<h2 id="content-policy-requirements">
  Content policy requirements
</h2>

You must publish a **standalone AUP page**, or a **dedicated chapter** in your Terms of Service, covering all of the following.

**Six prohibited-generation categories (listed one by one — no vague catch-alls):**

* Pornography / NSFW
* Violence / gore
* Hate speech
* Child-unsafe content (CSAM)
* Deepfakes / impersonation
* Copyright / trademark infringement

**Supporting mechanisms:**

* **Enforcement actions** — account bans, credit forfeiture, content removal, etc.
* **A user reporting channel** — users can report violating generated content, and you describe how reports are handled.
* **A description of platform-side content moderation** — your moderation workflow (automated filtering, human review, etc.).

<Card title="AUP template" icon="file-shield" href="/mor/account-reviews/aup">
  A complete Acceptable Use Policy covering everything above — the six prohibited categories listed one by one, plus enforcement, reporting, and moderation sections. Replace the placeholders and publish.
</Card>

<h2 id="checklist">
  Before you request review
</h2>

🔴 items decide whether an AI generation product is approved. 🟡 items strengthen the case.

<Steps>
  <Step title="🔴 Must be done">
    * Product uses **independent branding** — not an AI model's name or logo as your own
    * Marketing is accurate — no overstated capabilities, no implied provider endorsement
    * **Underlying models are disclosed** truthfully and specifically, and are industry-mainstream ([model disclosure](#model-disclosure))
    * A **moderation step runs on prompts and outputs** — your own, or [Prompt Sift](#moderation-api)
    * A public **AUP page or ToS chapter** lists the six prohibited categories one by one ([content policy](#content-policy-requirements))
    * At least one real, monitored **user reporting channel** exists
    * Enforcement actions in your policy are ones you can actually carry out
  </Step>

  <Step title="🟡 Strongly recommended">
    * Output is labeled or otherwise disclosed as AI-generated
    * An appeals path exists for wrongly-actioned users
    * Age verification in place if you allow any restricted content
  </Step>
</Steps>