Reference

Privacy Policy For Your mekar789 Account

Our Privacy Policy explains what we collect when you open a mekar789 account, use DANA or QRIS, and move between the lobby and your wallet status.

Account dataWallet recordsCookie choicesAccess requests
mekar789 Privacy Policy For Your mekar789 Account
CONTACT THE DESK

Get Help With Privacy Policy Requests

A clear contact path helps you resolve a Privacy Policy question without sending account details through an unsuitable channel. Use our support route when you need to check a phone-verification record, ask why a wallet reference appears in your account history, or request a copy of personal data. Include the account identifier connected with your request, but do not send a password or full payment credentials. We may ask for additional account checks before discussing private records, and access depends on local law.

Team online

Policy questions

Send a Privacy Policy request through our support desk with your account identifier and the exact question. We can explain collection, use, retention, cookies, or access steps without asking you to reveal your password.

Wallet records

If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference looks unfamiliar, mention the date and visible reference in your support message. We can route the request for account and payment-record checks.

Account changes

For a correction or deletion request, contact us from the account-linked route where possible. We may verify your phone before changing records, and some details can remain when local law requires retention.

DATA HANDLING

What We Do With Account Details

Our Privacy Policy connects practical account controls with the data behind them. A phone check supports account access, session records help us examine unusual sign-ins, and wallet references let us trace a…

Collection

We collect details you submit during account creation, including contact information and phone-verification data. We also receive technical details such as device type, browser activity, session timing, and pages used to support access and security checks.

Payment references

DANA, OVO, GoPay and QRIS can produce transaction references linked to your account. Bank transfer and virtual account records may also be used to reconcile a status question, while wallet passwords remain outside our requested support details.

Cookies

Cookies can remember session settings, help the account path work across pages, and show whether a sign-in is continuing on the same device. You can manage browser cookie controls, although some account functions may then need another sign-in.

Account security

We use phone verification, sign-in records, device signals, and account checks to reduce unauthorised access. If your login stalls before the lobby, contact support from the account-linked route and avoid sharing passwords or one-time codes.

Retention

We keep personal and transaction records only for the period needed for the stated service, safety, dispute, and legal purposes. Retention can vary by record type, and where local law permits you may ask what remains and why.

Your requests

You can ask for access, correction, clarification, or deletion by contacting our support route. We may confirm your identity before responding, and some requests may be limited when keeping a record is required by local law.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions we expect you to ask before opening an account or checking your records. They cover account data, cookies, device access, payment references, corrections, and contact steps. If your situation is not listed, send the support desk your question from the account-linked route. We will ask only for the checks needed to discuss private information, and where access or eligibility is discussed, it depends on local law.

The mekar789 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, game-page activity, and payment references. It explains why we use each category, how retention works, and how you can request access, correction, clarification, or deletion.

DANA and QRIS references can connect a transaction-status question to the correct account. OVO, GoPay, bank transfer, and virtual account references may serve the same purpose. We use visible transaction details for reconciliation and support checks, not as a request for your wallet password.

Contact our support desk from the account-linked route and state that you are making a Privacy Policy data request. Include your account identifier and the category you want, such as phone verification, cookies, sign-in records, or payment references. We may verify your identity first.

Yes, you can ask us to correct inaccurate account information through the support route. Describe the field that needs attention and provide the correct detail without sending a password or one-time code. We may complete a phone or account check before applying a change.

On mobile, cookies and device signals can help keep your account session connected from phone verification to the lobby. We use those records to support access and examine unusual sign-ins. You can adjust browser cookie settings, but the account may require another sign-in afterward.

Retention depends on the type of record and the service, safety, dispute, or legal purpose for which it is needed. DANA, OVO, GoPay, QRIS, bank transfer, and virtual account references can follow different retention needs. Where local law permits, ask support what remains.

You can submit a deletion request through our support desk and explain which data you want removed. We will assess the request under applicable rules, identity checks, and any duty to retain account or transaction records. Access and eligibility depends on local law.