Acceptable Use Policy
Last updated: April 30, 2026
S.A.M.I. is built for software work — designing, writing, reviewing, and shipping code. This page describes the things you may not do with S.A.M.I., regardless of plan. Violations may result in account suspension, content removal, and — for severe or repeated cases — termination and reporting to the relevant authorities.
Prohibited content
You may not use S.A.M.I. to generate, modify, or distribute:
- Child sexual abuse material (CSAM) or content that sexualises minors. Reports go directly to the appropriate hotline and law enforcement.
- Malware, ransomware, exploit kits, or attack toolkits intended to compromise systems you do not own or have written authorisation for.
- Deepfakes, voice clones, or fabricated media targeting real identifiable individuals without their explicit consent.
- Mass-scale spam, phishing, or harassment content — bulk email templates, comment-spam generators, mass-DM scripts, harassment kits.
- Content that incites violence or facilitates the manufacture of weapons designed to cause mass harm (biological, chemical, radiological, nuclear, or large-scale conventional).
- Disinformation or fraud targeting elections, public-health guidance, or financial markets.
- Content that infringes copyright, trademarks, or trade secrets belonging to a third party.
Prohibited behaviour
- Bypassing rate limits, quotas, or billing — sharing accounts, running automation that exceeds the limits of your plan, or chaining trial accounts.
- Reselling raw model access— wrapping S.A.M.I.'s output stream and exposing it as your own LLM API. Building a product that uses S.A.M.I. internally is fine; exposing the upstream provider as a pass-through is not.
- Reverse-engineering safety filters, scraping internal model identifiers, or attempting to extract training data from model providers.
- Probing the platform without authorisation — automated vulnerability scanning, attempting account takeover, or denial-of-service tests beyond a coordinated disclosure (see /security).
- Impersonating S.A.M.I. or its operator — using SAMI branding, logos, or domains in a way that misleads users about origin or affiliation.
Provider terms still apply
In addition to this policy, the upstream model provider you select carries its own usage terms. If a provider prohibits a use case (for example, certain medical or legal uses), that prohibition applies to your S.A.M.I. session as well. Violating the provider's terms is also a violation of this policy.
Enforcement
We respond to credible reports of violations. Depending on severity, the response ladder is:
- Warning + documented expectation that the behaviour stops.
- Temporary suspension of the offending session or model.
- Account suspension pending review.
- Permanent termination, billing refund of the unused term, and — where required — notification to law enforcement.
We log enforcement decisions internally and disclose the action taken in response to a valid legal order.
Reporting abuse
If you encounter content or behaviour that violates this policy, write to abuse@sami-agent.com. Include the time of the incident, the affected account or URL where possible, and a short description. We acknowledge reports within five business days.
Vulnerability reports go to security@sami-agent.com instead — see the Security page or /.well-known/security.txt.
Changes to this policy
We may update this policy as the product and the legal landscape change. Material changes are announced via the changelog and, for active Team / Enterprise customers, via email at least 14 days before they take effect.