Reference

pokemontoto Privacy Policy for Your Account

Your DANA, OVO, GoPay and QRIS activity is covered by the pokemontoto Privacy Policy, alongside your login details, device signals and support requests.

Account dataWallet recordsCookie choicesAccess requests

Explore Our Lobby Read FAQ

How Wallet Records Fit This Privacy Policy

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

We use account details to create your login, complete phone verification and protect access to the lobby. When you choose DANA, OVO, GoPay or QRIS, we may retain payment status, reference details and receipt checks needed to match activity to your account; bank transfer and virtual

1
account records can serve the same purpose. We do not treat a payment name as permission to use unrelated personal data. The Privacy Policy also covers device information from a mobile browser, cookie choices, support messages and security events. We keep records only for operational, dispute,
2
security or legal needs, then remove or anonymise them under our retention process. Some requests may be limited where local law permits, and account access depends on local law.

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

CONTACT YOUR DATA TEAM

Where To Ask About Account Data

A clear account route helps you raise a Privacy Policy question without sending personal details to the wrong place.

Account help path Use the help route after login for a Privacy Policy request. Include your account phone or email, but never send a password, wallet PIN or full payment credential in a message.

Wallet status query If DANA, OVO, GoPay or QRIS activity appears incorrectly, ask us to check the payment reference and account match. We can focus the response on that record rather than your full history.

Access request Ask for a copy, correction or permitted removal of personal data through the account support route. We may verify account ownership before acting on the request.

SIX DATA CONTROLS

Six Controls Behind Your Account Data

Our Privacy Policy is applied through practical account controls rather than broad promises. We separate login records from payment references, use cookies for stated purposes, check account ownership before sensitive changes and…

Collected data

We may collect your contact details, verification status, device signals, wallet references, support messages and account activity needed to provide access and protect the account.

Cookie choices

Cookies can remember session settings and help us detect unusual access. Your browser controls let you clear or restrict them, although some account functions may then require another login.

Account security

Phone verification and sign-in checks help us confirm that an account change comes from you. We may ask for additional proof before changing contact or wallet-related details.

Retention process

We retain records for account operation, payment matching, dispute handling, security review or legal duties. When a purpose ends, records are removed or anonymised under our process.

Correction requests

If your name, phone number or account record is inaccurate, contact us through the account path. We review the request against ownership checks before changing the record.

Policy contact

For a Privacy Policy question, identify the account using its attached phone or email and state the action you want. Requests remain subject to local law and account verification.

Privacy Policy Questions About Access

These answers cover the requests we expect you to make before opening or using an account. They focus on account records, cookies, wallet references and the steps needed to contact us. If your circumstances are unusual, use the account help path so we can assess the request under the Privacy Policy and local requirements.

It covers account and phone details, device signals, cookies, support messages, security events and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for account creation, verification, sign-in checks and account recovery. We may ask you to confirm ownership before changing it or disclosing account records.

Yes. The policy covers payment status, reference details and receipt checks linked to your account. It does not turn those wallet records into permission for unrelated uses.

Use the signed-in account help path and identify your account with its attached phone or email. State that you want a data copy, then complete any ownership check we request.

Yes. Tell us which detail is inaccurate and provide the account identifier linked to it. We review correction requests, verify ownership and apply any limits required where local law permits.

On a mobile browser, cookies can maintain your session, remember selected settings and help identify unusual access. You can clear or restrict them through browser controls, though another login may follow.

Retention depends on the record's purpose, such as account operation, payment matching, security, disputes or legal duties. We remove or anonymise records when that purpose ends, subject to local law.

pokemontoto Privacy Policy for Your Account

Where To Ask About Account Data

Six Controls Behind Your Account Data

Collected data

Cookie choices

Account security

Retention process

Correction requests

Policy contact

Privacy Policy Questions About Access

01 What does the pokemontoto Privacy Policy cover?

02 Why does pokemontoto need my phone number?

03 Does the Privacy Policy cover DANA and QRIS records?

04 How can I request my pokemontoto personal data?

05 Can I ask for incorrect account data to be changed?

06 How does the Privacy Policy handle cookies on mobile?

07 How long does pokemontoto keep payment and login records?

Related Pages