Cookie page alignment
Cookie wording should match this Privacy Policy, especially around analytics, device identifiers and preference tools. If cookies support account security, we describe that link in practical terms.
LEGAL REFERENCE
Privacy Policy for Your Account
data maco keeps your casino, slots and sportsbook account data under clear privacy rules, so you know what we collect before you open your account. We built this...
Indonesia privacy contextAccount data useCookie choicesQRIS wallet context
How This Policy Applies
This Privacy Policy explains how we collect, use, store and share data connected with your data maco account, lobby access, wallet references, device signals, support messages and preference choices. It applies when you visit datamaco.com, create an account, contact us, or use account features available in supported regions where local law permits. We process personal data only for defined purposes such as
account setup, security checks, fraud prevention, service messages, transaction reconciliation and compliance requests. We may update this policy when our account flow, legal duties or data tools change. If we make a material change, we aim to place a clear notice on the site so you can read the new wording before continuing.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
TRUST MARKERS
Policy Care Signals
We want this policy to read like a clear brand commitment, not a hidden legal wall. The signals below show how we keep privacy wording aligned with account...
Plain wording
We avoid vague privacy language where possible and explain why data is collected. That helps you connect each data point...
Purpose limits
We connect personal data to defined purposes before using it. That means account details, device signals and payment references are...
Access control
We limit internal access to teams that need data for account support, security checks, reconciliation or legal handling. This reduces...
Retention checks
We do not keep every data type for the same period. Account, support, security and transaction records may follow different...
Third-party care
When service partners help with hosting, security, analytics or payment references, we require their role to match our privacy purposes...
Update discipline
When our privacy wording changes, we check that the policy still matches real account screens and support flows. That keeps...
PLATFORM COMPARISON
Consistency Across Policy Pages
Your privacy expectations should stay consistent wherever you enter our brand pages. We align this Privacy Policy with nearby legal pages so consent, cookies, account terms and support handling do not feel...
Terms page alignment
Our terms explain account use, while this policy explains data handling behind that use. We keep both pages aligned so your rights and obligations are not split confusingly.
Promotion page alignment
If a promotion screen asks for account details or sends messages, the privacy purpose still comes back here. Marketing preferences should stay clear, changeable and tied to your choices.
Wallet context alignment
DANA, OVO, GoPay and QRIS references may appear in account flows, but privacy wording explains the data handling around those references, not a separate promise about payment availability.
Support page alignment
Support forms can include private account facts, so we keep support language aligned with this policy. You should know why we ask, how we use it and when we retain it.
Security page alignment
Security notices may describe login checks, device signals and risk flags. This policy connects those checks to privacy purposes so protection work does not become unclear tracking.
Regional access alignment
Where access is discussed, our pages should reflect supported regions and where local law permits. Privacy language should not imply wider access than our account flow can lawfully support.
AT A GLANCE
Visible Policy Layout Elements
This policy page is designed for quick reading on your phone and careful reading when you need detail. The layout highlights the privacy points most likely to matter...
Short purpose blocks
We group privacy purposes into readable blocks, so you can...
Context chips
Chips such as DANA, OVO, GoPay and QRIS appear only...
Action language
We write privacy actions in direct terms, such as access...
Mobile spacing
The page uses short cards and clear spacing because privacy...
Contact routing
Contact options sit near the policy details so you do...
Change visibility
When policy wording changes, the page is structured so update...
Privacy Policy Questions
We may collect account details, contact data, login records, device signals, support messages, preference choices and transaction references. We collect what is needed to create, protect and support your account.
We use your data to open and maintain your account, secure access, answer support requests, reconcile wallet references, send service messages and meet legal duties in supported regions where local law permits.
We do not sell your personal data. When partners help with hosting, analytics, security or payment references, their access must support our stated privacy purposes and remain limited to that role.
These names may appear in account and transaction references. This policy explains how related records are handled for verification, reconciliation, support and compliance, not as a promise that every option is always available.
Yes, you can ask us to correct account data that is inaccurate or incomplete. We may need to confirm your identity first so private account details are not changed by the wrong person.
Retention depends on the data type and purpose. Support messages, security logs, account records and transaction references may be kept for different periods based on legal, fraud prevention and service needs.
If we make a material change, we aim to place clear notice on the site. You should read the updated wording before continuing, especially when account, security or data rights sections change.