Reference

gurame123 Privacy Policy for Your Account

gurame123 Privacy Policy explains how we handle your account, device and wallet details when you open the lobby from Indonesia, including access from Yogyakarta.

Account dataWallet detailsDevice accessYour choices
gurame123 gurame123 Privacy Policy for Your Account
CONTACT PATHS

Account Questions Need A Clear Route

Privacy Policy questions should reach us through the contact route displayed in your account area, especially when a login or wallet status needs checking. Include the account phone number, the relevant date and a payment receipt reference, but do not send a wallet PIN or password. We use those details to locate the right record without asking you to repeat sensitive credentials.

Team online

Data access request

Ask us to identify the account, device or wallet records connected with your profile. We may request phone verification before releasing details through the account contact route.

Correction request

If your account name, phone detail or payment reference is inaccurate, tell us what needs changing and attach the relevant receipt. We will assess the request against account security checks.

Privacy concern

For a concern about cookies, device access or data sharing, describe the event and its date through our listed support path. Keep passwords, wallet PINs and one-time codes out of your message.

DATA PRACTICES

How Wallet And Device Data Stays Managed

We keep this Privacy Policy practical by linking each record to an account action: login, phone verification, wallet matching or a security check.

Account records

We use your account identifier and verified phone detail to recognise your profile, support sign-in checks and separate your records from another account during a contact request.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a receipt or status check. We do not need your wallet PIN to investigate that match.

Cookies and sessions

Cookies and session data can keep a signed-in device connected to the correct account and remember security context. You can adjust browser cookie controls, though some account steps may then need repeating.

Device security

We may record device and login signals when access looks unusual, such as a new browser or repeated failed attempts. These signals help us ask for an account check before continuing.

Retention choices

We retain records for the period needed to provide account support, resolve payment questions, protect access or meet a valid legal request. Ask us which retention reason applies to your record.

Change requests

You can request access, correction or clarification through the account contact route. Include your verified phone detail and the specific record so we can assess the request accurately.

Privacy Policy Questions About gurame123

These Privacy Policy answers focus on the account, device and payment details you may notice while using gurame123 from Indonesia. If your situation is not covered, send the specific account step or receipt reference through the listed contact route.

It covers account details, phone verification, login events, device signals, cookies and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

Phone verification helps us connect an account request to the correct profile and reduce unauthorised access. We may use it before providing account data or processing a correction request.

No. Our Privacy Policy distinguishes wallet payment references from wallet credentials. We may use a receipt or transaction reference for matching, but you should never send a PIN or password.

Use the contact route shown in your account area and ask for a data access request. Include your verified phone detail and the records you want identified, such as login or wallet references.

Yes, you can request a correction through the same account contact path. State the inaccurate field, provide the correct detail and include a receipt or account step when it helps us verify the change.

Cookies and session data may keep your mobile browser connected to the right account and security context. Browser controls can remove them, but you may need to repeat login or verification steps.

Yes. Account access and eligibility depends on local law. We may also retain or disclose particular records when a valid legal request or payment-security investigation requires it.