Reference

miyajp Privacy Policy for Your Account

miyajp Privacy Policy explains what we collect when you open an account, use the mobile lobby, or check DANA and QRIS payment status.

Account dataCookie choicesPayment recordsContact requests
Explore Our Lobby Read FAQ
miyajp miyajp Privacy Policy for Your Account
CONTACT THE TEAM

Privacy Policy Help For Account Questions

A clear contact path matters when a privacy question concerns a login or wallet record. Tell us which account step created the concern, such as phone verification, a QRIS receipt, or an OVO status message, and we can direct the request to the right handling process. We ask you to use the contact details shown with this policy so that we can connect the request with your account without asking you to send unnecessary personal data.

Team online

Data access request

Ask us to identify the personal data linked to your account and explain how it is used. Include the account contact detail you normally use, but do not send a wallet password, one-time code, or full payment credential in your first message.

Correction request

If your phone detail or account record is inaccurate, describe the specific field that needs attention. For a bank transfer or virtual account reference, share only the limited receipt detail needed for us to locate the relevant record.

Privacy contact route

For deletion, objection, or policy questions, use the contact route attached to this page. We may need to confirm account ownership before changing data, especially when the request relates to GoPay, QRIS, or a disputed transaction.

DATA HANDLING

Inside miyajp Privacy Controls

We keep the Privacy Policy practical by tying each data category to a real account action.

Account information

When you open an account, we may handle your contact detail, phone verification result, login history, and selected account settings. These records help us connect a privacy request to the correct account and prevent an unrelated person from changing your information.

Payment references

A DANA, OVO, GoPay, or QRIS transaction can create a reference, amount, status, and time record. Bank transfer and virtual account requests may carry similar reconciliation details, used to trace the account step without asking for your wallet PIN.

Cookies and sessions

Cookies and session signals can remember a signed-in state, language setting, or security event on your browser. You can manage cookie behaviour through your browser controls, though limiting some cookies may require you to repeat the login path.

Device security

Our security checks may examine browser, device, IP, and session signals around account access. These details help us identify unusual login behaviour and investigate a stalled wallet status, but they are handled as security data rather than as a public profile.

Retention choices

We retain account and payment records only for the period needed for the stated purpose, account security, dispute handling, or legal duties. When a deletion request cannot be completed because a record must remain, we explain the reason and the relevant limitation.

Policy changes

If this Privacy Policy changes in a way that affects your account data, we will present the updated wording through an appropriate account or policy path. You can ask us to clarify a change before continuing with phone verification or payment activity.

Privacy Policy Answers For miyajp

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover the data behind phone verification, mobile access, cookies, payment records, and requests sent to our team. If your question concerns a specific DANA, QRIS, or bank-transfer reference, use the policy contact route with only the details needed to locate that record.

It covers account details, phone verification, login and device signals, cookies, support messages, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. It also explains retention, security handling, request rights, and limits that depend on local law.

Phone verification helps us connect account access with the contact detail you provided and helps protect the account from unauthorised changes. We record the verification result and related security event, not a wallet password or one-time code sent to you.

Yes. The Privacy Policy covers the miyajp-side reference for a QRIS, DANA, OVO, or GoPay transaction, such as status, time, and reconciliation detail. The wallet or payment provider remains responsible for its own service and its separate handling terms.

Use the contact route shown with this Privacy Policy and describe the account detail involved. We may ask for an ownership check before sharing information. Do not include your password, one-time code, wallet PIN, or complete payment credentials in the first request.

You can request a correction when an account record is inaccurate and ask about deletion where the law allows it. Some security, dispute, transaction, or legal records may need to remain for a defined purpose; we will explain that limit when it applies.

Cookies and session data can keep your mobile browser connected to the correct account path and remember selected page settings. You can change cookie controls in the browser, but restricting required cookies may sign you out or make phone verification repeat.

Yes. Access, eligibility, and certain data requests depend on local law, and we apply the available account and privacy process where local law permits. If a rule limits a request or account action, our contact team can explain the relevant reason.

Related Pages

miyajp Indonesia Account information Esports Free Fire Krakatau Blast Megaways Live Roulette Wheel