Reference

selat66 Privacy Policy For Your Account

selat66 Privacy Policy explains what we collect when you create an account, verify your phone and use DANA or QRIS for account activity.

Account clarityWallet data detailPhone verificationMobile privacy controls
Explore Our Lobby Read FAQ
selat66 selat66 Privacy Policy For Your Account
REQUEST A RESPONSE

Privacy Help Beside Your Account Path

A privacy question should not leave you searching through unrelated account screens. Our support path is placed close to the cashier and account areas, so you can report a wrong detail, ask why a verification record is needed, or request a copy of information linked to your account. Include your registered phone number and the relevant date, while keeping wallet passwords and one-time codes private.

Team online

Account data request

Use the account support path when you want to know which personal details are linked to your profile. We may ask for phone verification before discussing records, so a request is connected to the correct account rather than another person.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send the date, amount reference and payment rail shown in your account. We use that information to trace the status without asking you to share a wallet password or security code.

Correction or deletion

Ask support to correct an inaccurate detail or assess a removal request through the account path. We explain any data that must remain for security or legal reasons, while eligible changes are applied after the account check is complete.

HANDLING DETAILS

What This Privacy Policy Covers Daily

Privacy is handled through practical account steps rather than a hidden setting. We separate identity checks from payment status references, protect sessions on the device you use, and keep the policy available…

Account records

When you open an account, we store the details needed to create that profile and complete phone verification. Changes to your phone number or account identity may require another check, helping us avoid applying a request to the wrong person.

Payment references

Our records can include a transaction reference, selected rail and status for DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. These entries help reconcile an account action; they are not a request for your wallet PIN.

Device sessions

We may record browser type, device signals and sign-in time to spot an unusual session. On mobile, closing the browser can end a session depending on its settings, so sign in again rather than sharing a saved account screen.

Cookies and storage

Small browser files can remember a session choice and support page operation. You can clear them through your browser settings, although doing so may sign you out and require phone verification before account access continues.

Retention decisions

We keep personal and payment-related records for as long as they support account security, dispute handling or a legal need. When a record no longer serves one of those purposes, we remove it or reduce its connection to you.

Your request route

You can ask what data we hold, request a correction or question a retention decision through account support. Include enough detail for us to locate your record, but never send a password, wallet PIN or one-time code.

Privacy Policy Answers For selat66

These Privacy Policy answers focus on the account, device and payment questions you may search before opening an account. We keep each response tied to an actual selat66 process, including phone verification, wallet references, browser storage and the support route. Where a request affects access or eligibility, the outcome depends on local law.

The selat66 Privacy Policy covers account details, phone verification, sign-in activity, device and browser signals, cookie use, payment references and support requests. It explains why we use each category, how long records may remain, and how you can ask for access, correction or removal.

We use your phone number to create and protect your account, complete the account step before access, and connect a privacy request to the right record. If you change that number, we may repeat verification. We do not need your DANA, OVO or GoPay PIN.

No. Our Privacy Policy concerns payment references such as rail, status and transaction date, not your QRIS, DANA, OVO or GoPay password. Those references help us investigate an account record or status question while sensitive wallet credentials stay outside the support request.

Open the account support path and ask for a copy or description of data linked to your profile. Include your registered phone number and the relevant account detail. We may complete a phone verification check before responding, and access depends on local law.

Yes. Send a correction request through account support and identify the detail that is inaccurate, such as a phone number or account record. We check the request before changing it, and we explain if a record must remain for security or legal reasons.

We keep data while it is needed for account security, payment reconciliation, dispute handling or a legal obligation. After that need ends, we remove the record or reduce its connection to you. A support response can explain the reason a particular record remains.

You can clear or restrict cookies through your mobile browser settings. The Privacy Policy notes that this may sign you out, remove session choices or require phone verification again. We still need limited account records for security, and device behaviour varies by browser.

Related Pages

selat66 Indonesia About Us FAQ selat66 Casino Basketball IBL Bet