Reference

mitrajp Privacy Policy for Your Account

Our Privacy Policy explains how mitrajp handles the account details needed for login, phone verification and wallet status across DANA, OVO, GoPay and QRIS.

Account clarityWallet contextCookie choicesContact route
mitrajp mitrajp Privacy Policy for Your Account
PRIVACY HELP ROUTE

Where To Ask About Your Data

A clear support path helps when a Privacy Policy question concerns login, phone verification or a wallet receipt.

Account contact Use the support route attached to your mitrajp account and state whether your request…
Payment receipt Include the DANA, OVO, GoPay or QRIS reference shown in your cashier record so…
Login concern If phone verification or mobile-browser access stalls, describe the device path and account step…
DATA HANDLING DETAIL

How We Handle Your Account Data

Our Privacy Policy is designed around practical account events: creating access, checking a phone number, showing wallet status and resolving payment records.

Account data

We may hold details such as your account identifier, phone verification result and support history so login questions can be…

Cookies

Cookies and similar browser storage can keep a session working between login steps.

Security checks

Phone verification and account checks help us distinguish an authorised request from an unfamiliar device.

Payment records

A DANA, OVO, GoPay or QRIS reference may be retained with status details to reconcile a cashier request and investigate…

Retention

We retain records only for the period needed for account operation, dispute handling, security review or applicable legal duties, then…

Your requests

You can ask what personal data we hold, request a correction, or ask about removal.

Privacy Policy Questions Before Access

These answers address the searches we hear most often before an account is opened or a wallet is connected. If your situation is different, use the account support route and describe the specific record or access step involved.

It covers account details, phone verification, cookies, security records, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification supports account security and helps us match a login or data request with the correct account. The verification result can be retained for security and support purposes.

Yes. The policy covers QRIS, DANA, OVO and GoPay status details and transaction references used to reconcile a cashier request. It does not require you to share unrelated wallet credentials.

Contact us through the support route connected to your account and describe the records you need. We may verify ownership before responding, so private account data is not released to the wrong person.

Yes. Send a correction request through account support with the affected detail and a clear explanation. We may ask for an account check before changing phone, identity or payment-status records.

Cookies or browser storage may keep your session and account steps working on a mobile browser. You can change browser permissions, but blocked storage may interrupt login or phone verification.

Yes. Account access, eligibility and certain data requests depend on local law. We apply the policy to supported Indonesia regions and show any required account conditions during the access flow.