Reference

Open Your Privacy Policy Path at home189

home189 Privacy Policy explains what we collect when you create an account, sign in from a phone, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet activity explainedAccount request pathIndonesia account context
home189 Open Your Privacy Policy Path at home189
REQUEST SUPPORT

Ask home189 About Your Privacy Choices

A clear support route helps you act on the Privacy Policy without guessing which account detail to send. Use the signed-in account support path for requests about your records, phone verification or wallet references; we ask for enough detail to identify you, not for an unnecessary password. If you are in Jakarta or elsewhere in Indonesia, the same account path keeps the request attached to your account history.

Team online

Account data request

Send an access, correction or deletion request through the support path inside your signed-in account. We compare the request with your phone verification details before discussing account data, which helps prevent another person from receiving your records.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, include the date, amount reference and wallet name shown in your account. We use that limited context to trace the record without asking you to share a wallet PIN.

Status and security help

For a stalled login, unexpected device alert or unclear data response, open the account support path and describe the screen you saw. We can check security events and payment receipt status while keeping your password and verification code private.

DATA HANDLING

Protect Your Data Around Live Roulette

Privacy work follows the same account path whether you browse Live Roulette, we77slot or another lobby area.

Account details

We use your account name, phone verification result and selected contact details to open the correct account, respond to requests and protect access. We do not ask for a password in a Privacy Policy request, and you should never include a verification code in support messages.

Device signals

When you move from a mobile browser to desktop, we may note device type, browser details, session time and security events. These signals help us recognise unusual access and keep a request linked to the right session without requiring a separate application.

Cookies and sessions

Cookies can keep your signed-in path available, remember security preferences and help us identify a broken session. Clearing them may sign you out or require phone verification again. The Privacy Policy explains this device behaviour so you can choose how to continue.

Wallet references

Payment records may include a DANA, OVO, GoPay, QRIS, virtual account or bank transfer reference. We use those references to match receipts, investigate status questions and maintain account records; we do not request your wallet PIN or full banking password.

Retention choices

We keep account and transaction records for the period needed for security checks, disputes, service administration and legal duties. When a record no longer serves those purposes, our retention process removes or separates it according to the applicable requirement.

Change request

You can ask us to correct inaccurate account details, explain a data use, provide eligible records or remove information that no longer needs to remain. We may verify ownership first, then reply through the account support path with the result or reason for any limit.

Browse Privacy Policy Answers for Your Account

These Privacy Policy answers focus on the questions you may have before opening or using a home189 account from Indonesia. We explain the account step, wallet reference, device signal and request path in direct terms, while any eligibility decision depends on local law and applies where local law permits.

The home189 Privacy Policy covers account details, phone verification, device and session signals, cookies, support messages and payment references. It also explains why we use each category, how long records may remain, and how you can request access, correction or deletion through support.

We use phone verification to connect a person to the correct account, reduce unauthorised access and confirm ownership before sharing account records. If you ask about Privacy Policy data, we may repeat an ownership check, but we will not ask you to reveal your verification code.

Yes. The Privacy Policy includes references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use a reference, date and status to reconcile a receipt or investigate a question; we do not need your wallet PIN or full banking password.

Sign in, open the account support path and ask for an eligible copy of your records. State which category you need, such as device signals, wallet references or support history. We verify account ownership first and respond through the same protected path.

You can request correction of inaccurate account details and removal of eligible data through support. Some account, security or transaction records may need to remain for disputes, service administration or legal duties. We explain the reason if a requested removal cannot be completed.

Cookies and related session signals help keep sign-in working, remember security choices and identify unusual access. Clearing them can sign you out or trigger phone verification again. The Privacy Policy describes this use so you can manage your browser without losing account context.

Use the support path inside your signed-in account for a Privacy Policy request, wallet record question or security concern. Include only the details needed to identify the issue. Eligibility for a particular data action depends on local law and is handled where local law permits.