Reference

mekar99 Legal: know the rules behind your account

Our Legal page puts account conditions, local access wording and policy contacts in one place before you open an account.

Account conditionsLocal-law accessData request pathPolicy contact
mekar99 mekar99 Legal: know the rules behind your account
POLICY HELP ROUTES

Where to ask about Legal terms

A clear contact path matters when a Legal clause affects your account or wallet status.

Account access Use the account help route when a phone verification step, location condition or Legal clause prevents access. Include the policy heading you are asking about so we can address the specific issue.
Wallet records For DANA, OVO, GoPay or QRIS questions, share the transaction reference and wallet status shown on your account. We use those details to separate a policy check from a payment-record mismatch.
Data requests Ask through the policy contact route to request correction, access or removal of eligible personal details. We may verify account ownership before changing records, and we will explain any local-law restriction.
DATA AND ACCESS

How we handle Legal responsibilities

We apply the Legal terms to practical account events rather than leaving them as general wording. That includes checking who controls an account, recording payment references, protecting login details and retaining records…

Data handling

We use account details, phone verification results and transaction references for access, support and policy checks. We limit those details to the purpose described in the current Legal wording.

Cookie choices

Cookies may keep a sign-in path and policy preferences working across your device. You can ask us about a cookie category or adjust available browser controls when a preference needs changing.

Account security

Keep your password and verification code private. If you suspect account access from another device, contact us with the account phone number so we can review the security step.

Record retention

We retain selected account and payment records only for the operational or legal purpose stated in our policy wording. A request may be limited where keeping a record is required.

Who to contact

Use our account support route for questions about Legal wording, identity checks, wallet matching or account access. Include one clear subject so the request reaches the relevant policy process.

Request a change

You may ask us to correct inaccurate account details or explain how an eligible request is handled. We verify ownership first and tell you when local law limits the requested change.

Answers about mekar99 Legal access

These Legal answers address the questions we expect before an Indonesian account is opened or a policy request is sent. If your situation involves a specific wallet, device or location, include that detail when you contact us so the response can follow the applicable account record.

The Legal page covers account conditions, local access, identity checks, payment-record matching, cookies, data handling, security duties, record retention and ways to request clarification or a change.

Access depends on local law and your eligibility at the time of account access. Where local law permits, we show the applicable account route and policy wording for your region.

Phone verification helps connect the account to the person opening it and supports security checks. We may require it before account access, especially when a wallet or transaction record needs matching.

Legal conditions require payment details to match the account record. For DANA, OVO, GoPay or QRIS, keep the receipt reference available because we may use it to resolve ownership or status questions.

Yes, you can contact us through the policy route to ask about access or correction. We verify account ownership first, then explain the result and any restriction required by local law.

Record retention follows the purpose described in the current Legal wording, such as account security or transaction checks. Some records may need to remain available when a legal requirement applies.

Send the policy heading, your account phone number and a relevant transaction reference if needed. Never send your password or one-time code; we use ownership checks through the support route.