Reference

Privacy Policy for spaceman slot Indonesia

spaceman slot Privacy Policy explains how we handle the account details that let you reach Sic Bo, Fish Hunter and the wider lobby, together with records linked to…

Account dataWallet recordsCookie choicesSecurity checks
spaceman slot Privacy Policy for spaceman slot Indonesia
HELP WITH PRIVACY

Get Help With Your Policy Request

A clear contact route matters when a data question affects your account. We ask you to sign in first where possible, because confirming the account holder helps us avoid sending private details…

Account access If you cannot sign in to request a copy or correction, contact us through the account-help route shown on the site. We may ask for your registered phone number and a verification step before discussing account data or changing contact details.
Wallet records For a DANA, OVO, GoPay or QRIS data question, send the payment reference and date through our support path. We use that reference to locate the relevant record without asking you to share a wallet password, PIN or one-time code.
Privacy requests To ask about access, correction, deletion or a cookie choice, select the privacy request route and describe the change clearly. We may need to confirm ownership before acting, then explain any legal or security reason a record must remain.
DATA HANDLING

What Our Privacy Process Covers

We separate ordinary account operation from privacy requests so each question reaches the right handling step.

Account details

When you open an account, we may collect your name or chosen account details, phone number and verification status. These details support sign-in and account ownership checks. We do not need your password in a support message, so keep it private at every step.

Payment matching

A wallet or bank record helps us confirm whether a transaction is pending, completed or needs attention. For DANA, QRIS, bank transfer and virtual account activity, we use references and status data to answer receipt questions without requesting your private wallet credentials.

Cookies and browser data

Cookies can remember a session, protect sign-in and help us understand whether a page works on your device. On mobile, browser storage may preserve a session until you sign out or clear it. Your browser controls can remove or restrict cookies, though some account functions may then need another sign-in.

Security controls

We monitor events such as repeated failed sign-ins, unusual device changes and phone verification activity. These signals help us investigate account access and protect payment status details. If we ask you to verify ownership, use the account step we provide and never send a password or one-time code.

Retention choices

We retain account, security and transaction records only for the period needed for the stated purpose, account support, dispute handling or a legal requirement. A deletion request does not always remove records that must remain for these reasons. We explain the applicable reason when a request is limited.

Changing your details

You can ask us to correct an inaccurate phone number, account detail or contact record through the privacy request route. Include the old and new detail where safe to do so. We verify the request first, then confirm whether the change was made or needs further evidence.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions we expect from an Indonesian account holder before sign-in or during a wallet enquiry. They cover the data collected through phone verification, mobile browsing, payments and support. If your situation is not listed, contact us through the privacy route and include enough detail for us to locate the account without sharing secret credentials.

It covers account details, phone verification, sign-in activity, device and browser data, payment references, support messages, cookies and security events. We use these categories to provide account access, match transaction status, protect your details and answer requests, subject to local legal requirements.

Phone verification helps us confirm account ownership before access or a sensitive change. It can also help us investigate repeated sign-in failures. We will not ask you to place a password or one-time code in a support message, and you should keep those credentials private.

We may keep the selected payment rail, transaction reference, amount, time and status for DANA, QRIS, OVO, GoPay, bank transfer or virtual account activity. These records help us match a receipt or investigate a pending status; they do not require your wallet PIN.

Yes, where local law permits, you can send an access request through the privacy contact route. Tell us which account detail or record you need, such as phone verification or a QRIS reference. We first confirm ownership, then explain the material we can provide.

Use the privacy request path and identify the inaccurate detail, such as an old phone number or contact record. We may ask for an account verification step before making the change. After checking the request, we confirm whether the correction is complete or needs supporting evidence.

You may request deletion where local law permits. We assess the request against account support, security, dispute and legal retention needs. If some records must remain, we explain why and limit their use to that required purpose rather than treating the request as a blanket removal.

You can adjust cookie permissions in your mobile browser settings and clear stored site data from that device path. Clearing cookies may sign you out or require another phone verification step. We may still retain essential security or transaction records when a valid account or legal reason applies.