Reference

Open piramid slot Privacy Policy for Clear Data Choices

piramid slot Privacy Policy shows what we collect when you create an account, sign in, use DANA or QRIS, and contact our support team.

Account dataWallet recordsCookie choicesAccess requests
piramid slot Open piramid slot Privacy Policy for Clear Data Choices
CONTACT OUR TEAM

Contact Us About Your Privacy Policy

A direct request helps us find the right account record without exposing it to the wrong person.

Account privacy request Send your request through the account support path and state the action you want…
Wallet record question When your question concerns DANA, OVO, GoPay, QRIS, bank transfer, or virtual account data…
Access or cookie help If a phone browser keeps a cookie or your account access stalls, tell us…
HOW WE HANDLE DATA

Explore piramid slot Privacy Controls

Privacy choices work best when they match the way you actually use the account. We record the steps needed for sign-in, phone verification, wallet status checks, and support replies, while cookies help…

Account data use

We use your account name, contact details, phone verification result, and sign-in events to create access, protect the account, and answer privacy requests. We do not need unrelated personal details for a request, so share only what helps us identify your record.

Payment references

A DANA, OVO, GoPay, or QRIS reference helps us match a wallet event with your account. Bank transfer and virtual account records may include the route selected, amount status, and reference code, but never ask us to send your wallet password.

Cookies on your device

Cookies can retain access preferences, session status, and security signals on the phone or computer you use. Clearing them may require another sign-in or phone verification step. Your browser controls let you remove or block cookies, though some access functions may change.

Account security checks

We use sign-in events, device signals, and phone verification to identify unusual access and protect your records. If a security check pauses the account, our support route can explain the next step after confirming that you control the account.

Retention of records

We keep account, payment, device, and support records only for the period needed for the purposes described in this Privacy Policy or for applicable legal duties. When a record is no longer needed, we remove it or separate it from direct account details.

Change or deletion request

Ask us to correct, access, restrict, or delete eligible data through the account support path. Include your account contact and the exact record involved. We may verify ownership first, then explain any reason a specific record must remain available.

Browse Privacy Policy Answers for Indonesia

These Privacy Policy answers address the searches we receive most often before an account is opened. We cover the account step, phone verification, cookies, wallet references, device access, and requests made from Indonesia. If your situation is different, contact us with the smallest useful set of account details and we will direct the request through the correct privacy path.

It covers data connected with account creation, phone verification, sign-in, device access, cookies, wallet references, payment status, and support messages. It also explains why we use those records, how long they may remain, and how you can ask for access or a correction.

Phone verification helps us connect an account request to the person seeking access and helps protect account records from an unauthorised request. We may use the verification result when you ask about DANA, QRIS, sign-in history, correction, restriction, or deletion.

Yes. The policy covers references created when you select DANA, OVO, GoPay, or QRIS, including payment status and the account connection needed to answer a receipt question. We do not ask for your wallet password, and you should not send it.

Use the support contact path connected to your account and write that you want an access request. State the account contact used during the account step and identify the record you want. We may complete phone verification before giving a response about your data.

You can request a correction or deletion through the same privacy contact route. Tell us which record is wrong or no longer needed. We check account ownership first, then explain the result. Some records may need to remain for applicable legal duties.

Cookies can keep session and access preferences on your phone, so clearing them may lead to another sign-in or phone verification step. Your browser settings control cookie removal. If access changes after that step, contact us without sending private credentials.

The policy is available for you to read, while account access and eligibility depends on local law. We apply the data choices described here to the extent permitted for your location and can explain the request path when you contact our support team.