Reference

axiata4d Privacy Policy for Indonesia

Our Privacy Policy explains how axiata4d handles your account details, mobile-browser activity and payment records when you use DANA, OVO, GoPay or QRIS.

Clear data purposesWallet record contextAccount request path
axiata4d axiata4d Privacy Policy for Indonesia
REQUEST SUPPORT

Get Help With Your Policy Request

A clear support path matters when a privacy question sits beside a login or wallet issue. From your account area, describe the request, add the relevant transaction reference if it concerns DANA or QRIS, and avoid sending a password or wallet PIN. We use the submitted details to identify your account and respond to the specific request.

Team online

Policy question

Ask which account details, cookie records or payment references relate to your request. Include your registered phone number without sharing your password, so we can locate the correct account safely.

Data correction

If your phone, name or account record needs correction, tell us what appears wrong and what should replace it. We may verify the request before changing a protected account field.

Wallet record check

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, provide the reference and status shown in your account. We use those details to separate payment support from privacy requests.

ACCOUNT CLARITY

What We Do With Your Account Data

We treat your account record as a working service record, not a reason to collect unrelated details.

Purpose-led collection

We use phone, account and transaction details for access, payment matching, support, security checks and required records. We do not ask for unrelated personal details simply because you open the lobby.

Cookie controls

Cookies and similar browser signals can keep your session active, remember basic preferences and help identify unusual access. You can manage browser settings, though some account steps may then need repeating.

Login protection

Phone verification is part of account access, and we may compare session or device signals when activity looks unusual. Never send your password, wallet PIN or verification code through support.

Retention decisions

We retain account, support and payment references only for the period needed for service, dispute handling, security checks or legal duties. A deletion request may not remove records that must remain.

Who handles requests

Our account support route receives privacy questions, correction requests and access requests. We may ask for account verification before discussing personal data, especially when a request involves wallet records.

Changing your details

Tell us which field or record needs changing and why. We check the request against your account before applying an update, then explain if a payment or legal record cannot be altered.

Privacy Policy Answers for axiata4d

These answers address the searches we receive about the axiata4d Privacy Policy, including payment records, cookies, account access and data requests. If your situation involves a specific DANA, OVO, GoPay, QRIS or bank reference, include that reference through the account support route.

The Privacy Policy covers account details, phone verification, browser cookies, device signals, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and verify account access, help identify the correct account during support and reduce confusion when a wallet or payment reference needs checking.

Yes. The Privacy Policy explains that DANA and QRIS references may be used to match payment status, investigate a transaction question, support your account and meet applicable record duties.

Yes, where local law permits. Send the field that needs correction through the account support route. We may verify your identity before changing phone, name or other protected account details.

Cookies can keep your mobile-browser session connected, remember basic preferences and help identify unusual access. Browser settings can restrict them, but login or verification steps may need to be repeated.

We keep payment references for the period needed for account servicing, dispute handling, security checks or legal duties. A deletion request may not remove records that must remain for those purposes.

Where local law permits, you can ask for the account data connected with your request. Include your registered phone number and request type, but never include a password, wallet PIN or verification code.