Gameplay or technical issue
- Device and browser
- Whether input was touch, keyboard, or controller
- Planet or star-system mode
- Room code, if the issue involved a shared survey
- What you expected and what happened instead
Open a channel
Gameplay question, account problem, privacy request, billing issue, security report, or an idea from the field—send it to the same support route and include enough context for us to investigate.
Support address
Use a short subject such as “Gameplay,” “Account,” “Privacy,” “Billing,” or “Security.” That makes it easier to route the message without asking you to repeat it.
This address handles general support and the privacy requests described in the Privacy Policy.
Never email a password, authentication token, complete private invite link, room access key, full payment-card number, or card security code. Project Helios support will not ask for those secrets.
Useful context
A concise report is usually enough. Include only the details relevant to the issue, and remove private access keys from copied links or screenshots.
Data requests
To ask about personal information, request a copy, correct account information, object to or restrict certain processing where applicable, or request account deletion, email support@projecthelios.io with the subject “Privacy request.”
Write from the account email when possible and identify the username or profile involved. We may need to verify that you control the account before completing a request. Do not send a password or authentication token as proof.
Some information may need to be retained when required for security, fraud prevention, payment records, legal obligations, or the establishment and defense of legal claims. The Privacy Policy explains the current data categories, purposes, retention approach, service providers, and advertising choices.
Security
For a suspected security issue, use the subject “Security report.” Describe the affected page or feature, the impact you observed, and safe reproduction steps. Avoid accessing another person’s account or data, disrupting active rooms, running denial-of-service tests, or publishing sensitive details before there has been a reasonable opportunity to investigate.
General feedback
Balance notes, confusing controls, accessibility barriers, performance problems, campaign feedback, and ideas for future surveys are all welcome. Specific examples are more useful than a score alone: which world you entered, what the crew tried, and where the experience stopped making sense.