Contact Us

Write to contact@controlresonant.xyz. There is no contact form or support account to create. A useful first message includes the page URL, a concise description of the issue, what you expected to find, and any evidence that helps us reproduce or verify it.

Messages are reviewed by the Resonant Field Guide editorial team as capacity allows. We cannot guarantee an individual reply or a fixed response time. When a report results in a public content correction, the updated page is the primary record of that change.

Keep in mindPlease use a clear subject such as “Content correction,” “Accessibility issue,” “Privacy request,” or “Copyright concern.”

For an incorrect release fact, route, mechanic, name, requirement, or link, identify the exact sentence or section. Include the game version, platform, region, difficulty, progression state, or source when one of those details could explain a different result.

We give priority to errors that can affect purchases, accessibility, missable progress, builds, or navigation. A disagreement without reproducible detail may remain open while we look for better evidence, especially before launch or immediately after a patch.

For a broken link, image, layout, search result, or interactive tool, tell us what you were trying to do and what happened instead. Browser, device type, screen size, and operating system are helpful when you are comfortable sharing them. A screenshot can help, but it should not expose account names, private tabs, notifications, or other personal information.

For an accessibility barrier, describe the page, control, reading order, contrast, keyboard step, screen-reader output, motion, or zoom level involved. We welcome practical descriptions of the blocked task even when you do not know the technical term for the issue.

Use the subject “Privacy request” and email contact@controlresonant.xyz. Identify the correspondence you want us to locate and whether you are asking for access, correction, or deletion. We may need enough information to verify that the message belongs to you, but we will not ask for unrelated identity documents by default.

The Privacy Policy explains the site's current collection, search, hosting-log, and optional video behavior. Requests may be limited where retaining a small record is reasonably necessary for security, legal compliance, or documentation of the request itself.

For a copyright, trademark, attribution, or reuse issue, identify the protected work, the exact URL, the material involved, your relationship to the rights holder, and a reliable contact method. For a permission request, describe the material, format, audience, and whether the proposed use is commercial.

The Copyright page contains the complete reporting checklist and explains the status of this general rights mailbox. Please do not describe the address as a registered DMCA agent contact unless that status is separately confirmed through the required public process.

Send only files needed to explain the issue. Avoid executable files, unusually large archives, leaked builds, confidential documents, passwords, payment data, government identifiers, account recovery information, or unrelated personal records. Unsafe or irrelevant attachments may be deleted without review.

If a screenshot contains personal information, crop or redact it before sending. Email is not a secure channel for highly sensitive material. The Privacy Policy explains how ordinary correspondence is used and retained.

We cannot access game or platform accounts, replace keys, issue refunds, change orders, restore saves, grant promotional items, modify entitlements, overturn store decisions, or provide official technical support for CONTROL Resonant. We also cannot confirm rumors or speak for the developer or publisher.

Contact the seller for an order or refund, the platform holder for an account or entitlement, and the official game support channel for game-service or account issues. You are welcome to report a broken or misleading support link on this site so we can correct the route we provide.