Reference

Privacy Policy for Your fujigaming Account

Our Privacy Policy explains what account, wallet and device details we collect, why we use them and how you can ask about changes.

Account clarityWallet data contextCookie choicesContact route
fujigaming Privacy Policy for Your fujigaming Account
CONTACT THE DESK

Where Privacy Questions Reach Us

A clear contact path helps you ask about your Privacy Policy rights without guessing which team to reach. We can connect an account question with the relevant login, phone verification or wallet-status step, while a payment receipt helps us locate a DANA, OVO, GoPay, QRIS, bank transfer or virtual account record. Use the support route shown beside your account and cashier area, and include only the details needed to identify your request.

Team online

Account privacy request

Ask us to explain the personal details linked to your account, including the phone verification stage. We may request an account identifier before discussing records, so we do not disclose account data to the wrong person.

Wallet record question

If a DANA, OVO, GoPay or QRIS reference appears incorrectly, send the receipt or transaction reference through our support path. We use that detail to trace the relevant status without asking you to share a wallet password.

Cookie or device help

For cookie choices, sign-in records or an unfamiliar device signal, tell us the browser and device path you used. We can explain the security check and the account step needed before making a data change.

DATA HANDLING

Inside fujigaming Privacy Controls

We keep the Privacy Policy practical by connecting each data category to an account action you recognise.

Registration details

We use the details entered during account creation to establish your account and complete phone verification before access. Keep your contact details current, because an outdated number can make a privacy request or security check harder to complete.

Wallet references

A cashier record can include a payment rail, reference, amount status and account match, rather than your wallet password. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references are used to resolve the related account event.

Device security

When you sign in from a new phone or browser, we may record device and session signals to identify unusual access. These signals help us decide when another account step or phone check is needed.

Cookies and sessions

Cookies can support sign-in continuity, language settings and security checks across the mobile lobby and desktop browser. You can clear or restrict them in browser settings, although some account functions may then require another sign-in step.

Retention choices

We keep account, support and payment references for the period needed to operate the service, investigate security events or meet applicable duties. After that period, records are deleted or separated from direct account identifiers where practical.

Changes and contact

To request access, correction or clarification, contact our support route with your account identifier and the specific data question. We may verify phone ownership first, then explain the available action under the Privacy Policy.

Privacy Policy Answers for Indonesian Accounts

These Privacy Policy answers focus on the account steps you are most likely to question before registration or while checking a wallet status. We explain the data connected with phone verification, mobile access, cookies, payment references and contact requests. If your situation needs a direct check, use the support route and avoid sending passwords or full wallet credentials.

It covers account registration, phone verification, sign-in, support messages, device and browser signals, cookies, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, requests for changes and contact steps.

We use your phone number to create the account record, complete the phone verification step and help protect access when a sign-in comes from a new device. The Privacy Policy explains this use; do not send a password when asking for help.

Yes. The Privacy Policy covers the payment reference and status connected with a DANA or QRIS request, along with OVO, GoPay, bank transfer and virtual account records. We use those details to match a cashier event, not to request your wallet password.

Contact our support route with your account identifier and state whether you want access, correction or clarification under the Privacy Policy. We may confirm phone ownership before responding, so the request is connected to the correct account.

We may record browser, device and session signals connected with sign-in, security checks and cookie settings. These records help identify unusual account access on mobile or desktop. The Privacy Policy explains the purpose, and you can ask support about a specific signal.

You can clear or restrict cookies through your browser controls. Some session or security functions may then ask you to sign in again or complete another account step. Our Privacy Policy explains why a cookie may be present and how to contact us.

The Privacy Policy is written for account and data questions in the Indonesian market, but access and eligibility depends on local law. Where local law permits, you can ask us about your records, corrections, retention or other available rights.