Reference

Privacy Policy for Your siberslot Account

siberslot Privacy Policy explains what we collect when you open an account, sign in, use DANA or QRIS, and contact our support team.

Account dataWallet recordsCookie choicesAccess requests
Explore Our Lobby Read FAQ
siberslot Privacy Policy for Your siberslot Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support path helps when you need to ask what data we hold, correct an account detail or understand a privacy choice. Use the support route shown on siberslot and include the email or phone number connected to your account, plus a short description of the request. For payment questions, add the DANA, OVO, GoPay or QRIS reference without sharing a password or verification code. We may ask for account checks before discussing personal records, because a privacy request must reach the person connected to the account.

Team online

Privacy request

Ask us to explain the personal data linked to your account or to clarify a section of this Privacy Policy. Include your registered contact detail so we can identify the correct record before replying.

Account correction

If your phone verification detail or account contact is wrong, tell us which field needs attention. We review the request against the account record and may request an account step before making a change.

Payment record

For a wallet or bank reference, mention the payment rail and transaction time rather than sending private credentials. Our support path can use that detail to locate the relevant record and explain its status.

DATA HANDLING

What Your Privacy Policy Covers

Privacy protection is part of the account path from your first sign-in through any later support request.

Account collection

We collect details you provide during account creation and phone verification, along with sign-in and support records needed to keep the account usable. We use those details for the stated account, security and service purposes.

Payment references

A DANA, OVO, GoPay or QRIS transaction can create a reference, amount and status record. Bank transfer and virtual account checks may also require a matching reference so we can investigate a cashier question without requesting your wallet password.

Cookies and devices

Cookies can support session continuity, language settings and basic site operation on your phone or desktop browser. If you clear them, you may need to sign in again and repeat some account steps before reaching the lobby.

Account security

We use phone verification and account checks to reduce unauthorised access. Keep your password and verification code private, and contact support through the site path if a sign-in record or device session does not look familiar.

Retention choices

We retain records for the period needed to operate the account, resolve a payment or support matter, meet security needs and follow applicable duties. The period can differ by record type, and you can ask what applies to your request.

Your request route

You can ask for access to, correction of or clarification about personal data by contacting support with your registered account detail. We verify the request first, then explain any limit that depends on local law or a continuing account duty.

Privacy Policy Answers Before Account Access

These Privacy Policy answers address the questions we expect you to ask before opening an account or connecting a local payment method. They explain the account data path, cookies, transaction references, access requests and the checks we may need before discussing a personal record. If your situation is not covered, contact us through the support route and refer to your registered account detail.

The siberslot Privacy Policy covers account details, phone verification, sign-in activity, cookies, support messages and payment references. It explains why we use those records, how we protect access, how long records may be kept and how you can ask about correction or access where local law permits.

We collect the details required for your account path, such as contact information and phone verification status, plus records created when you sign in or contact support. We use them to operate the account, check security and respond to account or payment questions.

Yes. A DANA or QRIS request can produce a transaction reference, amount and status record connected with your account. OVO, GoPay, bank transfer and virtual account requests can create similar records, allowing us to match a payment question without asking for private wallet credentials.

Cookies may keep your session active, remember selected settings and support basic account access on a phone or desktop browser. You can manage or clear them through your browser. Clearing cookies may sign you out and require another phone or account verification step.

You can contact our support path and request access to personal data linked to your account. Include your registered email or phone detail, and be ready for an account check. We explain the available response and any restriction that depends on local law.

Tell support which account detail is inaccurate and provide the registered contact used for verification. We review the request against the account record before changing it. Do not send a password or verification code, and understand that some records must remain for legal or security reasons.

Send a retention or deletion question through the site support route with your registered account detail. We assess the record type, any open payment or support matter and duties that apply where local law permits, then explain what can be removed and what must remain.

Related Pages

siberslot Indonesia siberslot Casino FAQ Live Baccarat Gold About Us