Reference

Open koin 404 Privacy Policy Before Access

koin 404 Privacy Policy explains how we collect, use and protect details connected with your account, mobile browser, payment status and lobby activity, including access to rajabaccarat and…

Account dataWallet statusCookie choicesPolicy requests
koin 404 Open koin 404 Privacy Policy Before Access
ASK OUR SUPPORT

Browse Your Privacy Contact Options

A clear contact route matters when a name, phone detail, device record or payment reference needs attention.

Account access Use the support route attached to your account when you need a copy of…
Payment reference For a DANA, OVO, GoPay, QRIS, bank transfer or virtual account question, share only…
Policy request If you want to ask about access, correction, deletion or cookie choices, use the…
DATA IN PRACTICE

Switch Through koin 404 Privacy Controls

Privacy work is part of the account path, not a separate promise made after payment.

Account records

We may store the name, phone detail and account identifiers you provide during account creation or phone verification.

Payment references

A DANA, OVO, GoPay or QRIS status can create a reference in your account record, while bank transfer and virtual…

Mobile cookies

When you open the lobby on a phone browser, cookies and similar storage can remember a session, language choice or…

Security signals

We can use login time, device type, browser signals and verification events to help identify unusual account access.

Retention period

We keep account, session and payment records for as long as needed for the purpose described in this policy, account…

Your requests

You may ask what personal data we hold, request a correction, ask about deletion or question a cookie choice, subject…

Find Privacy Policy Answers Quickly

These questions cover the points Indonesian account holders commonly raise before sharing details or connecting a payment route. Each answer refers to our Privacy Policy and the account steps used to locate, protect or change personal data. If your situation is not listed, use the support route and describe the record without including a password or wallet PIN.

It covers personal details, phone verification, account identifiers, mobile browser signals, cookies, session records and payment references. It also explains why we use those details for account access, security, payment tracing, support requests and legal duties where local law permits.

No. Our Privacy Policy distinguishes a payment status or transaction reference from your wallet secret. A DANA or OVO reference may be connected with your account record, but you should never send us a wallet password, PIN or security code.

We may use the QRIS reference, amount status and related account details to match a payment step with your account and answer a support request. The Privacy Policy does not require you to provide private wallet credentials when checking a QRIS record.

Yes. Use the support route shown in your account or on the contact page and ask for access to your record or a correction. We may confirm your identity first, then address the request under the Privacy Policy and applicable local requirements.

Cookies and similar storage may keep a sign-in session, device preference or security state available while you browse on mobile. You can clear or restrict them in your browser settings. The Privacy Policy explains that doing so may end the current session.

The retention period depends on why the record exists, such as account administration, payment tracing, dispute handling or a legal requirement. The Privacy Policy supports removal or restricted storage when a record is no longer needed for its stated purpose.

The policy is available for you to read before account access, while account eligibility and related processing depend on local law. Where local law permits, you can contact us about your data, cookies, payment references or account records.