Reference

Open your account with clear data terms

Your account setup, login device, wallet checks, and DANA, OVO, GoPay, or QRIS records are covered by this funbet303 Privacy Policy before you enter any room.

Account data scopeDevice login checksDANA record handlingQRIS receipt care
funbet303 Open your account with clear data terms
CONTACT ROUTES

Check privacy help before you join

Privacy questions should not sit in a queue without context, so we keep separate paths for account data, payment records, and device access concerns. When you contact us, share your registered username, the payment rail involved, and the rough time of the event. That helps us find the right record without asking you to send extra screenshots or personal documents too early.

Team online

Live chat window

Chat is available from 10:00 to 02:00 WIB for privacy questions linked to sign-in alerts, cookie choices, or wallet record checks. We may ask you to confirm your username before discussing account data.

Privacy email

Email [email protected] when your request needs file review, a correction trail, or a written response. Include the account name, contact number on file, and whether DANA, OVO, GoPay, or QRIS is involved.

Account centre request

From your phone, open Profile > Security > Data Request to ask for access, correction, or deletion where allowed. We log the request time and reply through your registered contact channel.

ACCOUNT CARE

Browse how we protect your data

We treat privacy as part of account operation, not as a separate promise hidden away from the cashier and login screens.

Account details

We store registration data such as username, contact number, email, and sign-in history so your account can be identified.

Payment records

DANA, OVO, GoPay, and QRIS records are used to match deposits, withdrawal checks, and refund tracing where relevant.

Device checks

We read device type, browser, IP signals, and login time to spot unusual access.

Cookie choices

Cookies help remember session status, language display, and basic navigation between account pages.

Room activity

Activity in rooms such as Rocket Crash, Bingo, Royal Fishing, and Dragon Tiger may create time-stamped records.

Retention review

We keep records for account safety, payment tracing, support handling, and legal duties, then reduce access when the record is…

Check answers about your privacy rights

The questions below focus on the privacy choices you are most likely to check before or after creating an account. Use them to understand what we collect, how to contact us, and how payment or device records are handled. If your case involves a specific transaction, include the wallet name and time so we can trace it faster.

We collect the details needed to identify your account, contact you, protect sign-in access, and connect wallet records. This may include username, phone number, email, device signals, IP data, and DANA, OVO, GoPay, or QRIS receipts.

We keep those records to match deposits, trace withdrawals, respond to wallet questions, and meet record duties. Receipt IDs and transaction times help us solve payment-related privacy requests without exposing more account data than needed.

Yes. Open Profile > Security > Data Request or email [email protected] with your registered username. We check that the request comes from the account holder before sharing data or giving a written response.

Start from Profile > Security, then choose the data request option. We may confirm your recent login device, registered contact, or wallet rail before changing sensitive contact details on your account.

Our cookies are used for session status, account navigation, language display, and security checks on our pages. You can clear cookies in your browser, but you may need to sign in again afterward.

We keep records while they are needed for account safety, payment tracing, support cases, and legal duties. When a record is no longer needed, we restrict access or remove it according to our internal process.

Use live chat from 10:00 to 02:00 WIB for quick privacy routing, or email [email protected] for a written case. Include your username, contact channel, and the payment rail if relevant.