Reference

Privacy Policy for your mekar99 account

mekar99 Privacy Policy explains what account, device and wallet data we handle when you open an account, complete phone verification or reach the lobby through a mobile browser.

Phone verificationMobile browser pathWhere local law permitsDANA and QRIS records
mekar99 Privacy Policy for your mekar99 account
CONTACT ROUTES

Where to ask about your account data

A clear contact path helps you resolve a Privacy Policy question without explaining your account history repeatedly.

Account data request Ask us to confirm the account data linked to your phone verification. Include your account identifier so we can check the request without exposing details to another person.
Wallet record check For a DANA, OVO, GoPay or QRIS record, share the payment reference and date shown in your receipt. We can match the status while keeping unrelated account activity outside the request.
Device access concern If a mobile browser or another device appears in your sign-in history, tell us which device you recognise. We can review the session details and help secure the account path.
DATA PRACTICE

How we protect account and device data

We handle Privacy Policy requests through practical account checks rather than broad promises. Sign-in events, phone verification and payment references help us separate your request from another account, while browser and device…

Account data

We may hold your phone number, account settings, sign-in events and transaction references because these records connect your account step with support and wallet checks.

Cookies

Cookies and similar browser storage can keep your session connected as you move from login to the lobby. You can manage browser permissions, though some account steps may then need repeating.

Security checks

Phone verification and device signals help us notice access that does not fit your usual account path. We may ask for an additional account detail before discussing wallet records.

Retention period

We retain account, payment and support records only while they serve account operation, dispute checks or legal duties. When the purpose ends, we remove or anonymise the relevant data.

Who to contact

Use the support contact displayed with this policy for questions about collection, cookies, retention or payment records. We will first confirm that the request comes from the account holder.

Change request

You can ask us to correct outdated account data or clarify how a record is used. Include the affected field and account phone so we can assess the request accurately.

Privacy Policy questions Indonesian customers ask

These Privacy Policy answers focus on the account steps you are most likely to check before opening an account. They cover wallet records, cookies, device access, retention and requests for changes, with the support route available when a question needs account-specific checking.

It covers account details, phone verification, sign-in activity, cookies, device signals, support messages and payment records linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

Phone verification connects the account to the person completing the account step and helps us check unusual access. We may use that detail before discussing account changes or wallet records.

Yes. The policy covers the payment rail selected, reference, receipt, amount and status connected to DANA or QRIS. Similar handling applies to OVO, GoPay, bank transfer and virtual account records.

You can request correction when an account field is outdated or inaccurate. Send the request through the support contact shown with the policy and include your account phone plus the field to be checked.

Cookies can keep your sign-in session connected while you move from the mobile browser to the lobby. Browser settings can limit them, but you may need to repeat verification or sign-in steps.

We keep payment references and related account records while they support account operation, dispute handling or legal duties. After that purpose ends, we remove or anonymise the relevant records.

You can ask what account, device or wallet data is linked to your profile. We verify the request through the account path first, and fulfil it where local law permits and operational duties allow.