Reference

What This Privacy Policy Covers

We use this privacy policy to explain what we collect, why we keep it, and how you can ask for a correction or export.

Account dataCookiesDevice logsRequest changes

Browse Lobby Read FAQ

How the policy works here

cincinslot Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We apply this privacy policy to data created when you browse the lobby, open a table, or send a support request. That can include your name, contact route, login time, IP address, device type, browser version, and the last digits or reference of a DANA, OVO,

1
GoPay, or QRIS transaction when you ask us to check a payment record. We keep only the details needed to run the account, verify the request, and meet record-keeping duties. We do not use that data for unrelated profiling or third-party marketing. Where access or eligibility
2
is mentioned, it depends on local law and is available only where local law permits. If you want to see, correct, or remove data, we will ask for a matching account step so we can protect the right record.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

CONTACT ROUTES

How to reach us about data

If something in this privacy policy needs a second look, send it through the account chat or the support email and attach the detail you want checked.

Live chat Use the chat box inside your account for fast privacy questions. Send your registered email, the page or payment reference involved, and we can trace the right record without asking for extra details.

Email Email works well for correction, export, or removal requests. Include the account name, the device you used, and any DANA, OVO, GoPay, or QRIS reference number so we can match the file.

Support hours We read privacy messages daily from 09.00 to 23.00 WIB. If you send one outside that window, it stays in queue and is answered in the same channel when our team comes back.

HANDLING STANDARDS

What we keep and why

Our privacy handling starts with the smallest record needed to run your account safely. We keep login history, device type, browser data, support transcripts, and payment references only for verification, dispute handling…

Data capture

When you open Aviator or Lightning Roulette, we log the time, device type, and session route so we can confirm the right account activity later. We do not use those logs to build public profiles.

Cookie use

Cookies store the page language, login state, and the last screen you opened. On mobile and desktop, that keeps the session stable without asking you to repeat the same step every time.

Account security

We compare device changes, IP shifts, and failed sign-ins before we allow sensitive actions. If a login looks unusual, the account step is sent back to your registered contact route for confirmation.

Retention

We keep support transcripts and payment references only as long as they are needed for service, accounting, or dispute handling. After that, they are removed or masked according to the applicable record period.

Request trail

For every privacy request, we track the time received, the channel used, and the name on the account. That trail helps us answer in order and prove which record was changed or left untouched.

Change checks

If you want a correction, export, or removal request, send it from the registered email or phone number and include the data point you want adjusted. We will verify the match before making a change.

Common privacy questions from you

These are the questions we answer most often when you want to check what we hold, who can see it, and how to send a change request. We keep the process tied to your registered contact route so the right file is handled. If your request comes from Jakarta or another Indonesian city, the same local-law rules still apply, and we use the same contact steps for mobile and desktop sessions.

We keep the details needed to run the account: name, contact route, login history, device type, and payment references when you send DANA, OVO, GoPay, or QRIS proof. We do not collect more than the request requires.

Cookies remember the screen language, session state, and the last page you opened so you do not need to repeat the same steps on mobile or desktop. They also help us spot repeated login failures.

Use the registered email or phone number, state the field you want changed, and attach the supporting detail. We compare it with the matching record before we update anything, then confirm the result in the same channel.

We keep records only as long as needed for account service, payment checks, support handling, or legal record duties. After that period, we remove or mask the data according to the applicable retention schedule.

Only the team members who need it for support, security, or record handling can access it. We do not share the file publicly, and any outside processing is limited to the service task in front of us.

Open the chat box in your account or send email from your registered address. Include your name, contact route, and the request type, and we will reply through the same channel during support hours.

What This Privacy Policy Covers

How to reach us about data

What we keep and why

Data capture

Cookie use

Account security

Retention

Request trail

Change checks

Common privacy questions from you

01 What data do you keep when I open an account?

02 Why do you use cookies on my device?

03 How do I ask for a data correction?

04 How long do you keep my records?

05 Who can see my personal data?

06 How do I contact you about this policy?

Related Pages