Reference

Privacy Policy For Your racik98 Account

Our Privacy Policy explains what data we collect when you open a racik98 account, use DANA or QRIS, and move between the lobby and cashier area.

Indonesia account dataWallet activity clarityDirect privacy requestsDevice access details
Browse Our Lobby Read FAQ
racik98 Privacy Policy For Your racik98 Account
HELP WITH DATA

Privacy Questions Follow Your Account Path

A clear support route matters when a privacy question starts with a login, wallet receipt or device session.

Account support path Use the support route attached to your racik98 account when you need a Privacy Policy answer. We can then connect your request to the relevant phone verification, login event or wallet record without relying on an unconfirmed identity.
Cashier record check If your question concerns DANA, OVO, GoPay or QRIS, include the payment reference shown in your receipt and the approximate time. We use those details to locate the transaction record while limiting unnecessary exposure of your wallet information.
Account correction Ask us to correct inaccurate account data through the same account support path. We may confirm your phone verification or request another account step before changing details that could affect access, transaction matching or security checks.
DATA HANDLING

How We Apply This Privacy Policy

Privacy choices are easier to use when the handling process is visible. We separate account access, payment reconciliation, device security and support records so each detail has a clear operational reason.

Account details

We collect the information needed to create and maintain your account, including your phone number, verification state and selected account details. This helps us distinguish an authorised sign-in from an access attempt that needs an extra check.

Wallet records

A DANA, OVO, GoPay or QRIS reference may be stored with account and transaction details so a receipt can be matched correctly. Bank transfer and virtual account records are handled for the same reconciliation purpose.

Cookies and sessions

Cookies and session storage help keep your chosen login state and protect page requests during a visit. Your browser can restrict or remove them, although doing so may require another sign-in or interrupt account access.

Device security

We may record browser type, device signals, connection details and failed access events to identify unusual activity. These signals support account protection and are considered alongside phone verification rather than used as a complete identity record.

Retention periods

We retain records while they are needed for account security, payment matching, a live support request or a legal obligation. When the reason ends, we delete, anonymise or reduce the record according to its operational purpose.

Your requests

You can ask what account data we hold, request a correction, question a processing purpose or ask about removal. Send the request through account support; we may verify your phone or account step before disclosing or changing private data.

Privacy Policy Answers For racik98

These Privacy Policy answers focus on the questions we expect you to have before opening an account or asking us to change an existing record. They explain the practical link between account access, local wallets, mobile devices and support requests. When a matter involves eligibility or access, it depends on local law, and our support path can explain which account step is required for your request.

It covers account details, phone verification, sign-in events, device and browser signals, cookies, payment references, support requests and retention. We describe why each category is used so you can connect the policy with practical events such as a QRIS receipt check or a new mobile login.

We use your phone number for account identification and the verification step required before account access. It can also help us locate the correct account when you ask about a DANA, OVO, GoPay or QRIS record. We do not treat an unverified number as proof of account control.

Yes. The Privacy Policy covers payment references and related account records for DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use these details to reconcile receipts, investigate status questions and keep the transaction history connected to the correct account.

We may store browser type, device signals, connection details, session events and failed access attempts. This helps us identify unusual sign-ins when you move from a mobile browser to desktop. Device data supports the security process, but phone verification and account checks remain important.

Contact us through the account support path and describe the detail that needs correction. Include the relevant account identifier, not unnecessary wallet credentials. We may ask you to complete phone verification or another account step before changing data linked to access or transaction matching.

We keep each record while it supports account security, payment reconciliation, an unresolved support request or a legal obligation. After that purpose ends, we remove, anonymise or reduce the record where appropriate. A support request can ask us to explain why a particular record remains.

You can request removal through account support, and we will assess the request against security, payment and legal requirements. Some transaction or verification records may need to remain for a stated purpose. We will explain the result and identify any data that can be removed or reduced.

Related Pages

racik98 Indonesia Account information Esports PUBG Mobile Access guide Live Roulette Turbo