Reference

Open mitra123 Privacy Policy For Your Account

Our mitra123 Privacy Policy explains how we collect, use, store and protect the account details you provide before entering the lobby.

Account dataWallet recordsCookie choicesAccess requests
mitra123 Open mitra123 Privacy Policy For Your Account
CONTACT ROUTES

Use Support Paths For Privacy Requests

Privacy questions should start with the account help route shown after you sign in, because it lets us connect your request to the correct account record. Include the phone number linked to your account and a clear description of the change or access request. If wallet status is involved, keep the DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference ready without sending your password.

Team online

Account access

Use the signed-in account help path when you need a copy of personal data, want to correct a phone detail or cannot complete the verification step.

Wallet record

For a privacy request involving DANA, OVO, GoPay or QRIS, provide the transaction reference and date so we can locate the relevant record without requesting your wallet password.

Security concern

If a device session looks unfamiliar, contact support through the account route and change your password immediately; we use the account record to assess the access concern.

DATA PRACTICES

Explore How We Handle Your Privacy

Clear handling matters when your account connects phone verification, wallet records and mobile sessions.

Account data

We may hold your account identifier, verified phone detail, sign-in records and support messages so we can provide access, answer a request and trace unusual activity.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match account activity. We use them for status checks rather than asking for your wallet password.

Cookies

Cookies and similar session tools can keep sign-in steps working, remember security settings and identify an active device. You can manage browser cookie controls, though some account functions may change.

Account security

Phone verification and session checks help protect access. If you change devices, sign out of old sessions where available and contact the account help route if activity does not look familiar.

Retention period

We keep account, transaction and support records for operational, security, dispute or legal needs, then remove or anonymise them when the applicable retention need ends.

Change requests

Ask us to access, correct or clarify your personal data through the signed-in support path. We may verify account ownership before making a change where local law permits.

Check Privacy Policy Answers Before Opening

These Privacy Policy answers cover the questions we expect you to ask about account creation, mobile access, wallet records and personal data. If your situation is different, use the support route connected to your account so we can assess the request with the right record.

The mitra123 Privacy Policy covers account details, phone verification, device sessions, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number for account verification, sign-in checks and support matching. It helps us connect a privacy request to the correct account, where access is available and where local law permits.

Yes. The Privacy Policy covers technical session data and cookies used when you sign in through a mobile browser or desktop. These tools help maintain account access and identify unusual device activity.

We use DANA and QRIS references to match account activity, check a payment status and resolve a support request. We do not need your wallet password for that process, and payment providers may hold separate records.

You can request access, correction or clarification through the signed-in account help path. Include your linked phone detail and the specific record concerned; we may verify ownership before responding.

We retain account, transaction and support records only while they serve operational, security, dispute or legal needs. After that need ends, records are removed or anonymised under the applicable process.

Use the account support route as soon as you notice an unfamiliar session, change your password and mention the device or sign-in time. We can then connect the security request with the relevant account record.