Reference

mwin328 Privacy Policy for Your Account

Our Privacy Policy explains how mwin328 handles account details, wallet records, device data and support requests when you use our services where local law permits.

Account dataWallet recordsCookie choicesAccess rights
mwin328 mwin328 Privacy Policy for Your Account
CONTACT PATH

Use Support When Privacy Questions Stall

A clear support route helps you act on the Privacy Policy without guessing which account step comes next. Send a request through the account support link and include the phone number connected to your profile, the relevant date, and a short description of your request. We use those details to locate the correct record without asking you to share a password.

Team online

Account access

If phone verification blocks access, tell us which account step stopped and the device type you used. We can check the access record while keeping your password and wallet PIN out of the request.

Wallet status

For a DANA, OVO, GoPay or QRIS privacy question, attach the payment reference rather than full wallet credentials. We use the reference to trace the account record and status.

Data request

Ask us to correct, provide or remove eligible account data through support. Include your registered phone number so we can verify ownership before changing a record or releasing account details.

DATA PRACTICE

Explore How We Handle Account Records

Our privacy work follows the account journey rather than treating every detail alike. We separate login and verification records from payment references, restrict internal access, and check unusual device behaviour before sensitive…

Collection

We collect details you provide during account opening, including your phone number and verification result. We also receive device, login and transaction references when those details are needed to operate or protect your account.

Cookie control

Cookies can keep a mobile browser session active and help us spot repeated login attempts. You can clear or restrict them in browser settings, although some account access functions may then require another login.

Account security

Phone verification and device checks help us assess sensitive access requests. We do not ask for your password, wallet PIN or one-time code through a privacy request, support message or payment status check.

Payment records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a payment event to the correct account. We retain the minimum transaction detail needed for checking and account records.

Retention

We keep account, security and transaction records only for the period needed for the stated purpose, account administration, dispute handling or legal duties that depend on local law.

Change requests

To request correction, access or deletion, contact support from your account and identify the record involved. We verify ownership first, then explain any lawful reason a specific record must remain.

Browse Answers About Privacy Policy

These Privacy Policy answers cover the searches we hear most often from Indonesian account holders. They explain what happens around login, wallet activity, cookies, device checks and data requests, with a direct route back to support when your case needs account-specific handling.

The mwin328 Privacy Policy covers account details, phone verification, device and login records, cookies, payment references, retention, security checks and requests to access, correct or remove eligible data.

We use your phone number to create and verify the account, connect privacy requests to the correct record and assess unusual access. We do not use it as a substitute for your password.

Yes. The Privacy Policy covers DANA, OVO, GoPay and QRIS references linked to your account, along with bank transfer and virtual account status used to match a payment event.

Open the account support link and request access to your data. Include your registered phone number and the record or date involved; we verify ownership before responding to the request.

You can request correction or removal of eligible data through support. We check account ownership first and will explain if retention is required for security, disputes or duties that depend on local law.

Cookies may remember a mobile browser session and help identify repeated login attempts. You can restrict them in browser settings, but clearing cookies may require phone verification or another login.

Some processing and access conditions depend on local law. If a regional rule affects your request or account, we will use the support path to explain the relevant handling.