Reference

slot97 Privacy Policy for Your Indonesia Account

Clear control over your account starts with knowing what we collect and why. Our slot97 Privacy Policy covers registration details, phone verification, device signals, cookies and payment references…

Account data explainedWallet references coveredAccess and change requests
slot97 slot97 Privacy Policy for Your Indonesia Account
SUPPORT ROUTES

Where to Ask About Your Personal Data

A direct support route helps you handle a Privacy Policy request without explaining your concern repeatedly. Start from the support link inside your logged-in account and include the email or phone number attached to your profile. We can then locate a wallet reference, explain an access decision or record a correction request. For a stalled cashier matter, keep the DANA, OVO, GoPay or QRIS receipt number ready so our team can match the right record.

Team online

Account request

Use the support link after login to ask for a copy of account data, confirm the phone verification record or request a correction to your registered details.

Wallet reference

Send the payment reference and rail name, such as QRIS or DANA, when asking about stored transaction data. We use those details to find the relevant record.

Security concern

If your access or device looks unfamiliar, contact support through the account route and change your password first. We may ask for verification before discussing private account details.

ACCOUNT SAFEGUARDS

How slot97 Protects Account Data

Our Privacy Policy is supported by practical controls around collection, access and retention. We separate account credentials from payment references, limit staff access to records needed for a support or security task…

Collected details

We may store your name, contact detail, phone verification result, account history, support messages and security events. We collect only what is needed for access, service handling and lawful obligations.

Cookie controls

Our cookies can remember session settings and help identify broken pages. Review cookie choices in your browser settings; blocking some cookies may require you to log in again.

Account security

We check device, browser and IP patterns around sign-in, then may request another account step when activity appears unusual. We never ask for your wallet password or security code.

Payment separation

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity, we keep reference and status details for matching. Wallet credentials remain outside the records we use for support.

Retention approach

We retain account and transaction records only for the period needed for security, dispute handling, service history and legal duties. When a record is no longer needed, we remove or anonymise it.

Your request path

Ask through the logged-in support route for access, correction or clarification. We verify ownership before releasing data, and we explain any restriction when a request cannot be completed.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the account and wallet questions you may have before opening an account. We keep the process practical: use your logged-in support route, identify the relevant payment reference, and expect an ownership check before we disclose private records. Availability and certain processing steps depend on local law.

It covers account details, phone verification, device and browser signals, cookies, support messages, security events and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

No. Our Privacy Policy states that we use transaction references, amounts, status and account identifiers for matching. Your DANA or OVO password and security code stay outside the records used for this process.

Log in, open the support route and request account data access. Include your registered phone or email so we can locate the profile, then complete an ownership check before any private record is shared.

Yes. Send a correction request through account support and identify the field that is wrong. We may ask for phone verification or another ownership step before changing contact or registration details.

Device, browser and IP signals help us identify unusual sign-ins and protect your account. They can also explain why another verification step appears before you open the lobby or check a wallet status.

We keep payment references for the period needed to match deposits, investigate disputes, protect account access and meet legal duties. After that period, records are removed or anonymised under our retention process.

Use the support link inside your logged-in account and describe the data concern clearly. For a QRIS or GoPay matter, add the receipt reference; we verify ownership before discussing account-specific details.