Reference

muliajitu Privacy Policy for Your Account

muliajitu Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support team.

Account dataWallet recordsCookie choicesSecurity requests
muliajitu muliajitu Privacy Policy for Your Account
CONTACT PATH

Ask About Your Privacy Policy Rights

A clear contact route helps you ask what data we hold, why it is used, or how to correct an account detail.

Data access request Ask us to identify the account data connected with your phone verification, sign-in history…
Correction request If your name, phone detail, or wallet reference is inaccurate, contact us through the…
Privacy contact Use the same support route for questions about cookies, retention, or a DANA receipt.
HANDLING DETAILS

How We Handle Your Account Data

We separate the details needed for account operation from optional device signals used to keep pages working.

Data we collect

We may collect your account identifier, phone verification result, sign-in time, device or browser details, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

Why we use it

We use account and transaction details to authenticate access, match a receipt with its status, detect unusual sign-in behaviour, answer support requests, and maintain records required for the service and applicable local rules.

Cookies and devices

Cookies can keep a session active, remember selected settings, and help us identify a device during sign-in. You can adjust browser cookie controls, though some account pages may not work as intended afterward.

Account security

Phone verification and sign-in checks help protect your account. We will not ask for your wallet PIN in a message, and you should close a shared browser session after checking Live Roulette or payment status.

Retention choices

We retain account, support, and transaction records only for the period needed for account operation, dispute handling, security checks, and applicable obligations. When a record is no longer needed, we remove or separate it.

Changing your details

You can request access, correction, or clarification through our account support path. Include the relevant phone or receipt reference; we may verify ownership before changing or disclosing private account data.

Privacy Policy Questions About muliajitu

These Privacy Policy answers address the searches we hear most often before account access. They explain payment records, cookies, device details, retention, and the contact route in plain terms. If your situation is not covered, send the account reference through support and we will assess the request under the policy and where local law permits.

It covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity.

No. Our Privacy Policy does not require you to send a wallet PIN through support. We may retain a payment reference or receipt status needed to match an account transaction.

Use the support contact path connected to your account and ask for a data access request. Include your account phone detail or relevant receipt reference; ownership checks may apply before disclosure.

Yes. Ask for a correction through account support and identify the affected phone, profile, or payment record. We may verify the account before changing information or confirming the result.

Cookies can maintain your sign-in session, remember selected settings, and support device checks. Browser controls can limit them, but account pages may not behave correctly when required cookies are blocked.

We keep payment references, support records, and account details for the period needed for operation, security, disputes, and applicable obligations. Records are removed or separated when that need ends.

Use the support route inside or beside your account area for questions about access, correction, cookies, retention, or a payment receipt. Include a reference, but never send your wallet PIN.