Reference

rtp maha168 Privacy Policy for Your Account

Our Privacy Policy explains what rtp maha168 collects when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Account dataWallet recordsCookie choicesAccess requests
rtpmaha168.club page image
PRIVACY HELP

Get Help With Account Data Requests

A clear support route helps when you want to ask about a Privacy Policy request, correct account details or understand a wallet record. Start from the support link beside the login area and include the phone number or account detail you used for verification. For a DANA or QRIS question, include the transaction reference, but never send a password or full wallet credential.

Team online

Access request

Use the support route beside login to ask which account details we hold. We may ask for the verified phone detail linked to your account before discussing private records.

Correction request

If your name, phone detail or account record needs correction, tell us what changed and why. We compare the request with your existing verification step before updating data.

Wallet record query

For DANA, OVO, GoPay or QRIS records, share the reference and date shown in your wallet receipt. We use that detail to locate the matching account event.

DATA CONTROLS

How We Handle Your Privacy Choices

We keep this Privacy Policy practical by linking each data use to an account task: verification, session protection, wallet matching or support.

Account details

We collect details needed to create and verify your account, including a phone verification result. We use them to recognise your account during sign-in and to handle correction or access requests.

Device signals

When you sign in on a phone or desktop, we may record device type, browser details, IP address and session time. These signals help us identify unusual access and investigate login errors.

Cookie settings

Cookies can remember session choices and support page settings. You can manage cookie choices in your browser; changing them may require another sign-in or make some policy request steps less convenient.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to match a payment event with the correct account. We do not need your wallet password for that matching step.

Retention period

We retain account, device and wallet records only for the operational, security or legal purpose described in this Privacy Policy. When a record is no longer needed, our handling follows the applicable retention process.

Changes and questions

You can ask us to explain, correct or review the personal data connected with your account through the support path. Include a clear request and verified account detail so we can respond safely.

Privacy Policy Answers for Indonesia

These Privacy Policy answers focus on the requests you are most likely to make before opening an account or while checking a wallet record. We explain the account step, device data, cookies, payment references and local access wording in plain English. If your question is not covered, use the support route beside login and send only the details needed to identify your request.

It covers account details, phone verification, device and session signals, cookie choices, support records, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

We use the verification result to connect you with the correct account, protect sign-in and handle data requests safely. It also helps us avoid discussing private records with the wrong person.

Yes. When you sign in from a phone, we may record device type, browser signals, IP address and session timing. These details support session protection and diagnosis of access problems.

We use DANA or QRIS references, dates and status details to match a wallet event with your account and answer a receipt query. We do not ask for your wallet password.

Yes. Send an access or correction request through the support path beside login, using a verified account detail. We may ask follow-up questions before releasing or changing private records.

Retention depends on the reason for collection, such as account security, wallet matching, support or an applicable legal requirement. We remove or handle records according to the relevant retention process.

Access and data handling depend on local law. Where local law permits, we process the account and wallet details needed for your requested access; otherwise, availability or processing may be restricted.