Reference

Privacy Policy For Your congpg Account

Our Privacy Policy explains how congpg handles your account details, wallet records and device access when you use the Indonesia site.

Account clarityWallet recordsCookie choicesPolicy requests
Browse Our Lobby Read FAQ
congpg Privacy Policy For Your congpg Account
CONTACT THE TEAM

Get Help With A Privacy Policy Request

A clear support route helps when you want to ask about a Privacy Policy record, correct account details or understand a wallet reference.

Account data request Ask us to identify the personal data connected with your congpg account. Include your registered phone detail and the account step that prompted your question, such as phone verification or a login from a new device.
Wallet record question For a DANA, OVO, GoPay or QRIS reference, send the visible transaction status and approximate date through our account support path. Do not send a wallet PIN, password or full payment credential in a message.
Correction or deletion If a Privacy Policy record is inaccurate, tell us what needs changing and why. We will check account ownership, assess any retention duty and explain the next step before making a correction or removal where local law permits.
DATA HANDLING

What We Do With Your Account Details

Your Privacy Policy rights are easier to use when each data purpose is visible. We use account details for login, phone verification, payment matching, fraud checks and support conversations tied to your…

Account security

Phone verification is part of account access, and we may compare login device signals with earlier sessions. If a sign-in looks unusual, support may ask for an account detail rather than a wallet PIN before helping you continue.

Payment matching

We keep payment references needed to connect a cashier result with your account. DANA, OVO, GoPay and QRIS status can appear in these records, while sensitive wallet credentials should remain with the payment provider.

Cookie controls

Cookies can preserve login flow, remember a selected setting and help us detect repeated access attempts. Your browser can block or clear them; after that choice, the lobby or account page may ask you to verify again.

Device behaviour

On mobile and desktop, we may process browser type, operating system, session time and basic network signals. These details support account security and troubleshooting without changing the Privacy Policy purpose of the underlying account data.

Retention checks

We review account, payment and support records against operational and legal needs. When a record no longer has a valid purpose, we remove it or separate it from direct account identifiers where local law permits.

Your request path

You can ask what personal data we hold, request a correction, ask about processing or seek removal where local law permits. Send the request through account support and include enough detail for us to locate your profile safely.

Privacy Policy Answers For congpg Accounts

These Privacy Policy answers address the account and wallet questions we expect from Indonesian customers before they open an account. They explain what we collect, why a verification step may appear, how to ask for a change and which details to leave out of a support message. If your case involves a specific record, use the account support path so we can check it securely.

The congpg Privacy Policy covers account details, phone verification, login and device signals, cookie activity, payment references and support messages. It explains why we use each category, how retention is assessed and how you can request access, correction or removal where local law permits.

Phone verification helps confirm that the person requesting account access controls the registered contact detail. We may use the result with login and device signals to protect the account. It is not a request for your DANA, OVO, GoPay or QRIS PIN.

Yes. The Privacy Policy covers payment references and status details connected with DANA, OVO, GoPay and QRIS, plus bank transfer or virtual account matching. We use these records to reconcile an account event, while payment credentials remain with the relevant provider.

Use the support path linked from your account and ask for a personal data access request. Include your registered phone or email detail and a short description of the records you need. We may verify ownership before sharing account or payment-related data.

You can ask us to correct an inaccurate account detail or explain a payment reference that appears wrong. Send the request through account support with the affected field and supporting context. We will check ownership and tell you the outcome or next step.

We keep personal data for the period needed for account access, payment matching, security, support handling or a legal requirement. Retention is checked by record type. When the purpose ends, we remove or anonymise the data where local law permits.

Yes. You can contact our support route with a Privacy Policy question before opening an account. Ask about cookies, phone verification, wallet references or a proposed data request. Do not include passwords, wallet PINs or complete payment credentials in your message.

Related Pages

congpg Indonesia About Us FAQ Account information Access guide