Reference

Your iinetogel Privacy Policy

Your iinetogel Privacy Policy explains how we handle account records, device sessions, cookie choices, and payment privacy for DANA, OVO, GoPay, and QRIS.

DANA privacy checksOVO wallet recordsGoPay activity logsQRIS receipt handlingDevice session controls
iinetogel Your iinetogel Privacy Policy
PRIVACY HELP

Contact Paths for Privacy Requests

Privacy help is available through channels you can reach before or after opening an account.

Live Chat Use live chat when you want a quick privacy status check. We ask for your account ID and masked phone number, then keep the chat record inside your support history for audit.
WhatsApp Desk WhatsApp works well for document-free privacy requests, such as correcting a phone digit or asking which wallet label we store. We mask sensitive details before they move into the support queue.
Email Request Email privacy requests to the address shown in your account area when you need a written trail. Include your account ID, request type, and whether DANA, OVO, GoPay, or QRIS is involved.
DATA PRACTICE

Privacy Handling Behind Indonesia Payments

We handle privacy as an account process, not a slogan. When you open Secrets of Cleopatra, Live Football Odds, or QRIS payment records, we separate gameplay logs from wallet receipts so each…

Account Details

We collect the name, phone number, login email, and wallet labels you enter during account creation. That record lets us connect privacy requests to the right account before any change is made.

Payment Receipts

DANA, OVO, GoPay, and QRIS receipts are stored with time, amount, status, and masked sender details. We use them to trace payment privacy questions without exposing your full wallet credentials.

Device Sessions

Your active device list appears under Account > Security > Devices. We store browser type, login time, and session status so you can ask us to close access you no longer recognise.

Cookie Choices

Cookies remember login state, language preference, and safety checks around repeated sign-ins. You can clear them through your browser settings, but the next login may require phone verification again.

Retention Schedule

We keep account and payment records only for operational, security, and legal reasons. Some records can be removed after verification, while payment receipts may need to stay longer for dispute checks.

Change Requests

When you ask to correct or delete details, we first match your account ID, phone, and recent wallet rail. This protects you from someone else trying to alter your record.

Privacy Questions Before Account Access

Before you open an account, you should know what we collect, why we collect it, and how you can ask for changes. These answers focus on the Privacy Policy only, including account details, payment privacy, device sessions, cookies, and contact steps for Indonesian account holders.

We collect details you provide during account creation, such as name, phone number, login email, password record, wallet label, and verification status. We also keep device sessions and payment receipt data for privacy and security checks.

We store masked payment records so we can match deposits, trace disputes, and answer privacy requests. The record usually includes wallet rail, time, status, amount, and account ID, not your wallet PIN.

Yes, you can ask support to check the main records linked to your account. We verify your account ID and masked phone number first, then explain what account, payment, cookie, and device records we hold.

Contact live chat, WhatsApp, or email during 09:00-23:00 WIB with your account ID and the record that needs correction. We verify the request before changing phone or wallet details.

You can ask us to delete eligible records, and we will assess the request under local law. Some payment or security records may need to remain where local law requires or permits retention.

Cookies keep your login state, language choice, and repeated sign-in checks on mobile browsers. If you clear cookies, your account may ask for phone verification again on the next login.

Only support staff assigned to privacy handling can access your request record. We mask sensitive fields, keep request history for audit, and do not ask for wallet PINs or one-time codes.