Skip to content
Sovereign route — served only inside the KingdomInternational route — frontier models, served abroad

Legal

Acceptable use policy

Last updated

What you may not do with the Sigmix API, and what happens if you do it anyway.

This build carries draft wording. Every section marked as a placeholder must be settled with Saudi counsel before launch.

01Scope

This policy applies to everyone who uses the Sigmix API or console, including people you give access to and any system you build on top of us.

It sits alongside the laws of the Kingdom of Saudi Arabia and the licence terms of the model providers. Where they are stricter than this policy, they win.

02Content you must not generate or process

  • Material that sexually exploits or endangers children, in any form.
  • Content that incites violence, terrorism, or hatred against a person or group.
  • Content that violates the values, public order or laws of the Kingdom of Saudi Arabia.
  • Non-consensual intimate imagery, or content that impersonates a real person in order to deceive.
  • Malware, exploit code, phishing pages, or instructions written to help someone break into a system they do not own.
  • Instructions for producing weapons, explosives, or chemical, biological, radiological or nuclear materials.

03Uses that are not permitted

  • Presenting model output as human-authored where a person would reasonably need to know it was not.
  • Deciding, without a person reviewing it, anything that materially affects an individual — credit, employment, housing, insurance, education or access to a public service.
  • Medical, legal or financial advice given to an end user as though it were professional advice.
  • Surveillance of individuals, biometric identification, or emotion inference in a workplace or an educational setting.
  • Building a profile of a person from data they did not knowingly provide.
  • Political messaging that conceals who paid for it.

04Technical conduct

  • Do not attempt to bypass rate limits, quotas, spend caps, or the routing constraints on your keys.
  • Do not probe, scan or stress the service other than against your own account, and tell us before you do that.
  • Do not resell raw API access, or route another organisation traffic through your keys, without a written reseller agreement.
  • Do not use output to train a competing model where the provider licence forbids it.
  • Do not share a key across organisations, or embed one in client-side code.

05Fair use and capacity

Capacity in the Kingdom is finite and shared. Sustained traffic far above your agreed pattern can degrade the service for everyone.

If you are planning a large batch or a launch, tell us in advance and we will provision for it. Unannounced load may be throttled.

06Data you send

Send only data you are lawfully entitled to send, and only to a key whose data classification matches it.

If you intend to send health, financial, biometric, credit or children data, tell us before you begin so the right controls and the right agreement are in place.

07Reporting abuse

If you see the service being used against this policy, or you find a security weakness, report it to us rather than exercising it. We will not pursue a good-faith report that stops at the point of proof.

08Enforcement

We may throttle, suspend or revoke a key or an account that breaches this policy. Where the breach is serious or ongoing, we act first and explain afterwards.

Where the law requires it, we report the matter to the competent authority.

A suspension can be reviewed by a person. Write to us and we will look at it.