Reference

made168 Privacy Policy, Explained Clearly

Our Privacy Policy explains what account details we collect, why we use them and how you can ask about your records before opening an account.

Account dataWallet recordsCookie choicesAccess requests
Explore Casino Lobby Read FAQ
made168 made168 Privacy Policy, Explained Clearly
CONTACT ROUTES

Get Privacy Policy Help Directly

A clear contact route matters when you want to ask about the Privacy Policy or check how your account data is used. Start with the support path linked from the made168 account area and include the phone number or email connected to your account. We use those details to locate the right record without asking you to send a password or wallet PIN. For a payment-related question, keep the DANA, OVO, GoPay or QRIS reference visible, but remove sensitive authentication codes before sending anything.

Team online

Account support

Use the account support channel for questions about phone verification, account access, stored contact details or a request to correct information. We ask you to confirm account ownership before discussing personal records, and we never need your password or wallet PIN.

Payment privacy

For a Privacy Policy question involving DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, send the transaction reference and date through support. We use that reference to trace the record while keeping full wallet credentials out of the conversation.

Access requests

If you want a copy, correction or removal request assessed, contact us from the email or phone connected to your account. Include the request type and your country so we can apply the right process where local law permits.

DATA CONTROLS

Six Practical Privacy Safeguards

Privacy work is part of the account flow, not a hidden page you need to search for after a problem.

Account details

We use contact details, phone verification status and account identifiers to create access, respond to requests and keep records connected to the right account. We do not ask you to place a password, PIN or one-time code in a support message.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can show that a transaction belongs to your account. We use the reference for status checks and reconciliation, while payment credentials remain with the relevant payment channel.

Cookies

Cookies may keep your session active, remember selected settings and help us understand whether an account page loads correctly. You can adjust cookie controls in your browser, although blocking required cookies may interrupt login or account verification.

Device security

We may record device type, browser details, connection data and access times to identify unusual sign-in patterns. If a new device triggers a check, complete the requested account step rather than sharing verification codes with another person.

Retention periods

We keep personal and transaction records only for as long as needed for account operation, security checks, dispute handling and legal duties. The period can differ by record type, and deletion may be limited where a lawful retention requirement applies.

Change requests

To request access, correction or deletion, contact support from your connected account channel and describe the record involved. We may ask for identity confirmation, then explain the result, any limit and the next step where local law permits.

Privacy Policy Questions You May Search

The Privacy Policy questions below focus on the records you are most likely to notice while using an Indonesian account. We cover phone verification, wallet references, cookies, device checks, retention and requests for access or correction. If your question concerns a specific payment or account event, use the connected support route and include only the reference needed to locate it.

The made168 Privacy Policy covers account details, phone verification, device and connection signals, cookie use, support messages and payment references. It explains why we use each category, how we protect access and how you can ask for access, correction or deletion where local law permits.

Yes. The Privacy Policy includes transaction references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references for account matching, payment status and dispute checks, but you should never send a wallet PIN, password or one-time code.

Phone verification helps us connect an account to the correct contact channel before access is provided. It can also help us identify an unusual sign-in or recover an account. Enter codes only in the account flow; support will not ask you to reveal them in chat.

You can contact us from the phone number or email linked to your account and ask for a copy of the personal data covered by the Privacy Policy. We may confirm your identity first, then explain what can be supplied and any legal restriction.

Send a correction request through the connected support path and identify the field that needs changing, such as a phone number or email address. Include the accurate replacement value only after account ownership is confirmed, and we will assess the request under applicable local requirements.

Retention depends on the type of record and why it was collected. Account, security and transaction records may need to remain available for service operation, dispute handling or legal duties. When a record is no longer needed, we assess it for deletion or anonymisation.

You can manage many cookie choices through your browser or the available site controls. Required cookies may still be needed for login, security and account steps. If you block them, some access functions may not work correctly, and support can help identify the affected page.

Related Pages

made168 Indonesia Liga 1 Handicap Odds made168 Casino Limbo Quick Arena About Us