Reference

inova288 Privacy Policy Explained Clearly

The inova288 Privacy Policy shows what account details we collect, why we use them and how you can ask about your records before opening an account.

Account dataCookie choicesWallet recordsSecurity requests
Explore Our Lobby Read FAQ
inova288 inova288 Privacy Policy Explained Clearly
CONTACT FOR PRIVACY

Get Help With A Privacy Request

A clear contact route matters when you want to check, correct or question personal data held with your account.

Account support path Open support from your signed-in account and choose the privacy request route. Tell us whether you want access, correction or deletion of a record, then include the phone detail used during verification so we can match the request safely.
Wallet record question For a DANA, OVO, GoPay or QRIS question, provide the transaction reference and its displayed status rather than a wallet password. We use those details to locate the relevant record while keeping your payment credentials outside our support exchange.
Login data concern If a mobile or desktop sign-in looks unfamiliar, tell us the approximate time, device type and account contact detail. We can review the security event, help protect the session and explain which account data was connected with that access.
DATA HANDLING DETAILS

What We Do With Your Privacy Choices

Privacy controls work best when each request has a clear operational route. We separate account details from wallet credentials, use device signals for security checks and keep cookies tied to stated purposes.

Account details

We use your contact details, phone verification result and account activity to provide sign-in, protect the profile and respond to requests. We do not ask you to send a DANA, OVO or GoPay password when checking an account or transaction record.

Cookies and browser use

Cookies can remember a session, support security checks and help the mobile browser return you to the correct account area. You can manage cookie settings in your browser, although switching them off may require another sign-in or limit certain privacy controls.

Payment references

A QRIS scan, bank transfer or virtual account may create a reference, amount and status record. We use that information to match a cashier event and answer a receipt question, while wallet login credentials remain with the relevant payment service.

Account security

Phone verification and device checks help us identify unusual access before account details are disclosed. If you change phone details or use a new mobile browser, we may request an additional account step so the request is linked to you.

Retention periods

We keep records only for as long as needed for the stated account, security, support or legal purpose. Transaction and security records can require longer storage than an unused preference; your privacy request can ask us to explain the reason for a particular period.

Changes and questions

Use the signed-in support path to request a copy, correction or removal of personal data. Include your account contact and a precise description, and we will verify the request before discussing protected details or confirming what action can be taken.

Answers About The inova288 Privacy Policy

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain the data connected with account access, mobile browsing, local wallet records and support requests. If your situation is different, use the account contact route and give us enough detail to identify the relevant record without sending a password.

The inova288 Privacy Policy covers account details, phone verification, device and browser signals, cookies, support exchanges and payment references. It explains why we use each category, how security checks work and how you can request access, correction or removal where local law permits.

We may collect the contact details you submit, the phone verification result, account activity and security events linked to sign-in. When you use DANA, OVO, GoPay or QRIS, we may also receive a transaction reference and status needed to match the payment.

No. Our Privacy Policy distinguishes payment references from wallet credentials. A DANA, OVO, GoPay or QRIS record may show a reference, amount or status, but you should not send a wallet password to support. We use the payment reference to investigate the related account event.

Sign in through your usual mobile or desktop browser, open the support path and select a privacy request. State that you want a copy of your account data, add the linked phone or email and complete any verification step required before protected records are shared.

Yes, you can ask us to correct an inaccurate record or remove data where the request is allowed. Send the request through account support with a precise description. Some transaction, security or legal records may need to remain, and we will explain that reason.

Cookies can keep your mobile-browser session connected, support unusual-access checks and remember selected settings. You can change them in browser controls. If cookies are disabled, the Privacy Policy still applies, but you may need to sign in again or repeat an account verification step.

Access and eligibility depends on local law. Where local law permits, this Privacy Policy explains how we handle account, device, cookie, support and payment-reference data. If a local rule affects a request, we will use the support path to explain the applicable limitation.

Related Pages

inova288 Indonesia Account information Live Blackjack Salon MMA One Championship About Us