Reference

Privacy Policy For Your setarjp Account

setarjp Privacy Policy explains what we collect when you open an account, sign in from a phone or desktop, use DANA or QRIS, and contact support about access.

Account clarityWallet contextDevice accessPolicy requests
Browse the lobby Read FAQ
setarjp Privacy Policy For Your setarjp Account
HELP WITH PRIVACY

Where To Ask About Your Data

A direct support request helps us connect your Privacy Policy question to the correct account record.

Account access If phone verification or a sign-in record looks unfamiliar, send an account access request through our support route. We compare the request with the account details we hold before discussing stored data, so your Privacy Policy question stays connected to the correct profile.
Wallet records For DANA, OVO, GoPay or QRIS questions, include the transaction reference and approximate date rather than a password or full credential. We can use that limited detail to locate payment metadata and explain how it appears under our Privacy Policy.
Data changes Ask us to correct an account detail or clarify a retention point through the same support path. Include the exact field you want checked, such as a phone number or device record, and we will assess the request under our Privacy Policy.
DATA HANDLING

What Our Privacy Controls Cover

Privacy controls matter at each account step, from phone verification to a QRIS receipt check.

Account records

We may hold your contact detail, phone verification result, account settings and access history. These records help us recognise your profile when you move from login to the lobby, and they let our team investigate an unfamiliar session without asking for your wallet password.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references, timestamps and status details in our records. We use this payment metadata to match a receipt or investigate a stalled status, not to request your private wallet credential.

Cookies and devices

Browser storage can remember a session choice, policy preference or device setting. On a shared phone, sign out and remove saved credentials after checking Batik Royale Slots or Live Blackjack Grand so the next person cannot enter your account through an open session.

Account security

Phone verification and sign-in checks help us identify the account owner before we discuss stored data. If access from a new device triggers a check, complete the account step through the displayed path and avoid sending verification codes to anyone claiming to be support.

Retention period

We retain records only while they support account security, payment reconciliation, dispute handling or a legal requirement. A request about deletion or retention must identify the account detail involved, because some records may need to remain for a defined legal or transaction purpose.

Your request

You can ask what account data we hold, request a correction, ask about processing or seek deletion where local law permits. Include a reachable account detail and a precise request; we verify ownership before sharing or changing personal records.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the account, device and wallet questions you may have before opening or using a setarjp account. We keep the wording practical: tell us what you want checked, provide only the detail needed to locate your record, and use the support path when a request requires account verification. Access remains subject to local law.

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

Yes. Our Privacy Policy includes transaction references, timestamps and status details connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account use. We use this limited payment metadata to match receipts or investigate status questions; we do not ask for your wallet password.

We use phone verification to connect an account request with the correct account holder and to protect discussions about stored data. The result can be retained with account security records. If your number changes, request a correction through support after we verify account ownership.

You can ask for access to personal records held for your account, including contact details, policy choices, device history and payment references. Send a precise request through support and include a reachable account detail. We verify ownership before disclosing records or discussing account-specific activity.

State the exact field that needs correction, such as a phone number, contact detail or account preference. We compare your request with the account record, may ask for an ownership check, and then explain the outcome under our Privacy Policy and applicable local requirements.

We retain records for the time needed to protect accounts, reconcile payments, handle disputes or meet legal duties. After that purpose ends, records may be removed or de-identified where local law permits. Ask support about a specific record rather than requesting an undefined account history.

Yes. Device and session data can still relate to your account when you use a shared phone or desktop. Sign out after checking the lobby, remove saved browser credentials, and avoid sharing verification codes. Contact support if an unfamiliar device appears in your access history.

Related Pages

setarjp Indonesia Account information Solo Live Table Access guide FAQ