PRIVACY

Local by default.

This technical-preview notice is not Chydio's final public legal policy. Chydio Forge keeps Unity operations, checkpoints, indexes, receipts, prompts, source, captures, and provider credentials on the user's machine by default. Selected context leaves the machine only when the user chooses an AI-provider operation. Chydio does not collect, proxy, or resell consumer-subscription tokens or API keys.

Chydio ID uses Firebase Authentication. Google or Apple supplies the identity information the user approves, and Firebase/Google processes phone numbers and verification traffic for authentication and abuse prevention. Chydio does not offer email/password accounts. Paid billing uses Stripe Managed Payments, with Stripe/Link acting as merchant of record and providing transaction-level support and order management. Chydio stores server-owned customer/subscription references and entitlement state, not complete payment-card details.

The control-plane foundation may store account status, paid-through entitlement, registered-device metadata, security and application-audit events, structured support and privacy requests, and consented aggregate product counts. Signed Stripe events are held in a private retry queue only while billing state is processed; their payload is deleted after success and queue metadata is scheduled to expire after seven days. It rejects prompts, source, project paths, provider responses, credentials, IP addresses, user-agent strings, and free-form support content from analytics. Chydio does not enable model-training data collection through this site.

Privacy export and deletion are currently structured request intake followed by verified manual review; they are not automatic. Remote Unity control and Studio collaboration are not enabled in this preview. Retention schedules, subprocessors, regional handling, legal bases, user rights, and verified request procedures must be finalized before public paid launch.

Contact: privacy@chydio.com.