Reference

Open With Clear Privacy Terms

One account connects Live Baccarat, Fortune Dragon, Aviator and your wallet history, so our Privacy Policy explains exactly which account details we collect and why.

Account data scopeDANA privacy checksCookie choicesProfile request path
pompa88 Open With Clear Privacy Terms
CONTACT PATHS

Switch To Privacy Contact Paths

Privacy requests work faster when you contact us from the account you want us to check. Use live chat for urgent access issues, the account form for correction or deletion requests, and the privacy ticket path when you need a written answer. We may ask you to confirm your registered phone, last wallet rail used or recent login device before we act.

Team online

Live chat 09:00-01:00 WIB

Use live chat when you cannot access your account, see a login you do not recognise or need help finding privacy controls. We confirm account ownership before discussing wallet records or device history.

Privacy ticket form

Open the account menu, choose Help, then Privacy Request to send correction, access or deletion questions. Add the DANA, OVO, GoPay or QRIS reference only when it relates to your request.

Profile security path

Go to Profile > Security > Privacy to check saved contact details, active sessions and cookie choices. If anything looks wrong, send a ticket before changing payment details or opening another account.

ACCOUNT CARE

Browse Our Data Handling Controls

We handle privacy as an account operation, not as a hidden clause. Payment records are separated from chat messages, session logs are checked for unusual access, and account-change requests are handled by…

Account data collection

We ask for details needed to create and protect your account, such as name, contact number, login credentials and verification records. Extra details are requested only when a wallet or security case needs checking.

Wallet record handling

DANA, OVO, GoPay and QRIS records are used to match payment status with your account balance. We do not place full wallet credentials in chat replies or public account screens.

Cookie and device signals

Cookies help remember language, session status and lobby layout on your phone browser. Device signals also help us notice unusual logins, especially when an account suddenly changes location or browser pattern.

Security verification

Before changing phone numbers, email addresses or payout details, we may ask for recent login checks or a payment reference. This reduces the risk of account takeover after a lost device.

Retention approach

We keep account and wallet records while they are needed for service, dispute handling, security checks or legal duties. When a record is no longer needed, we restrict access or remove it from active tools.

Request handling

You can ask to access, correct or remove eligible personal data through the privacy ticket path. We answer with the next account step, any verification needed and the expected handling window.

Check Your Privacy Questions

These answers focus on the Privacy Policy and the choices you can make inside your account. Use them before sending a ticket, especially if your question concerns payment references, cookie settings, account deletion, data correction or login records. For account-specific matters, we will still verify ownership before sharing any record.

We collect the details needed to create, secure and service your account, including contact data, login records, device signals, wallet references and messages you send. We avoid asking for data that is not linked to account operation.

Those rails create transaction references that help us match wallet activity to your account. We use the reference, amount status and time stamp for reconciliation, dispute checks and security checks, not for public display.

Yes. Use Profile > Security > Privacy or the privacy ticket form to request correction. We may ask you to confirm your registered phone, recent login device or a wallet reference before changing sensitive details.

Send a privacy ticket from the account menu and state which data you want removed. Some records may stay restricted for security, dispute handling or legal duties, especially wallet logs tied to DANA, OVO, GoPay or QRIS.

No. Clearing cookies only removes browser storage such as session memory and layout choices on that device. Your account records, wallet references and support messages stay in our systems until handled under the Privacy Policy.

Only staff assigned to account security, payment reconciliation or privacy handling can access the request details. We limit internal access by task, and we do not discuss your wallet records without ownership checks.

Some changes do. Updating contact details, recovering access or changing payout details can require extra verification, and access to certain functions depends on local law. We explain the next step inside your ticket reply.