Reference

modetoto Privacy Policy in Plain English

Our Privacy Policy shows how modetoto collects, uses and protects the details connected with your account, device and wallet activity.

Account clarityWallet contextPhone verification
modetoto modetoto Privacy Policy in Plain English
CONTACT PATHS

Where to ask about your data

A clear contact route helps when a privacy question is tied to a real account step. Start from the support path shown on our site and include your registered phone number only when requested. We use the smallest useful set of details to locate a record, check a wallet reference or respond to a request about your Privacy Policy rights.

Team online

Privacy request

Ask us to access, correct or explain personal data connected with your account. We may request phone verification before discussing account-specific records, helping us avoid releasing details to the wrong person.

Wallet question

For DANA, OVO, GoPay or QRIS records, share the transaction reference and approximate date rather than your wallet password. We use those details to trace status without asking for private wallet credentials.

Login concern

If a sign-in alert or phone verification issue concerns your privacy, tell our support desk what happened and which device you used. We can review the security event before changing account details.

HANDLING PRACTICE

Six checks behind your privacy choices

We handle privacy as part of ordinary account operations rather than as a separate promise. The checks below explain how we limit collection, protect sessions, manage cookies and respond to requests.

Purpose-based use

We use phone, account and transaction details for stated needs such as verification, account support, security checks and payment matching. We do not ask for wallet passwords to confirm DANA, OVO, GoPay or QRIS status.

Cookie choices

Cookies and similar device signals help keep you signed in, remember settings and identify unusual sessions. Your browser controls can restrict optional cookies, although some account or security functions may then behave differently.

Account security

Phone verification is used before account access and sensitive changes. We may examine device type, browser events and sign-in patterns when a session looks unusual, then ask for another account step.

Retention controls

We keep records for as long as needed for the purpose collected, including security, payment matching, disputes and legal duties where local law permits. When a record is no longer needed, we delete or de-identify it.

Access requests

You can ask what personal data we hold, request a correction or ask about deletion through our policy contact route. We may verify ownership first, especially when your request concerns account access or wallet activity.

Device changes

Moving from a mobile browser to desktop can create a new security event because the device context changes. If that affects access to Live Roulette or Great Rhino Megaways, support can check the event.

Privacy Policy questions from Indonesia

These Privacy Policy answers cover the questions we expect before you create an account. They focus on Indonesian payment records, device checks, account requests and the legal conditions that affect access. If your situation is specific, use the policy contact route rather than sending wallet passwords or unnecessary documents.

It covers account details, phone verification, device signals, cookies, security events, payment references and support requests connected with our site. It also explains retention, your available requests and access where local law permits.

We use your phone number to create and protect the account, complete phone verification before access and help locate the correct record when you contact support. We do not use it to request your wallet password.

Yes. The policy covers the payment reference, status and timing details needed to match DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity with your account, without requiring private wallet credentials.

We may collect device type, browser details, session signals and security events. These records help keep a mobile login working, identify unusual access and investigate why a new desktop session may require phone verification.

Use our policy contact route and describe whether you want access, correction or deletion of eligible records. We may verify your phone or account ownership first, then respond according to the rules that apply where local law permits.

Retention depends on why the record exists. We may keep account, payment and security records for support, dispute handling, fraud prevention or legal duties, then delete or de-identify them when that purpose ends.

Yes. Our Privacy Policy explains cookies used for sessions, settings and security. You can adjust browser controls on your phone, but restricting some cookies may affect sign-in, phone verification or access to account pages.