Reference

pototo Privacy Policy For Your Account Data

Your account data, wallet records and device choices are explained in the pototo Privacy Policy, so you can decide what to share before opening an account.

Account dataWallet recordsCookie choicesContact requests

Explore Our Lobby Read FAQ

How DANA And QRIS Data Is Used

pototo Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We use the details you enter during account creation to open the correct account record and complete the phone verification step before access. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account help us match a deposit or withdrawal request to your account

1
and investigate a missing status. We do not need your wallet password to perform that matching. Activity linked to titles such as Lightning Roulette or Aviator may appear in account records when needed for statements, support checks or security checks. Cookies can remember login preferences and
2
help us understand which page failed to load. Access or eligibility depends on local law, and we may request additional details where local rules require it. This Privacy Policy describes these uses in plain terms and applies to requests made through our account contact route.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Where To Ask About Your Account Data

A clear support path helps when a Privacy Policy request meets a login or wallet-status issue.

Account data request Ask us to confirm, correct or explain account details through the signed-in contact route. Include your registered phone number so we can connect the request to the right record.

Wallet status check For DANA, OVO, GoPay or QRIS questions, share the transaction reference and displayed status. We can trace the payment record without asking you to disclose a wallet password.

Access concern If a phone verification step or login check blocks your request, tell us the device path you used, such as mobile browser or desktop. We will explain which data is needed.

ACCOUNT SAFEGUARDS

What We Keep Behind Your Login

Our Privacy Policy separates account operation from unnecessary exposure of your personal details. We limit account actions through login and phone verification, keep payment references for matching and dispute handling, and use…

Data handling

We use your phone number, account identifiers and submitted details to create access, verify the account and respond to requests. Payment references are used to reconcile wallet or bank activity.

Cookies

Cookies may retain a login preference or record a page event, such as a failed QRIS step. Your browser settings can remove stored cookies, although some account functions may then need repeating.

Login protection

Phone verification comes before account access, and we use the sign-in path to reduce mistaken account changes. Never send a password or wallet credential in a support message.

Record retention

We retain account and payment records for the period needed to operate the account, resolve status questions, protect access and meet applicable local requirements. You may ask why a record remains.

Change requests

You can request a correction when your name, phone detail or account record is inaccurate. We may verify the request through the signed-in account or registered phone before changing it.

Policy contact

Privacy questions belong in the account contact route, where we can connect your request to the relevant record. If you cannot log in, describe the issue without attaching sensitive credentials.

Privacy Policy Answers For Indonesia

These Privacy Policy answers cover the questions you may have before opening an account, including wallet records, cookies, phone verification and access requests. We apply the stated process to account activity from Indonesia where local law permits, with the account contact route available for follow-up.

It covers account details, phone verification, wallet and bank references, cookies, security checks, retention and requests to access or correct your record. It also explains how to contact us about those uses.

We collect the details needed for account creation and phone verification, plus records created when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Yes. The Privacy Policy covers transaction references and displayed statuses used to match a deposit or withdrawal request. We do not need your wallet password to investigate that payment record.

Cookies can remember a login preference and help identify a page or device event, such as a failed wallet step. Your browser controls can clear them, though some settings may need repeating.

Yes. Send a request through the signed-in account contact route and state whether you want access or correction. We may confirm your registered phone before releasing or changing account details.

We keep records for account operation, payment matching, access protection and applicable local requirements. Ask through the contact route for the reason a particular record remains and what request options apply.

Access or eligibility depends on local law. The Privacy Policy does not change those requirements, so check that access is permitted in your location before opening or using an account.

pototo Privacy Policy For Your Account Data

Where To Ask About Your Account Data

What We Keep Behind Your Login

Data handling

Cookies

Login protection

Record retention

Change requests

Policy contact

Privacy Policy Answers For Indonesia

01 What does the pototo Privacy Policy cover?

02 Which data is collected when I open an account?

03 Does the Privacy Policy cover payment references?

04 How does pototo use cookies on my phone?

05 Can I request a copy or correction of my data?

06 How long does pototo retain account records?

07 Can I use pototo where local law permits?

Related Pages