Reference

cewekslot88 Privacy Policy Basics

Your account data, payment references from DANA, OVO, GoPay and QRIS, and device signals are handled under this Privacy Policy before you open your account and enter the…

DANA data contextOVO wallet recordsGoPay receipt checksQRIS reference handlingCookie choices
cewekslot88 cewekslot88 Privacy Policy Basics
CONTACT PATHS

Three Contact Paths For Privacy

Privacy help is open from 09:00 to 01:00 WIB through live chat, account inbox, and [email protected].

Live chat privacy check Use live chat for a quick privacy question while you are logged in. We ask for your username, last four digits of your phone number, and the page you used so we can trace the data record.
Email request record Send detailed requests to [email protected] with your username and preferred reply address. Do not send card photos in the first email; our team will ask only for documents needed for the specific request.
Account inbox reply Use the account inbox when you want the answer tied to your login. We can reply there about cookie choices, device records, wallet references, and data changes without exposing details in open chat.
DATA CARE

Six Ways We Handle Data

Six controls shape how we handle privacy inside your account: clear collection, payment matching, device checks, limited team access, retention handling, and request tracking.

Account data collection

When you open an account, we collect your username, mobile number, password record, and login time. These details let us connect your wallet, recover access, and answer privacy requests tied to your profile.

Payment reference handling

DANA, OVO, GoPay and QRIS activity creates receipt references, time stamps, and wallet status markers. We use those records to match deposits and withdrawals to your account and to investigate mismatched payment claims.

Device and cookie use

Cookies help keep your session active and remember basic choices such as language and login state. Device signals, including browser type and IP region, help us flag unfamiliar access before account changes occur.

Game session records

When you open Lightning Roulette, Crash Games, Bingo or Royal Fishing, we store session timing, category, stake reference, and result record. These logs support wallet accuracy and account history checks.

Retention and deletion

We keep data only as long as needed for account operation, dispute checks, legal duties, and privacy requests. If deletion is possible, we remove or anonymise data after confirming the account and record purpose.

Team access rules

Support staff see only the account fields needed for the case they handle. Payment checks, password resets, and privacy requests are logged so we can trace who handled your data and when.

Clear Answers Before You Open Account

These questions cover the privacy points you are most likely to check before sharing a mobile number, using DANA, OVO, GoPay or QRIS, or saving a device. Each answer explains what we collect, why we use it, and how you can ask us to correct, access, or remove data where the request is allowed by local rules.

We collect your username, mobile number, password record, login time, and wallet setup status. If verification is needed, we may ask for extra account proof connected only to that privacy or security request.

We keep payment references so your wallet can be matched to the correct account. The record may include receipt ID, amount, time, status, and channel name, not your full wallet login details.

Yes. Contact live chat or [email protected] with your username and registered mobile number. We will confirm the account first, then prepare the data we can share under local rules.

Cookies keep you logged in, remember basic choices, and help us spot unusual access. You can clear them through your browser settings, but you may need to log in again after doing so.

Only staff assigned to your request can view the relevant account fields. We log the case, channel, time, and handling step so the request trail can be checked if you follow up.

We keep payment and chat records for account operation, dispute checks, legal duties, and privacy request history. When the purpose ends and local rules allow removal, we delete or anonymise the record.

Go to Account > Security > Active Devices to check saved sessions, then contact us for changes. We verify your username, current mobile number, and a recent wallet reference before updating sensitive fields.