Reference

doktor88 Privacy Policy For Your Account

DANA, QRIS, device access and account details are covered in the doktor88 Privacy Policy, so you can see what we collect before opening an account.

Account dataDevice accessWallet contextPolicy requests
doktor88 doktor88 Privacy Policy For Your Account
ACCOUNT HELP

Where To Ask About Privacy Policy

A clear support route matters when a privacy question appears beside login or the cashier path. We ask you to use the support link connected to your account area and include the email or phone detail used for access, without sending a wallet password. Our team can sort a data access request, receipt reference or correction request while keeping the conversation tied to your account.

Team online

Access request

Ask what account, device or payment-reference data is connected with your profile. Include your registered phone detail so we can locate the right account without requesting your wallet password.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the relevant receipt reference through account support. We use it to check the matching status without exposing unrelated account data.

Change request

If a phone detail, account field or communication choice needs correction, tell us what should change and why. We may ask for a phone verification step before applying the request.

SECURITY PRACTICE

Six Privacy Controls Behind Your Account

We handle Privacy Policy requests as account work, not as a generic message. That means checking the account step, payment reference or device signal involved before changing a record.

Collected data

We may hold account identity details, phone verification status, login records, device signals and payment references. The Privacy Policy connects each category with the access, security or support purpose it serves.

Cookie choices

Cookies or similar browser signals can help retain session settings and identify unusual sign-in behaviour. You can ask support which browser data is relevant to your account and request clarification.

Account security

Phone verification before account access helps us distinguish your sign-in from an unfamiliar attempt. Keep your verification details private, and contact support if a device path looks different.

Retention periods

We retain records for the operational, dispute-handling or legal period connected with their purpose. A removal request can be assessed against any record that still needs to be kept.

Who to contact

The account support route is the first contact for Privacy Policy questions, including access, correction, removal and payment-reference concerns. State the request clearly so we can direct it correctly.

Requesting changes

Send the account field or data category you want changed, along with your registered phone detail. We may verify ownership before updating information or confirming what can be removed.

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the account details Indonesian customers ask about before access. You can use the same support path for a personal request involving login, device signals, wallet references or phone verification, where local law permits.

It covers account details, phone verification, login and device signals, cookies, payment references and support requests. It also explains why we use each category, how retention works and how you can request a change.

Yes. The policy covers references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. We use those references to match account status or answer a receipt question, not to request wallet passwords.

Phone verification helps connect an account access request with the person who registered the account. It also supports checks when a new device, unusual login signal or correction request needs confirmation.

Yes. Use the account support route and identify the registered phone detail or email connected with access. We can assess a request for account, device, cookie or payment-reference data where local law permits.

Send support the field that needs correction, the accurate replacement and your registered account detail. We may complete a phone verification step before changing the record or confirming the result.

Retention depends on the purpose of the record, such as account security, payment matching, dispute handling or a legal requirement. We assess removal requests against those purposes rather than deleting every record automatically.

The policy is available for account questions, while access or eligibility depends on local law. If you are unsure about a request from Indonesia, contact account support and describe the exact data concern.