Reference

Open s9s Privacy Policy Before Account Access

Our Privacy Policy explains what s9s collects when you create an account, verify your phone, browse Speed Baccarat or use DANA and QRIS.

Account dataWallet referencesDevice choicesPrivacy requests

Explore Our Lobby Read FAQ

Explore How Wallet Data Is Recorded

s9s Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Your Privacy Policy rights start with a clear account trail. When you enter your phone number and complete phone verification, we use those details to create and protect your account, while records connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity help us

1
match payment status to the correct account. We do not treat a wallet name alone as permission to access unrelated account content. Device type, browser signals and login events may be recorded to detect unusual access, including when you switch from a mobile browser to desktop.
2
Game or lobby activity, such as opening Aviator or Fish Hunter, may appear in account records where needed for service operation and dispute checks. Access to s9s depends on local law, and our Privacy Policy applies where local law permits. You can ask us which data
3
is held, why it is used and how to request a correction.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST HELP

Switch To Support For Privacy Requests

A privacy question should not get lost beside a cashier issue. Use the support route inside your account and identify the email or phone linked to your s9s profile.

Account support route Open support from your signed-in account and select a privacy request. Include your registered phone number so we can locate the correct profile before discussing account data.

Cashier privacy check If your request concerns DANA, OVO, GoPay, QRIS or a bank transfer record, share the payment date and status only. Do not send a wallet PIN or full security code.

Device access question Tell us whether the access came from a mobile browser or desktop, plus the approximate login time. This helps us review a device event while keeping your message focused.

DATA CONTROL PATH

Browse s9s Data Controls And Security

Privacy is handled through practical account controls rather than vague promises. We separate identity details, wallet references, device signals and support messages so a request can be checked against the right record.

Account identity

Phone verification connects your account to a reachable contact point. We use that step to confirm requests about access, profile details or changes to the information attached to your account.

Payment references

DANA, OVO, GoPay and QRIS records are used to identify payment status, not to expose your wallet PIN. Bank transfer and virtual account references are checked against the matching account.

Cookies and devices

Cookies and device signals can support login continuity, fraud checks and session control. You can review browser settings, while changing them may affect how account access works.

Security events

Login time, browser type and unusual session changes may be retained for account protection. If a device looks unfamiliar, support may ask for a fresh phone verification step.

Retention choices

We keep records for as long as needed for account operation, payment matching, security checks or a documented request. When a record is no longer needed, our handling follows the applicable retention process.

Change requests

You can ask us to access, correct or remove eligible personal data through the account support route. We may confirm your identity first and explain any record that must remain.

Ask About Privacy Policy And Your Rights

These Privacy Policy answers address the account steps Indonesian customers ask about most often. They cover phone verification, wallet records, device activity, cookies, retention and contact options, so you can decide what to share before opening an account.

The s9s Privacy Policy covers account details, phone verification, wallet references, device signals, cookies, login events, support messages and activity records needed to operate and protect your account.

Phone verification helps connect an access request to the correct account and supports account recovery. We may use it before discussing profile data, changing details or reviewing an unusual login.

Our Privacy Policy does not ask you to send a wallet PIN through support. DANA, OVO, GoPay and QRIS references are used for matching payment status, while sensitive credentials should remain private.

Yes, you can send an access request through the signed-in support route. Tell us the registered phone number and request scope; we may verify your identity before locating the records.

Contact support from your account and state which detail is incorrect. We can review profile, phone or payment-reference data, then explain the correction step and any verification needed.

Cookies may keep a mobile browser session usable and help us identify unusual access. You can adjust browser cookie settings, but restricting them may require you to verify or log in again.

Use the support path inside your account and write that your request concerns the Privacy Policy. Include your registered contact and relevant device or payment date, without sharing passwords or wallet PINs.

Open s9s Privacy Policy Before Account Access

Switch To Support For Privacy Requests

Browse s9s Data Controls And Security

Account identity

Payment references

Cookies and devices

Security events

Retention choices

Change requests

Ask About Privacy Policy And Your Rights

01 What does the s9s Privacy Policy cover?

02 Why does s9s need phone verification?

03 Does s9s store my DANA or QRIS PIN?

04 Can I request my personal data from s9s?

05 How can I correct information on my s9s account?

06 How does s9s handle cookies on mobile?

07 How do I contact s9s about Privacy Policy access?

Related Pages