Privacy Policy
This page focuses on personal data: what we collect, why we collect it, how long we keep it and how you can contact us about access, correction or deletion requests.
LEGAL REFERENCE
Privacy For Your bumi22 link Account
bumi22 link keeps your casino, slot, live table and sportsbook account data handled with clear collection, use and sharing rules from the moment you open your account. DANA...
Account data clarityIndonesia privacy contextDANAOVOQRIS
How This Privacy Policy Applies
This Privacy Policy explains how we collect, use, store and share personal data when you create or use a bumi22 link account, explore our casino lobby, check slot rooms, open live dealer areas or access sportsbook markets where local law permits. We collect only the account, contact, device, session, security and transaction-related data needed to run your account flow, verify activity, protect
the lobby and respond to your requests. When DANA, OVO, GoPay or QRIS appears in your account journey, we may receive limited references connected to status, timing and reconciliation, not full wallet credentials. We keep records for operational, legal, risk and support reasons, then restrict or remove them when they are no longer needed under our retention rules for supported regions.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
HELP CHANNELS
Privacy Contact Paths For You
If you need help with privacy, start from the contact route that matches your request. We keep these paths focused on account data, identity checks, transaction references and consent choices.
Team online
Account Privacy Chat
Use account chat when you want quick help about stored profile data, recent sign-in records or privacy settings tied to your bumi22 link account. We may ask for verification before discussing any personal record.
Email Data Request
Send an email when your request needs a longer written trail, such as access, correction or deletion questions. Include your account name, contact email and the privacy action you want us to assess.
Transaction Privacy Check
Choose this route when your concern involves DANA, OVO, GoPay or QRIS references shown on your account. We check status records, timestamps and reconciliation details without asking for wallet passwords.
WHY THIS PLATFORM
Policy Care And Control Signals
Our privacy work is checked across product, security and support teams before updates reach you. The aim is simple: keep policy language practical, current and tied to your account experience.
Clear Data Mapping
We map the personal data used across sign-in, account security, lobby access and transaction status flows. That mapping helps us explain each privacy purpose without mixing it with general promotion.
Access Need Checks
Internal access to account records is limited by role and purpose. Support, security and operations teams see only the data they need to answer your request or maintain the account flow.
Policy Update Checks
When our account flow changes, we check whether the Privacy Policy must change too. Updates focus on collection points, sharing reasons, retention timing and your ways to contact us.
Security Review Steps
We test privacy wording against security practice, including session records, device signals and fraud-prevention checks. This keeps the policy aligned with how your account is protected during use.
Payment Reference Limits
For DANA, OVO, GoPay and QRIS, we keep privacy language limited to transaction references we may process. We do not ask you to send wallet PINs or private wallet credentials.
Support Training
Our support team is trained to handle privacy questions without exposing extra account data. Before sharing details, we confirm your identity and keep responses tied to the request you made.
SIDE BY SIDE
Consistency Across Our Policy Pages
This Privacy Policy sits beside other legal pages, but it has one role: explain personal data handling. We keep wording aligned so your rights, records and contact routes remain easy to follow.
Terms Page
Our terms explain account rules, while this Privacy Policy explains data handling behind those rules. If both pages mention verification, this page tells you what personal data may be involved.
Cookie Page
Cookie language covers browser storage and similar tools, while this page covers broader account data. Where session data overlaps, we explain the privacy purpose here in plain account terms.
Promo Rules
Promotional pages may refer to eligibility checks, but this Privacy Policy explains the data used to support those checks. We keep reward wording separate from personal data handling.
Support Page
Support channels help you reach us, while this page explains how support records are handled. We may keep chat, email and verification logs to resolve requests and protect your account.
Security Page
Security content describes protection steps, while this Privacy Policy explains the personal data behind those steps. Device signals, session timing and risk flags are treated as privacy-relevant records.
Local Access Text
Where access depends on supported regions, this page explains data processing in that context. We use jurisdiction wording carefully so privacy expectations stay clear for Indonesia account activity.
PLATFORM SNAPSHOT
Policy Layout Built Around Clarity
The visible layout is built to help you scan privacy duties quickly. Each block stays tied to collection, use, sharing, retention or contact choices linked with your bumi22...
Clear First Paragraph
The opening paragraph states that this is a privacy page...
Short Context Chips
Chips such as DANA, OVO, GoPay and QRIS show where...
Contact Cards
Support cards separate quick privacy questions from written data requests...
Rights Language
Policy text is shaped around practical actions you may request...
Retention Cues
Retention wording appears near operational reasons for keeping records, such...
Local Law Framing
Access wording uses supported regions and where local law permits...
Privacy Policy Questions We Answer
We collect account details, contact data, device signals, session records, security logs and transaction references needed to operate your account. We avoid asking for wallet passwords, wallet PINs or unrelated private documents.
We use your data to create and maintain your account, secure sign-ins, process support requests, check transaction status and meet legal or risk duties. We do not use privacy wording to hide unrelated activity.
When these options appear in your account journey, we may process reference data such as status, amount, timing and reconciliation codes. Full wallet credentials are not required for normal privacy support.
Yes. Contact us through the privacy route and explain what you want to access or correct. We may verify your identity before acting, so account records are not shared with the wrong person.
We keep records only as long as needed for account operation, security, support, legal duties and dispute handling. After that period, we restrict, anonymise or remove records based on our retention process.
We may share limited data with providers that help run account security, support, hosting, analytics or transaction status checks. Each sharing purpose must relate to operating or protecting your bumi22 link account.
Use account chat for quick privacy questions or email us for written data requests. Include your account name and the action you need, but never send wallet PINs or passwords.