Reference

Privacy Clarity Before You Join

Blackjack, Buffalo King and Tennis Betting sit behind an account flow that asks only for data we need to run your wallet, support access and session security.

Account data explainedDANA OVO GoPay QRISCookie controlsSupport recordsLocal-law access

Explore The Lobby Read FAQ

Know What We Collect And Why

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

Your privacy starts with a clear account record: phone or email login details, wallet activity, device data and support messages are kept so we can run access, verify requests and protect your balance. We use payment references from DANA, OVO, GoPay and QRIS to match transactions

1
with your account, not to sell your personal profile. Cookie and device checks help us recognise repeated logins, spot unusual access and keep live casino, slots and sportsbook pages stable. If eligibility or access is discussed, it depends on local law and is available only where
2
local law permits. If you open your wallet from Jakarta and later switch device, we may ask for a confirmation step before showing sensitive account data.

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

CONTACT PATHS

Reach Us About Your Data

Privacy questions should reach the same team that can read your account trail. We keep contact routes clear so you can ask what we hold, correct a profile field or question a…

Live chat privacy desk Our live chat runs every day from 09:00 to 23:00 WIB and can receive privacy requests tied to login history, cookie choices or wallet records. We ask you to confirm the account before discussing private data.

Email data request Send a privacy request to the support email shown inside your account when you need a written record. Include your registered contact, DANA, OVO, GoPay or QRIS reference if relevant, and the change you want checked.

Account page checks Your profile page shows the contact details we use for login and support. If a field looks wrong, start a chat from the same device so we can compare the session with your recent access pattern.

DATA HANDLING

How We Protect Your Account Trail

We treat privacy as part of the wallet and lobby operation, not as a separate paperwork task.

Account identity

We collect login identifiers, profile fields and account status so your wallet, Blackjack tables and Bingo rooms open under the right record. We do not ask for extra personal fields when a simpler verification step is enough.

Payment records

DANA, OVO, GoPay, QRIS and bank transfer references are stored with timestamps, account ID and transaction status. That lets us match deposits and withdrawals while keeping payment data separate from game preference records.

Device signals

We read basic device and browser signals such as session token, IP range and cookie choice to spot unusual access. When the pattern changes quickly, we may ask for another account confirmation before showing wallet details.

Cookie choices

Cookies keep your session active, remember language and help us measure whether pages such as Crash Games or Mega Fishing load correctly. You can clear cookies in your browser, though you may need to log in again.

Retention checks

We keep account, payment and support records only for operational, legal and security reasons. When a record is no longer needed for those purposes, we remove it from active tools or restrict internal access.

Request handling

When you ask to correct or access data, we record the request, verify the account and answer through the channel you used. Complex wallet or security cases may need payment reference details before we respond.

Privacy Answers Before You Start

These questions cover the privacy topics we are asked about most before an account is opened or after a wallet check. The answers focus on what we collect, how payment and device records are used, and how you can reach us if something in your profile or session history looks wrong.

We collect the contact details needed for login, account verification, support replies and wallet matching. We may also store device, browser and session data so we can recognise your account when you return.

Payment references help us match your deposit or withdrawal with the correct account. We store the rail name, status, timestamp and reference, but we do not use those details to build unrelated marketing profiles.

Yes. Contact live chat or email support from your registered channel and confirm the account step we request. We may compare recent login and wallet records before changing a phone number or email.

Device memory helps us keep your session active and spot access that does not match your usual pattern. You can clear cookies in your browser, but doing so may require a fresh login confirmation.

Only staff roles that need the record for support, security or wallet handling can view your case. We keep request history so repeated issues can be solved without asking you to resend the same details.

Use live chat from 09:00 to 23:00 WIB or send email from the contact listed in your account. We verify ownership first, then explain what can be corrected, restricted or removed under applicable law.

Access and eligibility depend on local law and are available only where local law permits. Privacy requests are still handled through your verified account channel, with extra checks if wallet or security records are involved.

Privacy Clarity Before You Join

Reach Us About Your Data

How We Protect Your Account Trail

Account identity

Payment records

Device signals

Cookie choices

Retention checks

Request handling

Privacy Answers Before You Start

01 What personal data does pejuangjitu collect when I open an account?

02 How are DANA, OVO, GoPay and QRIS records used in the policy?

03 Can I ask to change the phone or email on my account?

04 Why does the site remember my device after I log in?

05 Who can see my support messages and account request history?

06 How do I ask pejuangjitu to explain or delete data?

07 Does access to my data depend on where I am located?

Related Pages