Reference

pajak toto Privacy Policy for Your Account Data

Our Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or check wallet status through DANA, OVO, GoPay and QRIS.

Account recordsWallet activityDevice choicesCookie controls
pajak toto pajak toto Privacy Policy for Your Account Data
CONTACT PATHS

Browse Privacy Help Beside Your Account Route

A clear contact path matters when a privacy question appears during sign-in or a wallet check.

Account help route Open the account help route beside the cashier path when you need a copy…
Payment reference Share the date, rail name and reference for DANA, OVO, GoPay, QRIS, bank transfer…
Access concern If phone verification or sign-in blocks a privacy request, tell us which device path…
DATA HANDLING

Explore How We Handle Your Privacy Requests

Our privacy work follows the account steps you can see: phone verification, sign-in, wallet checking and support contact.

Collection

We collect details you submit during account opening and phone verification, plus sign-in, device and session signals needed to connect…

Cookies

Cookies and similar storage can remember session choices and help the account path load correctly.

Account security

Phone verification, sign-in records and device signals help us check account access.

Retention

We keep account, security and transaction records only as long as needed for the stated purpose, support follow-up or a…

Data requests

You can ask for access, correction or clarification through the account help route.

Policy changes

If this Privacy Policy changes, we will place the revised wording on this page and show the effective date so…

Check Privacy Policy Answers Before Opening

These Privacy Policy answers cover the searches we expect before account opening: what we collect, why wallet references appear, how device activity is used, and how you can contact us. Read the relevant answer first, then use the account help route if your request needs an account-specific check.

It covers account details, phone verification, device and session signals, cookies, wallet references, support requests, retention and your available requests for access or correction.

We do not ask you to send a wallet password or PIN through support. Our records may show a payment reference or status for DANA and QRIS activity.

Phone verification helps connect account access to the correct person and supports security checks. We record the verification result and related account event, subject to local law.

Cookies can keep a sign-in session and remember selected settings. You can manage or remove them through your browser, although some account functions may then need another sign-in.

Yes, where local law permits. Use the account help route and state that you want an access request. We may verify account ownership before releasing records.

You can request a correction through account help. Include the field that appears wrong and the accurate replacement; we may ask for verification before changing it.

Use the account help route beside the cashier path and include your account identifier and relevant reference. Do not include your password, verification code or wallet PIN.