Reference

Terms & Conditions for mantap 21

mantap 21 Terms & Conditions set the rules for opening an account, using the lobby and requesting account changes in Indonesia.

Account eligibilityWallet and account checksDevice access rulesPolicy request path
mantap 21 Terms & Conditions for mantap 21
ACCOUNT HELP ROUTE

Where To Ask About Policy Terms

A clear support path helps when a clause affects your account, payment status or access request.

Account access If phone verification or login blocks your account, use the access support route shown…
Wallet status For a DANA, OVO, GoPay or QRIS question, send the payment reference and the…
Policy request When you want clarification, correction or removal of an account detail, name the exact…
DATA AND CONTROL

Six Account Safeguards We Explain

These Terms & Conditions also describe how we handle account records around access, payments and policy requests.

Account data

We use the details you submit to create and maintain your account, connect phone verification and respond to policy requests. Keep your name and contact details current, because mismatched records can delay an access or wallet-status check under the Terms & Conditions.

Cookie controls

Cookies can keep a signed-in session consistent between the login page and lobby on a supported browser. You can review cookie permissions in your browser settings; disabling some cookies may interrupt account continuity, so check the policy effect before changing them.

Login security

Your password and verification details belong only to you. We do not ask you to publish them in a support request. If access looks unfamiliar, stop using the session, secure your device and use the account access route so we can assess the relevant policy step.

Payment records

A DANA, OVO, GoPay or QRIS receipt helps us match a wallet request to the correct account record. Bank transfer and virtual account references serve the same purpose. Send only the requested reference details, not your password or full private security credentials.

Record retention

We retain account, verification and support records only as needed for account operation, security checks, dispute handling and legal obligations. The applicable period can depend on the request and local requirements, and we can explain the record category involved when you contact us.

Change requests

To request a correction or ask how your data is handled, use the policy support route from your account and identify the record concerned. We may ask for phone verification or another account check before changing details, protecting the account from an unauthorised request.

Terms & Conditions Questions Answered

We wrote these Terms & Conditions answers around the account questions you are most likely to ask before opening access. They cover eligibility, account details, wallet records, device behaviour, policy changes and contact steps. If your situation is not listed, use the support path linked to your account and describe the exact clause or action involved. We can then identify the required verification without turning a policy request into a general lobby conversation.

They cover account creation, phone verification, login security, lobby access, wallet records, policy requests, cookies and retention. The rules apply when you use casino rooms, sports topics or account services. Eligibility depends on local law, so check the access wording before completing your account.

Access is available where local law permits and may depend on location or eligibility checks. If you are in Indonesia, use the account path shown for your region, complete phone verification and keep your details accurate. We may pause access when a required check remains incomplete.

Contact us through the policy support route and identify the incorrect field, such as your phone number or account name. We may request verification before changing it. Keeping details aligned also helps match DANA, OVO, GoPay, QRIS, bank transfer or virtual account records.

Wallet and bank records must connect to the account path used for the request. Keep the receipt or reference for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. If status is unclear, send the reference through support so we can check the applicable account rule.

The account rules remain the same, but device behaviour can differ. On mobile, use the path from login through phone verification to the lobby; on desktop, check the browser session and cookie settings. A device change may trigger another security check before access continues.

Use the policy support route linked to your account, state the record you want corrected and explain why it is inaccurate. We may ask for phone verification or another account check. Where local law permits, we handle the request according to the applicable retention and security rules.

Sign in and open the account support route, then quote the clause or describe the action you are questioning. If login is blocked, use the access route on the sign-in page. Include your device type and account step, but never send your password or private security code.