RoyalXO Privacy
Privacy matters because casino accounts combine identity, payments, devices, documents and support records. This guide keeps its role separate from any external operator account.
Controller and contact
This editorial page does not open casino accounts or process deposits. It should collect only necessary interface preferences and basic technical logs.
Data categories
| Category | Purpose | Limit |
|---|---|---|
| Interface | Cookie banner and menu state. | Necessary preference only. |
| Technical | Security and hosting logs. | Short retention where possible. |
| Affiliate | Outbound sponsored link click. | No account data here. |
| External operator | Registration, KYC and payments. | Separate policy applies. |
Cookies and consent
Necessary storage keeps the interface usable. Non-essential analytics or marketing would need a clear choice and a way to withdraw consent.
Recipients and security
Hosting, security tooling and external destination sites can receive limited technical data. KYC files, payment records and account credentials should never be sent to this guide.
Rights, age and changes
Users should be able to ask about access, correction and deletion where applicable. Gambling content is for adults only, and policy changes should be dated and easy to find.
Retention boundaries
Payment and identity data should have a stated retention reason. The guide should not store that data and should keep affiliate routing separate from account processing.
The practical result is the same: continue only when the account evidence is clear, pause when rules are vague, and avoid any payment made under time pressure.
External operators
Once a user leaves through a sponsored link, the destination policy controls cookies, account data and KYC. That boundary must stay clear.
The practical result is the same: continue only when the account evidence is clear, pause when rules are vague, and avoid any payment made under time pressure.
Data minimisation
The guide should avoid forms that request birth date, documents, card details or account credentials. If a user reaches such a form from an informational page, it should be treated as an external operator flow with its own policy.
The decision should remain evidence-led: clear terms allow a cautious next step, unclear terms require a pause, and pressure signals mean the page should be left.