Skip to content

3-day free trial on the Starter plan. Cancel anytime before billing begins.

See plans
Desktop betaSign inCreate account

Privacy

Explain clearly what stays local, what reaches ClastX, and what leaves the product.

A developer should not have to guess how project context, billing data, support requests, and AI prompts move through the product.

What may stay local

  • Desktop-only project access, local files, and command activity should stay in the installed workspace unless the product explicitly sends something out.
  • Local UI state and on-device workflow context may remain on the customer machine depending on the feature.

What the ClastX server may receive

  • Account identity, billing state, selected model, and the workspace request data needed to power the product.
  • Usage, billing, and support information needed to enforce limits, answer support issues, and keep the service functioning.

What may go to AI or infrastructure providers

  • The prompt, relevant conversation history, selected model, and the working context needed to answer the current request.
  • Only the data required to complete the requested product action should be shared downstream.

Billing and support information

  • Payment providers may receive the data required to process subscriptions, renewals, cancellations, invoices, and top-ups.
  • Support contact details and support request content may be used to respond to product, billing, or account issues.

What is still evolving

  • Multi-user collaboration, broader hosted storage, and other future account features may change what the service stores over time.
  • This page should be updated as the live commercial stack becomes more complete.