Acceptable Use Policy
Effective 2 September 2026 · Auric 1.3.0-beta.1
In plain English: use Auric lawfully and don't abuse it or the AI providers it connects to. No illegal content, no attacking our systems, no using AI for prohibited purposes, and no circumventing the invite gate or rate limits.
1. Purpose and Scope
This Policy applies to all users of the Services. Violations may lead to suspension or termination under the Terms of Service. Capitalized terms follow Auric's Master Definitions in the Terms of Service.
2. Prohibited Conduct
You must not:
- break the law or infringe others' rights;
- upload or generate unlawful, harmful, or infringing content;
- attack, probe, overload, or reverse-engineer the Services, except as permitted by the Responsible Disclosure Policy;
- circumvent authentication, the invite gate, rate limits, Turnstile, or other controls;
- access accounts or data that are not yours;
- resell or misrepresent the Services;
- use automated abuse such as spam, credential stuffing, or scraping beyond permitted use;
- submit others' personal or sensitive data without a lawful basis; or
- use the beta for production or safety-critical systems.
3. AI-Specific Use
Your use of connected AI Providers must comply with the AI Usage Policy and with each provider's own usage policies. You are responsible for the prompts you send and for how you use Generated Output.
4. Enforcement
We may investigate, remove access, suspend or terminate, and report unlawful activity, with or without notice where risk or law requires.
5. Reporting
Report abuse or security issues to security@auric.cx. See the Responsible Disclosure Policy for security reports.
Document control
| Field | Value |
|---|---|
| Document ID | AUR-LEG-004 |
| Applies to | Auric 1.3.0-beta.1 — private beta |
| Status | Published — private beta |
| Owner | Auric |
| Review frequency | Quarterly during beta, or on material change |
| Related documents | Terms (001), AI Usage (005), Responsible Disclosure (007), Beta (008) |
| Applies to | Auric 1.3.0-beta.1 — private beta |
Change log
2 September 2026: The beta is described as private throughout, which is how access is actually granted — requested, confirmed, then opened in waves. No right, obligation, party or data practice changed.
1.3.0-beta.1 (2026-08-02): Published for the private beta. Review markers resolved against the implementation, unsupported AI-provider claims removed, and retention stated from the constants that enforce it.
© 2026 Auric. All rights reserved.