How Realz Handles Player Information Across Account Services
We use account information to create and confirm a profile, support registration and handle verification when it is requested. The account flow includes details such as email, name, date of birth and residential address, while verification may involve identity, address and payment documents.
Information also appears in support conversations when a player asks about access, a payment route, an offer or a responsible-play control. Keeping each request focused helps connect the information with its practical purpose and the relevant account process.
Information Collected for Account Purposes
| Information type | Practical purpose | Typical account context |
|---|---|---|
| Registration details | Create and confirm a profile | Email, name and date of birth |
| Address details | Maintain account information | Residential address |
| Verification material | Review requested checks | Identity, address or payment document |
| Support context | Understand a player question | Access, payment, bonus or safer-play topic |
The registration flow also uses email confirmation during activation. One account is permitted per person, household and IP address, so consistent account information helps distinguish the profile involved in a later question.
Cookies and Browser Activity Explained
Cookies are small browser records that can support a session, remember preferences or show how a service is used. They sit alongside account information rather than replacing registration or verification details.
- Essential cookies support basic browser functions and session continuity.
- Preference cookies can retain choices made during a visit.
- Analytics cookies provide broader information about service use.
- Third-party cookies may support an integrated feature supplied by another service.
Browser settings normally provide controls for reviewing, limiting or deleting stored cookies. Our Cookie Policy explains these categories and the available browser choices in more detail.
Making a Focused Information Request
A clear request identifies the account and the information category involved. Use the established support route without including an address or contact detail in the policy text.
- Request access to the account information connected with the profile.
- Point out a registration detail that needs correction or clarification.
- Identify a verification document category involved in the question.
- Describe the support conversation or account process concerned.
The account email provides useful context for the request. Passwords remain separate from messages, and verification material belongs in the designated account process when it is requested.
Using Information for Defined Services
Creating and confirming an account
We use registration details to establish the profile and email confirmation to activate it. Name, date of birth and residential address form part of the account information associated with that process.
Reviewing requested verification material
Identity, address and payment documents may be requested for verification. Complete, readable uploads are generally checked in under 24 hours, and a phone camera can provide the document image when the mobile route is used.
Supporting player account questions
We use the context supplied in a support conversation to understand whether the matter concerns access, a payment method, a bonus route or a safer-play request. Time-out and self-exclusion requests can be directed through support and the My Support section.
Account information stays connected with the purpose for which it is handled. A focused request makes it easier to identify the relevant registration, verification or support context and respond through the appropriate route.
Last updated: 12 November 2026