Richard Casino Data Handling
Table of contents
Data handling at Richard Casino follows the general principles that apply to online gambling services. Data is requested for accounts, payments and compliance, kept for the period rules require, and protected on the connection by encryption. Legal detail is left to the operator's published policy.
🧾 Categories of data
Four categories matter at Richard Casino. Registration data comprises a login pair, the country, personal details and the base currency. Identity data covers the photo ID and proof of address. Whichever payment method is used, its details count as payment data. Technical data covers cookies, device type and browser version.
🛠️ Purpose of each category
Registration data creates the account and serves as the login, and a change of the e-mail address is handled through support because the mailbox is tied to the account. Identity data confirms the holder before the first withdrawal. Payment data moves money through the cashier, and the cashier history lets the holder look back over earlier deposits and withdrawals. Technical data keeps a session open and helps the site render on phones, tablets and computers.
Each category is used for its stated purpose and not for unrelated ones, and the checks that rely on them are carried out once and not repeated without cause. The separation keeps the e-mail address from being mistaken for a payment detail, and the payment detail from being treated as an identity record.
🔁 Passing data on
Payment channels receive what is needed to process a transaction, and game studios receive what is needed to run a session. Where the operator is obliged to respond, requests from authorities receive an answer. For crypto, the transfer is recorded on a public blockchain that the operator does not control. Each party handles only its own part of the data.
🍪 Cookie use during a session
Cookies keep a session open, remember display preferences and support site analytics. Browser settings control whether they are accepted, and blocking them can interfere with login and the cashier. A session cookie ends when the browser closes or when the player logs out.
🧯 Protection measures
Connections are encrypted, and access inside the operation is limited to what the work requires. Anyone who wants to see, correct or delete personal data uses live chat or e-mail, and the account holder is confirmed first.
🕰️ Retention and closure
Payment and identity records are held for the period the applicable rules set, and they can be removed afterwards. A player leaving Richard Casino gets in touch with support to arrange it. Play ends with an account closure or with self-exclusion, but compliance records may stay for the period the rules demand. Closure is confirmed to the registered address, and the mailbox stays the reference for any later question about the account.
📬 Notices to the mailbox
Notices go to the registered e-mail address. They include the activation link, password resets and, where sent, promotional messages. Support can be asked to stop promotional messages. The address is both a login item and a communication channel, which is why keeping it reachable matters.
🔞 Age and the date of birth
Play is for adults, and age is confirmed from the identity documents submitted at the check. The same date of birth is used twice: it has to match the document and it times the birthday bonus. Support clears a mismatch before the first withdrawal is released.
🛡️ Where player limits are stored
Because ceilings, reminders, breaks and self-exclusion sit on the account server, every device applies them. A logout, a wiped browser or a replaced phone leaves them in force. A setting made once at Richard Casino therefore does not depend on the device used.
🧑⚖️ Who may ask what
Only the account holder may ask to see, correct or delete personal data, which is why the sender of a request is confirmed first. Answers go to the registered address. A request from anyone else is not acted on.
🏁 Data handling in brief
Four categories of data serve stated purposes at Richard Casino, only what a transaction or session needs is passed on, and data requests go to support, where the sender is confirmed before any answer is given.