Reference

Privacy details behind your dolar999 account

dolar999 Privacy Policy explains what we collect, why we use it, and how you can ask about your account data before opening an account.

Clear data purposesWallet details explainedAccount access controlsCookie choices available
dolar999 Privacy details behind your dolar999 account
CONTACT ROUTE

Reach us about your personal data

A clear contact route lets you ask what data is connected to your account, correct a detail or question a wallet record without explaining your whole account history. Use the support path attached to your account when a login or payment status stalls. Tell us the phone number linked to the account, the relevant date and the request you want us to check; do not send a password or wallet PIN.

Team online

Account data request

Ask us to identify the personal details connected to your account, including your phone verification record and recent access references. We may ask account questions before responding so a private request reaches the right account holder.

Wallet record query

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, include the payment reference and date. We use that information to locate the status record while keeping your wallet PIN and secret credentials out of the request.

Correction pathway

If your name, phone detail or account record needs correction, contact our support path from the account area. We compare the request with your verification details before changing information, and we explain any reason a correction cannot be made.

DATA PRACTICE

Controls we apply to account data

We keep this Privacy Policy practical by linking each data use to an account task: access, security, wallet matching, support or legal recordkeeping.

Data handling

We use account details to provide access, complete phone verification, check security signals and answer support requests. Activity labels such as a lobby visit or a Live Baccarat Royal page may help us investigate an issue, but they are not needed for every privacy question.

Cookie settings

Cookies and similar browser records help keep your session connected, remember basic preferences and identify unusual access. You can clear browser cookies through your device settings, although doing so may require another login or phone verification step.

Account security

We use phone verification and account checks to reduce the chance that someone else receives private details. Never share your password, wallet PIN or verification code in a support request, even when a payment status needs checking.

Retention practice

We keep records for the period needed to operate the account, investigate payment status, protect access or meet a legal requirement. When a record is no longer needed for those purposes, our handling process considers removal or further restriction.

Change requests

You can ask us to correct account details, explain a data use or provide the personal data connected to your account. Include a clear request and matching account detail; we may verify identity before making a change or releasing a copy.

Third-party context

Payment and technical partners may create references needed to process DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use those references for matching and status checks, while this policy explains the account data we handle.

Privacy Policy questions before opening

These Privacy Policy answers cover the account steps most relevant to Indonesia access: phone verification, mobile browsing, wallet records, cookies and requests for personal data. Read them before you open an account, then use the support path if your situation needs a record-specific answer. Eligibility and access depends on local law, so we cannot treat this page as a substitute for local requirements.

It covers account details, phone verification, device and browser records, cookie activity, support requests and payment references. That includes status information connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, while access depends on local law.

We use your phone number for account identification and a clear verification step before access or a sensitive data request. It helps us distinguish your request from another person’s request. Do not place verification codes in support messages.

Yes. The Privacy Policy covers practical browser and device signals used for session continuity, security checks, language settings and access troubleshooting. It does not mean we need every detail stored on your phone, and you can clear cookies through your device settings.

We may receive a reference showing that a DANA or QRIS request was started, matched, completed or left pending. We use that reference to check account status and resolve support questions. We do not ask you to send a wallet PIN.

You can contact us through the account support path and ask for the personal data connected to your account. Include your linked phone detail and a clear request. We may verify identity first, and the response can depend on local law.

Send a correction request through the support path, naming the detail that appears wrong and the change you seek. We compare the request with account verification records before editing it. If we cannot change something, we explain the reason.

We consider removal or restriction when information is no longer needed for account access, security, payment status checks, support handling or a legal requirement. The exact period can vary by record type and applicable local law, so ask support about a specific item.