VOLYXISBETA
Dev Blog
Sign InCreate Account
VOLYXISMenu
Dev Blog
Sign InCreate Account
Home/Privacy Policy

Privacy Policy

How Volyxis handles personal information across Volyxis accounts, licensing, billing, support and Bug Reports.

Privacy Policy

How Volyxis handles personal information when you use Volyxis, its Website, accounts, licensing, billing, support and Bug Tracker.

Effective
2 September 2026
Last updated
3 September 2026
Version
1.2

1. Who we are

Volyxis operates Volyxis. We are responsible for the personal information used to run the Volyxis Website, accounts, licences, billing, support and Bug Tracker.

This policy does not cover a game or service made and operated by a Volyxis customer. That customer is responsible for explaining how their own product uses personal information.

For privacy questions, contact us through Volyxis Support.

2. Information we hold

The information we hold depends on how you use Volyxis. It can include:

  • your email address, display name, password hash, account status and verification history;
  • optional profile details such as your name, studio, telephone number, address and avatar;
  • licence, activation, device, download and build records;
  • plan, subscription, invoice, tax, payment and refund status received from Stripe;
  • support messages, email-delivery records, Bug Reports, comments and screenshots;
  • IP address, browser or app user agent, request details and security events; and
  • content and media saved by approved Website administrators.

Please do not send passwords, full licence keys, full payment-card details or personal information that is not needed.

3. Your local projects

Your project files, maps, models, textures and audio ordinarily remain in the project storage you control. Licence activation and Build Game checks use identifiers, versions and digital fingerprints. They do not normally upload the creative files themselves.

We receive project content only when you choose to send it, for example in a Bug Report or support request.

4. Where it comes from

Most information comes from you when you register, edit your profile, activate the Editor, build a game, buy a plan, contact support or report a bug. Volyxis also creates service and security records when you use it. Stripe sends us limited billing updates, and Google can send us a reCAPTCHA risk result.

5. Why we use it

We use personal information to provide your account, Editor access, licences, builds, downloads, billing and support. We also use it to keep Volyxis secure, prevent abuse, diagnose faults, meet legal duties and deal with legal claims.

Under UK data-protection law, our usual reasons are performance of a contract, legitimate interests, legal obligation and, where we ask for it, consent. Our legitimate interests include security, fraud prevention, reliable operation and improving support. You can object to use based on legitimate interests; we will consider your circumstances and the law.

6. Accounts and profiles

We use account information to sign you in, verify your email, recover and secure the account, show your plan and keep an audit of important account changes. Optional profile details help us identify you or your studio when you choose to provide them.

Your public display name and public account avatar can appear beside a public Bug Report or comment. We do not show account email addresses or internal account identifiers on public bug pages.

7. Billing and Stripe

Stripe hosts paid checkout and subscription management. Stripe collects payment-card and fraud-prevention information under its own privacy policy. Volyxis receives the customer, subscription, invoice, payment, tax and refund details needed to provide the purchase and keep financial records.

Volyxis does not store the full card number or security code entered on a Stripe page. Read the Stripe Privacy Policy for details of Stripe's use.

8. Licences and builds

We keep records of plans, licences, activation, permitted devices, downloads and games built with Volyxis. These records let Volyxis provide access, check that a build follows your plan, investigate misuse and support you. Build records can include project and build identifiers, software versions and digital fingerprints of a build.

9. Bug Reports and screenshots

You choose whether a Bug Report is public or private. A public report can show its title, details, comments, activity, screenshots, display names and public account avatars to anyone. Search engines may index it. A private report is available only to its reporter and Volyxis Developers/Staff who need access.

A screenshot can still show personal information in the picture. Check and crop every screenshot before uploading it.

10. IP and security logging

When you use the Website, API or Editor, we can record your IP address, user agent, request route, request identifier, date and time, response status and related authentication or security events. We use this information to protect accounts, apply rate limits, investigate abuse and diagnose service faults.

We do not need your cookie value, password, access token or full licence key in an ordinary request log. Please report any concern through Support.

11. Google reCAPTCHA

Some account, support and bug forms use Google reCAPTCHA to reduce automated abuse. Google can receive IP, browser, device and interaction information and returns a risk result. A low result can block or delay a form. Contact Support if a genuine request is blocked.

Google's Privacy Policy and Terms apply to reCAPTCHA.

12. Email

We send service emails needed for account verification, password recovery, billing, security and support. We can also send Bug Tracker updates to people who follow or take part in a report. Access to a private bug is checked before a private update is sent.

We keep limited delivery records so we can confirm whether an important message was sent and diagnose failures. We do not send another notification to tell you about your own comment.

13. Cookies and external content

The Website uses a necessary session cookie for sign-in, form security and short messages. It contains a random session identifier, not an API access token. You can sign out or revoke sessions from your account controls.

Discord community features, YouTube's youtube-nocookie.com player and Vimeo embeds can receive network and browser information when they load. Their own privacy policies apply. Blocking third-party content can stop that feature working.

14. Who receives information

We share only what is reasonably needed with providers that host, secure, back up or deliver Volyxis and its email; with Stripe, Google, Discord, YouTube or Vimeo for the features described above; and with advisers or public authorities when the law requires it. We may also share information during a genuine business sale or reorganisation, with suitable protection.

Some providers process information outside the UK. Where the law requires a transfer safeguard, we use an approved safeguard or an adequacy decision. We do not sell personal information.

15. How long we keep it

We keep information only as long as it is reasonably needed for the purpose described here. The period depends on account activity, licence and build integrity, support needs, security, financial-record duties and possible legal claims.

Sessions and recovery links expire. Operational and security logs use limited retention periods unless an incident or legal need requires longer. Billing records are kept for the period required by tax and accounting law. Public Bug Reports remain available while published; private reports and attachments remain while needed for support, security or a dispute. Deletion from live systems may take longer to reach protected backups.

16. Your rights and complaints

Depending on the law and circumstances, you can ask for a copy of your information, correction, deletion, restriction or transfer. You can object to some uses and withdraw consent for future use. Some requests are limited where we must keep information for law, security or legal claims.

Send a privacy request through Volyxis Support. We may need to confirm your identity. We normally respond within one month. You can also complain to the UK Information Commissioner's Office or, where relevant, your local data-protection authority.

17. Changes and contact

We may update this policy when Volyxis, its providers or the law changes. We will publish the new version and date and give any further notice required by law.

For privacy, rights or security questions, use Volyxis Support. Do not include passwords, full licence keys or payment-card details.

Contents

Contents
  1. Who we are
  2. Information we hold
  3. Your local projects
  4. Where it comes from
  5. Why we use it
  6. Accounts and profiles
  7. Billing and Stripe
  8. Licences and builds
  9. Bug Reports and screenshots
  10. IP and security logging
  11. Google reCAPTCHA
  12. Email
  13. Cookies and external content
  14. Who receives information
  15. How long we keep it
  16. Your rights and complaints
  17. Changes and contact

Related Documents

Terms of ServiceEULA

Questions

Use Support for questions about these documents, your account or your licence.

Open Support
VOLYXIS
PrivacyTermsEULA
© 2026 Volyxis