Reference

Open markas338 login Privacy Policy

The markas338 login Privacy Policy explains what we collect when you create an account, sign in from a phone or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsDevice choicesContact routes
Explore Our Lobby Read FAQ
markas338 login Open markas338 login Privacy Policy
CONTACT OPTIONS

Ask about Privacy Policy choices

A clear contact path helps you handle a privacy question without repeating your account story across different teams. When you contact us about the Privacy Policy, include the account phone number, the subject of your request and the relevant date; do not send a wallet PIN or full banking password. We use the account record to confirm that a change, copy or deletion request comes from the right person. The same route can help when a QRIS receipt or device sign-in record needs clarification.

Team online

Account privacy request

Ask us to access, correct or delete personal details linked to your account where local law permits. We may request a phone verification step before changing the record, so the request is not applied to the wrong account.

Wallet record question

Send the payment date, method and reference when asking about DANA, OVO, GoPay or QRIS data. For BCA, BRI, Mandiri or BNI transfers, we use the available transaction reference rather than asking for your banking password.

Sign-in assistance

If a phone or desktop sign-in creates an unfamiliar device record, contact support with the approximate time and device type. We can explain the account entry, help protect the session and direct you back to the Privacy Policy.

DATA HANDLING

Switch through our privacy controls

We keep the Privacy Policy practical by connecting each control to an account action you can recognise.

Collected account details

We may collect your phone number, account identifiers and verification result when you open an account. These details support sign-in and account matching; we do not need your wallet PIN to connect a DANA, OVO, GoPay or QRIS reference.

Device and session signals

A mobile browser or desktop session can create technical records such as device type, browser setting, time and security events. We use these signals to recognise access patterns and investigate an unfamiliar sign-in without reading unrelated content on your device.

Cookies and preferences

Cookies can keep a session active, remember a language or preserve a setting you selected. You can adjust cookie controls in your browser, although turning them off may require another phone verification before the account opens.

Payment references

Our records can show a method, amount, status and reference for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We use this trail to match a cashier event and receipt, while sensitive wallet credentials remain with the payment service.

Retention and deletion

We retain account, security and transaction records only for the period needed for account support, dispute handling, fraud checks or a legal duty. When a valid deletion request applies, we remove or de-identify eligible records and explain anything that must remain.

Requests and corrections

You can ask for a copy, correction, restriction or deletion of eligible personal data through support. Include your account phone and request type; after verification, we explain the next step and respond according to applicable Indonesian requirements and local law.

Browse Privacy Policy answers

These Privacy Policy answers cover the searches we hear before an account is opened: what we collect, how wallet records are handled, which device details matter and how to request a change. If your case involves a particular account event, contact us with the phone number and transaction reference so we can address the correct record.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references connected with your account. It also explains retention, security handling and your request rights. Access or eligibility depends on local law, including the law applicable to your location in Indonesia.

Yes. The Privacy Policy covers the method, status, date and reference associated with DANA, OVO, GoPay or QRIS activity. We use those details to match a cashier event or receipt. We do not ask for or need your wallet PIN to investigate a payment record.

A phone or browser record helps us recognise your account entry, identify unusual access and investigate a session that you do not recognise. It can include device type, browser setting and sign-in time. These signals support account security and are handled under the Privacy Policy.

Contact support with your account phone number, the field you believe is incorrect and the correction you want. We may complete phone verification before changing the record. We then confirm what can be updated and explain any reason a related security or payment record must remain.

You can request deletion of eligible personal data through the contact route described on this page. We verify the account holder first, remove or de-identify records where local law permits, and explain any account, dispute, security or legal record that must be retained.

The retention period depends on why the record exists. Account and sign-in details support access and security, while BCA, BRI, Mandiri, BNI or virtual account references support payment tracing and disputes. We keep each category only as long as its operational or legal purpose requires.

Use our support contact path and state that your request concerns the Privacy Policy. Add your account phone, request type and relevant date, but never send a wallet PIN or banking password. We can then explain data access, correction, deletion, cookie or device-record questions.

Related Pages

markas338 login Indonesia Account information Football Score Chase About Us Access guide