Reference

Read the gwktogel Privacy Policy

The gwktogel Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or check wallet status for DANA, OVO, GoPay and…

Account dataWallet recordsDevice choicesCookie controls
gwktogel Read the gwktogel Privacy Policy
CONTACT ROUTES

Contact us about your account data

A direct support request gives you a practical way to ask about the Privacy Policy without guessing which team handles your concern.

Account help Use the account help route for a copy of personal data linked to your sign-in. We may ask you to complete phone verification before discussing account records, and you should never send a password, wallet PIN or one-time code in the request.
Payment status For a DANA, OVO, GoPay or QRIS question, share the payment reference and date through support. We use that reference to locate the status record, while keeping the wallet credential itself outside our support exchange.
Policy changes Ask us to explain a Privacy Policy change, data correction or removal request through the same contact path. We will confirm the request, check whether any legal or account-security reason requires limited retention, and reply with the available next step.
DATA PRACTICE

See how we protect account records

We handle privacy through everyday account controls rather than vague promises. Phone verification supports identity checks before account access, while session and device signals help us spot unusual sign-ins.

Data collected

We may receive your phone number, account details, verification results, support messages, device signals and payment references. For a QRIS or bank-transfer check, the reference helps us match the transaction without requiring your banking password.

Cookie use

Cookies can keep your session active, remember selected settings and help us understand technical errors. They are not a substitute for account verification. Ask support which cookie relates to your concern and what choice is available on your device.

Account security

Phone verification is used before sensitive account access, and device signals can be compared when a sign-in looks unusual. We may pause a request while checking identity, but support will not ask you to disclose a password or wallet PIN.

Payment records

Our records show the payment rail, reference, amount status and related account event needed for reconciliation. This applies to DANA, OVO, GoPay, QRIS, virtual account and bank transfer, while wallet login credentials stay with the payment provider.

Retention period

We retain information only while it supports account operation, security checks, payment matching, dispute handling or a legal requirement. When a purpose ends, we remove, anonymise or restrict the record according to the retention process in this Privacy Policy.

Change requests

You can ask us to correct details, explain our use of a record, provide access where available or consider removal. Send the request through account help with enough detail to locate it, and complete verification when the request affects account security.

Find answers about Privacy Policy

These Privacy Policy answers focus on the questions we expect you to have before opening an account or sending a support request. They cover the data created by sign-in, mobile browsing, wallet reconciliation and account changes. If your situation is not listed, contact us through account help with your account identifier and the relevant payment reference, while keeping passwords and one-time codes private.

The Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It explains why we use each category, how long we retain it, when disclosure may occur and how you can request access or a correction where local law permits.

We use your phone number for account creation, verification and sensitive access checks. It helps us connect a request to the correct account when you ask about a DANA or QRIS reference. We do not ask you to send your one-time code or wallet PIN to support.

Yes. The Privacy Policy covers the payment reference, rail, status and related account event needed to reconcile DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. Wallet passwords and banking credentials remain with the relevant payment provider.

We may receive browser, device and session signals connected with your sign-in, such as technical identifiers and unusual-access indicators. These details help protect the account and diagnose a mobile path from login to the lobby. You can ask support what record relates to your request.

Send a request through the signed-in account help route and describe the record you want copied or corrected. Include your account identifier and date, but not a password or wallet PIN. We may require phone verification before releasing or changing information where local law permits.

We keep personal data for as long as it is needed for account operation, security, payment matching, dispute handling or a legal requirement. After that purpose ends, we remove, anonymise or restrict the record under our retention process, subject to applicable local law.

Yes. Contact us through account help and name the page, device and cookie concern. Cookies may support sign-in continuity, settings or technical diagnostics. We will explain the relevant use and consider your request, although some session functions may require limited cookie processing where local law permits.