Reference

Privacy Policy for Your incesunited Account

Our Privacy Policy explains what incesunited collects when you open an account, sign in from a mobile device, browse Live Roulette Grand, or check DANA and QRIS status.

Clear collection rulesWallet data contextAccount access choices
incesunited Privacy Policy for Your incesunited Account
CONTACT PATHS

Ask About Your Privacy Policy Rights

A clear contact path helps you question a record, request a correction, or ask how your account details are used.

Account privacy request Use the account support channel to ask what personal details are connected to your profile. We will first match your request to the verified email or phone number on the account before discussing access, correction, or deletion options.
Wallet record question If a DANA, OVO, GoPay, QRIS, bank transfer, or virtual account entry looks unfamiliar, mention its date and status rather than sending secret credentials. We can review the account record and explain the privacy handling around that payment reference.
Device access concern Tell us if your mobile browser, tablet, or desktop session shows an account access you do not recognise. We may ask you to complete phone verification, then use the support path to help secure the affected sign-in.
HANDLING PRACTICES

How We Handle Personal Account Data

We keep this policy practical by linking each data use to an account task: opening access, confirming a wallet status, protecting a session, or resolving a support request.

Account records

We store details needed to create and maintain your account, including contact data and phone verification status. Activity such as opening MotoGP Grand Prix or changing a wallet setting may be connected to your profile so we can protect access and answer account questions.

Cookies and sessions

Cookies and similar browser storage help remember a signed-in session, preserve language or page choices, and detect unusual access. You can manage browser settings on your device, though blocking some cookies may require another sign-in before the Privacy Policy or account area opens.

Payment references

For DANA, OVO, GoPay, QRIS, bank transfer, and virtual account activity, we handle payment references and status data rather than asking support for wallet passwords. These records help match a transaction question to the correct account without exposing secret credentials.

Security checks

We use sign-in time, device type, browser signals, phone verification, and related account events to identify access that may not belong to you. If a session looks unusual, we may pause sensitive account changes until you complete an additional account check.

Retention periods

We retain personal records only for as long as needed for the stated account purpose, security checks, dispute handling, or a legal duty. When a retention period ends, records are deleted or separated from direct account identifiers where that is permitted.

Change requests

To request a correction, access copy, restriction, or deletion where local law permits, contact us through the signed-in support path. Include the account email or phone number, the requested action, and enough context for us to verify that the request is yours.

Privacy Policy Questions for Indonesia

These answers address the account and device questions we expect before you open an incesunited profile. They explain how the Privacy Policy relates to phone verification, local wallet references, cookies, game activity, and requests made through support. If your situation is unusual, use the account contact path and describe the specific record or sign-in event.

The incesunited Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages, and payment references. It also explains how records connected with lobby activity, such as Fishing War Arcade, may be used for access, security, service handling, and legally required retention.

Phone verification helps us confirm that the person opening or changing an account is connected to the contact detail supplied. We record the verification result and related account event, not your private wallet PIN. Access and eligibility depends on local law and applies where local law permits.

Yes. The Privacy Policy covers payment references and status details linked to DANA, QRIS, OVO, GoPay, bank transfer, or virtual account activity. We use those records to match a support question or account event, while you should never send a wallet password or full banking credential.

You can request a correction through the signed-in support path. Include the email or phone number on your account and identify the incorrect field. We may complete a phone verification step before changing it, and any request remains subject to local law and required retention.

Cookies can keep a session active, remember page choices, and help identify unusual sign-ins on a mobile browser or desktop. You can adjust cookie controls in your browser. If you block required cookies, we may ask you to sign in again before viewing account pages.

We keep each record for the period needed for its stated purpose, account security, payment questions, disputes, or a legal duty. When that need ends, we delete the record or separate it from direct account identifiers where local law permits.

Use the support contact path available after signing in and identify your account with its registered email or phone number. Ask for access, correction, restriction, or deletion where local law permits. For wallet questions, provide only the transaction date and status, never secret credentials.