Reference

seni108 Privacy Policy, Made Clear

Our seni108 Privacy Policy explains what account, wallet, device and cookie data we use when you open the lobby, including when you access Live Baccarat Elite or check…

Account dataWallet recordsDevice choicesCookie controls
seni108 seni108 Privacy Policy, Made Clear
HELP WITH PRIVACY

Get A Direct Answer About Data

A clear contact route matters when a phone check, wallet reference or cookie choice raises a privacy question. Use the support path beside the account and cashier areas, describe the request in plain English, and give only the details needed to locate your record. We can explain a data use, help you make a correction request, and tell you when a legal or security check is needed before we act.

Team online

Account access

If you cannot reach your account after phone verification, contact us through the account support path. Tell us the device type and the sign-in issue, but never send your password or a complete wallet security code. We use those details to route a privacy or access request safely.

Wallet records

For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account query, provide the transaction reference and approximate time. We can explain which payment record is held and why it may be needed for account matching, while keeping sensitive wallet credentials out of the request.

Data requests

Ask us to access, correct or clarify personal data through the same support route. We may ask for account details to confirm that the request comes from you. Our reply will set out any required step, any lawful restriction, and the next action available under this Privacy Policy.

OUR DATA METHOD

What seni108 Keeps And Why

We handle privacy as an account process, not as a broad statement detached from the lobby.

Account details

When you open an account, we use the details needed to create your profile and provide account access. Phone verification can be part of that path. We do not ask you to place wallet passwords in ordinary support messages, and we use account data to answer requests tied to your profile.

Payment references

A payment record can contain a rail name such as QRIS, DANA, OVO, GoPay, bank transfer or virtual account, plus a reference and status. We use this trail to reconcile an account action and investigate a mismatch. It does not give us your separate wallet password or banking login.

Cookies

Cookies and similar browser storage can remember a session setting, help keep account pages working and show whether a page has loaded correctly. You can manage browser controls where available. Turning some cookies off may affect sign-in or saved choices, but it does not erase records already required for account security.

Device security

We may use device, browser and session signals to spot unusual sign-in activity and protect your account. This can include checking a mobile browser path before showing account data. If a security check blocks access, contact us through the account route so we can explain the next verification step.

Retention checks

We retain account, payment and support records for the period needed for the stated service, security work or legal duty. A QRIS receipt reference may therefore remain after a page visit ends. When a record no longer has a valid purpose, we remove it or keep it in a restricted form where required.

Change requests

To request a correction, access copy or clarification, contact us with your account identifier and the precise data concern. We confirm identity before changing or releasing personal data. If a request conflicts with a security or legal retention duty, we explain that limit and the route still available.

Answers Before You Open An Account

These Privacy Policy answers focus on the questions we expect before an Indonesian account is opened or used. They cover the data connected with phone verification, mobile access, local payment references, cookies, retention and requests for changes. If your situation is not listed, use the privacy contact path and include the smallest useful detail.

It covers personal data connected with your account, phone verification, device sessions, cookies, support messages and payment references. That includes records linked to DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity when those details are needed to operate or protect your account.

Phone verification helps us connect account access to the person completing the account step and helps address sign-in issues. We may use the result for security and account administration. Access and eligibility depends on local law, so the available path can vary by permitted region.

Yes. The policy covers device, browser and session signals used to keep a mobile account page working, investigate unusual sign-ins and protect personal data. It also explains cookies and browser storage. You can manage available browser settings, although some account functions may then behave differently.

We may keep a rail name, transaction reference, amount status and timing so an account action can be matched and a failed step can be checked. We do not need your wallet password for that purpose. A receipt question is handled through the support path beside the cashier area.

Yes. Send a request through the privacy contact route with your account identifier and a precise description of the data you want checked. We confirm identity before releasing or changing records. Where local law permits, we explain the result, timing and any lawful reason a record must remain.

We keep records for the operational, security or legal purpose stated in the Privacy Policy. A payment reference or support exchange can remain after a session ends when it is still needed for reconciliation or protection. We remove or restrict records when that purpose no longer applies.

Use the support route near the account and wallet areas, and label the message as a privacy request. Include your account identifier, device path or transaction reference only when relevant. Do not send a password or complete security code. We will explain the next verification step or response path.