Reference

Privacy Policy for Indonesia Accounts

DANA, OVO, GoPay and QRIS account checks are covered by this Privacy Policy before you open your account, so you know which data we ask for and why.

Account data policyDANA and QRIS contextDevice session checks
kuntogelslot Privacy Policy for Indonesia Accounts
CONTACT ROUTES

Contact Us About Policy Data

Privacy requests should not wait behind game or wallet chat, so we route them by channel and verify you before we act. Live chat is staffed 09:00-23:00 WIB, while email is monitored daily for formal access, correction, and deletion requests. If you are in Semarang and need to update an OVO number, contact us before your next payment action so the account record stays aligned.

Team online

Live chat routing

Use the chat bubble for privacy questions that need fast routing, such as a phone change before a QRIS receipt check. We may ask you to confirm account email, last login date, and wallet rail.

Email requests

Send privacy requests to [email protected] with your username and the data action you want. We reply with the next step, expected time frame, and any identity check needed before release.

Account security path

Inside your account, open Profile > Security to review linked devices and sessions before contacting us. Screenshots from that page help us confirm whether a data access or correction request matches your account.

ACCOUNT CARE

Data Controls Around Your Account

We handle this policy area from the account record outward: what we collect, why it is needed, who can see it, and how long it stays with us.

Data we ask for

The account form asks for details needed to identify you, contact you, and connect wallet activity to the right profile.

Payment references

For DANA, OVO, GoPay and QRIS, we store payment rail references, amounts, time stamps, and status replies.

Cookies and devices

Cookies help keep your session active and show whether the same phone returns after login.

Game session records

Rounds in Garuda Gems, Rocket Crash, Bingo, or Sportsbook create balance records that may be kept with your account.

Retention timing

We keep account and transaction records for operational, tax, dispute, and legal needs.

Change requests

You can ask us to correct profile data, export eligible records, or erase data where rules allow.

Privacy Questions We Hear Most

Every request starts with the account you control, so keep your email and phone current before you ask for changes. We confirm identity first, then explain what can be adjusted, exported, or erased under the rules that apply to your location. Use the same device you normally use when possible; it helps us compare session data without asking for extra documents.

We collect the data needed to create your account, contact you, secure login, and connect wallet actions to your profile. That can include name, phone, email, username, device data, IP range, and payment references.

No. We store transaction references, amount, time stamp, and payment status returned by DANA, OVO, GoPay or QRIS. Your wallet PIN and private app login stay with the payment provider, not with us.

Email [email protected] from the email linked to your account and state that you want an export. We verify identity first, then prepare eligible records in a format we can safely send.

Yes, contact live chat between 09:00-23:00 WIB or email us if the change affects payments. We may ask for your last login date, current email, and recent wallet rail to confirm ownership.

Game session records connect account balance changes to specific activity, such as Super Sic Bo, Mega Fishing, or Sportsbook entries. They help us answer disputes, check account access, and support privacy requests about stored activity.

You can ask for deletion, and we will remove eligible data where rules allow. Some payment, dispute, tax, or security records may need to be kept for a period before removal or anonymisation.

Your request is handled by staff assigned to account safety, payment checks, or customer support. Access is limited to the data needed for that case, such as profile fields, device sessions, or wallet references.