Reference

data paito sgp Privacy Policy

data paito sgp explains how we collect, use, store and protect the details connected with your account, wallet activity and device access.

Account dataWallet recordsDevice accessCookie choices
data paito sgp data paito sgp Privacy Policy
PRIVACY HELP PATH

Where to ask about your data

A clear contact path matters when a Privacy Policy question concerns your own account.

Account privacy request Ask us to access, correct or clarify personal details held with your account.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, send the receipt identifier and approximate…
Access security concern If a sign-in or device entry looks unfamiliar, tell us through account support and…
HANDLING YOUR RECORDS

What our Privacy Policy covers

We keep the Privacy Policy practical by linking each data use to an account action you recognise.

Account creation

When you open an account, we use the phone number and details you submit to create the account path and…

Sign-in protection

A phone verification step can be used before account access, especially when a sign-in comes from a new browser or…

Cookie controls

Cookies can remember practical choices such as a session or language setting, while certain cookies help us understand whether a…

Wallet references

A payment reference is used to match a wallet or bank record with an account action.

Retention choices

We retain account, security and payment references for the period needed to operate access, resolve a dispute or meet a…

Request changes

You can ask us to correct inaccurate details, explain a data use or consider removal of a record through the…

Privacy Policy questions from Indonesia

These Privacy Policy answers address the searches we expect before account access: what we collect, why wallet references appear, how cookies work and how to request a change. We keep the wording tied to data paito sgp account actions, including phone verification and device access. If your question concerns local availability, remember that access depends on local law.

It covers account details, phone verification, device and browser signals, cookies, wallet or bank references, retention and requests concerning your records. It also explains how we use those details for access security and receipt matching, including DANA, OVO, GoPay and QRIS references.

We use your phone number to create and verify account access, and to help match a privacy request to the correct account. If a new device attempts sign-in, the verification step may help protect your account from access that you did not request.

No. Our Privacy Policy describes payment references and receipt details used to reconcile an account action, not your private wallet password or secret code. A DANA, OVO, GoPay or QRIS reference can help locate a record without exposing credentials.

Use the account support path and state whether you want access, correction or clarification. Include the phone number connected with your account and enough detail to locate the request. We may verify your identity before discussing records or making a change.

Cookies can keep a session active, remember a language choice or help us identify a page-loading problem. You can adjust them in your browser settings. If cookies are restricted, the Privacy Policy notes that you may need to sign in again.

We retain a record for as long as its operational, security or legal purpose requires. Account access records, wallet references and device signals can therefore have different retention periods. When the purpose ends, we delete or anonymise the record where the process allows.

You can send a removal request through account support, and we will assess which records can be deleted. Some details may need limited retention for security, dispute handling or legal duties. We will explain that reason and apply access where local law permits.