Reference

d55 Privacy Policy at a Glance

This Privacy Policy explains how d55 handles the data tied to your account, device, cookies, payment references, and support chats.

Account DataCookiesPayment RecordsRetentionLocal Law
Explore the lobby Read FAQ
d55 d55 Privacy Policy at a Glance
REQUEST ROUTES

Where To Reach Us

If you want to ask about access, correction, deletion, or a copy of the data tied to your account, start with the channel that matches your request.

Email request Send the request from the email linked to your account and say whether you want access, correction, deletion, or a copy of data tied to your record. We use the match to confirm the right account.
In-account message After login, use the message path if you want a faster handoff. It helps us route the case to privacy staff without exposing your full account record in a public channel.
Written follow-up If you need a written trail, ask support to keep the thread open until the request is finished. We can note the date, the action taken, and any follow-up needed.
SAFE HANDLING

How We Handle Your Data

We design the policy around plain data handling: collect only what we need, use it for account operation and support, and keep it for the period required by law or dispute handling.

Collection

We collect the details you enter, the device data that reaches us, and the payment reference tied to your request. That lets us run your account, settle support cases, and detect misuse.

Cookies

Cookies help us remember your sign-in state, language choice, and a few page settings. If you clear them, some parts may ask you to log in again or set preferences again.

Security

We protect account access with password controls, session checks, and alerts for unusual activity. If you use a shared device, log out after each session so your private data stays separate.

Retention

We keep records only as long as needed for account support, fraud checks, dispute handling, and legal duties. When the period ends, we delete or reduce the data we no longer need.

Access requests

You can ask for a copy, correction, or deletion where law allows. We may need to confirm your identity first, especially when the request touches payment logs or account history.

Contact checks

Please send privacy requests from the email linked to your account or through the signed-in message path. That keeps the request tied to you and lowers the risk of accidental disclosure.

Privacy Questions We Hear Often

These answers cover the main privacy questions around data, cookies, access, and change requests. We keep the process practical: ask from the email on file, confirm what you want changed, and we will reply with the next step. If a rule in your region limits access or retention, we follow local law and explain what that means for your request.

We collect the details you enter, device and session data, cookie identifiers, and payment references linked to account activity. We use them to run login, support requests, and the parts of the service that depend on your account.

Cookies remember your login state, language choice, and a few settings so you do not reset them on every visit. They also help us spot unusual behaviour and keep sessions stable.

Yes, where local law allows. Send the request from the email on file or through the signed-in message path, and we will confirm identity before we share any record.

Tell us which field is wrong, what it should be, and any proof we need to check the change. We will update the record where the law and account rules permit.

We keep data for the time needed to support your account, handle disputes, prevent misuse, and meet legal duties. After that, we remove or minimise what we no longer need.

Only staff and service partners who need it for account operation, security, payment checks, or support can see limited data. We do not sell personal data, and we limit access by role.

Related Pages

Songkran Splash d55 Casino Register Ocean Riches