Reference

Open musan288 Privacy Policy Details

musan288 keeps this Privacy Policy focused on the account data we need to run your profile, confirm device access, and answer requests tied to your wallet or login…

Account dataCookie signalsDevice accessLocal law

Browse Lobby Read FAQ

Explore How We Handle Data

musan288 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy explains what we keep, why we keep it, and when we share it only as needed to run the account. We collect registration details, login timestamps, device type, and transaction references so we can verify access, answer support questions, and stop misuse. If

1
you send funds through DANA, OVO, GoPay, or QRIS, we keep the payment reference against the profile that made it, then retain it only for the period needed to reconcile the ledger or handle a dispute. Rules can differ by jurisdiction, so access and data handling
2
depend on local law and are available only where local law permits. You can ask us to correct or remove data where the law allows, and we will process the request through our support channels.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

Switch To Privacy Support Channels

For privacy questions, we keep three contact paths open: live chat inside the account menu, email, and the profile form you can send from desktop or mobile browser.

Live chat Open the chat from the account menu if you want a fast answer about data access, cookies, or profile changes. We route it to the support desk that handles privacy requests during 08:00-23:00 WIB.

Email Send a written request when you need a copy of the records we keep, a correction, or a removal check. Add your registered email and the issue type so we can verify the account cleanly.

Profile form Use the form from desktop or mobile browser if you want to attach device details, wallet references from DANA, OVO, GoPay, or QRIS, or a screenshot that helps us trace the record.

HANDLING STANDARDS

Browse Our Data Safeguards

We keep the policy practical: collect only what helps verify your account, protect login sessions, and answer change requests.

What we collect

We keep registration details, login timestamps, device type, and transaction references only when they are needed for account access, support checks, or a request you send through the account form.

Cookie use

Cookie signals help us remember your session, language choice, and last device state so you do not have to reset the page each time you return from Android Chrome, Safari, or desktop.

Account security

If a login looks unusual, we may ask you to confirm the registered email, recent device, or wallet reference before we change anything. That step helps us protect the profile from unwanted access.

Retention window

We keep data only as long as needed for service, audit, dispute handling, and record duties under the law that applies to your account. After that, we remove or anonymise what is no longer required.

Request changes

You can ask for correction or removal where local law allows. Send the request through live chat or email, add the registered contact details, and we will reply after we verify the account.

Who to contact

For privacy matters, the support desk is the first stop. We route each request to the right team, whether it concerns cookies, login logs, device history, or wallet references from DANA, OVO, GoPay, or QRIS.

Open Common Privacy Questions

These questions cover the privacy points you usually check before opening an account: what we collect, how cookies work, how long we keep records, and how to reach us with a request. We keep the answers direct so you can see what happens to your account data, device logs, and payment references from DANA, OVO, GoPay, or QRIS when local law permits.

We collect the details needed to create and secure your profile: name or alias, registered contact details, login timestamps, device type, and the wallet or payment reference used for verification when local law permits.

We keep only the transaction references and status marks needed to match the ledger, answer a support request, or check a dispute. We do not need your full wallet history for routine account service.

Cookies help us keep the session active, remember language choice, and recognise a trusted device when you return from Android Chrome, Safari, or a desktop browser. They do not give us access to your device files.

Yes, where local law allows. Send the request through live chat or email, use the registered contact details, and we will verify the account before making correction, removal, or access changes.

We keep records only for as long as they are needed for service, security checks, dispute handling, and legal duties that apply to your account. After that, the data is removed or anonymised.

Use the support route on this page first. Our team can check login logs, cookie settings, and data requests, then send the case to the right desk without making you repeat the same details.

Yes. Access and data handling depend on local law and are available only where local law permits. If the rule changes in your region, we will apply the current requirement to the account.

Open musan288 Privacy Policy Details

Switch To Privacy Support Channels

Browse Our Data Safeguards

What we collect

Cookie use

Account security

Retention window

Request changes

Who to contact

Open Common Privacy Questions

01 What data do you collect when I open an account?

02 Do you store DANA, OVO, GoPay, or QRIS details?

03 How do cookies affect my account?

04 Can I ask for my data to be changed or removed?

05 How long do you keep account records?

06 Who should I contact about privacy questions?

07 Does access depend on where I am?

Related Pages