Reference

mekar 11 Privacy Policy Explained

mekar 11 Privacy Policy shows how we handle the details connected with your account, mobile browser access and wallet activity.

Account clarityWallet recordsCookie choicesAccess requests
mekar 11 mekar 11 Privacy Policy Explained
CONTACT YOUR WAY

Get Help With Privacy Policy Requests

A clear contact path matters when you want to ask about Privacy Policy handling, correct an account detail or check a wallet record. We keep privacy questions separate from ordinary lobby requests, so your message can identify the account step, device path or payment reference involved. Use the support route shown inside your account and include only the details needed to locate your request.

Team online

Account data request

Ask us which personal details are linked to your mekar 11 account and why they are held. We may ask you to complete the account verification step before releasing account-specific records.

Wallet record check

For DANA, OVO, GoPay or QRIS questions, include the payment date and reference shown in your account. We use that information to trace status without asking for your wallet password.

Correction request

Send the field you want changed, such as a contact detail, through the account support path. We check the request against your account before changing records connected with access or payment verification.

HOW WE HANDLE IT

Privacy Controls Around Your Account

Privacy Policy decisions affect the way your account works from first access through wallet status checks.

Account details

We use contact and verification details to create your account, confirm that a request belongs to you and protect access. You can ask what is held and request a correction where local law permits.

Mobile browser data

When you move from login to the lobby on a mobile browser, technical details such as device type, browser version and session events may be recorded to keep access working.

Cookie settings

Cookies can preserve your session, remember selected settings and help us understand page errors. You can manage browser cookie controls, although changing them may interrupt account access.

Payment matching

A DANA, QRIS, bank transfer or virtual account reference helps us match a payment request to the correct account. We do not ask for your wallet password or full banking credentials.

Security records

Login times, device changes and verification events help us detect account activity that needs checking. If a security question arises, we may pause a request until your account identity is confirmed.

Retention and contact

We retain records only as long as needed for account operation, payment reconciliation, disputes or legal duties. Contact us through the account support route to ask about deletion or restricted use.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and wallet questions you may have before opening an account or while using the mobile browser. We keep the wording practical: what we collect, why a verification step appears, how cookies work and where to send a request. Access to our services depends on local law and is available where local law permits.

It covers account details, verification records, browser and device events, cookies, payment references and support messages. It also explains retention, security handling and how you can request access or correction.

We use verification to confirm that an account request or data request comes from you, protect login access and match payment activity correctly. The requirement applies where local law permits.

Yes. We may use DANA and QRIS references, along with OVO, GoPay, bank transfer or virtual account details, to match payment status. We do not need your wallet password.

You can send an access request through the support route inside your account. We may verify your identity first, then explain the account details and related records we can provide under local law.

Cookies can keep your session active, remember settings and help identify page errors while you move from login to the lobby. Browser controls can remove them, but some account functions may then stop working.

Tell us which account field is wrong through the account support route and provide the corrected value. We compare the request with your verified account before changing records tied to access or payments.

Retention depends on the purpose of the record, including account operation, payment reconciliation, disputes and legal duties. Ask support about a specific record and we will explain the applicable handling where local law permits.