Reference

martabak188 Privacy Policy For Your Account

martabak188 Privacy Policy explains what we collect when you open an account, enter the lobby, or connect DANA, OVO, GoPay and QRIS.

Account clarityWallet recordsDevice choicesDirect requests
martabak188 martabak188 Privacy Policy For Your Account
ASK OUR TEAM

Get Clear Answers About Stored Data

A direct support path helps you understand a Privacy Policy question without sending payment details through an unrelated channel. Sign in, open the account help path near the cashier area, and describe the record or device session you want us to check. We may ask for account identifiers so we can respond to the right person.

Team online

Account data request

Use the support link inside your account when you want to ask what contact details, verification records or account identifiers we hold. Keep the request specific so we can locate the correct profile without asking you to share a password.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, mention the payment rail and approximate transaction reference. We use that detail to separate a wallet-status question from a wider Privacy Policy request.

Device access concern

If a mobile or desktop session looks unfamiliar, tell us through the account help path and change your password from the account settings area. We can examine the related access record while keeping your payment credentials out of the message.

DATA HANDLING

What We Do With Your Privacy Choices

Privacy Policy controls are practical: you can ask what we hold, why we use it and whether a correction is needed.

Collection purpose

We collect account and verification details to create the right profile, confirm access and respond to account requests. Lobby activity such as Live Baccarat Salon or Denpasar Lucky Slots may be linked to an account record when needed for security or account history.

Cookie choices

Cookies help keep your login path open and remember basic settings between pages. You can manage cookie controls through your browser, although restricting required cookies may interrupt account access or make the mobile path return you to login.

Account security

Phone verification comes before account access, and we use session and device signals to identify unusual sign-ins. Never send us a password, wallet PIN or one-time code; our Privacy Policy request process does not need those secrets.

Retention period

We retain account, payment-reference and support records only for operational, security or legal needs. When a record is no longer needed, we remove it or make it less directly linked to you where our obligations allow.

Correction request

If your phone detail, contact record or other account information is wrong, ask us to correct it through the signed-in support area. Include the field you want changed, but do not include a password or full wallet credential.

Access and eligibility

Our Privacy Policy applies to information handled through martabak188, but account access and eligibility depend on local law. If your location prevents access, we will use the available support path to explain what data request options remain open.

Privacy Policy Answers Before Account Access

These Privacy Policy answers cover the questions we expect before you open an account or connect an Indonesian wallet. They explain the records tied to account access, how to request a change and what to do if a device or payment reference needs attention.

It covers account details, phone verification, device and session signals, cookies, support messages and payment references from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account. It also explains why we use, retain, correct and remove those records.

Do not send a wallet password, PIN or one-time code to us. Our Privacy Policy concerns payment references and account matching, not secret wallet credentials. If a DANA or QRIS status needs checking, provide the relevant reference without exposing your private security code.

Sign in, open the account help path near the cashier area and ask for the account records connected to your profile. We may request an account identifier or phone-verification detail to confirm the request belongs to you before responding.

Yes. Send a correction request through the signed-in support area and identify the field that is inaccurate, such as a contact detail or account identifier. We may verify your account first, and you should never include a password or wallet PIN.

The Privacy Policy allows us to use device and session signals to support login continuity, recognise unusual access and protect your account. On mobile, required cookies may keep the path from login to the lobby working; your browser controls optional cookies.

We keep account, payment-reference and support records for operational, security or legal needs. Once a record is no longer required, we remove it or reduce its direct link to you where applicable obligations permit. A support request can ask about a particular record.

Account access and eligibility depend on local law. The Privacy Policy request path remains available through the account support area where local law permits, even when a location or account condition limits access to the lobby or a selected game category.