Reference

doraplay88 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open an account, sign in on mobile, browse Speed Baccarat or Fish Hunter, and use DANA, OVO, GoPay or…

Clear data purposesWallet record handlingAccount access controlsCookie choices
doraplay88 doraplay88 Privacy Policy for Your Account
CONTACT DATA HELP

Where to Ask About Your Privacy Policy

A direct support request gives us the clearest route to a privacy answer. From your signed-in account, use the support contact path and describe whether your question concerns login records, wallet status…

Account contact path Send a privacy question from the signed-in account path so we can connect your request with the correct profile. Include the email or phone detail attached to your account, but leave out DANA, OVO, GoPay and QRIS PINs.
Wallet status query If a payment record looks unfamiliar, tell us the rail used, such as QRIS or bank transfer, and the visible reference. We use that limited detail to locate the record without asking you to disclose a wallet password or full payment credential.
Access assistance For a privacy request after a failed sign-in, describe the device path, such as mobile browser or desktop browser, and the account step that stopped. We use those facts to separate an access issue from a personal-data request.
DATA HANDLING

What Our Privacy Process Covers

We keep the policy practical: you can see why a detail is needed, how it supports an account action and how to ask us to change the record.

Account details

When you open an account, we collect the details needed to create your profile and confirm account access. A clear phone verification step may be used before access is granted, helping us distinguish your request from an unfamiliar sign-in.

Device signals

Our records may include browser type, device identifiers, sign-in time and security events. These signals help us investigate a locked account or an unusual route from mobile login to the lobby without reading unrelated files on your device.

Cookies

Cookies can keep a session active, remember a language or measure a page request. You can adjust cookie controls in your browser, although removing essential cookies may require you to sign in again before opening account pages.

Payment records

We record the payment rail, amount reference supplied to us and status needed for account reconciliation. DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are handled as transaction data, not as permission to access your wallet.

Retention timing

We keep personal data while it serves account security, support, dispute handling or a legal record requirement. When that purpose ends, we remove it or separate it from your account where practical, subject to lawful retention obligations.

Change requests

You can ask us to correct an inaccurate account detail, explain a recorded data use or request deletion where applicable. We may verify ownership first, then confirm which records can be changed and which must remain for a stated legal reason.

Privacy Policy Answers for Your Account

These questions cover the requests we expect before or after account access. Each answer relates to how doraplay88 handles personal data, wallet records, cookies and security checks for Indonesian account activity. If your situation is not listed, use the signed-in support contact path and describe the exact record you want us to locate.

It covers personal data linked to your account, including contact details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It also explains how we handle DANA, OVO, GoPay, QRIS, bank transfer and virtual account records.

Phone verification helps us confirm that an account request belongs to you before access is provided. It can also support an account recovery check after an unfamiliar sign-in. We use the verification detail for that account purpose rather than requesting your wallet PIN.

Yes. Send a request through the signed-in account support path and identify the email or phone detail attached to your profile. We may verify ownership first, then explain which account, security and payment records can be supplied under applicable local requirements.

We keep the rail name, status and reference needed to match a payment event with your account. We do not need your wallet PIN for that purpose. If a record is disputed, provide the visible reference rather than private wallet credentials.

Use the account support contact path and state whether you want a correction or deletion request. We may ask for ownership checks. Where local law permits, we will change or remove eligible data; records required for security, disputes or legal duties may remain.

Yes. The policy covers data collected when you sign in through a mobile browser, move to the lobby or use account pages on a desktop browser. Device and session signals may be recorded for security, but cookies can be managed through your browser settings.

Contact us through the signed-in account support path and describe the data concern, such as a cookie, login event or wallet reference. Avoid sending passwords or PINs. We will use the account details supplied to locate the matter and explain the next step.