Reference

gosok Privacy Policy for Clear Account Control

Our gosok Privacy Policy explains what we collect, why we use it and how you can ask for access or correction.

Account dataWallet referencesCookie choicesAccess requests
gosok.club page image
CONTACT YOUR WAY

Use the Account Path for Privacy Help

A clear contact route matters when you want to understand or change personal data held with your account.

Account request Send an access, correction or deletion request through the account support path.
Wallet question For DANA, OVO, GoPay or QRIS data questions, share the payment reference rather than…
Security concern If you notice an unfamiliar login or account detail, report it through support and…
HOW WE HANDLE IT

Browse gosok Data Choices With Confidence

Our handling approach is practical: collect only what supports the stated account, security and payment-status purposes, then keep access to that data limited by role.

Collection

We collect account details you submit, verification results, device and browser signals, session events and payment references.

Cookies

Cookies can keep your mobile session active, remember language or display choices and help us understand page loading.

Account security

Phone verification before account access helps us match a sign-in request to your profile.

Retention

We retain records for the period needed for account support, security checks, payment matching and applicable legal duties.

Your requests

You may ask to access, correct or delete personal data, subject to identity checks and limits required by local law.

Policy contact

Use the account support route for Privacy Policy questions, data copies or changes.

Find Answers About Your Privacy Policy

These Privacy Policy answers address the questions you may have before opening a gosok account or requesting a data change. They cover collection, wallets, cookies, deletion and access checks, with local eligibility handled where local law permits.

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

We use your phone number to create and verify the account, support sign-in checks and respond to account requests. Phone verification can be required before account access is completed.

No. Our Privacy Policy concerns payment references and transaction status needed to match a DANA or QRIS event with your account. Your wallet password remains with the relevant payment service.

Use the account support path and state that you want a data copy. Add your registered phone number or email, then complete any identity check needed before private records are disclosed.

Yes, where local law permits. Send the incorrect detail and the replacement through account support. We may verify your identity first, then update the record or explain why a restriction applies.

Cookies can maintain your session, remember selected settings and help measure page loading. You can change browser settings, but blocking required cookies may make sign-in or account access ask again.

Retention depends on the purpose, such as account support, security, payment matching or legal duties. When the relevant period ends, we delete, anonymise or restrict records where appropriate.