Reference

Open md888 Privacy Policy Details

The md888 Privacy Policy explains how we collect, use and protect the details needed for account access, wallet checks and device sessions.

Account clarityWallet data contextDevice session carePolicy access
md888 Open md888 Privacy Policy Details
ASK OUR TEAM

Contact md888 About Privacy Policy

When a Privacy Policy question concerns your own account, we give you a clear route to identify the record involved and explain the change or request…

Account data questions Tell us which account detail you want clarified, such as your phone verification record…
Wallet receipt checks For a DANA, OVO, GoPay or QRIS question, keep the payment receipt and its…
Access and correction Ask us to explain, correct or remove a detail where the request is available…
HOW WE HANDLE DATA

Explore md888 Privacy Policy Controls

We keep the Privacy Policy practical by connecting each data purpose to an account action you recognise.

Account details

We use your phone number and account entries to create and maintain your access.

Device sessions

A device session can produce technical details about sign-in, browser activity and security events.

Cookies

Cookies can support the session needed to move from login to account pages.

Payment references

We may retain references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions.

Retention choices

We keep records for as long as needed for the stated account, security or transaction purpose, subject to applicable requirements.

Policy requests

You can contact us to ask what personal detail we hold, request a correction or ask about deletion where available.

Find Privacy Policy Answers Quickly

These Privacy Policy answers address the account questions you are most likely to have before opening md888 or checking a wallet record. We keep the wording tied to actual account steps, device sessions and Indonesian payment references, so you can decide what to share and where to ask for help. If your situation is different, our support route can identify the relevant policy section.

It covers account details, phone verification, sign-in activity, device session data, cookies and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how to ask about access, correction, retention or deletion where available.

We use phone verification to create and protect your account before account access. It helps us connect a request to the right account when you ask about a sign-in, device session or wallet record, and we only discuss private details through the account support path.

Yes. The Privacy Policy covers payment references that help us check a DANA or QRIS receipt and answer a status question. The same approach applies to OVO, GoPay, bank transfer and virtual account references, without publishing those details openly.

Use our support route and state the account detail you want corrected, along with the reason for the request. We may ask for phone verification or another account check before making a change, so the correction is applied to your own md888 record.

Cookies may support the active session used after login and while you open policy or account pages. Your browser can control cookie storage, but refusing some cookies may prevent session-dependent pages from working as intended on your phone or desktop.

You can contact us through the account support path and ask which personal details or payment references are held for your account. We verify the request, identify the relevant record category and explain any access limits that depend on local law.

You can ask about deletion through support, and we will explain whether the request is available for the record involved. Some account, security or transaction details may need to remain for an applicable requirement; we will identify that reason rather than leave the request unclear.