Reference

Privacy Policy For Your omototo Account

omototo Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet detailsCookie choicesAccess requests
Explore Our Lobby Read FAQ
omototo Privacy Policy For Your omototo Account
HELP WITH DATA

Three Ways To Ask About Privacy

A clear support route helps you act on this Privacy Policy without searching through unrelated pages. Sign in when possible so we can connect your request to the right account record, but tell us if access itself is the problem. Include the email or phone detail attached to your account, the wallet rail involved and the change you want us to check. We use those details to reduce back-and-forth and keep your request focused.

Team online

Account access

If phone verification or a device session blocks your request, use the account support path and explain which step stopped. We can identify the relevant account record without asking you to send a wallet password or full payment credentials.

Wallet records

For a DANA, OVO, GoPay or QRIS data question, include the transaction date and visible reference from your account. Do not send your wallet PIN. We use the reference to locate the matching status while keeping sensitive credentials out of the request.

Policy requests

Ask us for access, correction or deletion by naming the account detail you want changed. We may ask for a reasonable identity check before acting, so a request cannot be used to alter another person’s account or payment history.

ACCOUNT SAFEGUARDS

Six Privacy Controls We Keep Visible

Privacy work is easier to understand when each control has a practical purpose. We separate sign-in details from wallet credentials, limit account access by session, and use device signals to investigate unusual…

Account security

Phone verification is part of account access, and we may use sign-in, session and device signals to protect your account. We do not ask you to share a wallet PIN through support. Keep your login details private and sign out on shared devices.

Cookie choices

Essential cookies help maintain a signed-in session and keep policy pages working. Other cookie uses are handled according to the choices available in your browser or account path. Removing cookies can require you to sign in again on the same device.

Payment separation

DANA, OVO, GoPay and QRIS status details help us match a payment event to your account. We use the payment reference and status needed for that task, rather than requesting your wallet PIN or unrelated wallet content.

Retention period

We retain account, security and payment records for as long as needed for account administration, dispute checks and applicable legal duties. When a record is no longer needed for those purposes, we remove it or separate it from direct account identification.

Change requests

You can ask us to correct an account detail or request deletion through support. Include the specific field, not a copy of your password. We may preserve limited records when account security, payment reconciliation or local law requires it.

Contact route

The account support path is where you can ask who handles a data request, what detail we hold and why it is used. If you cannot sign in, describe the access issue and provide only the account contact detail needed to locate your record.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions you may have before opening an omototo account. We keep the wording practical: what we collect, why we use it, how you request a change and what happens when a record must remain. Access depends on local law, so your available rights can vary by location.

It covers data linked to your account, phone verification, sign-in sessions, device signals, cookie use and payment status. It also explains retention, security steps and how to ask for access, correction or deletion where local law permits.

We use your phone detail as part of the account access and verification path. It helps connect the correct sign-in to your account and supports security checks. We do not need your wallet PIN to handle a Privacy Policy request.

Yes. The policy covers payment references and status connected with DANA, OVO, GoPay and QRIS. We use those details to match an account event and resolve a receipt or status question, not to access unrelated wallet content.

Use the account support route and ask for a data access request. Name the account contact detail you use and describe the records you want. We may complete an identity check first, then respond according to applicable local law.

Yes. Send a correction request through support and identify the exact field that is wrong. If the change affects phone verification, payment matching or account security, we may ask for an additional check before updating the record.

You can ask for deletion through the support path. We assess the request against account security, payment reconciliation and legal duties. Where local law permits deletion, we remove or separate the eligible record and explain any data that must remain.

Retention depends on why the record exists. Session and security details support account protection, while DANA, OVO, GoPay, QRIS, bank transfer and virtual account records may support reconciliation or legal duties. We remove or separate records when those needs end.

Related Pages

omototo Indonesia FAQ bola396 bet66 Speed Baccarat