Reference

Privacy Policy for Your Indonesia Account

Baccarat, Lucky Neko and MotoGP Betting sit behind one account, and our Privacy Policy explains what data we collect when you open it, verify it and fund it…

Account data explainedDANA and QRIS contextDevice checks coveredSupport contact paths
pedro188 Privacy Policy for Your Indonesia Account
CONTACT ROUTES

Privacy Help Through Account Channels

Privacy questions move faster when they start from the same account details you use in the lobby.

Live Chat Open chat from your account menu between 09:00 and 23:00 WIB.
Email Desk Send privacy requests to [email protected] with your registered mobile number and the issue date.
Account Menu Use Profile > Security on mobile or desktop to update contact details, review login…
POLICY CONTROLS

What We Keep Behind Your Login

We handle privacy as an operating task, not a one-time notice. Each account action creates a small record: login time, device type, payment route, wallet reference or service conversation.

Account Data

We collect the details needed to open and maintain your account, including username, mobile number, password status and service history. We use them for login, account recovery and privacy request handling.

Payment Records

DANA, OVO, GoPay, QRIS and bank transfer references are stored with timestamps so wallet entries can be matched. We keep payment context separate from game preference notes where our systems allow it.

Device Signals

When you move between Android browser, iPhone browser and desktop, we record basic device and session signals. These checks help us spot unusual access before account details or wallet actions are changed.

Cookie Choices

Cookies keep your session active, remember language display and support fraud checks. You can clear them in your browser, though doing so may ask you to log in again before seeing the lobby.

Retention Periods

We keep account and transaction records for as long as operational, security or legal needs require. When data is no longer needed, we remove it or separate it from direct account identifiers.

Request Handling

You can ask us to correct contact details, check stored account data or close a privacy query through chat or email. We verify identity first, then route the request to the team that owns the record.

Answers About Your Data Rights

These questions focus on what you can ask us, what we check and how privacy choices affect your account. Keep your registered mobile number ready when you contact us, especially if the question involves DANA, OVO, GoPay, QRIS or a bank transfer reference.

We collect the details needed to create and protect your account, such as username, mobile number, password status, device signals and service history. Payment references are added when you use DANA, OVO, GoPay, QRIS or bank transfer.

Device and login records help us confirm that the same person is using the account across mobile and desktop. If a new browser appears, we may add checks before allowing wallet changes or privacy updates.

Yes. Contact chat or email with your registered mobile number and the detail that needs correction. We verify the request first, then update the account record or explain why a payment-linked record must stay unchanged.

We use payment references to match deposits and withdrawals to the right wallet record. The privacy file may include timestamps, route names and transaction IDs, but we do not need your full external wallet login.

We share limited data only when needed for payment processing, account security, service replies or legal obligations. Each partner receives the data needed for that task, not a full copy of your account profile.

Email [email protected] from your registered contact and describe the data you want to see. We may ask for recent account or payment details before releasing any file, because privacy access must be verified.

Closure stops normal account access, but some records may remain for payment matching, dispute handling, security checks or legal needs. When those reasons end, we remove the record or separate it from direct identifiers.