Reference

Open Your Privacy Policy Path

marshmelowu222 Privacy Policy explains what account, device and wallet data we use when you browse Live Roulette Salon or move through the account area.

Account dataWallet recordsDevice choicesRequest access
marshmelowu222 Open Your Privacy Policy Path
HELP WITH DATA

Find Privacy Policy Help Through Support

A clear support route matters when a Privacy Policy request concerns the wrong phone number, a wallet reference or an account record. Contact us through the support path shown after login and describe the request without sending passwords or wallet PINs. We may ask for account details so we can confirm that the request belongs to you.

Team online

Account request path

Use the signed-in support path to ask about a Privacy Policy matter, such as a copy of account data or a correction to your phone verification record. Keep the request specific, and we will use the account details already linked to your profile to locate the relevant record.

Wallet record check

If your request concerns DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, include the date and reference shown in your account. Do not send a PIN, password or complete payment credential. We use the reference to separate your request from another account.

Access concern

When login prevents you from reaching the policy request path, explain the device type and the account step where access stops. We can direct the request through the available contact route while keeping identity checks tied to the account rather than an open message.

DATA HANDLING

See How Privacy Policy Handles Data

We keep the Privacy Policy practical by linking each data type to a real account action: sign-in, phone verification, wallet status, support or device use.

Account creation

Opening an account creates a profile record with the details needed for account access and phone verification. We use that record to connect your requests, sign-in events and account notices. If a detail changes, ask through the signed-in support path so the correction reaches the right profile.

Device signals

When you sign in from a phone, tablet or desktop browser, technical signals can help us recognise the session, protect account access and diagnose a failed step. We do not need your device to store a payment PIN. Browser settings can also affect cookie choices.

Cookie choices

Cookies and similar browser storage can keep a session working, remember selected settings and help us understand which account page failed to load. You can manage browser permissions, though removing necessary storage may require another sign-in or interrupt a saved preference.

Wallet references

A DANA, OVO, GoPay or QRIS reference can be retained beside an account action so payment status questions can be checked. Bank transfer and virtual account records follow the same account-matching purpose. We do not ask support to receive secret wallet credentials.

Retention checks

We retain records for the period needed to operate the account, resolve disputes, protect against misuse and meet applicable legal duties. Retention can differ by record type. A Privacy Policy request can ask what remains connected to your account and why it is still held.

Correction requests

To request access, correction, deletion or a copy where available, use the account support route and state the action clearly. We may verify your identity before making a change. Eligibility and timing for a request depend on local law and the record involved.

Browse Privacy Policy Answers for Your Account

These Privacy Policy answers address the searches we expect from an Indonesian account holder before opening an account. They cover data categories, wallet references, cookies, account requests and local access conditions. If your case involves a specific record, use the support path attached to your account.

The Privacy Policy covers data connected with account creation, phone verification, sign-in, device sessions, cookies, support messages and payment references. It also explains retention, request handling and the situations where access or processing depends on local law.

DANA and QRIS references can help us match a payment status question to your account action. OVO, GoPay, bank transfer and virtual account references may serve the same purpose. We need a reference, not your wallet PIN or full payment credential.

Sign in, open the support path connected to your account and ask for access to your stored data. State whether you need a copy, a correction or another available action. We may confirm account ownership before responding, and the result depends on local law.

Yes. Device signals can help protect a session and identify where a login step fails, while cookies can keep settings and sign-in sessions working. Browser controls let you manage optional storage, although removing necessary storage may require another login.

Retention depends on the type of record and its purpose. We may keep account, payment or support records for operation, dispute handling, misuse prevention or legal duties. Ask through support which records remain connected to your profile and the reason for keeping them.

You can ask for a correction through the signed-in account support path. Explain which phone or profile detail is wrong and provide the account reference requested during verification. We may check ownership before changing it, and available correction rights depend on local law.

The Privacy Policy is available on this page before account creation, so you can check collection purposes, cookies, retention and request steps first. Access to the service itself depends on local law. For a personal question, use the account support route after signing in.