Reference

mekar88 Privacy Policy for Your Account Data

Our Privacy Policy sets out how mekar88 handles the details you provide when opening an account, signing in, using DANA or QRIS, and contacting support.

Account detailsWallet recordsCookie choicesAccess requests
mekar88 mekar88 Privacy Policy for Your Account Data
CONTACT PATHS

Privacy Help Beside Your Account

A clear contact path matters when you want to ask about personal data, a wallet record or a sign-in device.

Account support Use the support link after signing in to ask what account details we hold, why a record appears, or how to request a correction. We may ask for an account step that confirms you are making the request for yourself.
Wallet records For DANA, OVO, GoPay or QRIS questions, identify the payment rail and the account action involved. We use that context to locate a status record while limiting the amount of wallet detail included in our reply.
Access concerns If a phone, tablet or browser no longer opens your account, contact support through the account help path. Tell us the device type and sign-in issue, but keep passwords, verification codes and complete payment credentials private.
DATA PRACTICES

Cookies, Devices and Account Security

We handle privacy as part of each account step rather than as a separate message hidden from the cashier or sign-in flow.

What we collect

We may receive your phone number, account identifiers, sign-in times, device details, selected lobby actions and support messages. Payment records can include DANA, OVO, GoPay, QRIS, bank transfer or virtual account status, rather than your full wallet password.

Why we use it

We use account and device details to provide sign-in access, match payment status, detect unusual activity, answer privacy requests and keep records connected to the correct account. We do not need unrelated personal details to answer a normal policy question.

Cookies on your device

Cookies can remember a session choice and help us recognise a returning phone or tablet. You can manage cookies through your browser settings, although changing them may affect sign-in continuity or the way an account page loads.

Account protection

Phone verification can be requested before account access or before we discuss sensitive records. We also examine unusual device or sign-in signals. Never share your password or verification code with anyone contacting you about DANA, QRIS or your account.

Retention choices

We keep information only for the period needed for account operation, security checks, support handling and applicable record duties. When you ask about deletion, we explain which details can be removed and which must remain under local requirements.

Changing your details

Ask support to correct an inaccurate phone number, account detail or contact message through the signed-in account path. We may verify the request first, then confirm what was changed, what could not be changed and why.

Privacy Policy Questions About Access

These answers address the questions we expect you to ask before opening an account or connecting a local wallet. They cover the Privacy Policy, personal data, cookies, device behaviour, payment records and contact steps. If your situation involves eligibility or access, the answer depends on local law and the details visible in your account.

The Privacy Policy covers account details, phone verification, device signals, cookies, support messages and payment status records. It explains why we use those details, how we protect them, how long records may remain and how you can ask for access or correction.

Yes. The Privacy Policy includes records connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account steps. We use payment status and account references to match an action, not to request your wallet password or verification code.

Sign in and use the support link in your account area, then ask for an account data access request. Include the phone number linked to the account and the records you want clarified. We may verify your identity before releasing personal details.

You can request a correction through the signed-in support path. Tell us which phone number, account field or contact message is inaccurate and provide the updated detail. We may complete a phone verification step before changing the record or explaining why it remains.

Cookies can keep a session choice and help recognise the device during account access. Browser settings let you remove or restrict them. If you block required cookies, sign-in continuity or a policy request page may not work as expected on that phone or tablet.

We retain details for account operation, security checks, payment matching, support handling and applicable record duties. The period can differ by record type. If you ask for deletion, we explain what can be removed and what must remain where local law requires retention.

Send the complaint through the support link inside your account and label it as a Privacy Policy matter. Describe the record, device or payment rail involved without including passwords or full wallet credentials. We use the account path to route your request safely.