Reference

giok168 Privacy Policy, Made Clear

Your giok168 Privacy Policy starts with a clear account path: we explain what we collect during phone verification, why wallet details appear during payment checks, and how you…

Account dataWallet choicesDevice accessPrivacy requests
giok168 giok168 Privacy Policy, Made Clear
HELP WHEN NEEDED

Get Help With Privacy Requests

A clear support route matters when a phone number, wallet reference, or device record needs checking.

Account desk Use the account help path when you need a copy, correction, or explanation of…
Wallet desk For DANA, OVO, GoPay, or QRIS references, share the transaction date and status shown…
Privacy request Ask us to change, restrict, or remove eligible details through the support route.
DATA PRACTICE

How We Handle Your Account Data

We keep this policy practical by connecting each data use to an account action you can recognise.

Data we receive

We receive details you enter for an account, phone verification records, support messages, device signals, and transaction references connected with DANA, OVO, GoPay, QRIS, or bank transfer.

Cookie choices

Our website may use cookies or similar browser storage to keep sign-in steps working, remember selected settings, and measure page errors. You can manage browser storage through your device settings.

Account security

We use sign-in events, phone verification, and device signals to check unusual access. Keep your password private, and contact us if a login record does not match your activity.

Retention timing

We retain account, support, and payment-reference records for the period needed to operate the account, resolve disputes, meet legal duties, or protect against misuse.

Change requests

You can ask us to correct inaccurate account details or clarify how a record was used. Include the relevant phone number, email, and date so we can locate it.

Third-party boundaries

A bank, wallet provider, or browser may apply its own privacy terms. We handle the giok168-side record, while DANA, OVO, GoPay, and QRIS manage their own systems.

Privacy Policy Answers Before Access

These Privacy Policy answers address the account questions we expect before you open an account or request help. They cover wallet references, cookies, phone verification, mobile browsers, retention, and the steps we use to confirm a request belongs to you.

It covers account details, phone verification, sign-in events, device signals, support messages, cookies, and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account.

We use the payment reference and status needed to match an account request. We do not need your wallet PIN, and your wallet provider remains responsible for its own balance records.

Use the account help path and provide your linked phone or email, the detail needing correction, and the relevant date. We verify ownership before reviewing the request.

Phone verification helps connect an account action to the right account and supports security checks when access comes from a new mobile browser or an unfamiliar device.

We keep records only as long as needed for account operation, support, dispute handling, legal duties, or security checks. The period can differ by record type and local law.

Yes. Your mobile browser settings usually let you clear or restrict cookies and similar storage. Some sign-in or preference steps may work differently after those settings change.

Yes. Requests for access, correction, restriction, or removal are handled where local law permits. Eligibility depends on local law, and we explain the reason if a limit applies.