Reference

markas 338 Privacy Policy for Your Data

markas 338 explains how we collect, use and protect the details connected with your account, wallet activity and device access.

Account detailsWallet recordsCookie choicesDevice access
markas 338 markas 338 Privacy Policy for Your Data
CONTACT PATH

Where to Ask About Your Privacy Policy

A direct support route helps you act on this Privacy Policy without sending sensitive details to the wrong place.

Data access request Ask us what account details, phone verification records, device events or payment references we…
Wallet receipt check If a DANA, OVO, GoPay or QRIS receipt is attached to your account activity…
Correction request Tell us which account detail needs changing and why it is inaccurate.
DATA PRACTICE

Privacy Controls Around Live Roulette Diamond

Our handling process separates account identity from the activity needed to operate a session and answer a support request.

Account security

Phone verification helps us connect an access request with the correct account.

Device signals

Your mobile browser or desktop session can send device, browser, language and connection signals.

Cookie choices

Cookies can remember session settings, help keep you signed in during a visit and show us where a page is…

Activity records

Opening Sumatra Tiger Slots, Spaceman Crash Play or another lobby title can create an account activity record.

Retention requests

You can ask how long a category of data is kept and why it remains stored.

Policy changes

If we change this Privacy Policy, we will place the updated wording on this page and show the revised date…

Privacy Policy Questions About Your Account

These Privacy Policy answers focus on the questions you may have before opening or using an account from Indonesia. We explain the data connected with phone verification, cookies, wallets, device access and payment receipts in plain language. If your question is specific to your account, use the support contact path rather than placing private credentials in a message. Account access and eligibility depends on local law.

It covers account details, phone verification, login and device signals, cookies, lobby activity, payment references and support messages handled through markas 338. It also explains your options to ask for access, correction, retention details or other changes where local law permits.

DANA and QRIS references help us match a receipt or payment status with the correct account. We may retain the reference, amount status and related account event, but you should never send a wallet PIN, password or one-time code to support.

Yes. Send a data access request through the account support contact shown on the site. Include the phone number linked to your account and enough context to locate it. We may complete phone verification before discussing or providing private records.

Cookies can support a login session, remember settings and help us identify page errors. Your browser controls can remove or restrict them. Required cookies may be needed for account access, so removing them can prevent parts of the account path from working.

Device and browser signals may be recorded when you log in from a mobile phone or desktop. These signals can include browser type, language, connection details and security events. We use them to protect access and investigate account issues.

Use the support contact path and identify the detail that is wrong, such as a phone number or account name. We may ask for a verification step before changing it, so a third party cannot alter your profile or payment-linked records.

Ask us about deletion or retention for a specific data category through support. We assess the request against active account needs, security checks, payment reconciliation and legal duties. Some records may remain where local law permits or requires continued storage.