Reference

Privacy Policy For Your master123 Account

Our Privacy Policy explains how master123 handles the details you provide when you open an account, access the lobby, or check wallet activity through DANA, OVO, GoPay and…

Account dataWallet recordsCookie choicesAccess requests
master123 Privacy Policy For Your master123 Account
CONTACT PATHS

Three Ways To Ask About Privacy

A direct request gives you a clearer route to an answer about your Privacy Policy rights. Start from the account help path when you need to check a profile detail, use the cashier-related support path when a DANA or QRIS receipt contains a mismatch, or send a written request for a copy, correction, restriction or deletion assessment. Include the phone number or account reference connected with your request so we can verify ownership without exposing account details to the wrong person.

Team online

Account help

Use the account help path for Privacy Policy questions about your registered phone number, sign-in record, phone verification status or the personal details connected with your master123 account.

Wallet receipt check

If a DANA, OVO, GoPay or QRIS receipt appears against the wrong account detail, provide the payment reference through the cashier support path so we can compare status without requesting an unnecessary full statement.

Written data request

Ask for access, correction, restriction or deletion review through our written contact route. Include your account reference and the exact request so our team can confirm identity and reply about the applicable Privacy Policy step.

DATA CONTROLS

Six Privacy Checks We Apply

Your Privacy Policy protections depend on practical controls rather than broad promises. We separate account identity from payment reconciliation where the task allows, record device and sign-in events to investigate access problems…

Data collection

We collect details you submit during account opening, including contact information and verification data, plus records needed to operate access. We avoid asking for unrelated personal details when a simple account reference can resolve your request.

Cookie choices

Cookies can retain sign-in preferences, security settings and consent choices on your browser. You can adjust browser controls, although removing some cookies may require you to repeat account steps or phone verification.

Account security

Phone verification and sign-in records help us check whether an account request comes from the account holder. If access looks unusual, we may ask for an additional account detail before changing contact or wallet-related records.

Payment separation

DANA, OVO, GoPay and QRIS references are used to match receipts and wallet status with the correct account task. Bank transfer and virtual account details follow the same limited purpose when a payment needs reconciliation.

Retention periods

We keep account, support and transaction records only for the period needed for account operation, dispute handling, security checks or legal duties. When a record is no longer needed, we remove it or reduce its link to you.

Change requests

You can ask us to correct inaccurate details, provide eligible account data, restrict a use or assess deletion. We verify the request first, explain any limit, and record the outcome against the relevant Privacy Policy case.

Privacy Policy Questions Before Access

These Privacy Policy answers address the account and payment questions you may have before opening an account or returning to the lobby. We keep the route practical: identify the record, confirm that you own the account, and ask for the action you need. If a request involves access or eligibility, the outcome depends on local law and the account details available for verification.

The master123 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security controls and how to request access or correction.

Phone verification helps us confirm that an account request comes from the right account holder. We may use it before changing contact details, discussing wallet status, or releasing account data. This check reduces the chance that another person receives or alters your personal account records.

We use DANA and QRIS references to match a receipt, confirm a wallet status or investigate a payment question. We do not need an unrelated personal profile to perform that check. A request may require your account reference and payment reference so we can verify the correct record.

Yes. Send a correction request through the account help or written contact path and identify the detail that is inaccurate. We verify ownership before making a change, then confirm whether the record was updated or explain why a particular field must remain for an operational or legal reason.

Retention depends on the type of record and its purpose. Account and support details may be needed for access and security, while payment records may be needed for reconciliation or dispute handling. We remove or anonymise records when the relevant operational or legal period ends.

You can request an eligible copy, restriction or deletion assessment through our written contact route. We first verify that you control the account, identify the requested records, and check applicable duties. Access or deletion depends on local law and may not apply to every retained record.

Yes. The Privacy Policy applies when you sign in from a mobile browser, move through the lobby, or check wallet status from your phone. Browser cookies and device events may support security and preferences, while changing cookie settings can require another sign-in or phone verification step.