ClavueClavue
CLI · TUI · models

Privacy Policy

Last updated: August 5, 2026

This policy explains how Clavue / imux products operated by Kunshan Xingwang Mathematical Network Technology Co., Ltd. collect, use, store, and protect your information. It covers websites, APIs, mobile apps, and desktop clients. By using the Service you acknowledge this policy.

Covered products & dedicated URLs

Following common practice (Cursor / Warp / Claude): one master policy plus stable per-product URLs for App Store, Play Console, and installers. Product pages add surface-specific detail; this master policy controls.

Short alias: https://www.clavue.com/privacy/privacy-policy

1. Information we collect

Account information

  • Sign-up / sign-in: email, phone, display name, password hash, or third-party login identifiers (e.g. Google).
  • Membership and usage: plan, quota consumption, orders and payment provider receipts (no full card numbers).

Content and generation data

  • Chats and prompts: processed to generate responses; may be retained for cross-device history when enabled.
  • Image generation: prompts, outputs, timestamps, account identifiers and content hashes for safety, abuse prevention, and provenance (see Image provenance).
  • Desktop / phone remote: terminal injects, tool calls, and device-pairing metadata you initiate.

Device and technical data

  • IP address, user agent, app version, crash diagnostics, API request IDs.
  • Mobile update checks fetch latest-mobile.json / latest-imux-mobile.json (version metadata only, not chat content).
  • Desktop update checks hit appcast / latest.json (including the Windows windows_beta segment).

2. How we use information

  • Provide, maintain, and improve the Service and membership features.
  • Authentication, abuse prevention, quota metering, and payments.
  • Content safety review (including image prompt policy blocks).
  • Comply with law and respond to lawful requests.
  • Product analytics and notifications where consented or permitted by law.

3. Image provenance & compliance

To follow industry best practice (inspired by content-safety and content-credentials approaches), we:

  • Screen prompts before generation/edit and block categories such as sexual content, sensitive political content, CSAM, extreme violence, and non-consensual intimate imagery.
  • Bind generation records to the membership account, storing prompt hash, content SHA-256, request id, time, and policy version.
  • Embed non-visual PNG tEXt metadata (ClavueImageId / ClavueUserId / ClavueContentSha256, etc.) for forensics without changing visible pixels.
  • Operators may query provenance in the admin console by image id, user, hash, etc. (admin-token protected).

4. Sharing and disclosure

To generate outputs, prompts and necessary context are sent to configured upstream inference providers. We do not sell personal data to advertisers. We may disclose information to service providers (payments, email, infrastructure), for legal process, to protect users and the platform, or with your consent.

5. Storage and transfers

Data is stored on infrastructure we operate and necessary cloud providers. Where cross-border processing occurs, we take reasonable measures for comparable protection.

6. Retention and deletion

We retain data as needed while your account is active. You may request account deletion in settings; records required by law or for safety/provenance audits may be retained for the required period.

7. Your rights

Where applicable law provides, you may request access, correction, deletion, or export of personal data, or withdraw consent. Contact support@clavue.com.

8. Children

The Service is not directed to children under 13 (or a higher age where required). We will delete accounts if we learn they belong to children.

9. Local-first note (desktop / remote)

imux desktop and host agents process terminals, files, and tool approvals locally by default. Source trees and scrollback are not uploaded for advertising. Cloud membership, phone-link, or agent sends you initiate are covered in the product pages.

10. Changes

We may update this policy; material changes will be posted on the site or in-product. Continued use means acceptance of the updated policy.

11. Related terms

Contact: support@clavue.com