How we handle information connected with a Glorion account
We collect information connected with the account, identity, payments, devices and transactions. We use that information for account operation, payments, support, fraud prevention, improvements and our applicable obligations. These uses keep the account journey connected across registration, a payment route and a support request.
We also recognise that data questions deserve a route of their own. Our account settings and support route handle access, correction and deletion requests. We keep those rights visible alongside the information we collect so a player can connect a question about data with the personal account where that information is used.
How we use account information
We use account information to operate the account and support the player relationship. Payment and transaction information supports payment activity, while identity information forms part of the account context. We also use information for fraud prevention, improvements and applicable obligations. Each purpose relates to a stated part of the account journey rather than a generic description of data use.
Our privacy terms also cover support. When a player brings an account, payment or verification question through the support route, the information involved can be used to address that account context. This keeps a data question connected with the relevant player route rather than separated from it.
Information we may collect
Account and identity information
We collect account and identity information. Registration begins with Register, an email address and a password, and our account is personal, non-transferable and limited to one account per player. Identity information is also relevant where completed identity verification is connected with a first withdrawal.
Payment and transaction information
We collect payment and transaction information. We name cards, e-wallets, bank transfers and cryptocurrencies among deposit options, and withdrawals return to the deposit method. These payment-route conditions give transaction information a clear relationship with the account.
Device information
We collect device information. Our browser access covers desktop, tablet, iOS and Android.
How policy changes are communicated
Published changes
We publish material changes to our privacy rules. This gives account holders a visible point for recognising a change in how the policy is expressed.
Account-holder communication
We may also communicate material privacy changes to account holders. The account remains the relevant context for that communication, because the policy concerns the account, payment, identity, device and transaction information connected with it.
Cookies and analytics in brief
We use cookies for functions, preferences, analytics and advertising. Our cookie categories include essential, analytical and marketing cookies.
- Essential cookies support functions connected with use of our service.
- Preference cookies help retain selected preferences.
- Analytical and marketing cookies relate to analytics and advertising, with browser settings and opt-out choices providing controls.
Our cookie policy gives the fuller explanation of cookie categories and browser management. We keep the policy distinct from account rights, while both belong to the broader handling of information.
Your information rights
Access and correction
We support access and correction requests through account settings or our support route. A player can use that route when the question concerns information connected with the personal account.
Deletion requests
We also support deletion requests through account settings or our support route. The request belongs to the account context, alongside the information types and purposes described in this policy.
Sharing with service providers
We may share information with payment, identity, fraud-prevention, game, platform and analytics providers. These provider categories correspond with the account functions, payment activity, verification context, game services and analysis described in our terms.
Last updated: 3 November 2026