Acceptable Use Policy
1. Prohibited content and conduct
You must not use ZGo to create, request, distribute or facilitate any of the following:
- Sexual or NSFW content: pornography, explicit sexual content, sexual services, or sexualized content involving any person.
- Violence or gore: graphic violence, torture, mutilation, threats of violence, or content that promotes or instructs serious harm.
- Hate speech: content that attacks, dehumanizes, or promotes hatred against people based on race, ethnicity, nationality, religion, disability, gender, sexual orientation, or other protected characteristic.
- Child-unsafe content / CSAM: any sexual content involving minors, child sexual abuse material, grooming, exploitation, or endangerment of a minor. This is an absolute prohibition.
- Deepfakes and impersonation: face swaps, nudify tools, non-consensual intimate imagery, or content that makes a real person appear to say or do something they did not say or do, whether or not the person consented.
- Copyright or trademark infringement: use of protected works, characters, logos, brands, or other intellectual property without authorization.
You must also not use ZGo for illegal goods or services, fraud, scams, malware, phishing, unauthorized access, privacy violations, harassment, self-harm promotion, or attempts to bypass safety controls, rate limits, authentication, billing, or geographic restrictions.
2. Our moderation process
- Input screening: before sending the latest user prompt to a model, we screen it with Waffo Prompt Sift and our own rules. Only an
allowdecision proceeds. Ablock,review, or unavailable moderation result stops the request. - Output review: model outputs are checked against our content rules and provider safety controls before or during delivery. Streaming output is filtered as it is produced; completed output is withheld where a violation is detected.
- Provider controls: upstream model providers may apply their own safety filters and may refuse or truncate a request.
- Logging: we retain moderation decisions, reason codes, categories, timestamps, and a one-way prompt hash. We do not intentionally store the full raw prompt in ordinary moderation logs.
3. Reporting
Report suspected violations to support@zgoapi.cc with the subject “Content Safety Report”. Include the account email or request ID, the relevant URL or model, and a short description. Do not send suspected CSAM or unnecessary intimate material by email; describe it and wait for instructions.
4. Enforcement
Depending on severity and recurrence, we may:
- refuse a request or withhold an output;
- issue a warning or require changes;
- suspend API keys or accounts;
- remove content or disable access;
- terminate the account and retain records where required by law.
We may act immediately where necessary to protect users, providers, the public, or the service. Credits associated with prohibited use may be forfeited where permitted by law and the Terms of Service.
5. Appeals
If you believe a moderation decision was wrong, email support@zgoapi.cc with the subject “Safety Appeal”, the request ID, and a brief explanation. We will review the available information and respond through the same channel.
6. Changes
We may update this AUP to reflect changes in law, provider requirements, or our service. The effective date will be updated. Continued use after the effective date means you accept the revised AUP.