Reference

Open uncle empire Privacy Policy Clearly

Our Privacy Policy explains how uncle empire handles the account details you provide before you enter the lobby, including your phone verification, device signals and wallet records.

Account dataWallet recordsCookie choicesSecurity checks
uncle empire Open uncle empire Privacy Policy Clearly
PRIVACY HELP ROUTE

Check Privacy Help Through Your Account

A clear support route helps when you need to ask about the Privacy Policy rather than guess which team handles your request. Sign in, open the account help area near the cashier path and include the phone number linked to your account, the relevant date and the type of request. We use those details to find the right record without asking you to send a wallet PIN or password.

Team online

Account privacy request

Use the account help path to ask what personal data is held for your profile, why it is used or whether a correction can be made. Include your verified phone number and we will use the account record to route the request.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears unclear, send the payment date and status shown in your account. We can check the matching record while you keep your wallet password, PIN and one-time code private.

Security concern

If a sign-in alert or device session does not look familiar, contact support from the account help route and change your password before continuing. We may ask for account details to confirm ownership, never for your private wallet credentials.

DATA CONTROL BASICS

Explore Data Choices Before Account Access

The way we handle data is designed around practical account events, not broad collection for its own sake.

Account data handling

We use your phone number, verification result and account activity to create access, respond to support and protect the profile from unusual sign-ins. We do not need your DANA, OVO or GoPay password to match a payment status.

Cookies on your device

Cookies and similar browser storage can keep a session active, remember a selected setting or help us understand which policy pages are opened. You can clear them through your browser controls, though account steps may ask you to sign in again.

Phone and session security

Phone verification links an account step to the number you provide, while device and session signals help identify access that differs from your usual pattern. Never share a password, wallet PIN or one-time code with anyone contacting you.

Payment record separation

For QRIS, bank transfer and virtual account activity, we may retain a reference and status needed to reconcile an account request. The payment rail remains responsible for its own wallet or bank credentials, which we do not request.

Retention and removal

We keep personal data while it supports account operation, security checks, dispute handling or a legal requirement. When a record is no longer needed for those purposes, we remove it or reduce identifying details under our internal retention process.

Changes and data requests

To request access, correction or deletion of eligible data, use the support path beside your account and describe the change clearly. We may verify ownership through the phone linked to your profile before changing or releasing account records.

Ask About uncle empire Privacy Policy

These Privacy Policy answers focus on the account questions you are most likely to have before opening access or contacting support. They cover phone verification, local wallets, browser cookies, device signals, retention and correction requests. If your question involves eligibility or access in Indonesia, the answer depends on local law. For a record-specific request, use the support route attached to your account.

It covers the account data we receive, including phone details, verification status, device signals, session activity, support messages and payment references. It also explains cookies, security use, retention, access requests and the steps for asking us to correct eligible records.

Phone verification helps connect an account step to the number you provide and helps us protect access when a sign-in or payment question needs checking. We may use the verified number to confirm ownership, but we do not ask for your wallet PIN.

Yes. The Privacy Policy explains that we may receive payment references and status details from DANA, OVO, GoPay or QRIS to match an account request. We do not need your wallet password, PIN or one-time code to perform that check.

We may record device type, browser details, session timing and related security signals when you sign in or move through an account step. These details help identify unusual access and diagnose a page issue without requiring access to unrelated files on your device.

Open the account help route near the cashier path and describe whether you want access, correction or removal of eligible data. We may confirm ownership through your linked phone number before acting, and some records may remain where security or legal needs require retention.

We retain records while they support account operation, payment reconciliation, security checks, dispute handling or a legal need. Once those reasons end, we remove the record or reduce identifying details according to our retention process and applicable local requirements.

Use the support route inside your account and include the subject, relevant date and linked phone number. For a QRIS, bank transfer or virtual account question, add the visible reference and status. Do not send passwords, wallet PINs or one-time codes.