Reference

live sdy ini Privacy Policy For Your Account

The live sdy ini Privacy Policy explains what we collect when you open an account, use a mobile browser, or select DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesPolicy requests
live sdy ini live sdy ini Privacy Policy For Your Account
HELP PATH

Get Privacy Help Beside Your Account

A privacy request should be easy to connect with the right account record. Start from the account help route and include the email or phone detail used during registration, plus the subject…

Account request Ask us to access, correct or explain personal data through the account help route. Include your registered phone or email so we can compare the request with the account record before sharing any details.
Wallet record For a payment-data question, send the rail name and receipt reference, such as QRIS or DANA. We can trace the status without asking you to disclose a wallet PIN, password or security code.
Policy change If you want a correction or a restriction on a permitted data use, state the requested change clearly. We may ask for a verification step before acting so another person cannot alter your account record.
SECURITY PRACTICE

How We Handle Your Privacy Choices

We treat this Privacy Policy as part of the account process, not as a separate page with vague promises.

Account access

Before account access, we use the phone verification result and login events to reduce mistaken identity. We do not ask you to place a password, wallet PIN or one-time security code into a privacy request.

Payment matching

A payment record links the chosen rail with an account event and receipt reference. For DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, we use the minimum transaction detail needed to check status.

Cookie control

Essential cookies support login continuity, security checks and page settings. Optional cookies may help us identify page faults. Your browser controls can clear stored cookies, although clearing essential data may require another account sign-in.

Device signals

On a phone, tablet or desktop browser, we may receive device and browser signals such as type, version and session time. These signals help detect unusual access; they are not a request for contacts, photos or unrelated device files.

Retention timing

We keep account, payment and security records while they serve access, reconciliation, dispute handling or legal needs. When a record no longer has one of those purposes, our process removes it or limits its use.

Your request

You can ask for a copy, correction, clarification or permitted restriction by using the account help route. We verify the requester, review any conflicting legal or security need, then explain the action taken or why a limit applies.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain wallet records, mobile access, cookies, account verification and requests to change stored data. If your situation involves a particular receipt or login event, use the support path above and include only the reference needed to locate it.

It covers account details, phone verification, login and device events, cookies, support requests, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use these records for access, reconciliation, security, support and legal needs where local law permits.

Phone verification helps connect an account request with the person who created the account and helps detect unusual access. We use the result as an account-security signal; you should not send your password, wallet PIN or one-time code in a privacy request.

Yes. The Privacy Policy includes the payment rail selected, a receipt or transaction reference, account matching details and the status returned for DANA or QRIS activity. We use those fields to reconcile a record and do not need your wallet PIN to check its status.

When you use a mobile browser, we may receive device type, browser version, IP address, session time and security events. These signals help maintain account access and identify unusual sessions. We do not need unrelated phone files, contacts or photos for this purpose.

You can ask for access, a copy, correction or clarification through the account help route. Include your registered phone or email and describe the record concerned. We verify the request first, then assess security, dispute and legal requirements before responding.

Retention depends on the purpose: access, payment matching, security, dispute handling or a legal requirement. We keep a record while that purpose remains active, then remove it or restrict its use under our process. A receipt reference may remain while a payment question is unresolved.

Yes. Account access and any related data request depends on local law. Where local law permits, we assess your request and explain the available action. If a security or legal duty limits the response, we describe that limit without asking for unnecessary wallet or login secrets.