Reference

suhusawer Privacy Policy for Your Account

Your privacy choices stay connected to the account steps you can see: phone verification, browser access, wallet records and policy requests.

Clear data purposesWallet record contextAccount request pathIndonesia access terms
suhusawer suhusawer Privacy Policy for Your Account
DATA HELP ROUTES

Three Ways to Ask About Privacy

A clear contact route helps you act on this Privacy Policy without guessing which team to reach.

Account data Ask us to explain the personal details connected with your account, including the phone…
Wallet records For DANA, OVO, GoPay, QRIS, bank transfer or virtual account entries, tell us the…
Privacy requests Use the account support route to ask for correction, deletion where available, access or…
HANDLING DETAILS

How We Manage Account Privacy

Our privacy work follows the practical moments you experience: opening an account, moving between a phone and desktop browser, checking a wallet status or asking for a record.

Data we collect

We may collect your account contact details, phone verification result, device and browser signals, session events and payment references. When you open Fishing War Mobile Play or Liga 2 Handicap Odds, page activity may be recorded to keep the requested session working and identify technical errors.

Cookie choices

Cookies and similar browser storage can remember a sign-in state, protect a session and help us understand failed page loads. You can manage browser storage through your device settings, although removing it may require another phone check or make a saved account session unavailable.

Account security

We use phone verification and sign-in controls to reduce unauthorised access to personal and wallet-related records. If a device changes or a session looks unusual, we may pause the requested account action until you complete the relevant confirmation step.

Retention periods

We keep account, security and transaction records only for as long as needed for the stated purpose, technical integrity or a legal requirement. Records linked to QRIS, DANA or bank transfer may remain longer when a local rule requires transaction evidence to be preserved.

Changing your data

If your phone number, contact detail or account information is wrong, contact us through the support route with the requested correction. We compare the request with the account record, may ask for verification, and then update information that can lawfully be changed.

Who receives requests

Privacy questions are handled through our account support route rather than through public chat or a payment note. Include the subject of your request, such as cookies, device data or wallet history, so the appropriate team can respond without exposing unrelated information.

Privacy Policy Questions for Indonesia

These answers address the searches we hear most often about the suhusawer Privacy Policy. They focus on the records you can recognise in daily account use, including phone checks, mobile browser sessions and local payment references. If your situation is not covered, send a specific request through account support and include the relevant account step. We will assess it under this Privacy Policy and where local law permits.

It explains how we handle account contact details, phone verification, device and browser data, cookies, support messages and payment references. It also describes how you can ask for access, correction or deletion where available, subject to the requirements that apply to your account.

Phone verification helps us connect an account request with the correct account holder and reduce unauthorised access. We may use the verification result when you sign in from a new device, request account data or ask us to change a contact detail.

Yes. The Privacy Policy covers payment references connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account activity. We use these details to locate an account transaction or status question, while limiting the information shown in a response.

Contact us through the account support route and ask for an account data copy. Include the contact detail attached to your account and identify the records you need, such as phone checks, browser sessions or wallet references. We may complete an identity step first.

You can request a correction through account support. Tell us which detail is inaccurate and provide the current value or supporting context. We compare the request with your account record, complete any needed verification and change information where the Privacy Policy and local law allow.

Retention depends on the purpose of the record and any applicable local requirement. Account security events may be kept to investigate access issues, while DANA, QRIS, bank transfer and virtual account records may need longer retention for transaction evidence.

Access to an account, certain data requests and some processing activities depends on local law. If a rule limits availability or gives you a specific right, we apply that rule to the affected request and explain the next account step through support.