Back to home

Acceptable Use Policy

What you may not do with the Service, and how we respond when it happens.

Last updated: 31 October 2026

1. Scope

This policy applies to everyone who uses the Service, including through an API key. It supplements the Terms of Service. If you are unsure whether a use is permitted, ask support@maxonforge.com before you build on it.

2. Prohibited conduct

You must not use the Service to:

  • break any law, or infringe anyone’s rights, including intellectual property and privacy rights;
  • generate or distribute material that sexualises minors, incites violence, or harasses or threatens a person or group;
  • produce content intended to deceive at scale — including impersonation, fraudulent offers, or undisclosed synthetic media used to mislead;
  • build malware, conduct unauthorised intrusion, or attack systems and networks, including ours and other customers’;
  • evade rate limits, quotas or billing — including by creating multiple accounts to obtain repeated signup credit, or by rotating keys to defeat limits;
  • share, publish, or resell API keys, or make an account available to unrelated third parties as a credential;
  • attempt to extract provider credentials, model weights, or other customers’ data, or probe the Service for vulnerabilities without written permission;
  • send other people’s personal data to a model without a lawful basis to do so; or
  • misrepresent your identity or affiliation in a way that causes harm.

3. Provider terms also apply

Each request is served by a third-party model provider. That provider’s acceptable-use rules apply to your request in addition to ours. Using the Service does not exempt you from them, and a provider may itself block content or an account.

4. Your security obligations

  • Keep API keys secret and store them in a secret manager, not in client-side or public code.
  • Revoke any key you believe has been exposed, and tell us if you see unexpected usage.
  • Do not disable, bypass or interfere with the Service’s rate limiting or authentication.
  • Do not use one account as a shared credential pool for unrelated people.

5. How we enforce this policy

Depending on severity, we may rate-limit, suspend usage, revoke API keys, suspend or close an account, or withhold a signup credit where it is being farmed. Enforcement decisions that affect an account are recorded in an audit trail.

We do not automatically moderate the content of your prompts: requests are routed to the provider. That means enforcement is generally triggered by observed behaviour — abuse signals, reports, billing anomalies, or provider notices — rather than by reading your prompts.

Where the law requires it, or where there is an imminent risk of harm, we may act immediately and explain afterwards.

6. Reporting abuse

Report abuse or a security issue to support@maxonforge.com. Include what you observed and how to reproduce it. Please do not test a suspected vulnerability against other customers’ accounts or data, and give us reasonable time to fix an issue before disclosing it publicly.

7. Appeals

If you believe an enforcement action was mistaken, reply to the notice or contact support. We will review the evidence and tell you the outcome. We may not be able to share details that would expose another customer’s data or our security controls.