Reference

Privacy Policy for Indonesia Accounts

Your studibet78 account privacy is tied to clear account steps: phone OTP, Profile > Security > Devices, and wallet records for DANA, OVO, GoPay and QRIS.

Phone OTP checksDevice session controlsDANA and OVO recordsGoPay and QRIS context
studibet78 Privacy Policy for Indonesia Accounts
CONTACT PATHS

Privacy Help Through Local Channels

Fast privacy help matters when your phone, wallet, or device record changes. We give you three contact paths so you can choose the safest route for your request: signed-in chat, email, or…

Signed-in chat Use the chat bubble after sign-in for privacy questions about login alerts, device sessions, or wallet records. Our team answers daily from 10:00 to 22:00 WIB and may ask for OTP confirmation.
Email request Send detailed requests to [email protected] when you need copies, correction, or deletion checks. Include your registered phone number, not your OTP, so we can trace the account safely.
WhatsApp recovery If you cannot sign in, message our support WhatsApp from the number on your account. We confirm identity first, then route payment-data questions involving DANA, OVO, GoPay, or QRIS.
ACCOUNT SAFETY

Data Handling Around DANA and QRIS

Privacy work happens inside the account flow, not afterthought. Every data point we keep has a job: sign-in, wallet matching, cookie choice, support follow-up, dispute handling, or legal retention.

Account data

Registration data links your phone, email if added, username, and sign-in history. We use it to confirm account ownership before changes to profile, wallet links, or privacy request records.

Payment logs

DANA, OVO, GoPay, and QRIS entries store transaction references, timing, and account matching status. We use those details to resolve payment questions without opening your wallet app data.

Cookie choices

Cookie settings help us remember language, session state, and fraud signals without reading your private messages or files. You can clear browser cookies anytime, then sign in again through phone OTP.

Device records

Device records show browser type, IP range, and successful sign-ins from paths such as Profile > Security > Devices. If a session looks unfamiliar, contact us before adding new payment details.

Retention periods

Retention periods follow account use, payment record needs, and local law. We keep only what we need for wallet checks, dispute handling, security logs, and privacy requests you send.

Change requests

Correction requests start with your registered phone or email so we can match the account. We may ask for an OTP check before editing name, contact, or wallet data.

Privacy Questions Before You Join

These answers focus on practical privacy steps before and after you join. You will see what we collect, how wallet references are treated, how cookies behave on mobile browsers, and how to reach us when your data needs a change. We write the answers in account language because most requests start with a phone number, an OTP check, or a payment reference from DANA, OVO, GoPay, or QRIS.

We collect the details needed to create and protect your account: phone number, email if provided, login records, device signals, and wallet references. We use them for access, security checks, support, and payment matching.

No. We only record payment references you submit or that our cashier receives, such as transaction ID, time, amount, and rail name. We do not access your private wallet app balance or contact list.

Email [email protected] from your registered email or contact chat after sign-in. We verify your phone or OTP status first, then prepare account, device, support, and payment-reference records we can lawfully share.

Yes, send the exact field you want changed or removed. Some payment and dispute records may need to stay for legal or security reasons, but we will explain what remains and why.

Cookies keep your session, language choice, and basic security signals on your browser. If you clear them, you may be asked to sign in again and complete OTP before wallet or profile pages load.

Only staff who need to handle the request can see it, such as support leads or account-security staff. We log actions on the case so changes can be traced if you ask later.

If access or eligibility is affected, local law controls what we can offer and what records we must keep. Services are available only where local law permits, and privacy requests remain open through support.