Reference

Privacy Policy For Your 29 empire Account

DANA, OVO, GoPay and QRIS details stay connected to the account steps you choose, while our Privacy Policy explains what we collect and why.

Clear data purposesWallet detail controlsAccount access requestsCookie choices
29 empire Privacy Policy For Your 29 empire Account
PRIVACY HELP PATH

Privacy Help Beside Wallet Status

A clear support route matters when you want to ask about your Privacy Policy rights, correct an account detail or understand a wallet record. Start from the support path in your signed-in account and include the contact detail used for access, the relevant request and any receipt reference. We use that context to locate the right record without asking you to send a full payment credential. Your account area remains the practical starting point for privacy questions, login concerns and DANA or QRIS status checks.

Team online

Account access

Ask us to check a Privacy Policy request through the signed-in account path. Include the contact detail linked to your account and describe whether you need access, correction or deletion. We may ask for an account step to confirm that the request comes from you.

Wallet records

For a DANA, OVO, GoPay or QRIS question, share the payment route and receipt reference rather than a password or complete wallet credential. We can use the transaction status and account match to explain which data is held and what correction route applies.

Request follow-up

If your privacy request needs more detail, our support path can ask for the missing context inside your account. Keep the request specific, such as a cookie choice, stored contact detail or device record, so we can direct it to the correct handling step.

SECURITY AND RETENTION

Account Security For Mobile Access

Privacy work is tied to the way your account is used, not just to a notice on a page. We separate account details from payment references where operationally possible, protect sign-in events…

Data handling

We use contact details, verification responses and account activity for access, support and security checks. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used to match a status, while we avoid requesting credentials that are not needed for that task.

Cookie controls

Cookies can remember a session, language choice or privacy preference on the device you use. Your browser settings can restrict or remove them, although some account steps may then require you to sign in again or repeat a preference selection.

Account protection

Clear phone verification before account access helps us distinguish your sign-in from an unrecognised attempt. Keep your contact detail current, do not share an access code and contact support through the account path if a device or login record looks unfamiliar.

Mobile signals

When you move from mobile login to the lobby, we may record browser type, operating system, session timing and security events. These signals help investigate access issues around titles such as xrslot without becoming a reason to collect unrelated device content.

Record retention

We retain account, support and payment-status records for as long as needed for the purpose described, security checks and applicable legal duties. A request to remove data may have limits where a record must remain available for a transaction or dispute.

Change requests

You can ask for a copy, correction, restriction or removal of eligible personal details through the signed-in support route. Tell us which account detail is concerned and we may verify your identity before changing records connected with your access.

Privacy Policy Questions For Your Account

These Privacy Policy answers focus on the account actions you are most likely to take before access: creating a profile, checking a wallet status, signing in on mobile and contacting support. We keep the route practical for Indonesia and explain when a request may depend on local law. If your question is not covered, use the support path shown after you sign in and include only the details needed to locate your account.

The 29 empire Privacy Policy covers account details, phone verification, payment references, device and browser signals, cookies, support records and security events. It explains the purposes for using them, how retention works and how you can request access or correction through the signed-in account path.

Phone verification helps connect an account request to the person seeking access and can help identify unusual login activity. We use the result for account security and support handling, not as permission to inspect unrelated phone content. Keep your verified contact detail current.

Yes. The Privacy Policy covers payment references used to match DANA, QRIS, OVO, GoPay, bank transfer or virtual account status with your account. We do not need your wallet password to check a receipt or explain a pending status, and provider terms may also apply.

Sign in, open the support path and ask for a copy of the personal details connected with your account. State the contact detail used for access and the scope of your request. We may verify ownership before releasing records or explaining any legal limitation.

You can request a correction through the account support path when a contact detail, verification response or account record is inaccurate. Describe the field that needs changing and provide the replacement detail. We may retain the earlier record when security, transaction or legal duties require it.

Retention depends on the reason the record was created, such as account access, a wallet status, security work, support or a legal duty. We aim to remove or anonymise records when the stated need ends, but some transaction and dispute records must remain available.

Access and eligibility depends on local law, including which services and data rights apply in your location. Where local law permits, we process eligible requests for access, correction, restriction or removal. Our support path can explain the specific reason if a request has a limit.