LEGAL REFERENCE

How banyu4d Handles Your Account Data

This is the banyu4d privacy policy in plain language. We wrote it for the account you open with us, the device you sign in from, and the wallet...

Indonesia-alignedPlain EnglishUpdated regularlyAccount-scopedWallet-aware
Explore Games Read FAQ
banyu4d How banyu4d Handles Your Account Data

Our Privacy Posture and Your Rights

Our privacy posture follows the data-protection rules that apply where local law permits us to operate. We collect your account identifiers, sign-in device fingerprint, and the wallet reference you choose at top-up — nothing more than what's needed to keep your lobby session secure and your balance accurate. You can request a copy of your data, ask us to correct a field,

or close the account entirely; the request flow runs through your account panel. Retention windows match supported-region accounting rules, after which records are anonymised. Third-party processors only receive the minimum scope needed to settle a transaction or verify a sign-in.

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

HELP CHANNELS

Privacy Contact Paths

Privacy Inbox Send privacy requests — data export, correction, deletion...
Live Chat Escalation Open the chat widget from any banyu4d page...
Account Panel Controls Most privacy actions sit inside your account panel...
WHY VISITORS TRUST US

How We Keep This Policy Honest

Versioned Edits

Every change to this policy is dated and kept in a visible changelog. You can see what shifted, when it...

Indonesian Counsel Review

Local counsel familiar with Indonesia data rules reviews the wording before each release. That's how we keep the policy aligned...

Scoped Processor List

We publish the processors who touch your data — payment routing for DANA, OVO, GoPay, QRIS, plus sign-in security. Each...

Encryption At Rest

Account identifiers and wallet references are encrypted at rest. Sign-in tokens rotate, and the database keys sit separately from the...

Minimal Collection Rule

If a field isn't needed to run your account or settle a top-up, we don't ask for it. That keeps...

Human Review Window

Privacy requests are reviewed by a person, not an auto-responder. Complex cases — joint accounts, lost wallet access — get...

Consistency Across Our Policy Pages

Cookie Notice
The cookie page mirrors this policy on retention and processor scope, with extra detail on session versus analytics cookies and how to opt out from your account panel.
Terms of Use
Terms reference this privacy policy for any data-handling clause rather than restating it, so a single source governs what we collect and why.
Account Closure
The closure flow honours the deletion timelines stated here. Once you close, residual records follow the same supported-region retention window before anonymisation.
KYC Notes
Identity-check pages call back to this policy on storage and access. The KYC reviewer sees only the documents needed to clear the check, nothing about lobby activity.
Wallet Linking
DANA, OVO, GoPay and QRIS linking pages quote this policy on tokenisation. We store a reference, not your wallet credentials, and the rule is identical across all four.
Marketing Preferences
Promo opt-in pages defer to the consent rules written here. Toggle off in your panel and the change propagates without needing a separate privacy request.
Third-Party Embeds
Where game providers embed content, the data-sharing language matches this policy: provider sees session token only, not your wallet or contact details.
AT A GLANCE

What This Policy Page Shows You

01
Changelog Strip A dated strip at the top of each policy revision lists what changed in plain words. Skim it on return visits to spot anything that affects your account before reading the full text.
02
Section Anchors Each clause has a stable anchor link so you can bookmark or share a specific paragraph — useful when our chat desk asks you to point at the exact wording you're querying.
03
Plain-Language Summary Every dense clause carries a one-line summary in lighter type. Read the summary first, dive into the formal wording only if you need the precise scope.
04
Request Buttons Inline buttons trigger the relevant action — export, correction, closure — straight from the policy page. No need to hunt through the account panel for the right setting.
05
Processor Table A simple table names each processor, the data scope they receive, and the country their servers sit in. Filter by purpose to see only payment or only sign-in entries.
06
Contact Footer The privacy desk contact sits at the bottom of every section, not just the page foot. You're never more than one scroll away from reaching a human reviewer.

Privacy Questions We Hear Most

We collect your contact field, a hashed password, the device fingerprint of your sign-in, and the wallet reference you pick for top-ups. Lobby activity is logged for balance accuracy, nothing else.

We never store full wallet credentials. The payment processor returns a token, and that's what sits on your account. Sharing is limited to the routing partner needed to settle each top-up.

Retention follows supported-region accounting rules, typically a fixed window after closure. Once that window ends, records are anonymised so they can't be tied back to you, your device, or your wallet.

Yes. Open your account panel, head to the privacy section, and trigger an export. The file lands in your inbox within the response window, covering identifiers, sessions, and top-up history.

Most fields edit directly from your account panel. For locked fields tied to identity checks, send a correction request to the privacy inbox with supporting documentation and a reviewer handles it.

Material changes trigger a notice when you next sign in, plus an entry in the dated changelog at the top of this page. Minor wording tweaks appear in the changelog without an interrupt.

A named handler on our privacy desk picks up the ticket. They reply directly until the request closes — no anonymous queue, no auto-responses pretending to be resolution.