Reference

Privacy Policy for Your havitogel Account

havitogel Privacy Policy shows how we handle the account, wallet and device details connected with titles such as Speed Blackjack Live and Banjarmasin Night Spins.

Clear data categoriesWallet status contextRequest paths
havitogel Privacy Policy for Your havitogel Account
SUPPORT PATH

Privacy Questions Through Your Account

A clear support route matters when you want to understand a record rather than simply use the lobby. From your account area, send a privacy request with the phone number or account identifier connected to your profile, then describe whether you need access, correction or deletion review. If your question concerns DANA, OVO, GoPay or QRIS, include the payment reference and date, not your wallet PIN. We use the same path for cookie questions and device-access concerns.

Team online

Account request

Open the account support path and state the Privacy Policy request in plain English. Include your registered phone number or account identifier so we can locate the correct record before discussing sign-in events, verification details or account data.

Wallet reference

For a DANA, OVO, GoPay or QRIS query, share the receipt reference, amount and date shown in your payment record. Do not send a wallet PIN, one-time code or full login secret when asking us to check status data.

Policy change request

If a stored detail is outdated or you want to ask about retention, identify the field and explain the requested change. We may ask for an account step or phone verification before disclosing personal data or applying a correction.

DATA PRACTICES

Six Practical Data Handling Commitments

We treat privacy as an account process you can inspect, not a hidden page at the bottom of the site.

What we collect

We collect details needed for account creation and phone verification, together with sign-in records, device signals and support messages. When you use DANA, QRIS, OVO or GoPay, we may receive a reference and status result rather than your wallet password.

Cookie choices

Cookies and similar storage can remember a session, protect an account step and help us understand whether a page loads correctly on your phone or desktop. You can review browser controls and ask support how a cookie category relates to your visit.

Account security

We use phone verification, sign-in records and device signals to help identify unusual account access. Keep your phone code and wallet credentials private. If a sign-in looks unfamiliar, contact us through the account support path before sharing any payment reference.

How retention works

We retain account, transaction-reference and support records for as long as needed for the stated account purpose, dispute handling and applicable local requirements. Retention can differ by record type, so your request should name the specific data category you want explained.

Accessing your records

You can ask which personal details are linked to your account and request a copy where the applicable process allows it. To protect your record, we may confirm the phone number or another account step before releasing information to you.

Correcting details

If your phone number, profile detail or payment reference is inaccurate, tell us what appears wrong and what should replace it. We assess the request against account records, and we explain any reason a field cannot be changed immediately.

Privacy Policy Questions Indonesian Customers Ask

These Privacy Policy answers focus on the account steps you are most likely to notice in Indonesia. We cover payment references, phone verification, cookies, device access and requests for copies or corrections. For every access question, eligibility depends on local law, and the service is available where local law permits. If your case is specific, use the account support path with the smallest useful set of details.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains requests for access, correction and retention details where local law permits.

Phone verification helps connect an account step to the correct phone number and helps us respond safely to access requests. It can also help identify unusual sign-ins. We will not ask you to send a wallet PIN or one-time code through a privacy request.

Yes. The Privacy Policy covers payment references and status information connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use those details to match an account event or answer a receipt question, not to request your wallet password.

Use the account support path and state that you want an account-data request. Include the phone number or account identifier connected to your profile and specify the record type, such as sign-in history, phone verification or payment reference. We may confirm ownership before responding.

Yes, you can request a correction for an inaccurate profile detail, phone number or payment reference. Tell us what is shown and what should replace it. We compare the request with account records and explain any restriction that applies under local requirements.

Cookies can keep a session active, support an account step and help identify page-loading problems on your phone or desktop. Your browser settings provide controls for stored data. You can also ask us which cookie category relates to a particular account or lobby visit.

Yes. Access and eligibility depend on local law, and our Privacy Policy applies where local law permits. If you ask about an account record, we still use the available support path to explain the relevant data process without suggesting access is available in every location.