Reference

unit288 Privacy Policy For Your Account

unit288 Privacy Policy explains what we collect when you create an account, verify your phone, open Live Roulette Gold or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet record detailsPhone verification contextMobile cookie choices
unit288 unit288 Privacy Policy For Your Account
CONTACT PATHS

Privacy Questions Near Your Cashier

A clear contact route helps when a privacy request and an account issue arrive together. Start from the on-site support path while signed in, or use the contact route shown on the unit288 support page if you cannot enter your account. Include the email or phone linked to your account, the request you want handled and any relevant payment reference, while leaving out wallet passwords or full banking credentials. We use those details to locate the right record without asking you to send unnecessary data.

Team online

Account support

Use the signed-in support path for a Privacy Policy request tied to phone verification, a login event or your account profile. We can compare the request with the account step already recorded and ask for a suitable identity check before changing personal details.

Wallet records

For DANA, OVO, GoPay or QRIS questions, send the transaction reference and date shown in your receipt. We use the reference to trace status without requesting your wallet PIN, password or complete bank credentials.

Access help

If the mobile browser will not load the contact route, switch to the account support page on desktop and state that the request concerns Privacy Policy. We will keep the support message with the case record used to respond.

DATA PRACTICES

How We Handle Privacy At unit288

We keep this policy practical by linking each data use to an account, payment or security task.

Account details

We collect details such as your chosen account identifiers and contact information to create the account, send account messages and locate your records when you contact us. Phone verification is recorded as a result and account-security event, not as permission to read private phone content.

Payment records

A DANA, OVO, GoPay or QRIS action can create a reference, amount, currency, timestamp and status in our records. Bank transfer and virtual account activity may include the matching bank reference, while wallet passwords and PINs remain outside our requested data.

Cookies

Necessary cookies keep a signed-in session, preserve security checks and return you to the correct page after a cashier step. Optional measurement cookies may record page activity in a grouped form. Your browser settings can remove or block cookies, although some account steps may then need repeating.

Account security

We use phone-verification results, sign-in history, device signals and unusual payment patterns to protect account access. If a request changes contact details or wallet status, we may pause the change until the account-control check is complete and may ask you to confirm a recent account step.

Retention periods

We keep personal data only for the period needed for the stated account, security, payment reconciliation or legal purpose. A deleted profile may still leave a transaction reference or support case where retention is required. When the period ends, we remove, aggregate or securely restrict the record.

Request changes

You can ask us to access, correct, restrict or delete eligible personal data through support. Tell us which record is wrong and include the linked email or phone. We may request a verification step, answer within the period required by applicable law and explain any record we cannot remove.

Privacy Policy Questions For unit288

These answers address the searches we hear most often about account data, payment references and policy requests. They are written for the unit288 account flow, including phone verification, mobile access and Indonesian wallet records. If your situation is not covered, use the support route and describe the exact record or account step involved.

The unit288 Privacy Policy explains our use of account identifiers, contact details, phone-verification results, sign-in events, device signals, cookies and payment references. We use them for account access, security, reconciliation, support and legal duties, not to request your DANA, OVO or GoPay password.

Yes. The Privacy Policy covers QRIS receipts, bank transfer references and virtual account status when they are connected to your account. These records help us match a cashier action, investigate a missing status and answer a support request. We do not need your banking password or wallet PIN.

Use the signed-in support path, or the contact route on the support page if you cannot enter your account. State whether you want access or correction, identify the relevant account detail and include your linked email or phone. We may complete a phone-verification check before releasing or changing records.

We collect limited device and browser signals to keep sessions working, detect unusual sign-ins, diagnose a page error and protect payment status. For example, a mobile browser opening Aviator Fast Round may create technical session data. These signals do not give us access to files, contacts or wallet passwords.

The Privacy Policy separates necessary cookies from optional measurement cookies. Necessary cookies support sign-in, security checks and a return from QRIS or wallet steps. You can block optional cookies through browser settings; blocking necessary cookies may sign you out or require you to repeat a phone-verification step.

You can request deletion of eligible personal data through support. We first check account control and identify records covered by the request. Some payment references, security events or support cases may need to remain for a legally required period; we will explain that limitation rather than silently removing the record.

The policy is available for you to read, but account access and any data request depend on local law. Where local law permits, we handle access, correction, restriction or deletion requests through support. If a legal exception applies, we will identify the affected request and explain the next available path.