Safety & compliance
Acceptable Use Policy
AiPixel standards for safe AI-generated content, moderation, reporting, and enforcement.
Last updated: August 18, 2026
1. Scope
This Acceptable Use Policy ("Policy") applies to all prompts, reference images, generated images, edited images, and related content submitted, generated, stored, or shared through AiPixel. It applies to every user and supplements our Terms of Service.
2. Prohibited Content Categories
AiPixel prohibits using the service to generate, edit, upload, store, or distribute the following categories. The prohibition applies whether the content is photorealistic, illustrated, fictional, or created through an attempt to bypass safety controls.
- Pornography / NSFW content: sexually explicit, pornographic, or erotic sexual content, including sexualized nudity intended for arousal.
- Violence / gore: graphic violence, gore, mutilation, torture, gratuitous injury, or content that glorifies or facilitates violent harm.
- Hate speech: content that attacks, dehumanizes, threatens, or promotes discrimination or violence against people based on protected characteristics.
- Child-unsafe content: any sexual or exploitative content involving a minor, child sexual abuse material (CSAM), sexualization of minors, or content that otherwise endangers children.
- Deepfakes / impersonation of real people: deceptive or non-consensual synthetic media that impersonates a real person, including non-consensual intimate imagery.
- Copyright / trademark infringement: content that unlawfully copies, reproduces, modifies, or distributes protected works, logos, brands, or marks, or falsely suggests endorsement or affiliation.
2.1 Zero-Tolerance Violations
We block and urgently investigate child sexual abuse material, sexual content involving minors, terrorism or extremist propaganda, instructions for weapons of mass destruction, incitement to genocide or ethnic hatred, and non-consensual sexual deepfakes. Where required or appropriate, we preserve relevant records and report suspected criminal content to competent authorities.
2.2 Other Prohibited Conduct
- Impersonating a real individual, company, or public institution for deception; spreading fraud, scams, or materially deceptive misinformation; bulk spam; privacy or publicity-rights violations; and prompts intended to jailbreak or bypass AiPixel safety measures.
3. Content Moderation
AiPixel uses a layered moderation process. Prompts and reference-image requests are checked before being sent for generation, and provider safety responses are checked before output is delivered or retained as a completed creation. Requests or outputs identified as violating may be blocked, marked failed, and withheld from the user.
- Automated review uses keyword, semantic, intent, and image-safety signals, plus anomaly and abuse-pattern detection. The upstream image-generation provider also performs safety screening and may return a violation status.
- Human review is used for user reports, escalated automated flags, appeals, and high-severity cases. Reviewers assess context and may request additional information.
- We periodically review moderation outcomes and reported content to improve filters, reduce false positives, and identify repeated abuse.
| Level | Examples | Default response |
|---|---|---|
| L1 Critical | Child safety, terrorism, WMD, non-consensual sexual deepfakes | Immediate block, account termination, and authority report where required |
| L2 High | Severe violence, hate, impersonation, or repeated infringement | Remove content and suspend account pending review |
| L3 Medium | Confirmed general policy violation | Remove content, warn, restrict features, or clear related credits |
| L4 Low | Minor or uncertain misuse | Warning, request to edit, or report-triggered review |
4. Reporting
Report content or behavior that violates this Policy, including child-safety concerns, terrorism, impersonation, or infringement of your rights. Reports are handled confidentially and reviewed objectively. Deliberately abusive or knowingly false reports may result in action against the reporter.
5. Reporting Channels
Email [email protected] with the subject "Content Report". Include the content URL or creation identifier, a description of the concern, and any relevant evidence. For urgent child-safety, terrorism, or imminent-harm reports, use the subject "URGENT SAFETY REPORT". This is the same support channel used for safety reports and is monitored during business days; critical reports are prioritized.
6. Response and Processing Timelines
We acknowledge reports when received and follow this workflow: intake, severity triage, automated and human review, decision, enforcement, and notification. If a case needs more time, we will explain the delay and provide an updated expectation where possible.
| Severity | Initial response | Target resolution |
|---|---|---|
| L1 Critical | Within 2 hours | Within 24 hours |
| L2 High | Within 24 hours | Within 3 business days |
| L3 Medium | Within 3 business days | Within 7 business days |
| L4 Low | Within 5 business days | Within 15 business days |
7. Enforcement Actions
Depending on severity, intent, prior history, and legal obligations, we may take one or more of the following actions: remove or prevent access to content; issue a warning; restrict generation or other features; suspend an account; permanently terminate an account; clear or withhold credits used for violating activity; preserve evidence; and report criminal conduct or cooperate with lawful investigations. We may act immediately without prior notice for critical or urgent risks.
8. Appeals
You may appeal an enforcement decision within 10 days of notice by emailing [email protected] with the subject "AUP Appeal". Provide the account email, decision date, and relevant context. An appeal is reviewed within 10 business days by a reviewer who was not responsible for the original decision. An appeal does not restore content or access while a safety investigation is ongoing.
9. Updates and Contact
We may update this Policy as our service, safety practices, or legal obligations change. The current version is always published at /acceptable-use. Questions, safety reports, and appeals can be sent to [email protected].