Reference

Open help1121slot Terms & Conditions

Auto Roulette, Royal Fishing, and Ganesha Gold all sit under the same account rules, so you know how we check identity, device access, and payment entries before you…

DANAOVOGoPayQRIS
help1121slot Open help1121slot Terms & Conditions
CONTACT CHANNELS

Browse help1121slot Contact Paths

If a clause affects your account, contact us through WhatsApp or live chat and keep the same phone number on the thread. We answer in English during 08:00-22:00 WIB, and we use the case record to check name, device, and payment rail before we reply. For a formal correction, email works better because it gives us a clear trail.

Team online

WhatsApp desk

Send the clause number, your registered name, and the last action you took. We use that thread to confirm the account, cross-check the payment rail, and answer in English during our 08:00-22:00 WIB window.

Live chat

Open live chat when you need a quick read on access, device switching, or a withdrawal hold. We can pull the policy point together with your recent session data without asking you to resend the whole story.

Email request

Use email for a formal correction request, especially if you want us to update account data or close a profile. Include the matching phone number, your ID name, and one clear screenshot so we can verify faster.

DATA AND ACCESS

Switch Between Data and Access Rules

We keep policy handling tied to the account itself, not to unrelated tracking. Device logs help us spot unusual sign-ins, cookie data stays limited to session and preference…

Data handling

We store the name, phone number, payment reference, and session trail needed to verify deposits via DANA, OVO, GoPay, or…

Cookies

Cookies keep your session signed in, remember language choices, and help the page load the same way on mobile Chrome…

Account security

Use one account, one device profile, and a phone number you can access.

Retention

We keep transaction and support logs only for the period needed to handle disputes, reconcile payments, and meet local record…

Change requests

If you need to update your name, phone number, or device access, send the request from your registered contact and…

Contact route

For access questions, send the clause number and the affected date to WhatsApp or live chat.

Open Common Questions on the Terms

These questions cover access, data, and account changes, so you can check the rule before you open your account. If your case involves a device swap, a payment mismatch, or a request to amend details, the answer usually points you to the same support path and the same contact record. That keeps the check short and helps us work from the right clause the first time.

They cover account creation, access checks, payment references, device use, support requests, and closure rules. If a rule affects your region, it applies only where local law permits and only for the account you control.

Access depends on local law and is available only where local law permits. If you open from another location, we may still ask for a matching phone number, browser check, or account check before any session continues.

A matching name and phone number help us confirm that the payment rail and the account belong together. That extra step reduces mistaken changes, delayed withdrawals, and disputes over a session or balance.

We use cookies for sign-in, language memory, and session stability. We also keep a small log of device and browser data so we can trace unusual sign-ins and protect the account from misuse.

We keep support and transaction records only as long as needed for verification, dispute handling, and local record duties. After that, the data is removed or anonymised according to our retention process.

Yes. Send your request from the registered contact, explain the change, and attach a screenshot or document if support asks for it. We check the request manually before we update the record.

Use WhatsApp or live chat for a quick clause question. If you want a formal correction, email the team with the clause number, your name on file, and the date you saw the issue.