Reference

Open mitra138 Privacy Policy with clarity

mitra138 Privacy Policy explains what we collect when you open an account, verify your phone, use a mobile device, or select DANA and QRIS at the cashier.

Account dataWallet referencesDevice choicesContact steps
mitra138 Open mitra138 Privacy Policy with clarity
CONTACT PATHS

Use support when privacy questions arise

You do not need to guess where a privacy request belongs. Start from the account support route and include the phone number linked to your account, the subject of your request and…

Account message Send a privacy question through the signed-in account support path. Include your registered phone number and request type so we can check the correct account record.
Cashier status For DANA, OVO, GoPay or QRIS data questions, share the transaction reference shown in your account. We can check the recorded status without requesting your wallet password.
Access concern If an unfamiliar device or login appears, contact support through the account path and change your password. We may ask account questions to confirm that the request comes from you.
HANDLING DETAILS

Explore the controls behind this policy

Privacy choices work best when the operating steps are visible. We separate account identity details from wallet references, use device signals to assess unusual sign-ins, and keep access records only for the…

Account creation

When you open an account, we collect the details needed to create login access and complete phone verification. A clear account step helps us connect requests to the right profile.

Wallet references

DANA, OVO, GoPay and QRIS may return a reference, amount and status for matching purposes. We do not ask you to disclose a wallet password through our support route.

Cookie choices

Cookies can keep a session active, remember basic settings and help us identify repeated sign-in problems. You can manage cookie controls in your browser, though some account steps may then need repeating.

Device security

We may record browser type, device signals, IP address and login time to spot unusual account access. If a device looks unfamiliar, change your password and contact us through the account path.

Data retention

We retain account and transaction references for service, dispute handling and legal requirements, then remove or de-identify them when they are no longer needed for those purposes.

Change requests

Ask us to correct, access or delete eligible data through support. Include your registered phone number, the requested change and a safe contact route; we may verify ownership before responding.

Browse answers about Privacy Policy

These Privacy Policy answers address the account and payment questions you may have before opening access. We keep the examples tied to real mitra138 steps, from phone verification and mobile sign-ins to DANA and QRIS references, so you can decide what to share and how to contact us.

It covers account details, phone verification, login records, device signals, cookies, support messages and payment references. It explains why we use each category, how long records may remain, and how you can request access, correction or deletion where local law permits.

We use your phone number to create and identify your account, complete the required verification step and connect a support request to the correct profile. If you do not provide it, account access or certain account actions may not be available.

No. When you use DANA, OVO, GoPay or QRIS, we may receive a transaction reference and status for account matching. Your wallet password and private wallet credentials stay with the relevant payment service, so do not send them to support.

We may record device type, browser details, IP address, login time and related technical signals. These details help us identify unusual access, investigate a failed sign-in and protect the account path without needing the contents of your personal device.

Use the signed-in account support path and state whether you want access, correction or deletion. Add your registered phone number and the specific record involved. We may verify account ownership before handling the request, and timing depends on local law.

We keep records for account service, payment matching, dispute handling and legal duties. After those needs end, we remove or de-identify data according to our retention process. Exact periods can vary by record type and applicable local requirements.

Yes. Contact us through the account support route and mention the browser or device path involved. We can explain session cookies, sign-in records and related settings. Your browser controls cookies, but changing them may require you to repeat account steps.