Reference

Open opmtoto Privacy Policy With Clarity

opmtoto Privacy Policy explains how we handle the details connected with your account, mobile browser, wallet activity and support requests, including steps around DANA and QRIS.

Account detailsWallet recordsCookie choicesAccess requests
opmtoto Open opmtoto Privacy Policy With Clarity
CONTACT PATHS

Find Privacy Help Beside Your Account

A clear contact path helps you act on this Privacy Policy without searching through unrelated pages.

Account privacy request Use the support route connected to your account to ask what personal details we hold, why they are used or how to request a correction. We may ask for a phone verification step before discussing account-linked records.
Wallet record question For DANA, OVO, GoPay or QRIS receipt questions, share the transaction reference rather than a wallet password or full private credential. We use the reference to compare payment status and keep the request limited to the relevant record.
Locked-out contact If your normal login route stalls, contact support without sending a password, one-time code or complete payment credential. Tell us the device path you used, such as a mobile browser or desktop browser, so we can route the privacy request safely.
DATA HANDLING

Explore The Privacy Controls We Apply

We handle Privacy Policy requests through practical account and payment checks rather than broad promises.

Account records

When you open an account, we use the details needed for account creation, phone verification, sign-in and support. We do not ask a game selection such as Bundesliga Mix Parlay to justify unrelated personal data collection.

Payment references

DANA, OVO, GoPay and QRIS activity can create references, timestamps and status records. Bank transfer and virtual account records may also be retained for reconciliation, receipt checks and account security without exposing your private wallet credential to support.

Browser cookies

Our cookie use supports session continuity, selected settings and basic security on the mobile or desktop browser path. You can adjust cookie controls in your browser; blocking essential cookies may interrupt sign-in or require you to repeat an account step.

Account security

Phone verification helps us distinguish an account holder from an unauthorised request. We may compare sign-in details, device signals and payment references when a request involves account recovery, wallet status or a change to personal records.

Retention approach

We retain account and transaction records for as long as needed for the stated service, reconciliation, security checks or legal duties. When a record is no longer needed, we delete it or remove identifying elements where practical.

Change requests

You can ask us to access, correct or remove eligible personal details through support. Include the account phone number or relevant reference, but never send a password or one-time code; we may verify ownership before making a change.

Browse Answers About Privacy Policy

These Privacy Policy answers address the searches we hear most often before account opening. They cover the records connected with your sign-in, the local wallet rails shown in your account, browser cookies, deletion requests and the practical route for contacting us. If your request concerns eligibility or access, that outcome depends on local law.

The opmtoto Privacy Policy covers account details, phone verification, device and browser signals, cookie settings, support conversations and payment references. It explains why we use those records, how we protect account access, how retention works and how you can request access, correction or removal.

Yes. Privacy Policy treatment includes references connected with DANA, OVO, GoPay and QRIS transactions, such as status, timestamp and reconciliation details. The relevant wallet or payment provider may also apply its own privacy terms, so check that provider's terms for its separate processing.

Use the support route linked to your account and ask for an account data request. Include the phone number or account reference needed to locate your record, but do not send a password or one-time code. We may complete phone verification before releasing account-linked details.

You can request correction or removal through support, and we assess the request against the record involved. Some payment, security or legal records may need to remain for reconciliation or legal duties. Where removal is possible, we delete or de-identify the relevant details.

Privacy Policy coverage includes cookies used for session continuity, selected settings and essential sign-in behaviour on your mobile browser. You can change cookie controls in the browser settings. If essential cookies are blocked, you may need to repeat login or another account step.

We keep records for the period needed for the service, account security, payment reconciliation or legal duties rather than applying one universal period to every record. Once a record is no longer needed, we delete it or remove identifying elements where practical.

The policy is written for our Indonesia account flow and local payment references, but access and eligibility depends on local law. We apply it where local law permits. If you need a location-specific privacy answer, contact support with your account region and request details.