Reference

Privacy Policy Built Around Your Account

Your account data, wallet checks, and session cookies are explained here before you open an account with adipatislot; we keep DANA, OVO, GoPay, and QRIS context clear so…

DANA record contextOVO wallet checksGoPay request pathQRIS scan recordsCookie controls
adipatislot Privacy Policy Built Around Your Account
REQUEST PATHS

Privacy Help When You Need Changes

Fast privacy help should not feel hidden, so we keep the contact choices visible inside your account menu and on the website footer. Start from Account > Help > Privacy Request, or message our live chat during posted hours. We may ask you to confirm email, phone, or wallet reference before we change, export, or remove account data.

Team online

Live chat

Live chat is open 09:00-23:00 WIB for privacy questions tied to login alerts, cookie consent, or wallet record checks. We confirm your account first so the chat transcript stays linked to the right request.

Email desk

Send privacy requests to [email protected] with your username, registered email, and the data action you want. We answer from the same thread so you can track dates, identity checks, and our final reply.

Account menu

Use Account > Profile to check saved contact details and Account > Security to change your password. If a field is locked, ask us through chat so we can verify ownership before editing.

ACCOUNT CONTROLS

How We Handle Your Privacy Record

Our policy is written around the data we actually touch: signup details, login history, wallet references, cookie choices, and game-session records.

Signup data

At registration, we collect the details needed to create your account and send security messages.

Payment records

DANA, OVO, GoPay, and QRIS references are used to match wallet activity with your account ledger.

Cookie choices

Cookies help remember login state, language choice, and consent settings on your device.

Security logs

When you log in, we record device type, IP range, browser version, and session time.

Retention checks

We keep active account records while you use the service and hold some wallet or dispute records longer when required…

Request handling

Privacy requests are handled by trained account staff, not open lobby teams.

Privacy Questions Before You Open Account

These are the privacy questions we hear before and after account creation. Each answer points to a practical step: what data enters the account, how wallet records are matched, how cookies behave on your device, and how to contact us when something looks wrong.

We collect the details needed to create and secure your account, such as contact data, login credentials, device data, and wallet references. If you enter Super Sic Bo or Cleocatra, we also record session activity for account history.

We store transaction references, status results, timestamps, and account matching records for DANA, OVO, GoPay, and QRIS. We use them to confirm wallet activity, answer privacy requests, and resolve account questions tied to your ledger.

Go to Account > Profile for editable contact fields, then save the corrected data. If the field is locked, contact live chat from 09:00-23:00 WIB so we can verify ownership before making the change.

Cookies keep your session active, remember consent choices, and help us check whether a login looks familiar. If you clear browser cookies, we may ask you to sign in again before showing account or wallet data.

Yes. Send the request through Account > Help > Privacy Request or email [email protected] with your username and registered email. We verify the account first, then provide the relevant record through a controlled reply.

We keep account data while your account remains active and retain some wallet or dispute records when needed for evidence. During scheduled checks, data that no longer serves a privacy or account purpose is removed or de-identified.

Only staff assigned to account and privacy handling can see the request details. Chat agents may collect the first facts, but identity checks, data changes, exports, and removal actions are handled in a restricted case flow.