Reference

Privacy Policy for Your drajat99 slot Account

drajat99 slot Privacy Policy explains what we collect when you open an account, sign in, verify your phone, or use DANA and QRIS.

Account dataWallet recordsCookie choicesSecurity requests
drajat99 slot Privacy Policy for Your drajat99 slot Account
CONTACT OUR TEAM

Three Ways to Ask About Privacy

A clear contact path helps when you want to understand a record, correct an account detail, or ask how a cookie works. We route Privacy Policy requests through the same account support path used for login and wallet status questions, so you do not need to explain your full history in a separate place. Include the phone number linked to your account and the subject of your request, but do not send a password or wallet PIN. We respond through the available support channel after checking that the request comes from the account holder.

Team online

Account support

Use the account support channel when you need access to your stored details or want to correct a phone number. We check account ownership before discussing records, and we never ask you to send your password, wallet PIN, or one-time verification code.

Wallet status help

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account record looks unfamiliar, tell us the reference and date through account support. We compare the record with your account history before explaining what was stored or correcting a clear mismatch.

Security contact

Report suspected account access through the security contact path as soon as you notice it. We may pause sensitive account changes while checking the phone verification trail, device details, and recent sign-in activity linked with your drajat99 slot account.

HANDLING YOUR DATA

Six Practical Privacy Controls

We keep this policy practical by linking each data use to an account action you can recognise.

Account details

We collect the details needed to create and maintain your account, including contact details used for phone verification. We use them to sign you in, connect account requests with the correct record, and send replies about a Privacy Policy request.

Payment references

A wallet or bank reference can remain in account records after you check a payment status. This may include DANA, QRIS, OVO, GoPay, BCA, BRI, Mandiri, or BNI context. We use the reference to trace status without storing your wallet PIN.

Cookies and devices

Cookies help remember a session and selected settings when you move from login to the mobile lobby. Device and browser details help us spot an unusual sign-in. You can manage cookies through your browser, although some account steps may then need to be repeated.

Account security

Phone verification adds an account step before access and sensitive changes. We may compare sign-in time, device signals, and recent account actions when a request looks unusual. Never share a one-time code; our team does not need it to answer a policy question.

Retention approach

We keep records only for the period needed for account operation, security checks, payment tracing, dispute handling, or a legal obligation that applies where local law permits. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Changes and access

You can ask what account details we hold, request a correction, or ask about deletion through account support. Tell us the account phone number and the change requested. We verify ownership first, then explain any record that must remain for security or legal reasons.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions you are most likely to have before opening or using drajat99 slot. We keep the wording tied to actual account steps, device behaviour, and local payment records rather than describing unrelated lobby functions. If your situation is not covered, contact account support with the phone number connected to your account and we will route the request.

It covers account details, phone verification, sign-in and device records, cookie choices, payment references, security checks, retention, and requests to access or correct data. It applies when you use the account path where local law permits, including activity connected with DANA, OVO, GoPay, QRIS, or bank transfer status.

Phone verification helps us connect a person with the correct account before access or sensitive changes. It also gives our support team a check when you ask about a record. We do not ask you to disclose your password or one-time code during a Privacy Policy request.

We may store a payment reference, status, date, and account connection needed to trace a DANA or QRIS request. The same principle can apply to OVO, GoPay, bank transfer, or virtual account records. We do not need your wallet PIN to check a status.

Yes. Contact account support with the phone number linked to your account and explain whether you want access to a record or a correction. We first confirm account ownership, then respond about the available record. Some details may remain where security, dispute handling, or local law requires it.

Cookies can keep a session and selected settings available while you move from login to the mobile lobby. If you block or clear them, you may need to verify your account again or repeat a setting. Your browser controls cookie choices, while our policy explains their account purpose.

We retain account, security, and payment-reference records only while needed for account operation, status checks, disputes, or a legal obligation where local law permits. After that period, we remove the record or separate it from direct identifiers when the record still has a valid operational purpose.

Use account support and state that your request concerns the Privacy Policy or account security. Include the linked phone number, a short description, and any relevant date or payment reference. Do not include your password, wallet PIN, or one-time code. We verify ownership before discussing account records.