LEGAL REFERENCE

How visabet Handles Your Account Data

This is our privacy policy page — the part of visabet that explains, in plain English, what we collect when you open an account, what we keep on...

Account dataDevice signalsCookie controlsWallet referencesIndonesia scope
visabet How visabet Handles Your Account Data

Our Privacy Posture, Plain and Clear

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

SUPPORT

Reaching Us About Your Data

If you want a copy of what we hold, a correction, or a full deletion request, these are the paths our privacy...

Privacy inbox Email our data desk directly from the address...
In-app chat Open the chat bubble once you're signed in...
Postal address For formal data requests you'd rather put in...
TRUST MARKERS

Why You Can Rely on This Policy

Our privacy policy isn't a one-off document — it's reviewed on a cycle and tied to the same controls our cashier and lobby teams work under. Here's how...

Quarterly review

Our policy text is re-read every quarter against the live product, so what's written here matches what the account, cashier...

Named data owner

A single team inside visabet owns this policy end to end. That means requests don't bounce between departments — one...

Encryption in transit

Every page you load on visabet, including the cashier and account screens, is served over TLS. Your wallet tokens and...

Minimal collection

We ask for what's needed to run your account and meet our regulator obligations — nothing more. Optional fields stay...

Audit logs

Every internal access to your record is logged with a timestamp and a reviewer ID, so if you ever query...

Local scope

For Indonesia accounts, your data is processed inside our supported-region stack. We don't shuffle records around the world to chase...

PLATFORM COMPARISON

Consistency Across Our Policy Pages

Our privacy text lines up with the terms, cookie and account-closure pages so you don't read one thing here and find a different rule elsewhere on visabet.

01

Privacy vs Terms

The data points named in our terms are the same ones described here — account email, device, wallet reference and session log. No hidden category sits in one document but not the other.

02

Privacy vs Cookies

Our cookie page lists the trackers; this page explains what we do with the signals they produce. The two are written to be read together, not in isolation.

03

Privacy vs KYC

Identity documents collected during verification are covered under a stricter retention window than general account data, and that distinction is spelled out the same way in both pages.

04

Privacy vs Cashier

Wallet tokens described in the cashier flow are the exact references named here. DANA, OVO, GoPay and QRIS are tokenised the same way across both documents.

05

Privacy vs Account Closure

When you close your account, the deletion timeline cited on the closure page is the one we apply here. There is no separate, longer retention hidden in this policy.

06

Privacy vs Marketing

Opt-in preferences set on the marketing page govern what we send you. This policy never overrides a choice you made there — it only describes how the choice is stored.

07

Privacy vs Complaints

If you raise a data complaint through our dispute path, the same privacy desk handles it. The complaints page points back to this document for definitions.

What This Policy Page Actually Covers

These are the building blocks of our privacy posture — the parts of visabet you'll see referenced through this document. Each one maps to a real...

Account record

Your email, phone and login history form the core record. We use it to authenticate you, recover access if you're locked out, and meet the regulator's account-trail requirements.

Device signals

Browser, operating system and rough location are logged at sign-in so we can spot a session that doesn't look like yours and pause it before it reaches the cashier.

Cookie layer

Functional cookies keep you signed in; analytics cookies tell us which lobby rooms are loading slowly. You control the analytics layer from the banner on first visit.

Wallet tokens

Your DANA, OVO, GoPay or QRIS link is stored as a token tied to your account, not as raw wallet credentials. The token is what our cashier sees, nothing more.

Session logs

Game rounds, bet stakes and lobby movements are written to a session log we retain for the period regulators require, then purged on the standard cycle.

Communication record

Emails and chat threads between you and our team are kept so the next reviewer can pick up the context. They're scoped to your account and never repurposed.

Privacy Questions We Hear Often

At sign-up we take your email, phone and date of birth, plus the device you registered from. Anything beyond that — wallet link, identity document — is collected later when the relevant flow needs it, not upfront.

We share data only with processors that run parts of our stack — payments, identity checks, hosting — and only the minimum each one needs. We do not sell your data to marketing networks under any circumstance.

Your wallet is linked through a tokenised reference. We hold the token; the wallet provider holds your actual credentials. That means a breach on our side never exposes your PIN or bank login.

Once you close your account, we retain only what regulators require us to hold — typically transaction history for the statutory window. The rest, including marketing preferences and session logs, is purged on our standard cycle.

Yes. Email the privacy desk from the address linked to your account and request an export. We'll verify it's you, compile the record and send it back through the same channel within the published window.

Our cookie layer is split into functional and analytics. We do not run third-party advertising cookies on visabet. The analytics layer can be switched off from the banner on first visit or in your account preferences.

Material changes are flagged on sign-in and emailed to the address on your account before they take effect. You'll see the change date at the top of this page so it's clear which version you're reading.