Reference

Open the upinslot Privacy Policy

upinslot explains how we collect, use and protect your account details when you open access to the Indonesia lobby.

Account clarityWallet recordsCookie choicesAccess requests
upinslot Open the upinslot Privacy Policy
CONTACT ROUTES

Switch to support for policy help

A clear contact path helps when you want to ask about the Privacy Policy, correct an account detail or check how a wallet record is used.

Account request Use the support route inside your signed-in account to ask what personal details are attached to your profile. We may request phone verification before discussing account-specific records, which helps prevent another person from receiving your data.
Wallet question For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the payment reference rather than your wallet password. We use that reference to locate the relevant entry and explain its handling under this Privacy Policy.
Correction request Tell us which account field appears wrong and what should replace it. We compare the request with your verified account details, then confirm whether the change can be made where local law permits.
HANDLING DETAILS

Explore how we protect policy rights

We keep the Privacy Policy practical by linking each data action to an account or service need.

Account data

We may hold your phone number, verification result, login history and account settings so we can provide access and respond to account requests. We do not need your wallet PIN for a policy enquiry, and you should never send it in chat.

Payment references

A DANA, OVO, GoPay or QRIS reference can help us match a cashier event to your account. Bank transfer and virtual account references may also be retained for reconciliation, receipt checks and payment disputes.

Cookies

Cookies can remember a session setting, help maintain sign-in security and show which page needs technical attention. You can manage browser cookie controls, although removing some cookies may require you to repeat an account step.

Device security

We may record device type, browser signals and login time to identify unusual account access. This does not give us your device contents. If a sign-in looks unusual, we may ask for phone verification before restoring access.

Retention

We keep each category only for the period connected to account operation, security, payment reconciliation or a legal requirement. When a record no longer needs retention, we remove it or separate it from direct account identifiers.

Your request

Ask us to access, correct or remove eligible personal details through the account support path. Include your registered phone number and the request type; we verify ownership before sending records or changing the profile.

Browse Privacy Policy answers

These Privacy Policy answers cover the account, device and wallet questions we expect you to ask before opening access. They explain the practical route for checking records, changing details and contacting us. If your request involves a specific account or payment reference, sign in first where possible so we can verify ownership without exposing personal details.

The upinslot Privacy Policy covers account details, phone verification, login and device signals, cookies, support messages, game-page activity and payment references. It explains why we use these records, how we protect them, how retention works and how you can request access or correction where local law permits.

We may collect your registered phone number, verification status, account settings, login events, device signals and support messages. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, we may also keep the payment reference needed to match the account event.

Sign in and use the support route shown near your account area. Ask for an account data access request and include your registered phone number. We verify that you own the account before sharing records, and the response depends on local law and applicable retention duties.

Yes, you can ask us to correct an eligible account field through signed-in support. State the field and the replacement detail, but do not include a password or wallet PIN. We compare the request with phone verification and confirm the result where local law permits.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay and QRIS, plus bank transfer and virtual account records. We use these references to reconcile account events and receipts; we do not need your wallet PIN to answer a policy request.

Cookies may keep a session active, remember a setting and help us identify technical errors on the account path. You can adjust browser controls or remove cookies, but some account steps may need repeating. Device signals are handled separately for sign-in security.

You can send a deletion request through the signed-in support route, stating which account details you want removed. We first verify ownership and check whether security, payment reconciliation or legal duties require retention. Any action remains subject to local law.