Reference

gos4d Privacy Policy for Your Account

Your gos4d Privacy Policy starts with a clear view of the data used to open an account, verify your phone, access the lobby and connect DANA, OVO, GoPay…

Account clarityWallet data contextDevice accessPolicy requests
Explore Our Lobby Read FAQ
gos4d gos4d Privacy Policy for Your Account
POLICY HELP ROUTE

Get Privacy Policy Help Before Access

Questions about the Privacy Policy should be raised before you open an account or whenever your account details change. We keep the request focused: tell us which data point, wallet reference, device event or account step you want checked. Our support route is intended for policy questions, including a stalled phone verification or a wallet status that does not match your receipt. Do not send a full password or wallet PIN in a message.

Team online

Account request

Ask us to explain the phone number, verification result or sign-in record connected with your account. Include the account contact detail you can safely confirm, but leave out your password, wallet PIN and one-time security code.

Wallet question

For DANA, OVO, GoPay, QRIS, bank transfer or virtual account data, share the payment reference and approximate action date rather than private wallet credentials. We can then check how the reference was linked to your account.

Device concern

If a phone or browser appears in your access record unexpectedly, contact us with the device type and sign-in context. We will use the policy request to check the session details and explain the next account-security step.

DATA HANDLING PRACTICE

Inside gos4d Privacy Policy Controls

We handle privacy as an account process rather than a broad statement. The controls below explain what we look at during phone verification, how cookies support a returning browser, why wallet references…

Account records

When you open an account, we use the supplied contact detail and phone-verification result to create and protect the account record. This helps us distinguish an access request from an unverified attempt without asking for your wallet PIN.

Cookies and sessions

Cookies and similar session details can keep your browser connected after sign-in and help us identify unusual access. You can manage browser cookie settings, though changing them may affect the way policy notices or account screens appear.

Phone security

A phone verification step helps connect an account request with the contact number supplied to us. We may retain the result and related security event so a later access question can be checked against the correct account.

Wallet matching

Payment references from DANA, OVO, GoPay and QRIS are used to match a wallet action with the relevant account record. We do not need your wallet PIN to investigate a receipt, status mismatch or account query.

Retention purpose

We retain account, security and payment-reference records for as long as they serve account support, reconciliation, dispute handling or legal needs. When a record is no longer needed for those purposes, our process addresses its removal.

Change request

To request a correction, access copy or explanation of your personal data, contact support with the account detail you can safely verify. We may ask follow-up questions before changing a record linked to your account.

Privacy Policy Questions About gos4d

The questions below cover the points Indonesian account holders commonly check before opening an account. Each answer stays within the Privacy Policy: what we collect, why we use it, how wallet references are matched, how device access is handled and how you can request a change. Access depends on local law and is available where local law permits.

The gos4d Privacy Policy covers account details, phone verification, sign-in and device events, cookies, payment references, support requests, retention and requests to correct or access your data. It explains how these records support account security, payment matching and policy-related contact.

When you open an account, we may collect your phone number, verification result, sign-in events and necessary device or browser details. We use these details to connect you with the right account and investigate access concerns without requesting your DANA, OVO or GoPay PIN.

We may receive payment status and reference details for DANA, OVO, GoPay and QRIS when you use those rails. These references help match an account action with a payment record. They are handled for reconciliation, support and security, not as a request for your wallet PIN.

Device and browser details help us recognise a returning session, identify unusual sign-in activity and respond when you report an unexpected access event. A phone or desktop path may create different session records, so we use that context when checking your account request.

Contact our policy support route with the account detail you can safely confirm and state whether you want a correction, an access copy or an explanation of a data use. We may ask additional questions to prevent a change being made to the wrong account.

We keep account, security and payment-reference records while they support account access, payment reconciliation, dispute handling, support or legal needs. The Privacy Policy does not treat every record alike; when a record no longer serves those purposes, our retention process addresses removal.

The policy is written for account access connected with Indonesia, including wallet references such as QRIS and local phone verification. Access and eligibility depends on local law, and the service applies where local law permits. Contact us if your location creates a policy question.

Related Pages

gos4d Indonesia Access guide About Us FAQ Liga 2 Mix Parlay