Reference

Privacy Policy for Your Account

Our Privacy Policy tells you exactly what data we collect when you open an account, enter the lobby, check Baccarat or Wild Bandito, and use DANA, OVO, GoPay…

Account data explainedDANA privacy contextOVO wallet recordsGoPay and QRIS logs
permenslot Privacy Policy for Your Account
PRIVACY HELP

Three Ways to Reach Privacy Support

Privacy questions should not sit in a queue built for general lobby chat. We route account-data requests through channels that let you identify your account, describe…

Live chat privacy queue Use live chat from 09:00 to 23:00 WIB for quick privacy questions about login…
Email request trail Email support when you need a written privacy request, such as correcting your name…
Account message centre Open the message centre after login if you want privacy replies kept inside your…
DATA HANDLING

Six Privacy Controls We Use

Your privacy controls are tied to real account actions, not vague promises. We separate wallet references from game activity where practical, limit staff access by role, and log changes that affect your…

Account data collection

When you join, we ask for details needed to create and protect your account, such as contact data, login credentials, and verification signals. We use that data to run access checks and support account recovery.

Payment privacy records

DANA, OVO, GoPay and QRIS activity creates wallet references, timestamps and status records. We use those records to match deposits, check withdrawals, investigate failed payments, and answer your privacy request accurately.

Cookie and device signals

Cookies help remember session state, language choice and security checks on your phone browser. Device signals may include browser type, IP region and login time so we can spot unusual access patterns.

Game activity separation

When you open Baccarat, Aviator, Super Bingo or Royal Fishing, we store session records needed for account history and dispute checks. Payment data is handled separately from game-round details where our systems allow it.

Retention and deletion requests

We keep records only as long as needed for account service, payment checks, security, and legal duties that apply where access is permitted. You can ask us to review, correct or remove eligible records.

Staff access control

Support staff see only the privacy details needed for your request, and payment checks require account verification before any wallet discussion. We log internal actions so privacy handling can be traced.

Privacy Questions Before You Join

These answers cover the privacy questions we hear before you open an account or send a wallet request. They focus on account data, device behaviour, cookies, payment records and how to contact us. If your request involves eligibility or access, we apply local law checks and handle access only where local law permits.

We collect the details needed to create, secure and service your account, including contact data, login credentials, device signals and verification records. We do not ask for private data that is unrelated to account access.

We store payment references, timestamps, wallet labels and transaction status so deposits and withdrawals can be matched to your account. Support may use those records after verification when you ask about a privacy or payment record.

Yes. Send the correction request through live chat, email or the account message centre with your account ID and the field that needs correction. We may verify your phone number before changing sensitive details.

Cookies help keep your session active, remember basic settings and support security checks. Game activity records, such as opening Aviator or Baccarat, are stored separately from wallet records where our systems allow that separation.

We keep account, payment, support and security records only for service, dispute checks, fraud prevention and legal duties that apply in permitted locations. When a record is no longer needed, we remove or restrict it.

Contact support from your registered account and state that you want a data copy. We verify identity first, then explain what records are available, expected timing, and any legal limits that apply.

We may record the device type, IP region and login time to protect your account. If the access looks unusual, support can use those signals to check the event after you verify ownership.