Reference

gagakjitu Privacy Policy And Your Data

Our Privacy Policy explains what gagakjitu collects when you open an account, access Andar Bahar or use DANA and QRIS, and why each data point is needed.

Account dataWallet recordsDevice choicesYour access rights
gagakjitu gagakjitu Privacy Policy And Your Data
CONTACT PATHS

Get Privacy Help Beside Your Account

A privacy question should not be mixed with a general lobby request, so we keep the route close to your account and payment records.

Account contact Use the support contact linked to your gagakjitu account when you want to ask what personal data we hold. Include your account identifier and the email or phone route attached to it; never send your password, wallet PIN or complete payment credentials.
Wallet record query If your request concerns a DANA, OVO, GoPay or QRIS record, mention the date, amount reference shown in your account and the payment rail used. We use those details to locate the relevant entry while avoiding unnecessary wallet data in the reply.
Access assistance When a phone check or device prompt blocks a privacy request, tell us which step appeared and whether you are on mobile or desktop. We can direct you through the account path without asking you to disclose a password or one-time verification code.
CONTROLLED DATA

How We Handle Your Privacy Choices

We treat your account record as a working set of data rather than an open profile. Login events, phone verification and wallet references are used for defined account and payment purposes, while…

Data collection

We collect details you provide during account opening, including your contact route and verification status. We also receive transaction references when you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, so the account record can be matched correctly.

Cookie settings

Cookies can remember a selected language, session state or device preference. You can adjust cookie controls in your browser, although disabling some cookies may interrupt the account path or require you to repeat a sign-in and phone verification step.

Account security

We use phone verification and sign-in signals to help protect your account. A new device may receive an extra prompt before access is completed. Keep your password private, sign out on shared hardware and contact us if a device event does not match your activity.

Retention process

We retain account, payment and support records for as long as needed for account operation, dispute handling, security checks and legal duties. When a record no longer serves one of those purposes, we remove it or separate it from direct account identifiers.

Correction requests

You can ask us to correct an inaccurate contact detail or account entry through the account contact route. We may request an account identifier and a verification step before changing data, which helps prevent another person from editing your profile.

Deletion questions

You may ask whether your account data can be deleted, subject to records we must keep for security, disputes or legal duties. We will explain which entries can be removed, which must remain, and how the decision depends on local law.

Privacy Policy Answers For Your Account

These answers address the searches we receive about the gagakjitu Privacy Policy, especially account opening, Indonesian wallet records and device access. You can use the contact path above when your situation needs a record-specific response. Keep your request limited to the details needed to identify the account, and remember that access or retention decisions depend on local law.

The gagakjitu Privacy Policy covers account details, phone verification, device and connection signals, cookies, support messages and payment references. It explains why we use those records, how long we retain them, how you can request correction or access, and when local law affects the outcome.

Phone verification helps us confirm that the person opening or accessing an account controls the contact route supplied. It can also help identify an unusual device event. We do not ask you to send a one-time code or password through support messages.

Yes. The policy covers transaction references connected with DANA, OVO, GoPay and QRIS, as well as bank transfer and virtual account records. We use those references to match account activity, investigate a receipt or status question, and protect the payment trail.

Use the support contact linked to your account and ask for a personal data access request. Include your account identifier and verified contact route, but leave out your password, wallet PIN and complete payment credentials. We may verify ownership before responding.

You can ask us to correct an inaccurate name, phone route, email route or other account detail through support. We may require an account check before making the change. Payment and security records may need a separate explanation when they cannot be edited.

Cookies can retain session settings, language choices and device preferences, so the account path does not reset each time. Your browser controls them. If you block required cookies, you may need to sign in again or repeat phone verification before access.

We keep records while they are needed for account operation, security checks, payment matching, dispute handling or legal duties. After that, we remove or anonymise them where appropriate. The exact result of a deletion request depends on local law and the record involved.