Reference

Open castletoto Privacy Policy Clearly

Our castletoto Privacy Policy explains what we collect when you create an account, sign in from a mobile device, or select DANA, OVO, GoPay and QRIS.

Account dataWallet recordsDevice securityCookie choices

Browse Our Lobby Read FAQ

Browse How Payment Data Is Used

castletoto Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We collect the account details you enter during registration, including your contact information and verification status, so we can match each session to the right account. When you use DANA, OVO, GoPay or QRIS, we receive transaction references, amount status and confirmation details needed to reconcile

1
your wallet activity; we do not need your wallet password. Bank transfer and virtual account records may include a bank reference and sender name when supplied by the payment rail. Device identifiers, browser settings, sign-in time and security events help us detect unusual access. We use
2
this data for account operation, payment reconciliation, fraud checks, support responses and legal duties where local law permits. If you open Live Baccarat or another lobby area, activity records remain linked to your account rather than treated as anonymous session data. You can ask us what
3
we hold, request a correction or ask about deletion, subject to records we must retain under applicable local law.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT OPTIONS

Check Privacy Questions Through Support

A clear contact path helps when you want to ask about a data field, payment reference or account record. Start from the signed-in support chat so we can connect your request with the correct account without asking you to post private details publicly. If you cannot sign in, use the account access route and include only the contact detail needed to locate your record.

Team online

Account support chat

Ask why a registration field, phone verification result or device signal appears in your account record. We use the signed-in chat to check identity before discussing private account details.

Wallet data check

For DANA, OVO, GoPay, QRIS or bank transfer references, send the transaction date and visible status only. We can trace the payment record without requesting your wallet password or full security code.

Privacy request

Request a copy, correction or removal assessment through support after we verify your account. Tell us which record concerns you, and we will explain any retention required by local law.

CONTROL DETAILS

Explore Account Data Controls

We handle privacy requests through the same account checks that protect your sign-in and wallet history. Our process separates identity verification from payment credentials, limits internal access to operational needs and records…

Account records

We store registration details, phone verification status and account activity together so support can identify the correct record. You may ask which fields are held and why each field is needed.

Cookie settings

Cookies and similar device storage can keep a session active, remember selected settings and help detect unusual sign-ins. You can adjust browser permissions, though some account functions may then require another sign-in.

Payment separation

DANA, OVO, GoPay and QRIS references help us match a payment event, but wallet passwords and one-time security codes should stay with your payment provider. We do not ask you to share them in support.

Security checks

A new device, repeated failed sign-ins or an unusual location may create a security event for review. Phone verification before account access helps us distinguish your request from an unknown sign-in.

Retention steps

We keep records only as long as needed for account operation, payment matching, security checks or legal duties. When a deletion request meets the requirements, we remove or anonymise eligible data.

Change requests

You can ask us to correct a phone number, contact detail or other inaccurate account field through support. We may request account verification before changing data that affects access or payment matching.

Find Privacy Policy Answers

These Privacy Policy answers focus on the questions you may have before creating an account or asking us to change an existing record. Each answer points to a practical account, device or payment step, so you know what to prepare when contacting castletoto.

It covers account details, phone verification, device signals, cookies, payment references, support records, security events and retention. It applies when you access castletoto where local law permits.

Phone verification connects account access to the contact detail you supplied and helps detect unauthorised sign-ins. We may check it again before discussing private records or changing access data.

Yes. The Privacy Policy explains that DANA and QRIS may provide transaction references, status and confirmation details. We use those records to reconcile activity, not to collect your wallet password.

We may record browser type, device identifier, sign-in time, language settings and security events. These details help protect your account when you move between a mobile browser and desktop.

Open the signed-in support chat and ask for a data copy. We first verify that you control the account, then explain the records available and any limits required by local law.

Yes. Send the inaccurate field through support, such as a contact detail or phone number. We may verify your account before making a change that affects sign-in or payment matching.

We retain payment references for the period needed to match wallet activity, resolve account questions, protect against misuse or meet legal duties. You can ask support about a particular record.

Open castletoto Privacy Policy Clearly

Check Privacy Questions Through Support

Account support chat

Wallet data check

Privacy request

Explore Account Data Controls

Account records

Cookie settings

Payment separation

Security checks

Retention steps

Change requests

Find Privacy Policy Answers

01 What does the castletoto Privacy Policy cover?

02 Why does castletoto collect phone verification data?

03 Does the Privacy Policy include DANA and QRIS data?

04 What device details does castletoto store?

05 How can I request a copy of my account data?

06 Can I ask castletoto to correct my details?

07 How long does castletoto keep payment records?

Related Pages