Reference

melayu4d Privacy Policy For Your Account

melayu4d Privacy Policy explains what we collect, why we use it, and how you can ask about your account data before opening the lobby.

Account clarityWallet data careCookie choicesSecurity checks
melayu4d melayu4d Privacy Policy For Your Account
HELP WITH PRIVACY

Reach Us About Your Privacy Policy

A clear contact path matters when you want to understand a record or change an account detail. Our support route covers privacy questions alongside login and wallet-status concerns, so you can identify the relevant account step without sending sensitive details into a public channel. Include your registered phone number only through the private support route, describe the request, and tell us whether it concerns access, correction, deletion or cookie preferences. Support is available every day from 09:00 to 22:00 WIB through live chat and the account contact form.

Team online

Privacy request

Use our private account contact form when you want a copy of your personal data, a correction to your phone details, or an explanation of a record connected with DANA, OVO, GoPay or QRIS.

Live chat path

Live chat runs from 09:00 to 22:00 WIB every day. We can explain how a privacy request moves through verification, especially when login or wallet status prevents you from reaching the relevant account screen.

Account contact

If your request concerns another person’s data, we will ask for a lawful reason and may decline access. Do not send passwords, wallet PINs or complete bank credentials; our team only needs enough detail to locate the request.

DATA HANDLING

What We Protect Inside Your Account

Privacy work is part of the account flow, not a separate promise that disappears after registration.

Account records

We use your phone number and verification result to establish account access. Login timestamps, device type and security events help us identify unusual access, while your password remains yours and should never be sent to support.

Wallet references

A DANA, OVO, GoPay or QRIS reference can help us match a cashier event to your account. We use the reference for status checks and reconciliation, not as a reason to collect unrelated wallet content.

Device behaviour

We may receive browser, operating-system and session details when you sign in from a phone or desktop. These signals support fraud detection and page continuity; they do not give us access to private files on your device.

Cookie settings

Cookies can remember a session, language choice or security preference. You can clear or restrict them in your browser, although some account functions may then ask you to verify again before continuing.

Retention timing

We keep personal records while they serve account support, security, transaction reconciliation or a legal need. When that purpose ends, we delete or anonymise the record through our internal retention process.

Request changes

Ask us to access, correct or remove eligible data through live chat or the private contact form. We verify the request first, explain any necessary limit, and confirm the action through the account contact route.

Privacy Policy Answers For melayu4d

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They explain the practical steps behind phone verification, wallet records, cookies, device signals and requests for account data. If your situation is not covered, contact us from the private account route rather than posting personal details in chat groups or public messages.

The Privacy Policy covers data created when you open or access an account, verify your phone, contact support, use wallet screens or browse from a device. It explains our handling of identity details, login events, cookies, payment references and requests to access or correct your records.

DANA and QRIS can create references linked to an account action, such as a cashier status check. We use those references to trace the relevant event and resolve a question. We do not need your wallet PIN or unrelated wallet content for that process.

Yes. Send a correction request through the private account contact form or live chat from 09:00 to 22:00 WIB. Tell us which detail is wrong, such as a phone number, and complete our account-control check before we change the record.

Ask for a copy through the private support route and describe the account records you need. We verify that you control the account, then explain the available data and any lawful limit. Do not send your password, wallet PIN or full bank credentials.

Yes. The Privacy Policy explains that browser, operating-system and session signals may be used for security and page continuity when you sign in. We do not access private files on your phone, and you can manage cookies through your browser settings.

We keep records only while they support account service, security, transaction reconciliation or a legal need. Once the purpose ends, we delete or anonymise the record through our retention process. Ask support about a specific record and we will explain its status.

Yes. Account access and any data request depend on local law. Where local law permits, we process eligible access, correction or removal requests after account verification. If a legal or security reason limits a request, we explain that limit through the private support route.