Acceptable Use Policy

Effective and last updated: August 14, 2026.

This Acceptable Use Policy ("AUP") applies to all use of Aivrae, including accounts, API keys, API requests, prompts, files, Outputs, prepaid credits, model integrations, and applications built on the Service. It forms part of the Terms of Service.

1. General rule

You may use Aivrae only for lawful, authorized, and responsible purposes. You are responsible for your Inputs, Outputs, applications, end users, and compliance with applicable law and third-party model-provider rules.

You must not use Aivrae to create, request, facilitate, distribute, or conceal prohibited content or activity, even if a selected model is technically capable of producing it.

2. Prohibited activity

2.1 Illegal activity, fraud, and deception

You may not use the Service for fraud, scams, phishing, identity theft, forged documents, deceptive commercial practices, evasion of law enforcement, sanctions violations, or other unlawful conduct.

2.2 Child-unsafe content

Any sexual, exploitative, abusive, grooming, or otherwise unsafe content involving minors is prohibited. This includes real, fictional, illustrated, synthetic, or AI-generated child sexual abuse material and attempts to sexualize a person who is or appears to be a minor.

2.3 Pornography and NSFW content

Pornographic, sexually explicit, non-consensual intimate, fetish, sexual-service, or other NSFW generation is prohibited. You may not attempt to bypass safety systems using coded language, prompt obfuscation, image transformations, or model switching.

2.4 Violence, gore, self-harm, and dangerous conduct

You may not generate or facilitate graphic gore, instructions to commit serious violence, credible threats, targeted harassment, encouragement of self-harm, weapons construction, or other content likely to cause physical harm.

2.5 Hate and harassment

You may not promote hatred, dehumanization, discrimination, or violence against protected groups, or use the Service for stalking, doxxing, bullying, or targeted harassment.

2.6 Deepfakes and impersonation

You may not create deceptive deepfakes, face swaps, voice clones, forged evidence, or impersonations intended to mislead others about a person's identity, actions, endorsement, or authorship. Non-deceptive parody or authorized creative use must be clearly disclosed and must comply with applicable law and provider rules.

2.7 Intellectual property and privacy violations

You may not infringe copyright, trademark, publicity, privacy, database, trade-secret, or other third-party rights. You must have permission to upload or transform protected material and may not use Outputs to pass off another person's work, brand, or identity as your own.

2.8 Malware, security abuse, and unauthorized access

You may not create or distribute malware, ransomware, credential-stealing tools, exploit code intended for unauthorized use, spam, denial-of-service traffic, botnet activity, or instructions primarily designed to compromise systems. Security testing is permitted only with clear authorization and within the authorized scope.

2.9 High-impact and professional decisions

You may not use unverified AI Outputs as the sole basis for decisions that determine another person's eligibility for employment, housing, credit, insurance, education, healthcare, legal services, or other high-impact opportunities. You may not represent AI Outputs as advice from a licensed professional when they are not.

2.10 Platform abuse and safety circumvention

You may not:

  • evade rate limits, billing, quotas, account restrictions, or model safeguards;
  • probe for or expose credentials, private system prompts, routing secrets, or personal information;
  • create accounts or rotate keys to avoid enforcement;
  • resell account access or API credentials without written authorization;
  • interfere with monitoring, moderation, logging, or fraud controls; or
  • submit automated traffic that materially degrades the Service for others.

3. AI image and video safety

For image and video generation, Aivrae applies or relies on layered safety measures, which may include:

  • automated prompt screening before a request is routed;
  • upstream model-provider safety controls;
  • automated output checks before or during delivery;
  • human review of flagged cases or user reports; and
  • preservation of limited moderation and enforcement records.

Generated media must not be presented deceptively as authentic evidence or as human-created work where that misrepresentation could cause harm. Applications that publish generated media should provide an appropriate AI-generated-content disclosure.

No moderation system is perfect. Passing an automated check does not mean content is lawful or permitted under this AUP.

4. Enforcement

When we reasonably believe this AUP has been violated, we may:

  • block, delay, or refuse a request or Output;
  • remove or disable access to task results;
  • rate-limit, rotate, or revoke API keys;
  • restrict, suspend, or terminate an account;
  • freeze credits or payments while fraud or abuse is investigated;
  • preserve relevant records and notify an upstream or payment provider; or
  • report conduct to authorities when required by law or reasonably necessary to address imminent harm.

Serious or repeated intentional violations may result in forfeiture of remaining credits to the extent permitted by law and the Refund Policy.

We may use automated systems and human review to enforce this AUP. Enforcement decisions may consider content, context, account history, technical indicators, payment risk, and provider notices.

5. Reporting violations

Report suspected abuse to [email protected]. Include relevant request IDs, account or application details, URLs, screenshots, transaction references, and a description of the concern where available. Do not email illegal content or exposed credentials; provide a safe reference instead.

We will review credible reports and may request additional information. We may not disclose investigation details or actions when doing so would affect privacy, security, legal obligations, or another investigation.

6. Appeals

If you believe a request or account was restricted in error, email [email protected] from the registered account email with the relevant request ID and an explanation. We may require identity or account-ownership verification before reviewing an appeal.

7. Changes

We may update this AUP to reflect changes in law, model-provider policies, safety risks, or Service capabilities. The current version and effective date will be published on this page.