Reference

merahtoto99 Privacy Policy, Made Clear

The merahtoto99 Privacy Policy explains what we collect when you open an account, sign in on mobile, or use DANA, OVO, GoPay and QRIS.

Account dataWallet detailsDevice signalsCookie choices
merahtoto99 merahtoto99 Privacy Policy, Made Clear
DIRECT POLICY HELP

Get Privacy Answers Near Your Account

A privacy question should not interrupt your account path. We ask you to use the support contact shown inside your signed-in account, especially when a phone verification result, wallet reference or cookie setting needs context. Include the email or phone linked to your account, the relevant date and a short description; never send a password or full wallet credential. We can then locate the right record without asking you to repeat sensitive details.

Team online

Account contact

Use the signed-in account contact when you need to ask why a phone verification record, sign-in event or profile detail appears in our Privacy Policy data.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account concerns, send the transaction reference and date so we can separate payment status from personal data.

Access request

Ask through the same account support route to request a copy, correction or removal assessment. We may confirm account ownership before discussing private records.

YOUR DATA CONTROLS

How We Handle Your Privacy Choices

We keep this Privacy Policy connected to the actions you take, rather than treating every detail as permanent profile data.

Account records

We use your account details to create access, match your phone verification and protect the sign-in path. If a name or contact detail changes, ask us to check the stored record.

Cookie settings

Cookies can keep a session open and help us detect broken pages on mobile or desktop. You can clear browser cookies, although signing in again may be required afterward.

Device protection

Device and connection signals may help identify unusual sign-in behaviour or repeated access errors. They support account security and are not a replacement for your password or phone verification.

Wallet matching

DANA, OVO, GoPay and QRIS references help us reconcile a cashier action with your account. We use the reference and status needed for that check, not your wallet password.

Data retention

Records remain while they serve account security, transaction tracing, dispute handling or a legal requirement. When that purpose ends, we assess deletion or aggregation under the applicable rule.

Your requests

You may ask for access, correction, restriction or deletion assessment through account support. We confirm ownership first and explain any reason a record must remain available.

Privacy Policy Questions For Indonesia

These Privacy Policy answers address the account actions you are most likely to make on merahtoto99, from first phone verification to a QRIS status check on mobile. We keep the wording practical so you know what to send, what we may confirm and when access depends on local law. If your question is not listed, use the account support path with the smallest useful set of details.

It covers account and contact details, phone verification, sign-in and device signals, cookies, wallet references, support messages and retention. It also explains how we handle requests to access or correct data connected with your account.

Phone verification helps us confirm that the person opening or entering an account controls the stated contact route. We may retain the result and related security event so we can investigate access problems or unusual sign-in activity.

No. For DANA, OVO, GoPay and QRIS, we use the transaction reference and wallet status needed to match a cashier action. You should never send a wallet password, one-time code or full credential through support.

Yes, you can ask through the signed-in account support route for a copy of data connected with your account. We may confirm ownership using your account contact before releasing private records or describing their contents.

Send the requested correction through account support and identify the affected field, such as a contact detail or profile name. We compare the request with account records and may ask for a verification step before changing it.

The period depends on the purpose and applicable rule. Security events, wallet references and transfer records may remain while needed for account protection, reconciliation, disputes or legal duties, after which we assess deletion or aggregation.

You can request a deletion assessment through account support. We review the request against security, transaction tracing and legal needs; where local law permits, data no longer needed for those purposes can be removed or made non-identifying.