Reference

skwslot Privacy Policy for account access

Our Privacy Policy explains the data connected to your phone verification, login activity, and DANA or QRIS wallet status.

Phone verificationCookie choicesDANA recordsQRIS status
skwslot skwslot Privacy Policy for account access
HELP ROUTES

Find policy help from cashier

A clear support route helps when a privacy question is tied to a login or wallet record. Start from your account area, then use the help path beside the cashier status when a DANA receipt, QRIS reference, or phone verification needs checking. Our support handling keeps the request connected to the account step you describe, rather than asking you to repeat details across unrelated pages.

Team online

Account privacy request

Open the account help path and state whether you need to see, correct, or remove personal data. Include the phone verification step involved so we can identify the right account record without requesting unnecessary details.

Wallet status check

Use the cashier help path when a DANA, OVO, GoPay, or QRIS status appears incomplete. Share the transaction reference shown in your account, not wallet credentials, so we can check the recorded status safely.

Cookie preference question

Use the privacy request path if your cookie choice is not behaving as expected on mobile. Tell us which browser page you used and whether the setting changed after logging in or leaving the account area.

DATA CONTROLS

Six checks for account data

Your account data is handled for defined account, security, and support purposes. We separate phone verification from wallet status checks, and we use login signals to identify unusual access attempts rather than…

Data we collect

We record details you provide for account creation, including contact and verification details, plus technical signals from login sessions. This lets us confirm account access and keep a clear record when you ask about a specific account action.

Why wallet data is used

Wallet references from QRIS, DANA, OVO, GoPay, virtual account, and bank transfer activity are used to match status updates to your account. We use the reference shown in the cashier flow, not your wallet password or private credentials.

Cookie choices

Cookies can remember session and preference settings after you move from login toward Blackjack, Crash Games, or another lobby area. You can adjust browser cookie controls, although some account functions may need session cookies to remain available.

Account security

Phone verification and login signals help us check that an account access request comes from the expected account path. Keep your verification code private, and report an unfamiliar login through account help as soon as you notice it.

Retention approach

We keep personal and transaction-related records only while they are needed for account operation, security checks, support handling, dispute questions, and applicable obligations. When records are no longer required, we handle them under our internal deletion process.

Changing your details

You can request a correction where phone, account, or payment-reference details are inaccurate. Use the support route within your account, explain the record that needs changing, and provide only the details needed to locate that record.

Privacy Policy questions for your account

These answers cover the Privacy Policy questions we receive around account access, cookies, and Indonesian wallet records. They focus on practical steps: where to find a request path, what to include with a QRIS status question, and how device settings affect a login session. If your case involves a particular payment reference or verification step, use the account help route so we can check the matching record.

The skwslot Privacy Policy covers personal details used for account creation, phone verification, login security, cookie preferences, wallet status records, and support requests. It also explains why we handle those details and how you can ask about a record connected to your account.

Yes. The Privacy Policy covers the transaction reference and status linked to DANA and QRIS activity in your account. We use those records to match a cashier update, investigate a missing status, and respond when you provide a receipt reference through support.

Open the account support path and identify the detail that needs correction, such as a phone verification record or wallet reference. Give us enough context to locate the record, but do not send wallet passwords, verification codes, or other private credentials.

Yes. You can adjust cookie controls in your mobile browser settings and return to the account path to check the result. Session cookies may be needed to keep a logged-in account available while you move from login to the lobby.

We collect phone verification details to connect account access to the number you provide and to help check unusual login activity. This supports account security and lets us locate the correct record when you request help with access or a data change.

We keep account and wallet-status records for the period needed to operate your account, handle security checks, answer support questions, resolve disputes, and meet applicable obligations. When a record is no longer needed, it enters our internal deletion process.

Use the support path in your account and state that your request concerns the Privacy Policy. Mention whether the issue relates to cookies, phone verification, login access, or a DANA, OVO, GoPay, QRIS, virtual account, or bank transfer record.