Reference

Open buwah4d Terms & Conditions

These Terms & Conditions explain how your account, payments, and access work on buwah4d.

AviatorSuper Sic BoJewels of ProsperityMobile and desktopLocal law

Browse lobby Read FAQ

Explore jurisdiction rules and payment checks

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

Our Terms & Conditions set the rules for account use, payment checks, content access, and record keeping. If you are in Denpasar or anywhere else in Indonesia, the same policy applies only where local law permits, and we may ask you to confirm your name, phone

1
number, and payment source before a deposit or payout moves forward. DANA, OVO, GoPay, and QRIS are the local rails we support, but each transfer still follows name matching, failed-payment handling, and audit checks. We can pause access if login behavior, device data, or payment details
2
do not fit the account record. We may also update the terms when our operating process changes, and we will expect you to use the version that is active at the time of your action.

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

CONTACT ROUTE

Browse contact paths for policy questions

If a clause feels unclear, contact us before you change account details or send funds.

WhatsApp Use WhatsApp during 09:00-21:00 WIB for terms questions tied to login, payment checks, or account changes. Send your registered number, and we will point you to the exact clause that applies.

Live chat Open live chat from mobile or desktop when you want a quick read on access, device checks, or a payment rule. We keep the same policy wording there, so your answer matches this page.

Email Write to our email address for longer requests, such as a correction to your details or a copy of the request record. Include your account name and the date so we can verify the change.

DATA CARE

Switch through data, cookies, and records

We keep policy handling narrow: only the details needed to run your account, confirm access, and answer your request are stored.

Data use

We use registration data, login timestamps, and payment references to handle the terms that apply to your account. We do not ask for more than we need to verify access, answer disputes, or keep an audit trail.

Cookies

Cookies help keep your session open when you move between mobile browser, desktop, and account pages. They also store language and device settings so the terms page loads with the same layout you last used.

Security

We check unusual login patterns, changed device fingerprints, and repeated failed entries to protect account access. If something looks off, we may pause the session until you confirm the change through your registered contact.

Retention

We keep account and request records only for as long as the terms and local law require. After that window, we remove or anonymise the data we no longer need for service, audit, or dispute handling.

Request changes

To request a correction or deletion, send your registered name, account ID, and the exact field you want changed. We use that match to avoid accidental edits and to keep the request linked to the right record.

Contact route

For policy access questions, write through WhatsApp, live chat, or email and mention whether the issue is about login, payments, cookies, or record changes. That helps us route the case without asking extra questions.

Open answers to common policy questions

These questions cover access, record changes, cookies, and how we handle a terms request. If your case involves payment checks or a login from a new device, the answer still depends on the same active policy and local law. When in doubt, send the exact clause and date so we can point you to the right line.

No. Access depends on local law and is available only where local law permits. If your location changes, we may ask you to confirm it again before you continue using the account.

We keep the name, contact number, login record, and payment references needed to run the account and answer a terms request. We do not collect extra details unless the request or a security check needs them.

Device checks help us confirm that the login matches the account history, especially when you switch between mobile and desktop. If the pattern changes suddenly, we may ask you to verify through your registered contact.

Send your registered name, account ID, and the field you want corrected through WhatsApp or email. We compare that request with the record on file before making any change.

No. Cookies do not change the written terms, but they can store your language choice and session state so the page loads the same way on your next visit. You can clear them in your browser at any time.

WhatsApp and live chat are checked from 09:00-21:00 WIB, and email stays open for longer requests. If you include the exact clause or action date, we can answer faster.

Those local rails are accepted within the account rules, but each transfer still follows name matching and verification. If the payer details do not match, we may hold the action until the record is checked.

Open buwah4d Terms & Conditions

Browse contact paths for policy questions

Switch through data, cookies, and records

Data use

Cookies

Security

Retention

Request changes

Contact route

Open answers to common policy questions

01 Can I use the account where local law does not permit it?

02 What details do you keep for Terms & Conditions handling?

03 Why do you ask for device checks?

04 How do I request a correction?

05 Do cookies change the written terms?

06 How fast do you answer terms questions?

07 How do DANA, OVO, GoPay, and QRIS fit the terms?

Related Pages