Reference

Privacy Choices for Your bintang78 Account

Your account data, payment records, and device sessions are handled under this Privacy Policy before you open Speed Blackjack, Rocket Crash, or any wallet page.

Account data explainedDANA and QRIS recordsCookie controlsDevice session checks
bintang78 Privacy Choices for Your bintang78 Account
CONTACT ROUTES

Reach Us About Your Privacy Requests

Privacy questions should reach a channel where we can verify your account without exposing extra data.

Live Chat Live chat runs 09:00–23:00 WIB from the help bubble after sign-in.
Email Privacy Desk Send privacy requests to [email protected] with your username, registered phone, and the change you…
WhatsApp Check If you use WhatsApp support, message us from the number linked to your account.
ACCOUNT CARE

How Your Data Stays Manageable

We treat privacy work as an account service, not a hidden back-office task. You can see key settings after sign-in, including your profile details, password tools, and active sessions.

Account Data

Your profile record includes username, phone, email, password status, and account activity. We use these details to sign you in, respond to privacy requests, and link support chats to the correct account.

Payment Records

DANA, OVO, GoPay, and QRIS activity creates timestamps, reference codes, and wallet-status records. We use them to match deposits, check withdrawal requests, and resolve wallet questions without asking for your wallet password.

Cookie Controls

Cookies remember your session, language preference, and security state. You can clear browser cookies from your device settings, but you may need to sign in again before opening account or wallet pages.

Device Sessions

To see active access, go to Account > Security > Sessions after sign-in. If you notice a phone or browser you do not recognise, end that session and contact support right away.

Retention Rules

We keep account and wallet records only as long as needed for service, security checks, dispute handling, and legal record duties. When data is no longer needed, we remove or separate it from active account use.

Correction Requests

If your phone, email, or display name is wrong, contact us from the current registered channel. We verify the request before changing details, then confirm when the account record has been updated.

Privacy Answers Before You Join

These answers explain the privacy points you are most likely to check before opening an account or sending a support request. We keep them practical: what data we collect, how payments appear in records, how cookies work, and how you can ask us to update or remove data where local law permits.

We collect account details such as username, phone, email, password status, sign-in records, device data, support messages, and wallet activity. We use this data to run your account, protect access, and answer requests.

We share payment data only with parties needed to process or verify that payment, such as the relevant rail or service provider. We do not ask for wallet passwords and we do not sell your account data.

Yes. Contact support from your current registered phone or email, then provide the new number. We may ask for a recent payment rail, such as QRIS or DANA, to confirm the request belongs to you.

Cookies keep your session active, remember basic preferences, and help us detect unusual access. If you clear cookies on your browser, you may need to sign in again before opening wallet or account pages.

You can ask us to delete or reduce account data where local law permits. Some payment and security records may need to stay for record duties, disputes, or account-protection checks before removal.

Sign in and open Account > Security > Sessions. You can check recent devices, browsers, and access times there. End any session you do not recognise, then message support so we can check the account.

Our support team receives requests through live chat, WhatsApp, and [email protected] during 09:00–23:00 WIB. Requests involving account changes are routed to staff who can verify identity before making updates.