RoyalSea

Account data, technical data and the rights beside them

A RoyalSea account is built on registration data of email, password, currency, name, date of birth, address and mobile number, and the operation of the platform adds IP addresses, device data and transaction histories, which are processed for fraud prevention and anti-money-laundering. We describe here how that data is used, which rights a player keeps, and how the policy changes are announced.

How We Use Information

Our use of data follows the purposes the account creates, and each purpose has its scope. Registration data identifies the account holder and documents the age of 18 or above that participation requires. Technical data such as IP addresses and device data protect the account: they back the fraud prevention and anti-money-laundering checks that payment regulation requires, and they support the security confirmations that arrive by email or SMS on certain cashier actions.

Security Data in the Account

Transaction histories keep a full record of deposits, bonuses and withdrawals, which is what a dispute or a document check is measured against. The automatic logout after longer inactivity and the temporary lock after several failed login attempts belong to the same protection set, since access data is data too.

How Changes to This Policy Are Announced

A change to this policy reaches players through the published channels of our account, and the confirmed route runs over the email address held in the profile alongside our policy pages. We keep the announcement ahead of the change taking effect, so a player can read the new scope before it applies. The email and SMS confirmations that guard cashier actions follow the same principle: the notification comes first, and the account holder decides with the facts in hand.

Your Rights Over Your Data

The rights of a player run through our support team, and the route stays written and traceable. A request over the support email names the account and the right claimed, and the verification of the requester protects the account from third-party access. Self-exclusion requests travel the same route, and a permanent exclusion is processed by the support team as the responsible gambling rules describe it.

Access, Correction and Deletion in Practice

Access to stored data starts with a support request, and the account settings themselves show and edit the profile fields of name, address and mobile number. Correction of wrong details follows the same route, with document checks attached where a change touches verification. Data connected to anti-money-laundering duties stays under its regulatory retention, so deletion requests are weighed against the processing purposes stated here rather than answered with a blanket yes.

Data We May Collect

The collection table of the account, with the purpose beside each type:

Data typePurpose
Registration data: name, date of birth, address, mobileidentity of the account holder, age documentation
Email and passwordaccount access, confirmations
Transaction historiescashier record, dispute handling
IP addresses and device datafraud prevention, anti-money-laundering
Payment-method datadeposits, verified payouts

Last updated: 20 November 2026