Reference

merahtoto Privacy Policy for Your Account

Our Privacy Policy shows how we handle your account data, phone verification, wallet records and mobile-browser cookies before you open the lobby.

Account dataWallet recordsCookie choicesSecurity requests
merahtoto merahtoto Privacy Policy for Your Account
CONTACT ROUTES

Ask Us About Privacy Policy Requests

A direct request helps us locate the right account record without unnecessary sharing. When you contact us about this Privacy Policy, include your registered phone detail, the subject of your request and any relevant receipt reference; we use those details to confirm the account before discussing personal data. Our support route also covers cookie questions, account closure requests and corrections to inaccurate records.

Team online

Account data request

Use the account support route to ask what personal data we hold, why it is used or which account step created the record. We verify ownership before replying.

Wallet record query

For a DANA, OVO, GoPay or QRIS receipt question, include the payment reference and account phone detail. We use the cashier support path to match records safely.

Cookie or access help

Tell us whether the issue appears on a mobile browser or desktop session. We can explain cookie choices, login events and the privacy steps linked to your device.

DATA PRACTICES

Protect Your Data Through Clear Steps

Privacy depends on practical handling at each account stage, from the first phone check to a later wallet receipt query.

Collection at account opening

We collect the details needed for account creation and phone verification before account access. A request should use the registered contact route so we can separate your record from another account.

Payment data handling

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are kept for account matching, receipt checks and transaction support. We do not treat a wallet label as your full identity.

Cookie choices

Cookies can retain session settings and help us understand whether a login attempt comes from a familiar browser. You can review browser controls, although changing them may affect account access.

Account security

We review login events, device signals and phone verification status when protecting an account. If a session looks unusual, we may ask for additional account confirmation before discussing personal data.

Retention approach

We retain account, payment and support records only for operational, security and legal needs. When a record is no longer required for those purposes, we assess it for deletion or restricted handling.

Changes and corrections

You can ask us to correct account data, explain a processing purpose or update a privacy choice. Include the requested change and registered phone detail so our team can check ownership.

Find Answers About Privacy Policy

These Privacy Policy answers address the account and payment questions you are most likely to have before opening an account. We keep each response tied to a practical step, such as phone verification, cookie control or a wallet receipt request, so you can decide what to do next.

It covers account details, phone verification, wallet and transaction references, cookies, device signals, login events, support requests, retention and the process for asking us to correct or explain your data.

Phone verification helps connect an account request to the correct person before access or a data request is handled. It also helps us protect account conversations from an unrelated device.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those records are needed for matching, support or security checks.

Contact our account support route with your registered phone detail, the data you want corrected and the reason for the request. We confirm ownership before making or discussing an account change.

On a mobile browser, cookies can keep a session active and record selected settings. Your browser controls can change cookie behaviour, but removing necessary cookies may interrupt login or account access.

We keep personal, payment and support records while they serve operational, security or legal needs. We then assess whether to delete, restrict or retain a record under an applicable duty.

Yes. Send a Privacy Policy request through the account support route and ask about access to your record. We verify the account first, then explain the relevant operational handling without exposing another account.