AI Usage Policy
Effective 18 September 2026 · Auric 1.3.0
In plain English: Auric is not an AI model. The Auric engine on your computer makes one optional AI request: if you set your own ANTHROPIC_API_KEY, ending a session with end_session sends that session's recorded state, active decisions and open loops to Anthropic to summarise it, under your Anthropic account and terms. Without a key, nothing is sent and Auric writes a plain summary instead. Your AI coding tools talk to their own providers; Auric is not in that path. AI output can be wrong; you are responsible for checking it.
1. Purpose and Scope
This Policy governs AI features across the Services. Auric orchestrates interactions; it does not train, host, or own the models. Capitalized terms follow Auric's Master Definitions in the Terms of Service.
2. How AI Works in Auric
- Explicit and opt-in: the only AI request Auric makes happens when an agent calls end_session and you have set ANTHROPIC_API_KEY. Nothing is sent on a schedule.
- Your own tools, your own provider: your AI coding tools talk to their providers directly; Auric is not in that path.
- What reaches Auric's servers: for account-based services, limited account, waitlist and workspace metadata (name, slug, repository name and remote URL) — never file contents.
- What is not sent to Auric: your Project Data and Operational State stay on your device; Auric does not upload them to its servers.
3. Provider Terms Govern
Once content reaches a provider, that provider's terms, privacy policy, retention, and any model-training practices apply. Review them. Auric cannot retrieve or delete content held by a provider.
4. Accuracy, Reliability, and Responsibility
Generated Output may be inaccurate, incomplete, biased, or unsafe. You must review and validate it before use — especially for code that is executed, deployed, or relied upon. Auric makes no representation about AI correctness or fitness.
5. Ownership of Output
Ownership and permitted use of Generated Output are determined by the applicable provider's terms and by law. Auric claims no ownership of your prompts or outputs.
6. Acceptable AI Use
You must not use connected AI to produce unlawful, infringing, harmful, or provider-prohibited content, or to evade provider or Auric controls. See the Acceptable Use Policy.
7. Local Models
If you work against a local model, nothing leaves your device on that path either; you remain responsible for that model's licensing and behaviour.
8. Changes and Contact
If these terms change materially we will update the effective date on this page and, where the change affects you meaningfully, tell you by email before it takes effect. Contact: hello@auric.cx.
Document control
| Field | Value |
|---|---|
| Document ID | AUR-LEG-005 |
| Applies to | Auric 1.3.0 — private beta |
| Status | Published — private beta |
| Owner | Auric |
| Review frequency | Quarterly during beta, or on material change |
| Related documents | Terms (001), Privacy (002), Acceptable Use (004) |
| Applies to | Auric 1.3.0 — private beta |
Change log
18 September 2026: Published with Auric 1.3.0. The local beta needs no web account or workspace registration; account terms apply only to authenticated services where used, and founding positions are recorded against the registered beta email address. The AI Usage and Privacy policies now describe the engine's one optional AI request, and the Privacy and Security policies describe its requests to auric.cx.
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.