Reference

mekar11 Terms & Conditions Made Clear

Our Terms & Conditions set the rules for opening an account, using the lobby, moving funds through DANA or QRIS, and requesting help when an account check is…

Account eligibilityWallet and cashier rulesData and security termsPolicy contact path
mekar11 mekar11 Terms & Conditions Made Clear
HELP WITH TERMS

Get Policy Help Beside Your Account

A clear support route matters when a Terms & Conditions question affects login, wallet status or a policy request.

Account access If a phone verification step prevents access, send the account identifier and the exact message shown. We use those details to explain which Terms & Conditions rule applies and what correction may be needed.
Wallet status For DANA, OVO, GoPay, QRIS or bank transfer questions, include the payment reference and selected rail. We can then separate a pending payment check from an account restriction under these terms.
Policy request Ask about data, cookies, retention or a change to your account details through the policy support path. Please state the requested change clearly so our team can assess it against the applicable terms.
HOW WE APPLY THEM

Six Practical Rules Behind Our Terms

We apply these Terms & Conditions through identifiable account steps rather than vague notices. Phone verification connects a request to the account record, payment references help us trace wallet activity, and browser…

Data handling

We use submitted account details to create, verify and administer your access under these Terms & Conditions. Payment references help us reconcile DANA, OVO, GoPay, QRIS and bank transfer activity.

Cookie choices

Cookies can keep a browser session connected to the correct account and remember necessary page settings. You can manage browser cookie controls, although changing them may interrupt account access.

Account security

Keep your phone access and sign-in details private, and contact support if a verification message or account event looks unfamiliar. We may pause a request while ownership details are checked.

Record retention

Account, payment and support records are retained for the period needed to operate the service, resolve disputes and meet applicable obligations. The relevant period can vary with the record type.

Requesting changes

You may ask us to correct account details or clarify how a record is used. Include the phone-linked account identifier and requested change so we can review the right record.

Who to contact

Use the policy support path for questions about these Terms & Conditions, data handling, cookies, retention or account closure. Payment references should accompany wallet-related requests where available.

Terms & Conditions Questions Answered

These questions cover the account decisions people usually check before opening an account with mekar11. We keep the answers tied to the written Terms & Conditions, including local access wording, phone verification, payment references, browser use, data requests and the route for asking us to clarify a rule.

You can open the Terms & Conditions page before creating an account and return to it from the policy area while signed in. Read the current wording before using DANA, QRIS or another listed payment rail.

Yes. Account access and eligibility depends on local law. We may restrict an account or request additional details where local law permits, so your location and submitted account details must be accurate.

We may require phone verification before account access continues. Use a phone number you control, keep the verification step private, and contact support if the code or account record does not match.

Yes. The terms cover DANA, OVO, GoPay, QRIS, bank transfer and virtual account instructions. Select the named rail shown at checkout and retain the payment reference if a status check is needed.

Send a policy request through the support path with your phone-linked account identifier and the exact correction needed. We may ask for details that confirm ownership before changing the account record.

Necessary cookies can keep your browser session connected to the correct account and support required page functions. Browser controls may remove them, but doing so can interrupt sign-in or policy access.

Use the policy support path and state whether you are asking about closure, retained payment records or another term. Include your account identifier so we can route the request to the correct record.