Reference

Privacy Policy For Your meki55 Account

meki55 Privacy Policy explains how we use account, device and wallet details when you open an account, sign in and reach the lobby.

Account clarityWallet dataCookie choicesIndonesia access
meki55 Privacy Policy For Your meki55 Account
CONTACT YOUR WAY

Privacy Questions Reach Our Support Path

A clear contact route matters when a Privacy Policy question concerns your phone verification, device session or wallet receipt. We ask you to contact support from the email or chat route shown on the meki55 account page, using the phone number attached to your account where possible. This helps us locate the correct record without asking you to send a wallet password, card secret or full authentication code. Requests from Medan and Semarang follow the same account-based process, and access depends on local law.

Team online

Account privacy request

Use the support chat linked from your account area to ask what personal details we hold or why a phone verification record appears. Include your account phone number and the subject of the request, but never send your wallet password or one-time security code.

Wallet record question

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, attach the payment reference rather than private wallet credentials. We use that reference to locate the relevant cashier event and explain which data was received for reconciliation.

Correction or removal

Ask support to correct an inaccurate profile field or assess whether eligible data can be removed. We may need to verify account control before acting, and some security or transaction records can stay when local law permits or requires retention.

DATA CONTROL POINTS

Six Ways We Handle Your Privacy

We treat Privacy Policy work as an account operation rather than a hidden page. Our process separates sign-in details from wallet references, limits staff access to the records needed for a task…

Data collected

We may receive your phone number, profile details, verification result, login timestamps, browser type, device identifiers, support messages and payment references. We collect these categories because they help connect your account request to a secure session or a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event.

Cookie handling

Cookies can keep your login session, remember language or region settings and help us identify a broken page. You can manage them in your browser. Blocking necessary cookies may require you to sign in again or may prevent a cashier or policy page from working correctly.

Account security

Phone verification helps us confirm account control before sensitive changes. We also inspect sign-in and device signals for unusual activity. If a new Android phone or desktop browser triggers a security check, follow the account prompt and contact support instead of sharing an authentication code.

Retention timing

We retain account, security and transaction records only for operational, dispute and legal needs described in the Privacy Policy. A deletion request does not automatically erase records connected to an open issue, a payment reconciliation or an obligation that local law permits or requires us to keep.

Your requests

You can ask for a copy of eligible personal data, correction of an inaccurate field or clarification about a processing purpose. We verify the request against your account before responding, which protects your details if another person tries to use your phone number or device.

Policy changes

When our handling practices change, we place the updated Privacy Policy on this page and may show a notice during account access. Check the page before changing wallet details or completing phone verification so you can see the current purposes, retention wording and contact route.

Privacy Policy Questions About meki55

These Privacy Policy answers address the account and wallet questions we expect you to ask before using meki55 in Indonesia. They explain the practical route for viewing data, changing details, handling cookies and contacting us. If your question concerns eligibility or account access, the answer depends on local law and the current policy wording on this page.

It covers the personal and technical data connected with your meki55 account, including phone verification, login events, device signals, cookies, support messages and wallet references. It also explains our purposes, service-provider sharing, retention approach, your request options and the contact route for privacy questions.

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may receive a reference, amount status and timing needed to match a cashier event. We do not ask for your wallet password. The payment provider remains responsible for credentials held inside its own service.

Yes. Contact us through the support chat or email route shown in your account area and ask for an eligible data copy. Include your account phone number and a clear request subject. We verify account control first, then explain the available records and any lawful limits.

Send a correction request through the account support route, identifying the field that is inaccurate and the replacement detail. We may ask for phone verification before changing it. A corrected profile does not necessarily alter historical security or transaction records that must remain for operational or legal reasons.

Cookies can maintain a sign-in session, remember settings and help us diagnose a page problem on an Android phone or desktop browser. You can control them through browser settings. If you block necessary cookies, you may need repeated login steps or lose access to some account functions.

The retention period depends on the type of record and its purpose. We keep data while it supports account security, payment matching, support handling or a dispute, then assess removal under our retention process. Some records stay when local law permits or requires retention, even after an account request.

Use the support chat or email contact shown inside the meki55 account page and label the request as a Privacy Policy concern. Share the account phone number and relevant reference only. Do not send a wallet password or authentication code. We use the verified route to respond to you.