Reference

Privacy Policy for Your sultanlido Account

Our Privacy Policy explains how sultanlido handles the account details behind Live Roulette Salon, Mahjong Wins Slots and your wallet choices.

Account clarityWallet referencesPhone verificationCookie choices
Browse Our Lobby Read FAQ
sultanlido Privacy Policy for Your sultanlido Account
CONTACT ROUTES

Get Privacy Help Beside Account Support

A clear contact route matters when you want a copy, correction or explanation of your account data. Start from the support path shown after login and include the phone number or account identifier used during verification, without sending a wallet password or one-time code. We use those details to locate the right record, check your request and keep the conversation attached to your account. Your access still depends on local law.

Team online

Account data request

Ask through the support route inside your signed-in account when you need to know which account details we hold. Include your verified phone reference and the specific request, such as access, correction or deletion, so we can check ownership before responding.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, tell support which payment rail and transaction reference is affected. We use the record to trace status without asking you to disclose a wallet PIN, password or one-time verification code.

Login privacy concern

For an unfamiliar login, changed device or suspicious account message, use the account support path before sharing further details. We may ask for a phone verification step and recent account context to protect your record from an unauthorised change.

DATA PRACTICES

Six Practical Privacy Controls

We handle privacy as part of the daily account flow rather than as a separate promise.

Account records

We use account identifiers, contact details and phone verification results to create access, recover an account and connect support messages to the correct record. You should keep your login details private; our support team will not need your password or one-time code.

Device signals

A phone or desktop browser may send device type, browser version, IP-related signals and login time. We use these details to spot unusual access, keep the sign-in path secure and understand why a session may need another verification step.

Cookie controls

Cookies can remember a session, protect sign-in and retain a choice you make in the browser. You can adjust cookie settings in your browser, although switching them off may require you to sign in again or repeat a security check.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, we may retain a reference, status and account match rather than your wallet password. This lets us investigate a receipt or status question without collecting unrelated wallet credentials.

Retention steps

We retain records while they support account security, payment reconciliation, support handling, legal duties or a disputed transaction. When a record no longer serves one of those purposes, we remove it or separate it from direct account identification.

Change requests

You can ask us to correct inaccurate account details or explain how a record is used through the support route shown in your account. We check identity first, assess the request under local law and tell you if a record must remain for a stated reason.

Privacy Policy Questions From Indonesia

These answers address the questions we hear before an account is opened or a wallet is connected. They focus on the sultanlido Privacy Policy, including phone verification, browser access, payment references and requests about personal data. If your situation is specific, use the support path shown in your account and avoid sending passwords or one-time codes.

The sultanlido Privacy Policy covers account and contact details, phone verification, login and device signals, cookies, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security and requests about your data.

We use phone verification to confirm account ownership, support sign-in protection and help recover access when a device changes. The result can be kept as an account security record. Access or eligibility depends on local law, and we assess requests under that law.

Yes. When you use the mobile browser path from login to the lobby, we may receive device type, browser details, session events and security signals. Cookies can remember your session or a setting, and your browser controls can limit cookies, though sign-in may need repeating.

We may store the payment rail, transaction reference, amount status and account match needed to check a deposit record or receipt. We do not need your DANA or QRIS PIN, wallet password or one-time code. OVO and GoPay references follow the same account-linking approach.

Use the support route shown after you sign in and state whether you want access, correction, deletion or an explanation. Include your verified phone reference and the affected record, such as a login event or QRIS transaction reference. We verify ownership before acting.

We keep data while it is needed for account security, payment reconciliation, support handling, legal duties or a disputed transaction. After that need ends, we remove the record or separate it from direct identification. The retention outcome can depend on local law and the request type.

Use the account support path for a Privacy Policy question, especially when it involves phone verification, a device change or a DANA, OVO, GoPay or QRIS reference. Describe the concern clearly, but never include your password, wallet PIN or one-time verification code.

Related Pages

sultanlido Indonesia Access guide sultanlido Casino Live Roulette Salon FAQ