Beta Program Terms

These Terms govern participation in the Auric private beta. They incorporate and supplement the Terms of Service; where they conflict on beta-specific matters, these Terms control. Capitalized terms follow Auric's Master Definitions in the Terms of Service.

Access is by invitation, may be limited, and may be revoked or expire at any time; invites can lapse, and an expired invite can no longer authenticate. There is no entitlement to continued access.

Founding positions are assigned automatically, in the order beta access is granted, until the founding cohort is full. Being on the waitlist, confirming your email, or waiting for an access wave does not by itself make you a Founding Member. The fee exemption attached to a founding position is set out in Section 9 of the Terms of Service.

You acknowledge that:

• the Services are pre-release and may contain defects;
• features may change, be added, or be removed without notice;
• breaking changes and data loss are possible;
• there is no uptime, availability, SLA, or support guarantee;
• the Services are not suitable for production, regulated, or safety-critical use; and
• recovery of lost data is not guaranteed — keep your own backups (your Project Data is local; back it up).

You may send us feedback. It is governed by the feedback terms in the Terms of Service, which apply here in full.

The beta may expose Confidential Information — unreleased features, roadmap, performance, and invite mechanics. Do not disclose it publicly or share screenshots of unreleased functionality without asking us first.

Data handling follows the Privacy Policy. Experimental features may collect additional diagnostics; where this is material, we disclose it in-product. Beta data may be reset between phases.

We may modify, suspend, or discontinue the beta, in whole or in part, at any time. On termination, your access ends; local data remains yours on your device.

The disclaimers and liability limits in the Terms of Service apply to the beta in full.

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.

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.