SUPPORT · ROUTE THE SIGNAL

Send less.
Solve safely.

Choose the narrowest route and send only the metadata needed to investigate. These addresses are designated launch inboxes; delivery, monitoring, response targets, and staffing must be verified before public paid release.

PRODUCT

Forge or account help

Installation, local actions, Chydio ID, pairing readiness, or paid-entitlement mismatch.

support@chydio.com
TRANSACTION

Receipt or payment

Use the Link receipt or order-management link for charges, receipts, payment methods, tax documents, cancellation, and order status.

Read billing boundaries
PRIVACY

Data request

Access, export, correction, deletion, retention, or privacy questions. Requests require verified manual review during preview.

privacy@chydio.com
SECURITY

Security report

Suspected account takeover, exposed Chydio token, authorization bypass, or vulnerability. Revoke exposed credentials first.

security@chydio.com

LOW-DATA INTAKE

Enough context.
Nothing sensitive.

01Use a route labelStart the subject with Product, Access, Billing entitlement, Privacy, or Security.

02Send safe metadataInclude operating system, Chydio Forge version, approximate UTC time, action name, non-sensitive error code, and whether retrying reproduced it.

03For billing access onlyInclude plan name and the Link order or receipt reference. Do not include card or bank details.

04Wait for a scoped requestSupport may provide a redaction guide or one-time upload path if evidence is genuinely needed. No public upload intake exists in this preview.

DO NOT SEND

Keep secrets and projects out of support email.

Never send passwords, SMS codes, recovery codes, full card or bank details, API keys, consumer-subscription tokens, CLI or remote-access tokens, Firebase credentials, project archives, source files, project paths, prompts, model responses, screenshots containing secrets, or unrelated personal data.

PREVIEW OPERATIONS

What is live today?

The public site and identity foundation are in technical preview. Remote Unity control, paid subscriptions, Studio collaboration, automated privacy fulfillment, service-level commitments, and production support operations are not yet enabled. The published inboxes must not be described as monitored until Chydio verifies delivery and operating coverage.