Reference

dita168 Privacy Policy For Your Account

The dita168 Privacy Policy explains how we handle your account details, wallet records and device access when you use our Indonesia service.

Account dataWallet recordsDevice accessCookie choices
Explore Lobby Read FAQ
dita168 dita168 Privacy Policy For Your Account
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact path matters when a privacy request is connected to a login or wallet record.

Account access Use the account-help path when you need to ask how your phone verification record, login history or device details are used. We may ask you to confirm account ownership before discussing personal data, and you should never send your password in a privacy request.
Wallet reference For a DANA, OVO, GoPay or QRIS privacy question, include the date and reference shown in your account rather than full wallet credentials. This lets us locate the relevant status record while limiting the personal details included in your message.
Request follow-up When you ask for correction, access or removal, we record the request against your account case and explain any identity check. Keep the confirmation from our support route so you can refer to the same privacy request without opening duplicate cases.
DATA CONTROLS

Inside dita168 Privacy Handling

We separate account details from the operational records needed to keep a session and wallet status clear.

Account details

We use details such as your account identifier and verified phone record to connect you with the correct account. The phone step is checked before we discuss account data, which helps prevent a privacy request from being sent to the wrong person.

Cookie settings

Cookies can keep a browser session connected and remember security-related choices. You can adjust cookie controls in your browser, although blocking necessary cookies may interrupt account access or require you to repeat the phone verification step.

Device signals

We may record browser, operating system, approximate session timing and security events to identify unusual sign-ins. These signals help protect your account but are not used as a substitute for the ownership checks required for a personal data request.

Wallet records

A DANA, OVO, GoPay or QRIS reference can show that an account action reached a payment-status stage. We use the reference to reconcile status, not to request your wallet password, card secret or other credentials through support.

Retention period

We keep personal data and account records only while they serve account operation, security, dispute handling or a legal need. When a category is no longer required, our process removes it or changes it so it no longer identifies you.

Change requests

You can ask us to access, correct or remove eligible personal data through the account-help route. Tell us which record concerns you, such as a login or QRIS status, and complete ownership checks before we make a change.

Privacy Policy Answers For dita168

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain the practical route for account data, device records, cookies, payment references and personal requests. If your situation is not covered, use the account-help path with the smallest useful set of details. We will tell you what verification is needed and whether local law affects the request.

It covers data connected with your account, phone verification, device sessions, cookies, wallet-status references and security events. It also explains retention, access and correction requests. The policy applies to your use where local law permits, and access depends on local law.

Phone verification helps us confirm account ownership before access and before we discuss personal data. It connects the verified phone record with the correct account, while reducing the chance that another person can request details about your login, DANA status or account history.

Yes. The Privacy Policy covers payment-status references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match an account action with its status, and we do not ask support requests to include wallet passwords.

Use the account-help route and state whether you want access, correction or removal of an eligible record. Mention the relevant account step, such as phone verification or a device session. We may request ownership checks before confirming or changing personal data.

Cookies can maintain a browser session and remember security choices on your phone or desktop. You can change cookie controls in your browser. Blocking necessary cookies may interrupt access, remove session continuity or require another phone verification step.

We retain data while it supports account operation, security, dispute handling or a legal requirement. Once a category is no longer needed, our process removes it or changes it so it no longer identifies you. The applicable period can depend on local law.

Yes. Ask through the account-help route and identify the account or session concerned. We may hold browser type, operating system, session timing and security events. Ownership checks can be required before we disclose personal data linked to your device access.

Related Pages

dita168 Indonesia Live Blackjack Grand Access guide About Us Account information