Reference

maha4d Terms & Conditions for Your Account

Clear Terms & Conditions help you understand account access, wallet records and the rules around titles such as Lightning Roulette, Limbo and Mobile Legends on maha4d.

Account accessWallet recordsPolicy changesSupport route
maha4d maha4d Terms & Conditions for Your Account
POLICY HELP PATHS

Get Policy Help Through Your Account

A clear contact path matters when a Terms & Conditions question affects your account or wallet status. We ask you to start from the support route visible after login, so our team can match your request with the correct account record. Include the relevant payment reference, device path or policy section, and we can direct the next step without asking you to repeat the full history.

Team online

Account access

If a phone verification step or login check stops your access, send the account details requested through our signed-in support route so we can explain the relevant Terms & Conditions clause.

Wallet status

For DANA, OVO, GoPay or QRIS questions, include the payment receipt and status shown beside the cashier path; we use those details to identify the applicable account rule.

Policy changes

When you want to question, correct or request a change to an account record, use the same support route and name the exact Terms & Conditions section involved.

CLEAR ACCOUNT CONTROLS

Keep Data and Account Choices Clear

Our Terms & Conditions connect account use with practical controls: accurate details, phone verification, payment matching and secure access on your chosen device.

Data handling

We use account details, phone verification results and payment references to apply the Terms & Conditions, check account ownership and respond to requests connected with DANA, OVO, GoPay or QRIS.

Cookie use

Cookies may retain session and preference signals needed for policy notices and account navigation. Your browser settings can control cookies, though changing them may affect signed-in access.

Account security

Keep your phone details, password and signed-in device private. If access looks unusual, we may pause the account path and request verification under these Terms & Conditions.

Record retention

We retain account, payment and support records for the period needed to apply these terms, resolve disputes, meet local requirements and confirm the history of a requested change.

Requesting corrections

To correct a name, phone detail or account record, contact us through the signed-in support route with the affected field and supporting evidence; we will explain the next check.

Who to contact

Use our account support path for Terms & Conditions questions, data requests and access concerns. Include your account reference, device type and the policy wording you want clarified.

Terms & Conditions Questions for maha4d

These questions address the points you are most likely to check before opening an account or connecting a local wallet. Our answers focus on the Terms & Conditions, including eligibility, account records, payment matching, device access and requests for changes. Where a situation needs account-specific checking, use the signed-in support route with the relevant reference.

You can read the current Terms & Conditions on this page before opening an account. We recommend checking the page again after a policy notice, payment change or account-access update.

Yes. Access depends on local law, your location and your eligibility. Our Terms & Conditions apply where local law permits, and you must not use the account where access is restricted.

No. Our Terms & Conditions require wallet activity to match your account details. Use your own DANA, OVO, GoPay or QRIS path, and keep the payment receipt for any status question.

We may hold account access while checking the mismatch. Follow the signed-in support route, provide the requested account details and wait for the verification outcome before trying another account path.

We may update the Terms & Conditions when account controls, payment partners or local requirements change. The updated wording takes effect after publication, so check the page when we display a notice.

Send a correction request through the signed-in support route and identify the exact field, such as your phone detail or account name. We may ask for evidence before applying the change.

Yes. They apply whether you use a mobile browser or desktop path, including login, phone verification and wallet status. Keep one secure account path and avoid sharing signed-in device access.