Acceptable use policy.
Do not use Erebine to break the law, harm people, or push abuse through our systems. These rules are part of the Terms and apply to you and to anyone you build for.
// 01
Absolutely prohibited
- Child sexual abuse material (CSAM), whether real or AI-generated, and any sexualization or grooming of minors. We report CSAM to NCMEC and terminate the account. Zero tolerance.
- Non-consensual intimate imagery, including AI-generated forgeries.
- Content that is illegal to create or distribute, or that facilitates clear illegality: trafficking, terrorism, fraud, or weapons and CBRN procurement.
// 02
Not allowed
- Infringing intellectual-property, privacy, or publicity rights.
- Malware, spam, phishing, or credential harvesting.
- Harassment, threats, doxxing, or incitement to violence or self-harm.
- Probing, scanning, or fuzzing the router or workers outside documented endpoints; bypassing quotas, rate limits, isolation boundaries, or worker leases.
- Misrepresenting AI output as human-generated where that deceives or harms.
- Emotion recognition: identifying or inferring a person's emotions from images, video, audio, or transcripts of them. The rule covers every endpoint and every EIM image, including image, video, and audio input, batch transcription, and realtime voice.
- Voice cloning for others: offering a text-to-speech application that produces synthetic speech resembling an input voice as a service to third parties, or shipping one in your own product. Building one for your own use is allowed, and everything you feed it, the input voice included, has to be content you hold the rights to.
// 03
Models and uploads
- You must hold the rights to any model, adapter, dataset, or file you upload.
- You may not upload weights or data whose export or use is restricted by US law.
- We may scan, quarantine, or remove uploads to enforce this policy or the law.
// 04
GPU EIM images
The GPU container images of the Erebine Inference Microservice (EIM) carry vendor software under the vendors' own terms. Those terms restrict use, not only redistribution. They govern the vendor components in an image, not the Erebine layer, and this policy holds you to them whether you use the hosted service or pull an image yourself. /docs/license names them and says where each license text sits inside the image.
On the NVIDIA (CUDA) EIM images, each NVIDIA component comes under its own NVIDIA agreement: the CUDA Toolkit End User License Agreement for the CUDA runtime and the other CUDA Toolkit libraries; the License Agreement for NVIDIA Software Development Kits, with a supplement for each, for cuDNN, cuSPARSELt, and NVSHMEM; and, in eim-vllm-cuda and eim-vllm-omni-cuda, the NVIDIA Software License Agreement for the CUTLASS DSLs. The copy inside the image is the text that shipped with the component, and the text at each link can be a later revision; where the two differ, this page says so. Between them, these agreements prohibit:
- Using the NVIDIA components outside systems with NVIDIA GPUs. Each agreement licenses its component for applications "only for use in systems with NVIDIA GPUs".
- Reverse engineering, decompiling, or disassembling them, and removing their copyright or other proprietary notices.
- Copying, distributing, modifying, or creating derivative works of them, except as the agreements expressly allow.
- Bypassing, disabling, or circumventing any encryption, security, digital rights management, or authentication mechanism in them.
- Using them in a way that would make them subject to an open-source license.
- Indicating that a product you built with them is sponsored or endorsed by NVIDIA. The CUDA Toolkit EULA and the SDK agreements allow it under an agreement with NVIDIA for that purpose.
- Using them, without an agreement with NVIDIA for that purpose, in any system or application whose use or failure can reasonably be expected to threaten or result in personal injury, death, or catastrophic loss. The cuSPARSELt and NVSHMEM agreements say so and give avionics, navigation, military, medical, and life support as examples. The current published CUDA Toolkit EULA and cuDNN agreement instead say that NVIDIA does not test or certify the software for such uses, and the CUTLASS DSL agreement that NVIDIA does not design or test it for them; all three make meeting the applicable legal and regulatory standards your responsibility. Earlier revisions of the CUDA Toolkit EULA and the cuDNN agreement carry the cuSPARSELt prohibition, so read the copy in your image.
- In
eim-vllm-cudaandeim-vllm-omni-cuda, the CUTLASS DSL agreement also prohibits replacing an NVIDIA component it governs with other software that implements NVIDIA APIs, and reverse engineering output generated with the software to translate it to a non-NVIDIA platform.
Benchmarks. None of these agreements has a term on publishing benchmark, regression, or performance results, or competitive analysis. This policy reads no permission into that silence. Read the agreements before you publish; NVIDIA directs questions about the CUDA Toolkit EULA and the SDK agreements to nvidia-compute-license-questions@nvidia.com.
The AMD (ROCm) EIM images carry no vendor use restriction of that kind. AMD licenses ROCm per component, under MIT, Apache-2.0, NCSA, and BSD licenses, and what those ask of you is notice: keep the copyright and license text with any copy you pass on. The two ROCm packages AMD ships in binary form under the AMD Software End User License Agreement, ROCprof Trace Decoder and AOCC, are not in the images.
These restrictions pass through. If you give anyone else access to an image, or to a product or service built on one, you have to bind them to terms at least as protective first. Section 18 of the Terms sets that out.
// 05
If you build for others
If you expose the service to your own users through your endpoints:
- You are responsible for your end users' use of the service.
- You must pass through equivalent acceptable-use restrictions to your users and moderate their use. We provide hooks to help.
// 06
Enforcement
We may investigate suspected violations and may throttle, suspend, or terminate accounts. Confirmed CSAM or sanctioned-party use results in immediate termination and, where required, a report to authorities. Appeals: contact@erebine.ai.
// 07
Reporting
- Report content or abuse: contact@erebine.ai or the in-product report control.
- Copyright: /dmca.
- Non-consensual intimate imagery: the removal request form, or contact@erebine.ai. A valid request carries your full name as a signature, the item id or a link to the content with a description of it, a good-faith statement that it is not consensual, and an email address you confirm; we remove the image within 48 hours of that confirmation.