Reference

Open rajampo Legal terms before account access

rajampo Legal gives you a clear view of access conditions, account checks and data choices before you open an account.

Access depends on local lawAccount details stay reviewablePayment records have a clear pathCookie choices remain available
rajampo Open rajampo Legal terms before account access
CONTACT ROUTES

Ask about Legal through your account path

A policy question should not leave you guessing which team to reach. We route Legal requests through the account help path, with payment context available when…

Account access request Use the account help path when Legal wording affects login or phone verification.
Payment record query For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, include the…
Policy change request Ask us to correct account details, clarify a clause or explain a policy update…
DATA PRACTICE

Explore how our Legal controls work

Legal is also about what happens to the details you share after an account step. We separate access checks, payment records and support requests so each request has a clear purpose.

Data purpose

We use account details for access checks, phone verification, support matching and payment record handling. A request about Mobile Legends or another lobby title does not require unrelated personal details.

Cookie choices

Cookies can support sign-in continuity and policy-page preferences. You can review available cookie choices in the browser path, then decide whether those settings remain active on your device.

Account security

Phone verification is part of the account access step. Keep your phone and login details private, and contact support through the account path if access activity does not match your actions.

Payment records

A DANA, OVO, GoPay or QRIS receipt helps us match a wallet event to the correct account. Bank transfer and virtual account references serve the same checking purpose.

Retention questions

Our Legal wording explains why certain account, verification and payment records may remain available after a request. Ask support which record category applies before requesting a change.

Requesting changes

You can ask us to correct personal details, explain stored records or clarify a policy clause. Include the affected account step and your requested outcome in the support path.

Browse answers about rajampo Legal access

These Legal answers focus on the decisions you may face before account access or when checking a policy record. We keep the route practical: read the clause, confirm the account step, and use support when the wording or data request needs a direct answer. Access remains where local law permits, including for Indonesian account holders using local payment rails.

rajampo Legal covers access conditions, account information, phone verification, cookies, payment records, retention, policy changes and the support route for questions about those matters.

Access depends on local law and is available where local law permits. Your location and applicable eligibility rules can affect account access, so check the Legal terms before completing the account step.

Phone verification helps connect an account request to the correct contact detail and supports access security. Keep the number available during account setup, and ask support if the verification step stalls.

DANA and QRIS receipts may be used to match a payment event with your account record. For questions, provide the receipt reference and account phone number through the support path.

Yes. Use the account support path to request a correction or clarification, identify the affected detail, and explain the change you want. We may need to confirm account ownership first.

Cookies may remember browser settings or sign-in continuity. The Legal path explains available choices, and you can review those settings from the browser you use to reach the account.

Contact us through the account help path and name the clause, account step or payment record involved. Include relevant DANA, OVO, GoPay, QRIS or bank references when applicable.