Legal and compliance
Summary of legal docs and operational compliance for the Clavue platform and imux product. Formal pages control.
Formal documents
Data & membership
- Membership data (accounts, sessions, usage) lives under IMUX_MEMBERSHIP_STORAGE_DIR; Clavue session secrets are not shared with third-party model vendors as product keys.
- Chat content is forwarded through the membership gateway to upstream inference to produce replies; do not submit secrets or government IDs.
- Payments via Alipay / WeChat and similar; full card numbers are not stored in the client.
Security practices
- Transport: api.clavue.com / www use TLS (Let’s Encrypt).
- Content safety: membership chat gateway applies light high-confidence blocks (configurable; does not impede local toolchains).
- imux local: tool calls respect seatbelt / path policy and approvals, complementary to cloud text policy.
Acceptable use
Do not use the service for malware, unauthorized intrusion, CSAM, or clear violent-crime assistance. Accounts may be rate-limited or disabled.
Third-party components
imux integrates open-source components such as Ghostty/libghostty; see docs/third-party-compliance.md and product legal pages.
This page is a product docs summary, not legal advice. Contact support via the site for commercial or compliance inquiries.