Terms alignment
Our account terms describe your relationship with 3d bet, while this Privacy Policy explains data handling. We keep the wording aligned so account rules do not hide separate privacy permissions.
LEGAL REFERENCE
Privacy Policy for Indonesia accounts
3d bet puts casino, slots and sportsbook privacy controls in plain English before you open your account. See how your data, login records and DANA, OVO, GoPay or...
Indonesia privacyAccount dataLogin recordsQRIS context
How our privacy posture works
This Privacy Policy explains how we collect, use, store and protect data connected with your 3d bet account in supported regions of Indonesia. We collect data you give us during account creation, contact forms, login checks and account safety steps. We also keep technical records such as device signals, session activity, approximate location and fraud-prevention markers so we can protect your account
flow. Payment references connected with DANA, OVO, GoPay and QRIS may appear in our records when they are needed to confirm account activity, resolve privacy requests or meet legal duties. We do not write this policy as a licence to share everything. We share limited data with service providers, compliance partners and security tools when needed, and we expect them to handle
it under confidentiality, retention and access controls.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
PLAYER SUPPORT
Contact us about privacy
Your privacy request should reach the right desk without a long search. Use the contact path that matches your concern, include your account email or phone number, and we will check the request against our records before replying.
Team online
Privacy inbox
Send data access, correction or deletion questions to our privacy inbox. Include the contact detail linked to your account so we can match your request without asking for extra documents too early.
Account safety desk
If you think your login data, device record or account contact has changed without your action, reach our safety desk. We will lock sensitive changes while the privacy check is active.
Transaction reference help
For privacy questions involving DANA, OVO, GoPay or QRIS references, send the time, amount and account contact. We use those details only to locate the record and answer your request.
PLATFORM TRUST SIGNALS
How we keep policy clarity
We want this Privacy Policy to read like a clear promise, not a legal wall. Our checks focus on accuracy, plain wording, current contact paths and the privacy...
Named policy owner
A privacy owner inside 3d bet keeps this page aligned with account forms, login screens and contact flows, so the...
Change log control
When wording changes, we keep an internal change log covering the reason, date and affected privacy topic. That helps us...
Plain-language pass
Before publication, policy text is checked for direct wording and practical examples. We avoid vague promises, overlong clauses and terms...
Data minimisation check
New account fields and verification steps are tested against the data we actually need. If a field is not needed...
Provider access mapping
We map which service providers may touch account data, technical logs or payment references. That map helps limit access, set...
Indonesia wording check
Local references are checked so the page fits supported regions in Indonesia. DANA, OVO, GoPay and QRIS are mentioned only...
PLATFORM COMPARISON
Consistency across legal pages
Your privacy rights should not change just because you move from one policy page to another. We keep connected legal pages aligned, so account data, cookies, security, promo contact and closure wording...
Cookie alignment
Cookie wording connects with this page whenever cookies affect analytics, session safety or saved choices. You should see the same privacy logic whether the topic is browser data or account data.
Security alignment
Security pages explain protection measures, while this page explains data use behind those measures. We keep both sides consistent so login checks, device signals and alerts are not described differently.
Promo contact alignment
If you contact us about a promo board, privacy rules still apply. We keep contact wording consistent so your account, message history and preference data are handled under the same policy.
Account closure alignment
Closure requests can affect storage, access and deletion timing. We align closure wording with this Privacy Policy so you know which records may be removed, kept or restricted after closure.
Local access alignment
Where local law permits access in supported Indonesia regions, the same privacy standards apply across our pages. We avoid separate wording that would weaken your data request path.
Contact alignment
Every legal page points privacy requests back to clear contact paths. That keeps your access, correction, deletion or concern request from being split across different desks with different wording.
AT A GLANCE
Visible privacy layout cues
We designed this policy page so privacy choices are easier to scan before you open your account. The visible layout highlights where data is collected, why it is used, how to contact us and...
01
Hero privacy summary
The opening block gives you the core privacy promise before any longer wording. It sets the subject immediately: account data, login records, contact details and local transaction references handled with clear limits.
02
Context chips
Short chips show the local account contexts tied to the policy. They are not sales tags; they help you notice where DANA, OVO, GoPay and QRIS references may connect with records.
03
Contact card row
Contact cards split privacy requests by purpose, so you can reach the right desk faster. Each card explains what to include and why we ask for those details.
04
Consistency block
The comparison section shows how this policy connects with related legal pages. That layout helps you spot conflicts quickly and understand which page controls each privacy topic.
05
Plain FAQ answers
FAQ answers use direct wording for common privacy concerns, from data collection to sharing and retention. Each answer stays short enough to read before you continue into account steps.
06
Action-focused wording
Buttons and prompts on this page point you toward clear privacy actions, such as contacting us, checking data, or opening your account after you understand the policy.
Privacy Policy questions answered
We collect the details you provide, such as contact data and account identifiers, plus technical records like login time, device signals and session activity. We use them for access, safety, service and legal duties.
Those names may appear in records when your account activity creates a transaction reference. This Privacy Policy explains how we handle those references, not how to choose a funding option.
We share limited data only when needed for hosting, security, analytics, compliance, customer contact or account operations. Each provider receives the minimum needed for its role and must follow handling restrictions.
We keep records for as long as needed for account access, dispute handling, security, legal duties and audit needs. When a record is no longer needed, we delete, restrict or anonymise it.
Yes. Contact us with the account email or phone number and the detail you want corrected. We may ask for verification before changing data that could affect access or account safety.
Cookies and similar tools help sessions work, remember choices, measure page performance and protect access. When those tools connect with your account, we handle the related data under this Privacy Policy.