Reference

coloksg Privacy Policy For Your Account

Our Privacy Policy explains how we collect, use, protect and retain the details connected with your coloksg account.

Clear data purposesWallet reference controlAccount access stepsMobile and desktop paths

How Your Privacy Policy Works

coloksg Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy starts with the details needed to create and protect your account, including contact information, phone verification records, login events and device signals used to reduce unauthorised access. When you use DANA, OVO, GoPay or QRIS, we may retain payment references and status information

1
so our cashier path can match an account action with the correct request; we do not need your wallet password to perform that check. Bank transfer and virtual account references are handled for the same account-matching purpose. We use information to provide the requested account service,
2
answer support requests, maintain security records and meet obligations that apply where local law permits. If you stop using the account, some records may remain for a defined retention period when needed for security, dispute handling or legal duties. You can ask what we hold, request
3
a correction, or contact us about deletion, subject to applicable limits.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

PRIVACY HELP PATH

Get Privacy Policy Help From Account Support

A clear contact route matters when a Privacy Policy question concerns your login or wallet status. Start from the account support path and include the email or phone detail linked to your account, the device you used, and the subject of your request. We use those details to locate the right record without asking you to send a wallet password or full payment credential. If your concern began after a QRIS scan, DANA status check or bank transfer reference, mention that event so we can separate a data request from a cashier query.

Team online

Account data request

Ask us to confirm which account details we hold, why they are used and whether a particular record came from registration, phone verification, device access or a DANA, OVO, GoPay or QRIS payment reference.

Correction path

If your phone number, contact detail or account identity record is outdated, send the requested correction through account support. We may ask for an account step that confirms you control the request before changing the record.

Wallet status query

For a Privacy Policy question linked to QRIS, DANA or bank transfer activity, provide the transaction reference and approximate time. We check the payment status without requesting your wallet password, card secret or banking login.

DATA HANDLING DETAILS

What We Do With Your Account Records

Your Privacy Policy rights are easier to use when the handling steps are visible. We separate account identity details from payment references where our operational process allows, restrict internal access to work…

Account details

We may hold your registration contact, phone verification result, login history and account preferences. These records let us connect a request to the correct account and investigate access problems without treating every device as the same person.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references such as amount status, time and matching code. We use these operational details to identify a request, not to collect your wallet password.

Device signals

A browser or phone may provide session, language, operating system and security-event signals. We use them to keep login continuity and identify unusual account access; the mobile route does not require a separate downloadable app.

Cookie choices

Essential cookies can support sign-in, account navigation and the return from a payment step. Optional browser storage may support preferences. You can clear or restrict cookies in your browser, while some account screens may then need another login.

Retention period

We remove or anonymise records when the stated purpose ends, unless a longer period is needed for security checks, a payment dispute, account protection or a duty that applies where local law permits.

Requesting changes

To ask for access, correction, deletion or a purpose explanation, contact account support with your registered contact and a concise request. We may verify account control before responding, and we explain any restriction on the requested change.

Privacy Policy Answers For coloksg Accounts

These Privacy Policy answers address the account questions we expect before registration or a wallet action. They explain what data is connected to your coloksg access, why payment references appear, how cookies affect a phone or desktop session, and where to send a request. If your situation is not listed, use account support and include only the details needed to identify your request. Access and any data handling depend on local law.

The coloksg Privacy Policy covers account registration, phone verification, login and device signals, cookies, support requests, payment references and record retention. It also explains how to request access, correction or deletion, subject to applicable security and legal requirements.

We use the phone verification result to connect account access with the contact detail supplied during registration and to reduce mistaken or unauthorised entry. We keep the verification record for account security and service administration, not as your wallet password.

No. Our Privacy Policy concerns the account and payment references needed to match a request, such as status, time and transaction code. We do not ask for your DANA, OVO, GoPay or QRIS wallet password to check a payment event.

Contact account support with the registered email or phone detail, then state that you want a copy of your account data under the Privacy Policy. We may ask you to complete an account verification step before sending records to the confirmed contact.

Yes, you can request a correction or deletion through the privacy support path. We first confirm account control and then assess the request against security, payment-dispute and legal retention needs. If a record must remain, we explain the reason.

Essential cookies help maintain login, account navigation and a return from a payment step. You can restrict or clear cookies in your browser, but the mobile or desktop account path may ask you to sign in again or may lose non-essential preferences.

The Privacy Policy applies to the account data handled through our Indonesia-facing access path, including DANA, OVO, GoPay and QRIS references. Account access depends on local law, and we apply any required limits or changes for your location.

coloksg Privacy Policy For Your Account

Get Privacy Policy Help From Account Support

Account data request

Correction path

Wallet status query

What We Do With Your Account Records

Account details

Payment references

Device signals

Cookie choices

Retention period

Requesting changes

Privacy Policy Answers For coloksg Accounts

01 What does the coloksg Privacy Policy cover?

02 Why does coloksg need my phone verification record?

03 Does the Privacy Policy store my DANA or QRIS password?

04 How can I request my data from coloksg?

05 Can I ask coloksg to correct or delete data?

06 How do cookies affect my Privacy Policy choices?

07 Where does the Privacy Policy apply to Indonesian access?

Related Pages