How we help with a Glorion account question

We organise account questions around the part of the journey a player is handling: registration, a payment route, a welcome condition or a verification checkpoint. Our support route is most useful when the message identifies that moment clearly and keeps the personal account protected. We ask players to use the account support route for account-specific assistance rather than sharing private details in an open setting.

Questions our support route can help organise

Account access and registration

We begin registration with Register, an email address and a password. Our account is personal, non-transferable and limited to one account per player. A message about registration is clearest when it states that it concerns the account opening or access route, without repeating private credentials.

Payments, withdrawals and verification

We name cards, e-wallets, bank transfers and cryptocurrencies among deposit options. Withdrawals return to the deposit method, and checks may delay activation or a withdrawal. Completed identity verification is connected with a first withdrawal. A player can use our support route to distinguish a payment-method question from a verification checkpoint.

Welcome terms and player controls

We set a EUR 15 minimum deposit, 30x wagering and seven days of validity for the welcome package. We also offer daily, weekly and monthly deposit limits, session time limits, reality checks and self-exclusion choices. These are separate topics, so a message is easier to understand when it names the relevant offer term or account control.

What to prepare before writing

  1. State whether the question concerns registration, a selected payment method, a withdrawal, a welcome-package condition or an account control.
  2. Give the relevant account context in general terms, such as the device route or the deposit stage, while keeping the email address and password private.
  3. Name the confirmed condition at issue: for example, the EUR 15 welcome minimum, the return-to-deposit-method rule or the verification checkpoint.
  4. Keep the request focused on one account moment, so our team can read the question without mixing a payment route with a separate offer or game query.

We encourage players to preserve account security throughout the contact process. A personal account remains the place for its own details; the support request can describe the issue without exposing a password or turning a routine question into a list of private information.

A clear route for each account moment

We use our support route to help players frame a question around a confirmed account condition. A registration question can focus on Register, email address and password. A payment question can focus on the chosen method and the return-to-deposit-method condition. A welcome question can focus on the selected deposit stage, 30x wagering or the seven-day package period.
We also recognise that a player may need a pause rather than a transaction answer. Our deposit limits, session time limits, reality checks and self-exclusion choices each have their own role. A message about those tools is most useful when it identifies the chosen type of boundary — a daily, weekly or monthly limit, a time limit, or a self-exclusion period from 24 hours to permanent account closure.
Our browser route is available for desktop, tablet, iOS and Android. When a device context matters to the question, it can be stated alongside the account moment, while the personal-account rule remains unchanged across the named access routes.