Reference

garengongko Privacy Policy for Your Account

garengongko Privacy Policy explains what account data we collect, why we use it and how you can ask about it before opening an account.

Account data clarityCookie choicesPhone verificationIndonesia access
garengongko garengongko Privacy Policy for Your Account
CONTACT ROUTES

Where to Ask About Account Data

A clear contact route matters when a phone number, wallet reference or device entry needs attention. Start from the support link inside your account area and include the account step that caused the concern, such as phone verification or a QRIS status check. We use the submitted details to locate the relevant record, answer your request and avoid asking for unrelated data. Do not send a password or full payment credentials in a support message.

Team online

Account support link

Use the support link after signing in when you want to ask about account data, a phone verification record or a correction. Include your account identifier and a short description of the issue so we can locate the right record without requesting extra personal details.

Wallet status query

If DANA, OVO, GoPay or QRIS shows an unclear status, contact us through the account support path and share the transaction reference only. We use that reference to check the payment record while keeping your wallet PIN, password and full payment credentials out of the request.

Access concern

For an unfamiliar mobile sign-in or a phone verification concern, tell us the device type, approximate time and account identifier through support. That gives our team a focused security trail and lets us discuss the relevant data without exposing another account's records.

DATA PRACTICE

Security Across Your Mobile Path

We keep this policy practical by tying data handling to the account actions you can see.

Data we handle

We handle account identifiers, phone verification results, sign-in events, device and session signals, support messages and payment references. For DANA, OVO, GoPay, QRIS or bank transfer records, the reference helps us match status without needing your wallet PIN or banking password.

Cookie choices

Necessary cookies support sign-in continuity and protect the account session on your mobile browser. Where a cookie is optional, we use it only for the stated site function. You can clear browser cookies, although doing so may require phone verification again during your next account access.

Account security

Phone verification helps connect account access to the number you submitted, while session and device signals help us investigate unusual sign-ins. Keep your password private and contact support if a device entry looks unfamiliar; we will ask for focused account details, not your secret credentials.

Record retention

We keep account, support and payment-reference records while they serve access, security, dispute handling or legal needs. When a record is no longer needed, we remove it or separate it from direct account identifiers where the process allows, subject to local requirements.

Request a correction

You can ask us to correct an inaccurate phone, account or contact record through the support link in your account area. State what appears wrong and what should change. We may verify ownership before making an update so one account holder cannot alter another person's data.

Contact and access

Questions about this Privacy Policy, data access or deletion assessment belong in the account support route. Include the policy topic and your account identifier, but leave out passwords, wallet PINs and complete card or bank credentials from every message.

Privacy Policy Questions for Indonesia

These answers address the account and payment-data questions you may have before using the site. They explain how to reach us, what a mobile session can record and how wallet references such as QRIS fit into the Privacy Policy. Where access is discussed, it depends on local law.

The garengongko Privacy Policy covers account registration, phone verification, sign-in sessions, device signals, cookies, support messages and payment references. It explains why we use those records, how long operational needs may require them and how you can ask for access, correction or a deletion assessment.

We do not ask you to send a wallet PIN in support messages. DANA, OVO, GoPay and QRIS may appear as payment context or a transaction reference so we can check status. Keep your wallet credentials private and share only the reference needed for a specific account question.

A mobile browser session may create device, session and sign-in records that help us connect activity to your account and investigate unusual access. We use those signals for account operation and security, not as a request for unrelated personal data. Clearing cookies may require phone verification again.

Use the support link inside your account area and state that you are asking about account data under the Privacy Policy. Add your account identifier and the record type, such as phone verification or a QRIS reference. We may confirm account ownership before discussing or releasing data.

Yes, you can request a correction through the account support route. Explain which phone, account or contact detail is inaccurate and provide the proposed change. We may verify ownership first, then update the relevant record where the request is supported by our account and legal processes.

We retain account, support and payment-reference records while they are needed for access, security, dispute handling or legal requirements. After that need ends, we remove or de-identify records where possible. Retention can vary by record type and by requirements that apply where local law permits access.

Use the support link in your signed-in account and label the request as a Privacy Policy concern. Describe the issue without sending a password, wallet PIN or full banking credential. For an unfamiliar sign-in, include the device type, approximate time and account identifier so we can focus the check.