Reference

Privacy Policy for Your mijit88 Account

mijit88 Privacy Policy explains what we collect when you create an account, verify your phone, sign in from a mobile device and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsCookie choicesData requests
mijit88 Privacy Policy for Your mijit88 Account
DATA HELP DESK

Privacy Questions Reach Our Support Path

A clear contact route matters when you want to ask about personal data rather than a wallet status. We direct privacy questions through the support channel displayed inside your account area, so the request can be matched with the correct account record. Include the email or phone detail connected to your account, the request you want us to assess, and a safe description of the issue. Do not send a password, wallet PIN or full payment credentials. We may ask for account verification before discussing private records.

Team online

Account privacy request

Use the support channel inside your account to ask for access, correction or clarification. We may confirm your phone verification first, then match the request with the account record rather than discussing private details in an open message.

Wallet record question

If a DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference looks unfamiliar, send the date, amount reference and account contact detail through support. We can check the record without asking you to reveal a wallet PIN.

Sign-in data concern

When a mobile or desktop sign-in looks unusual, contact the same account support route and describe the device path. We can focus on the session, phone verification and account access record while keeping your password out of the request.

DATA CONTROL POINTS

How We Handle Privacy Inside mijit88

Privacy controls work best when they match the way you actually use an account. We separate account identity, device activity and payment references so a support request can be checked without collecting…

Account collection

During account creation, we collect the details needed to create and maintain your profile, including the contact route used for phone verification. We ask you to keep those details current so ownership checks and privacy replies reach the right person.

Payment references

A wallet or bank record can contain a reference to DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri or BNI processing. We use the reference to reconcile activity and investigate a receipt, not to request your private banking password or wallet PIN.

Cookies and sessions

Cookies and session markers can support sign-in continuity between your phone and the lobby. If you clear browser storage, you may need to verify the account again. Your browser controls can remove cookies, while account support can explain a session question.

Device protection

We may record device type, browser signals and sign-in time to identify unusual access. This helps us distinguish your normal mobile path from a new session. Never place a password, one-time code or wallet PIN in a support message.

Retention period

We keep personal records only for the period needed to administer the account, answer disputes, trace payment references or meet legal duties. When a record is no longer needed for those purposes, our handling follows the retention rules that apply to the service.

Changes and requests

To request a correction, access copy or policy clarification, use the support path in your account area and describe the exact data concern. We may ask for phone verification before changing a record, and we explain any limit required by applicable law.

Privacy Policy Questions About mijit88

These Privacy Policy answers address the account questions we expect before you open an account or send a support request. They cover the information connected with phone verification, device access, cookies and local wallet references. If your situation is not listed, use the account support channel and describe the specific record you want us to check. We will assess the request against the policy and applicable law.

The mijit88 Privacy Policy explains how we handle account details, phone verification records, device and session signals, cookies, support messages and payment references. It also describes retention, account protection and the route for requesting access or correction before you continue using your account.

Yes. The Privacy Policy covers the account references created when you request a DANA, OVO, GoPay or QRIS transaction. We use those references to reconcile activity and investigate a receipt or status question; we do not need your wallet PIN to handle that request.

Phone verification helps us confirm that an account request belongs to the person who controls the stated contact route. We may use that record when you ask for a data change or account recovery. We will not ask you to place a one-time code in an open support message.

You can send an access or correction request through the support channel shown inside your account area. State the exact record you want checked and include the connected contact detail. We may verify ownership first, then explain what can be supplied or changed under applicable law.

The Privacy Policy covers cookies and session markers used to keep a sign-in path working or remember a browser preference. Clearing them can end a recognised session and prompt another phone check. Your browser settings control cookie removal, while support can clarify a session concern.

We retain payment references, device signals and account records for as long as needed for account administration, dispute handling, security checks or legal duties. The precise period can depend on the record and applicable rules. A support request can ask why a particular record remains stored.

Yes. Requests for access, correction, deletion or other handling depend on local law and the details of the record. Send the request through your account support route, and we will confirm the identity check, available action and any reason a legal duty requires continued retention.