Reference

Privacy Policy for Your fungame Account

Our Privacy Policy explains what fungame collects when you create an account, verify your phone, browse Live Baccarat Royal or use DANA and QRIS.

Account and phone checksWallet record handlingCookie and device choicesPolicy contact path
fungame Privacy Policy for Your fungame Account
CONTACT ROUTE

Get Privacy Help Beside Account Support

A clear contact route helps when a wallet record, phone check or device entry needs clarification. Open the support link from your account area and mention the email or phone detail connected to your fungame profile; do not send a wallet password or full payment credentials. We use the request to locate the relevant record, explain the Privacy Policy step involved and tell you if identity confirmation is needed.

Team online

Account privacy request

Use the support link inside your signed-in account when you want to ask about stored profile data, phone verification or a login record. Include the request type and your account contact detail so we can match the case without asking you to disclose a password.

Wallet record question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account records, provide the transaction reference and date shown in your payment history. We can explain the data held for status checking, while wallet credentials should remain with your payment provider.

Correction or deletion

Ask through the same account support route if a profile detail is wrong or you want a deletion request assessed. We may confirm your identity before changing records, and some data may remain where retention depends on local law or an unresolved payment matter.

DATA HANDLING

What We Do With Your Account Data

We keep this policy practical by linking each data category to a visible account action. Phone verification supports sign-in checks; device signals help identify unusual access; payment references help reconcile wallet status…

Account records

We store the details needed to create and maintain your account, such as your contact identifier, phone verification result and selected account settings. These records let us connect a privacy request to the correct profile instead of disclosing details to an unverified requester.

Payment references

A DANA, OVO, GoPay or QRIS entry may include a reference, status, amount and timestamp. Bank transfer and virtual account records follow the same reconciliation purpose. We use these details to match account activity, not to request or retain your wallet password.

Device and browser data

When you sign in on a phone, tablet or desktop, we may receive browser type, operating system, approximate session signals and security events. On mobile, you can manage cookie permissions through your browser settings and clear stored site data there.

Cookies and sessions

Necessary cookies keep a signed-in session and preserve security choices, while preference cookies help remember selected settings. Clearing cookies can sign you out and remove saved choices, but it does not erase account records; request that separately through support.

Retention controls

We retain account, support and payment references for as long as needed for the stated purpose, dispute handling or obligations that depend on local law. When the period ends, we remove or de-identify the record through our retention process.

Requesting changes

You can ask what personal data is linked to your account, request a correction or ask for deletion assessment from the account support route. We may request phone or account verification first, then explain any reason a record must remain available.

Privacy Policy Answers for fungame

These Privacy Policy answers cover the account steps and payment records you are most likely to ask about before joining. We keep the wording tied to actual actions: phone verification, mobile browser settings, wallet references and the support path in your account. If a request involves eligibility or regional access, the result depends on local law.

The fungame Privacy Policy covers account details, phone verification, device and browser signals, cookies, support messages and payment references. It explains why we use each category, how retention works and how you can ask about, correct or assess deletion of data linked to your account.

No. We use transaction references, status, amount and time to reconcile DANA or QRIS activity with your account. Your wallet password and authentication credentials stay with the payment provider. Never include them in a support request about a payment record.

Open the support link inside your signed-in account and ask for the personal data connected to your profile. Include your account contact detail and request type. We may complete phone or account verification before describing records, protecting the account from an unverified request.

Yes, you can ask for a correction or deletion assessment through account support. We first confirm the request relates to you, then check whether the record is still needed for payment reconciliation, dispute handling or an obligation that depends on local law.

Necessary cookies help keep your signed-in session and security choices working in a mobile browser. You can clear or restrict them through your browser settings, although doing so may sign you out. Cookie changes do not automatically delete account or payment records.

Device and browser signals help us identify unusual sign-in activity, protect phone verification and investigate an account-access request. We may note the browser type, operating system and session signals, but these details are handled for security and policy purposes rather than wallet-password storage.

Our data-handling explanations apply to the account process, while eligibility and regional access depend on local law. If you are in Indonesia, including Denpasar or another city, use the account support route for a question about a specific request or available access.