Reference

Privacy Policy for Your kino388 Account

Our Privacy Policy explains what we collect when you open a kino388 account, use DANA or QRIS, and move from mobile login into the lobby.

Account data explainedWallet records clarifiedMobile privacy steps
kino388 Privacy Policy for Your kino388 Account
CONTACT ROUTES

Where To Ask About Privacy Policy

A clear contact route helps you question a record without sending sensitive details into the wrong place. Start from your signed-in account help area, describe the Privacy Policy issue, and include only the reference needed for us to locate the request. We can then direct account, wallet and data questions to the appropriate handling path.

Team online

Account Help

Use the account help path when you need to ask why phone verification, a login event or a device marker appears in your personal data. We will use the account reference you provide to locate the relevant record without asking you to post a password.

Cashier Questions

For a DANA, OVO, GoPay or QRIS record, describe the payment reference and the date shown in your account. Our support path can explain how that entry is linked to account security or receipt matching under this Privacy Policy.

Privacy Requests

If you want access, correction or removal of eligible personal data, send the request through the account support route. We may ask for an account step that confirms your identity before changing or disclosing records.

HANDLING DETAILS

What We Do With Your Personal Data

Our handling process is built around identifiable account actions rather than broad collection.

Account Creation

When you open an account, we use the details submitted in that step to create your profile and support phone…

Payment Matching

A DANA, OVO, GoPay or QRIS reference may be stored with the related account event so we can match a…

Cookie Choices

Cookies and related browser storage can keep a session active, remember a selected route and help identify repeated sign-in attempts.

Mobile Sessions

When you move from mobile login to a lobby page such as Aviator Mobile Play, device and session signals can…

Retention Checks

We keep personal records for the period needed to provide the requested account service, investigate a payment reference or maintain…

Change Requests

You may ask us to correct inaccurate account details or explain how a record was used.

Privacy Policy Questions For kino388

These answers address the questions you may search before opening an account or checking a wallet record. They focus on the Privacy Policy itself: what data we handle, how you can reach us, what happens on a mobile device and which account step may be needed before we disclose or change personal information.

The Privacy Policy covers personal details submitted during account creation, phone verification records, login and device signals, cookie activity, payment references and support requests. It explains how we use those records for account access, wallet matching, security checks and responses to your data questions.

We can store transaction references and status details connected with DANA or QRIS activity, such as a receipt match or account event. The record helps us investigate a cashier question; it does not mean we need your wallet password. Share only the reference requested through account support.

Those payment names appear because a wallet or bank record can be linked to an account action. OVO, GoPay, bank transfer and virtual account entries may help us match a receipt, check an unexpected status or answer your question about personal data connected with that payment event.

Start from the signed-in account support path and ask for access to your personal data under the Privacy Policy. Include your profile reference and a clear request. We may confirm phone verification or another account step before releasing records, so the response reaches the correct person.

Yes, you can request a correction when an account detail is inaccurate or out of date. Use account support, identify the field and explain the change. We check the request against your account before editing it, and some payment records may need a separate reference check.

Cookies and browser storage can preserve a session route and help us recognise unusual login behaviour. Clearing them from your mobile browser may sign you out or remove saved settings, so you may need to verify your account again before reaching the lobby.

Where local law permits, you can ask us to remove eligible personal data through the account support route. We first confirm your identity and check whether a record is still needed for a payment reference, security investigation or account request before deciding what can be removed.