Privacy vs Terms
Terms govern your account behaviour; this page governs your data. Where they touch — verification, for instance — both pages use identical wording so neither overrides the other.
LEGAL REFERENCE
How We Handle Your Account Data
This is the vegas bet privacy policy — a plain read of what we collect when you open an account, why we collect it, and how long it...
Data we collectHow we store itYour controlRetention windowsContact paths
Policy Posture and Jurisdiction Notes
We process your personal data where local law permits and only inside supported regions for Indonesia. The categories we handle are account identity (name, date of birth, contact), verification documents, session and device signals, and transaction references tied to your chosen e-wallet rail. We keep verification records for the period our licensing obliges, then purge. Marketing consent is separate from account consent
— you can revoke the first without closing the second. Cross-border transfers happen only to processors bound by equivalent data terms, and we never sell your record to third parties for advertising profiling.
Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.
24/7 SUPPORT
Privacy Contact Paths
Reach our privacy desk through any of the channels below when you want to access, correct, or erase data on file.
Data Requests Inbox
Email our privacy desk directly with your account reference and we'll acknowledge within two business days, then return a structured copy of your record inside the statutory window.
In-Account Controls
Sign in and head to the account privacy panel to update contact details, withdraw marketing consent, or trigger a data export without contacting an agent at all.
Live Chat Escalation
Open chat from the lobby footer and ask for the privacy queue; the agent routes your case to the data officer rather than handling it on the floor.
WHY VISITORS TRUST US
Editorial Trust Signals for Policy Review
Here's who reviews this policy, how often, and what we cross-check before publishing a new version.
Named Data Officer
A named officer signs off every policy revision and owns the response queue. You're not writing to a generic mailbox — the role is staffed and accountable to our licensing terms.
Quarterly Reviews
We revisit this text every quarter and after any meaningful change to processors, payment rails, or verification vendors so the wording matches what actually happens on the platform.
Versioned History
Each revision is timestamped and archived. If you want to see what the policy said when you opened your account, request the prior version through the privacy inbox.
Processor Register
We keep a working register of sub-processors handling your data and update it before any new vendor goes live, not after, so the document stays accurate at all times.
Encryption in Transit
Account sessions and document uploads run over current TLS profiles, and verification files sit in encrypted storage with access tied to specific compliance roles, not the broader operations team.
Independent Audit
Our data handling is reviewed by an external assessor on a fixed cycle, and the findings drive changes you eventually see reflected in this policy text.
SIDE BY SIDE
Consistency Across Our Policy Pages
This privacy notice sits alongside our other legal pages. Here's how the wording lines up so you're not reading contradictions.
Privacy vs Cookies
Cookie notice covers browser-side storage and consent toggles; this page picks up once data leaves your device and lands on our account servers.
Privacy vs KYC Notice
KYC details document categories and retention; this page explains the lawful basis and your rights over those same documents in matching language.
Privacy vs Payments
Payment terms describe rail mechanics for QRIS and e-wallet flows; we reference only the transaction metadata we retain, not the rail rules themselves.
Privacy vs Marketing
Marketing consent is logged separately and can be revoked without affecting your account; both pages state this in the same words to avoid confusion.
Privacy vs Complaints
The complaints page routes service issues; data complaints have a dedicated path through the privacy desk and bypass the general service queue.
Privacy vs Closure
Account closure triggers the retention clock described here; the closure page links back to this section rather than restating it differently.
AT A GLANCE
What Defines This Policy Page
A quick scan of the layout elements you'll find on this privacy page and what each one is for.
Plain-Language Summary
Each clause opens with a short editorial line in plain...
Anchored Sections
Every clause has a stable anchor link you can share...
Revision Date Header
The header carries the current revision date and a link...
Rights Checklist
A dedicated panel lists your access, correction, erasure, portability and...
Processor Disclosure
An inline disclosure names the categories of sub-processors involved in...
Contact Block
A fixed contact block at the foot of the page...
Privacy Policy Questions
We collect your name, date of birth, contact details, a verification document, and the device and session signals tied to your sign-in. Payment references appear once you link a QRIS, DANA, OVO or GoPay rail.
Verification records stay on file for the retention period our licensing obliges, then we purge them on a scheduled cycle. The current window is stated in the retention clause and updated whenever the obligation changes.
Yes. Marketing consent is logged as a separate flag from account consent. You can switch it off in the in-account privacy panel and your account remains fully active with the lobby unchanged.
Sign in and trigger an export from the privacy panel, or email the privacy desk with your account reference. We acknowledge within two business days and return a structured copy inside the statutory window.
No. We don't sell or share your account record with third parties for advertising profiling. Processors only receive the minimum data needed to deliver verification, payments routing or session integrity for your account.
Data sits with processors bound by terms equivalent to ours, in supported regions where local law permits. Cross-border transfers happen only under those safeguards, and the processor register on file names the categories involved.
Closure starts the retention clock described in this policy. Records we're legally obliged to keep stay for the obliged window; everything outside that obligation is removed on the next scheduled purge cycle.