Reference

Open rupiah168 Legal access with clarity

rupiah168 Legal explains how we handle account access, personal data, cookies, payment records and policy requests before you open an account.

Account policyData handlingLocal access
rupiah168 Open rupiah168 Legal access with clarity
CONTACT PATHS

Switch to the right Legal contact route

A clear contact path helps us deal with Legal questions without exposing your account credentials. Use the account-area support route for access wording, data requests or a correction to a policy record. Include the issue, date and payment reference when the matter concerns QRIS, DANA or a bank transfer. We can then match the request to the correct account record and tell you what we need next, while you keep passwords and verification codes private.

Team online

Account access

For a Legal question about phone verification or account entry, use the support route inside your account area. Tell us whether access depends on local law in your case, and we will point you to the applicable policy step without asking for your password.

Wallet records

If a DANA, OVO, GoPay or QRIS record needs checking, send the payment date and reference through the cashier support path. We use those details to locate the entry, while your private wallet PIN and one-time code remain yours to protect.

Policy requests

For a data copy, correction or deletion request, choose the policy contact route shown after account login. Add the phone number linked to your account and the exact change you seek, so we can verify ownership before acting.

DATA PRACTICE

Browse how Legal safeguards your account

Legal handling is practical: we use account data to operate access checks, payment matching and policy responses, not to create vague claims about your identity.

Account data

We use the phone number and account details supplied during access checks to match your request with the correct record. This supports Legal responses about entry, payment status and policy changes without treating another person’s account as yours.

Cookie choices

Cookies can support session continuity and account-area navigation on your device. You can manage browser cookie choices, but changing them may affect access to policy pages or require another login before we can receive a Legal request.

Account security

Keep your password, phone access and one-time codes private. We use phone verification before account access where required, and our contact route will not need those secrets to assess a Legal or payment-record question.

Record retention

We retain account, payment and contact records for the period needed to address policy duties and trace requests. A DANA receipt, QRIS reference or bank transfer date can help us locate the relevant record when you ask.

Who to contact

The account-area support route is the right place for Legal questions about access, data or cookies. Describe the request in your own words and include only the account detail needed for us to verify ownership.

Request changes

You can ask us to correct account data, provide a copy or explain a retention decision through the policy contact route. We verify the account holder first, then confirm whether local law permits the requested action.

Check Legal answers before you join

These Legal answers cover the questions we expect before account creation: who may access the service, what data connects to a payment record, how cookies affect a session and where to send a request. Read the relevant answer before entering your phone number, especially if you are checking access from Indonesia or asking about a DANA, QRIS or bank transfer entry.

Legal describes our rules for account access, data handling, cookies, payment records and policy requests. It does not replace local requirements. Access depends on local law, so you should confirm that you may use the service before opening an account.

Yes. Account access depends on local law and may require phone verification before entry. If a local rule affects your request, we use the account-area contact route to explain the relevant condition rather than asking you to bypass it.

A record may include the payment method, date, amount, reference and account match for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use these details to trace a status question, not to request your wallet PIN.

After account login, use the policy contact route and request a data copy. Include the phone number linked to your account and a clear description of the records you seek. We verify ownership before responding or confirming what can be supplied.

You can request a correction through the account-area support route. Give the record date, payment reference or account detail that appears incorrect. We compare the request with our records and tell you whether the change is permitted under local law.

Cookies may keep a session active and help the account area recognise your device. Browser controls let you change cookie choices, although a stricter setting can require another login before you submit or receive a Legal request.

Share the account phone number, request type, date and relevant DANA, QRIS or bank transfer reference when applicable. Never send a password, wallet PIN or one-time code. The support route shown in your account area will identify the next verification step.