Reference

Your markas338 Privacy Policy, Made Clear

Our Privacy Policy shows how markas338 handles your account details, phone verification, wallet records and device activity before you open the casino or sports lobby.

Account dataWallet recordsCookie choicesContact steps
markas338 Your markas338 Privacy Policy, Made Clear
CONTACT ROUTES

Get Help With A Privacy Request

A direct support route helps when you want to ask what we hold, correct an account detail, or question a wallet record. Start from your signed-in account and include the phone number attached to your profile, the request you want handled, and any relevant receipt reference. If you are in Jakarta or elsewhere in Indonesia, we may ask for a secure account check before discussing private records.

Team online

Account request

Send a privacy question through the signed-in support path and identify the account phone number. We use that account step to avoid sending personal records to an unrelated contact.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer, or virtual account records, include the receipt reference and date. We can then separate our account record from the provider's own data.

Access concern

If your account opens on one device but not another, tell us the device type and sign-in time. We use those details to check session security without asking for your password.

DATA PRACTICE

How Your Account Data Is Handled

We keep this policy practical: account records support sign-in, phone checks, payment matching, security checks, and your requests about stored data.

Account details

We use your submitted name, phone number, and sign-in details to maintain the account path and complete phone verification before private account records are discussed.

Payment references

Our records may show a wallet name, bank rail, amount reference, and status for DANA, QRIS, BCA, BRI, Mandiri, or BNI. Provider-held credentials stay with that provider.

Cookie settings

Cookies can retain sign-in state, language choice, and security signals on your browser. Clearing them may require you to complete phone verification again when returning.

Device security

We may record browser type, device signals, and session times to spot unusual access. We never need your password or wallet PIN to check a session.

Retention period

We keep records while needed for account operation, payment disputes, security checks, or legal duties. When a record no longer serves one of those purposes, we remove or anonymise it.

Change requests

Ask us to correct eligible details or explain a stored record through support. We verify account ownership first, then confirm what action we can take under local requirements.

Privacy Policy Answers For Indonesian Accounts

These Privacy Policy answers cover the searches we hear most often before account access. They explain wallet records, cookies, device checks, retention, and contact steps in plain language. If your question concerns a specific account, sign in first so we can check the correct record without exposing private details.

It covers account details, phone verification, sign-in activity, cookie settings, support messages, payment references, device signals, retention, and requests to correct or remove eligible personal records.

We record limited payment references so a DANA or QRIS action can be matched to your account and its status. Wallet credentials and PINs remain with the payment provider.

Yes. Send the request through signed-in support, include your account phone number, and complete our ownership check. Where local law permits, we will explain which eligible records can be provided.

Contact support from the account connected to the detail, state the correction clearly, and complete phone verification if requested. We check the change against account security and local requirements.

Yes. Cookies may retain sign-in state, language choice, and security signals on your mobile browser. Clearing browser data can end the session and require another phone check.

We retain payment references only as long as needed for account operation, receipt matching, disputes, security checks, or legal duties. The period can vary by the record and local law.

Use the signed-in support path and describe the concern without sending a password, wallet PIN, or one-time code. Include a receipt reference or device detail only when it helps locate the record.