Reference

datukqq Privacy Policy For Your Account

Your account details, phone verification and wallet records have a clear place in the datukqq Privacy Policy.

Account dataPhone checksWallet recordsCookie choices

What Our Privacy Policy Covers

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

Our Privacy Policy covers the information you provide during account creation, including your name, contact details and phone verification result. We also record sign-in events, device and browser signals, support requests, and transaction references needed to match a DANA, OVO, GoPay, QRIS, bank transfer or virtual

1
account action to the correct account. Payment records can include a reference, amount and status, while we do not treat your wallet password as a detail for ordinary support chats. We use these records to operate account access, identify unusual sign-in activity, answer privacy requests and
2
meet applicable obligations. Where access is discussed, it depends on local law. The policy applies to account activity connected with our Indonesia-facing pages and may change when our data practices change.

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

CONTACT ROUTES

Privacy Help Beside Account Support

A privacy question should not leave you searching through the lobby. Use the support route shown in your account help area and include the email or phone detail connected with your account…

Account help Open the account help route after signing in and select the privacy subject. We can use your verified phone detail to locate the request while keeping wallet passwords out of the conversation.

Payment reference For DANA, QRIS, OVO or GoPay questions, send the transaction reference and status shown in your account. That gives our support team a specific record to check without requesting unnecessary wallet access.

Access concern If your account cannot open after phone verification, use the same support route and describe the device and browser path. We will separate an access issue from a privacy request before responding.

CONTROL CENTRE

How We Handle Data Requests

We keep this policy practical: you can ask what account data we hold, why a record exists, and how to correct a detail that no longer matches your account.

Account collection

When you open an account, we collect the details needed for registration and phone verification. We use those details to connect your sign-in, support request and transaction references to the right account.

Cookie controls

Cookies and similar browser signals can help keep your session working and remember selected settings. You can review browser cookie controls on your mobile or desktop path, although disabling them may affect account access.

Security checks

A phone verification step helps distinguish your account access from an unrecognised attempt. We may compare sign-in, device and browser signals when an access pattern needs checking, without asking for your wallet password.

Payment records

A DANA, QRIS, OVO, GoPay, bank transfer or virtual account action may leave a reference and status record. We retain those details only as needed for account matching, support checks and applicable obligations.

Retention requests

Retention depends on the reason a record exists and any applicable legal requirement. Ask through account help if you want us to explain a record period or assess whether a detail can be removed.

Correction path

To request a correction, identify the account contact and describe the field that is wrong. We may ask for a phone verification step before changing it, so another person cannot alter your account data.

Privacy Policy Questions From Indonesia

These answers address the privacy searches we hear most often from people opening or using an account in Indonesia. They cover the records connected with access, wallets, cookies and support, including the practical details needed to send a clear request. If your situation is not listed, use the account help route and refer to the Privacy Policy in your message.

It covers account details, phone verification, sign-in and device signals, cookies, support messages, and transaction references. It also explains how we handle DANA, OVO, GoPay, QRIS, bank transfer and virtual account records connected with your account.

Phone verification helps connect the person opening an account with the correct account record. It can also support an access check when a sign-in from a new browser or device does not match earlier activity.

Yes. Use the account help route, identify the contact detail linked with your account, and name the field that needs correction. We may request phone verification before changing it to prevent an unauthorised update.

We may keep a transaction reference, amount and status so a DANA or QRIS action can be matched with your account. Send the reference through support if you need a record checked, and do not send your wallet password.

Yes. Cookies and browser signals can support session continuity and selected settings when you use a mobile browser. Your browser controls let you manage cookies, but turning them off may affect sign-in or other account functions.

The period depends on why the record exists and any applicable legal requirement. You can ask through account help for an explanation of a particular record, including a support message or payment reference.

Send it through the support route shown in your account help area and use a clear subject such as access, correction, cookie choice or data record. Access to the service depends on local law, and we may verify your account first.

datukqq Privacy Policy For Your Account

Privacy Help Beside Account Support

How We Handle Data Requests

Account collection

Cookie controls

Security checks

Payment records

Retention requests

Correction path

Privacy Policy Questions From Indonesia

01 What does the datukqq Privacy Policy cover?

02 Why does datukqq need phone verification?

03 Can I ask datukqq to correct my account data?

04 How are DANA and QRIS records handled under this policy?

05 Does the Privacy Policy explain cookie use on mobile?

06 How long does datukqq keep personal data?

07 Where can I send a Privacy Policy request?

Related Pages