Follow Your Data from Registration to Account Closure

Wazbee’s published Privacy Policy identifies Luxora LLC and affiliated companies in its privacy wording. It describes the collection of identity, contact, payment, device, session and interaction information and connects those categories with account operation, transactions, support, legal compliance, fraud controls, analytics and marketing. The policy says information may remain after account closure for as long as necessary or required by local law, including the cited AML/CFT rules and Financial Intelligence Unit guidance.

The clearest player control stated in the policy concerns marketing. Promotional preferences can be changed in My Details or through support. Privacy questions and reports of suspected account compromise should be sent to support@wazbee.

Independent policy-page check: 10 September 2026

The Organisations Named in the Policy

The Privacy Policy defines references to Wazbee as Luxora LLC and affiliated companies. In a separate document, the current Terms identify Luxora LLC as the owner of wazbee and Affmatic LTD as the company operating payment procedures. The documents describe different functions, so the payment operator should not automatically be treated as the privacy contact or controller for every account record.

The policy also refers broadly to business partners, third-party providers and authorities. It does not publish a complete provider-by-provider list, so a specific payment or verification request should be read together with the notice and instructions shown for that account action.

Information Given During Account Use

Registration and later account activity can involve identity and contact details, profile information, payment records, support messages and marketing preferences. Verification may require evidence of identity, address or ownership of a payment method. The Terms also allow video verification.

Keep profile details accurate and respond only through the route stated in the account request. If a name, address or contact detail is wrong, identify the field clearly when contacting support and retain the case reference.

Device, Session and Interaction Data

The policy includes information generated when a person visits or uses the service. This can cover device and session details as well as interactions with the site. Wazbee uses these broader data categories for purposes that include operating the account, fraud controls, analytics and marketing.

Browser settings can display or remove stored site data. Removing it may also end a session or reset browser preferences, so sign-in details should be available before changing those settings.

What the Published Uses Mean in Practice

The policy connects these uses with account operation, transactions, support, legal compliance, fraud prevention, anti-money-laundering controls, analytics and marketing. It does not set out a separate lawful-basis analysis for each row.

Payment and Verification Records

A payment can create records about the method, amount, currency, status and related account checks. These records may be used to handle deposits and withdrawals, reconcile transactions, prevent fraud and meet AML requirements.

Keep the transaction identifier and the matching bank, wallet or blockchain record when raising a payment question. Do not place a password, one-time code or complete payment credential in a routine support message.

Sharing Uses Broad Recipient Groups

The Privacy Policy refers to affiliates, business partners, third-party providers and authorities. Sharing is described in connection with operating the service, processing transactions, meeting legal requirements, preventing fraud and supporting the other published uses.

That broad wording does not identify every recipient involved in an individual case. Read the information attached to the relevant account, payment or verification step before submitting data to another service.

Retention Can Continue After Closure

Closing an account does not establish a single deletion date for every record. The policy permits retention for as long as necessary or required by local law and expressly points to AML/CFT obligations and Financial Intelligence Unit guidance. It does not convert those legal bases into a fixed published retention period.

No granular schedule is published for each data category. A privacy question about a particular record should therefore identify the account event and record involved rather than assume that every item follows the same period.

Marketing Preferences Are a Direct Control

The policy says marketing can be stopped through My Details or by contacting support. After changing the preference, keep the confirmation and note the channel and date if another promotional message needs to be traced.

The published material distinguishes this marketing choice from the wider account, transaction, security and compliance uses described in the policy. A marketing opt-out should therefore be treated as a promotional preference, not as an instruction to erase the account record.

Account Security Starts with the User’s Devices

Use a unique password, protect the registered email account, lock personal devices and sign out on shared hardware. These steps reduce exposure on the player’s side while the account remains active.

Report suspected account compromise to support@wazbee. Use the same address for a general privacy question, follow the response route given for the specific case and retain the correspondence.

Children and Shared Devices

Wazbee accounts are for people aged 18 or older who meet the legal gambling age that applies to them. Identity and age information can form part of account checks.

On a device used by a minor, keep payment credentials and account passwords out of the browser, use a separate profile and apply parental controls. Sign out after each session instead of relying on a closed tab.

FAQ