Reference

Privacy Policy for Your empire29 Account

empire29 Privacy Policy gives you a clear account of what we collect, why we use it, and how you can ask for a change before opening an account.

Clear data purposesPhone verification recordsWallet activity controlsIndonesia access rules
empire29 Privacy Policy for Your empire29 Account
HELP WITH REQUESTS

Request Help With Privacy Choices

A privacy request should be easy to connect to the right account, so we ask you to use the contact path shown in your signed-in account area whenever possible. Include the phone number or account identifier linked to your request, but never send a wallet PIN or password. We may ask for a verification step before releasing account data or changing details, protecting your request from an unauthorised person.

Team online

Access request

Ask for the personal data linked to your account through the account support path. We may confirm your phone verification first, then explain the available records and any lawful reason a particular field cannot be shared.

Wallet question

If a DANA, OVO, GoPay, or QRIS reference looks unfamiliar, send the payment date and visible reference through support. We use those details to locate the matching account event without asking you to reveal a wallet PIN.

Change request

For a correction or deletion request, tell us which account detail needs attention and why. We may retain a transaction or verification record when it is needed for reconciliation, dispute handling, or a legal obligation.

DATA PRACTICE

How empire29 Handles Account Data

We keep this Privacy Policy tied to the actions you take: creating an account, confirming a phone number, signing in from a device, and checking a wallet or bank reference.

Collection

We may receive your phone number, account details, device and browser signals, sign-in time, support messages, and payment references. These records help connect a verified account with the correct session and transaction status.

Cookies

Cookies can keep a signed-in session working, remember selected settings, and help us understand basic page errors. You can manage cookie controls in your browser, although limiting essential cookies may interrupt account access.

Account security

Phone verification and sign-in checks help us distinguish your account from an unfamiliar device. Never share your password, wallet PIN, or one-time code; our privacy process will not require those secret credentials.

Retention

We retain records for the time needed to operate the account, reconcile DANA or bank activity, handle disputes, and meet applicable obligations. When a record is no longer needed, we delete or anonymise it where feasible.

Your requests

You can ask what personal data we hold, request a correction, or ask about deletion through the contact path in your account area. We may verify your identity and explain limits that depend on local law.

Policy contact

For a privacy concern, include your account identifier, the affected date, and a short description of the issue. We use this context to trace the relevant record while avoiding unnecessary collection of extra personal details.

Privacy Policy Questions for Indonesia

These answers address the privacy searches we hear most often before account creation and during wallet activity. They explain the practical path for checking records, protecting a sign-in, and asking us to change personal data. If your situation is not covered, use the account contact route and include only the details needed to locate your request.

It covers account details, phone verification, device and browser signals, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity. It also explains purposes, retention, security steps, and your available requests.

We use your phone number to create and verify the account, help prevent mistaken access, and connect a privacy request to the correct record. We may ask for another verification step before sharing or changing account data.

Yes. A wallet or bank reference can show that an account action reached DANA, OVO, GoPay, QRIS, a virtual account, or bank transfer reconciliation. We use the reference to check status and disputes, not to request your wallet PIN.

Use the privacy or support contact path shown after you sign in, and include your account identifier plus the records you want to see. We verify the request before responding, and the available scope depends on local law.

You can ask us to correct inaccurate account details or delete eligible records through the account contact path. Some transaction, verification, or dispute records may need to remain for reconciliation or a legal obligation.

We may record device type, browser signals, session timing, and related security indicators. These details help identify unusual sign-ins and keep the verified account connected to the right session without needing access to your private device files.

Account access depends on local law. Where local law permits, you can create and use an account after the required phone verification and account checks. This Privacy Policy explains the data connected with those steps, not a promise of eligibility.