Reference

Open velbett Privacy Policy

Our Privacy Policy sets out what account data, wallet logs, device records, and browser cookies we keep, why we keep them, and how you can ask for changes…

Account dataCookie handlingChange requests

Browse Our Lobby Read FAQ

Explore data use and retention

velbett Service availability depends on jurisdiction. Users are responsible for checking local law before access.

We keep only the records needed to run your account, secure the login flow, and answer a request about your data. That can include your name, contact details, device type, browser signals, session cookies, and payment references from DANA, OVO, GoPay, or QRIS when you use

1
them. If you open slots, live tables, or crash games, we may also store session logs so we can match activity to your account and handle a dispute cleanly. We hold these records for as long as they are needed for service, legal, tax, or fraud
2
checks, then remove or anonymise them where our process allows. If access or eligibility is discussed, it depends on local law and is available only where local law permits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

HELP CHANNELS

Browse privacy support channels

If you want a copy of your data, a correction, or a deletion request where the law allows it, start with live chat or email and use the same account email you registered with. Our team answers from 09:00-21:00 WIB every day, and a short follow-up on WhatsApp is used only after we confirm ownership. From Yogyakarta or anywhere else in Indonesia, the verification path stays the same.

Team online

Live chat

Use live chat for the fastest privacy request. We ask for your registered email, the request type, and a short ownership check so we can match the right account before we make any change.

Email

Send a message to our support inbox when you need a record copy or a correction in writing. We log the time, the request subject, and the reply thread for audit handling.

WhatsApp is for short follow-ups after your first check-in. We keep it brief, confirm the same account email, and move the request back to email if we need a written record.

CONTROL POINTS

Switch your privacy controls

Our privacy process is built around simple, traceable steps: we record only what we need, we protect login access with email checks, and we keep a request trail so you know what…

Data use

We use account details, device signals, and payment references only for login, session control, fraud checks, and support handling. We do not add extra fields unless you send them to us in a request or a payment dispute.

Cookies

Cookies help us keep you signed in, remember language choice, and hold the page state while you move between desktop and mobile. If you clear them, you may need to verify again on the next login.

Device logs

We log device type, browser, time stamp, and IP pattern to spot strange access and to answer a privacy request accurately. That record is tied to your account email, not to a public profile.

Retention

We keep records only as long as needed for service, dispute handling, legal duties, or fraud checks. When the reason ends, we delete or mask the data under our internal retention process.

Change requests

To change your details, send the request from your registered email and say what must be updated. We may ask for a matching code before we edit the record, then we confirm completion.

Escalation path

If a request needs more time, we tell you the reason and the next step through the same channel. You can ask for a copy of the request trail so you can see our handling.

Open common privacy questions

These answers cover the privacy requests we hear most often: access, correction, deletion where allowed, cookies, and how we verify ownership before we touch an account. If your case involves local law, we follow the rule that applies in your region and keep the request inside the same support thread. The same process is used for mobile and desktop logins.

Open live chat or email us from your registered address and ask for a data copy. We verify ownership first, then we send the record set we can share under the law that applies to your account.

Yes. Send the exact field you want changed, such as name, phone, or email, and use the account email we already store. We confirm the request with a code before we edit the record.

We keep device type, browser, time stamp, and IP pattern when needed for login checks, support tracing, and abuse checks. Those logs stay tied to the account email and are not shown publicly.

We use session cookies to keep you signed in, remember language choice, and hold the page state while you move around. If you clear them, the next login may ask you to verify again.

We keep records only as long as needed for service, dispute handling, legal duties, or fraud checks. After that, we delete or mask them under our retention process, unless local law says otherwise.

You can reach our privacy path through live chat, email, or WhatsApp follow-up after we confirm ownership. From Jakarta, Yogyakarta, or elsewhere in Indonesia, the same verification step applies.

We adjust the policy wording and the request flow to match the new rule where it applies. If a request is restricted, we explain the reason in the same support thread and keep a record of the reply.

Open velbett Privacy Policy

Browse privacy support channels

Live chat

Email

WhatsApp

Switch your privacy controls

Data use

Cookies

Device logs

Retention

Change requests

Escalation path

Open common privacy questions

01 How do I request my data?

02 Can I correct my account details?

03 Do you keep device and browser logs?

04 What cookies do you use?

05 How long do you keep records?

06 Who can contact you about privacy?

07 What happens if local law changes?

Related Pages