Reference

merdeka138 Privacy Policy for Your Account

Our Privacy Policy explains what merdeka138 collects when you open an account, verify your phone, use a mobile device or select DANA and QRIS.

Clear collection rulesWallet data contextYour request optionsIndonesia access
merdeka138 merdeka138 Privacy Policy for Your Account
HELP WITH REQUESTS

Privacy Questions Reach Our Support Route

A clear contact route helps when you want to ask about a record, correct an account detail or understand a wallet reference. Start from the support link beside the account and cashier areas, include your account identifier and describe the request. We may ask you to complete an account check before discussing personal data. The current support hours and available contact route are shown on our contact page.

Team online

Account data request

Use the support route beside your account area to ask what personal details we hold. Include your registered contact detail so we can locate the correct merdeka138 record.

Wallet reference check

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the transaction date and reference through support. We will compare it with the related account record.

Correction request

Tell us which account detail needs correction and why. We may request phone verification before changing the record, helping prevent another person from altering your profile.

DATA HANDLING PRACTICE

What We Protect Across Your Access

Our handling process separates account identity, transaction references and device signals so each request has a clear purpose.

Account details

We use your registered contact information to identify your account, complete phone verification and respond to Privacy Policy requests. We do not ask for your wallet password through support.

Transaction records

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match payment status with the correct account. These records support reconciliation and dispute handling.

Mobile signals

Browser type, operating system, session time and related device signals help us spot unusual access. On your phone, these checks work alongside the normal login and verification steps.

Cookie choices

Cookies keep a signed-in session connected and help us measure page use. You can clear or restrict them in your browser, although some account functions may then need another login.

Retention approach

We retain personal and transaction records for operational, dispute or legal needs. When a record is no longer needed, we remove it or separate it from direct account identification.

Account protection

Before discussing or changing personal data, we may ask for an account check through the registered contact path. This helps keep requests tied to the correct account holder.

Privacy Policy Questions From Indonesia

These answers address the questions you may search before opening an account or asking about an existing record. They explain the Privacy Policy in practical terms, including payment references, cookies, phone checks, corrections and access requests. If your situation is not covered, use the support route shown beside your account area.

The merdeka138 Privacy Policy covers account details, phone verification, wallet and bank references, device signals, cookies, retention and requests to access or correct your personal data.

Yes. When you use DANA or QRIS, we may retain the transaction reference and status needed to match the cashier request with your account. We do not need your wallet password.

Phone verification helps connect an account request to the registered contact detail before access. It also lets us check that a Privacy Policy request or profile correction comes from the right account holder.

We may use browser type, operating system, session time and related device signals. These details help identify unusual access and keep your mobile session connected without replacing your account credentials.

Use the support route beside your account area and state that you want a personal data request. Include your registered contact detail; we may complete an account check before responding.

Yes. Send the incorrect detail and the requested correction through support. We may ask for phone verification or another account check before changing the record linked to your profile.

We keep account, device and transaction records for operational, dispute or legal needs. When the purpose ends, we remove the record or anonymise it under our retention process.