Reference

Open iinetogel Privacy Policy Before Account Access

Your account details, wallet references and mobile-browser activity are covered in the iinetogel Privacy Policy before you open the lobby.

Account clarityWallet recordsCookie choicesRequest changes
iinetogel Open iinetogel Privacy Policy Before Account Access
CONTACT PATHS

Check iinetogel Privacy Policy Support Routes

A clear contact path helps when your Privacy Policy question concerns a locked sign-in, a wallet reference or a correction request.

Policy questions Send the section or data concern through the support route shown in your account…
Wallet references If your request involves DANA, OVO, GoPay or QRIS, share the transaction reference rather…
Correction requests Tell us which account detail appears wrong and what should change.
DATA PRACTICES

Explore How Our Privacy Policy Handles Data

We keep this policy practical by linking each data use to an account action you recognise. Sign-in security, payment matching, cookie controls and retention are handled as separate areas, so you can…

Account collection

We collect details needed for account creation and phone verification, then use them to connect your sign-in with the correct account record. We do not need unrelated personal details for this step.

Wallet matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references can help us match a payment status to your account. Wallet passwords and access codes should never be sent to support.

Cookie controls

Cookies can remember sign-in context and help us understand whether a page request works on your mobile browser or desktop. Your browser settings provide a way to restrict or clear them.

Sign-in security

We use account checks such as phone verification and sign-in activity checks to reduce mistaken access. If a device or login looks unusual, we may request an additional account confirmation.

Record retention

We retain account, support and payment-reference records for the period needed for account operation, security checks and policy requests. A retention question can be sent through the displayed support contact.

Change requests

You can ask us to correct account details or explain how a record is used. State the requested change clearly; we may verify your phone or account before making an update.

Browse Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the questions you may have before opening an account or checking a wallet status. Each answer points you toward the relevant account step, device setting or contact route, while access remains subject to local requirements.

It covers account creation, phone verification, sign-in records, wallet references, cookies, security checks, retention and requests to correct data. Access depends on local law and applies where local law permits.

We use your phone number for account verification and to help match sign-in activity with the correct account. If a correction is needed, that same account step can help confirm your request.

Yes. The policy explains how DANA, QRIS, OVO, GoPay, bank transfer and virtual account references may be used to match payment status. Do not send wallet passwords or access codes.

Cookies can retain sign-in context and help identify whether account pages work on your mobile browser or desktop. You can clear or restrict cookies through your browser settings before contacting support.

Yes. Contact us through the support route displayed in your account area, name the exact field to change, and provide your registered contact detail. We may complete phone verification first.

We keep account, support and payment-reference records only for the period needed for account operation, security checks and policy requests. Ask support about a specific record or retention concern.

Use the contact route shown inside your account area and describe the policy section or data record involved. Include your registered email or phone detail, but never share a password.