Reference

Privacy Policy for koi55 Account Data

koi55 Privacy Policy explains how we handle the details linked to your account, wallet activity and device access before you open the lobby.

Account recordsCookie choicesWallet referencesAccess requests
koi55 Privacy Policy for koi55 Account Data
CONTACT ROUTES

Privacy Help Beside Your Account

A privacy question should not leave you searching through unrelated pages.

Account help Use the account help route for questions about the Privacy Policy, phone verification, stored…
Wallet status For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, send the receipt…
Access trouble When login or phone verification stalls, tell us whether you are using a mobile…
DATA PRACTICE

How koi55 Handles Privacy Requests

Our handling process follows the purpose behind each data field rather than collecting details without a reason.

Account data

We use your registered contact details and phone-verification status to connect sign-in activity with the correct account.

Cookies and sessions

Cookies can keep your signed-in session, language choice and security state working between pages.

Payment references

DANA, OVO, GoPay and QRIS references, along with bank transfer or virtual account records, help us match a cashier event.

Account security

We record selected sign-in, verification and device events to identify unusual access.

Data retention

We keep account, payment and security records only for the period needed for the stated purpose, account administration and applicable…

Changes and contact

To request a copy, correction or permitted deletion of personal data, contact us from the signed-in account route or the…

Privacy Policy Questions for Indonesia

These Privacy Policy answers focus on the account and payment questions you are most likely to have before opening koi55 access. We explain what happens during phone verification, how device cookies work, which wallet records we can see and where to send a privacy request. If your situation depends on a local rule, access depends on local law and we will handle the request within the applicable process.

It covers account details, phone verification, sign-in and device events, cookies, support messages, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains request routes, retention purposes and the checks we use before changing private records.

Phone verification helps us connect an account request to the person controlling the registered contact detail. It can also reduce mistaken access when a new device signs in. If a verification step fails, contact support through the access route and do not send your wallet PIN.

Yes. Send a correction request through the signed-in account help route, identify the field that is wrong and include your registered phone number. We may verify account ownership before changing it. Whether a request can be completed depends on local law and the record involved.

Yes. The Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use those references to match receipts and account events. They do not give us your wallet password or PIN.

Our mobile browser session may use cookies for sign-in continuity, language preferences and security checks. Clearing cookies can sign you out and remove saved preferences. After clearing them, sign in again, complete phone verification if requested and check that your account details are correct.

We keep each record for the time needed for its stated purpose, account administration, security checks and applicable legal duties. Account, payment and security records can have different periods. Contact the account help route if you want the retention category for a specific record.

Use the privacy or account help path available from your signed-in account. If login is unavailable, use the contact route on the koi55 access page and describe the request without sharing a wallet PIN. We may ask for ownership details before releasing or changing data.