Reference

Open kotagg Privacy Policy Before Account Access

Our Privacy Policy explains how kotagg handles your account data before you enter the lobby, including phone verification, mobile browser cookies and wallet records linked to DANA, OVO…

Clear data purposesCookie choicesAccount request pathWallet privacy context

Explore Our Lobby Read FAQ

Check Privacy Policy Before Using DANA

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

Before an account is opened, we use the details you submit to create your profile, verify your phone and protect account access. During a wallet action, we may record the selected rail, such as DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, together with

1
status details needed to match the request. We do not treat a payment choice as permission to use unrelated data. Cookies can help keep your session active and remember settings on your mobile browser, while required security records help us investigate unusual access. You can ask
2
us to explain, correct or remove eligible data through the support path below. Requests may require account checks so we do not disclose data to the wrong person. Access to kotagg and related processing depends on local law, and this Privacy Policy applies where local law
3
permits.

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

REQUEST SUPPORT

Ask kotagg About Your Privacy Policy

A direct support request gives you a practical route when you want to understand or change personal data held with your account. Start from the account help area, include the email or phone linked to your profile, and describe the Privacy Policy question clearly. We may request a simple identity check before discussing wallet records or account history.

Team online

Account data request

Use the account support form to ask what personal data is linked to your profile. Include your registered phone number so we can locate the correct account before replying.

Cookie question

If a mobile browser keeps or blocks a kotagg cookie, contact support with your device type and browser path. We can explain required session cookies and available preference changes.

Wallet record query

For a DANA, OVO, GoPay or QRIS record, provide the account reference and approximate action date. We use those details to check the relevant privacy record without exposing another account.

DATA HANDLING

Browse kotagg Privacy Policy Controls

Privacy work is tied to real account steps rather than broad promises. We separate profile details from the purpose that needs them, use access checks before responding to…

Account creation

When you open an account, we use submitted contact details and phone verification to establish the profile.

Cookie handling

Cookies support sign-in continuity, security checks and selected preferences.

Payment records

A wallet or bank action can create a rail, amount, status and reference record.

Account security

Phone verification and unusual-access checks help protect your profile.

Retention approach

We retain personal data and security records for the period needed for account operation, dispute handling or a legal requirement.

Change requests

You can request access, correction or deletion of eligible personal data through account support.

Find Answers About Privacy Policy

These Privacy Policy answers focus on the account questions you may have before opening access from Indonesia. We explain what is collected, how wallet records are treated, how cookies work on your device and how to send a request. If your case needs a personal check, use the account support path rather than sending sensitive data in an open message.

The kotagg Privacy Policy covers account details, phone verification, cookies, security records and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity.

We use your phone number to create and verify the account, help protect sign-in access and connect a support request to the correct profile. We do not use it for unrelated purposes.

Yes. The Privacy Policy covers QRIS records connected with your account, such as a reference, status and timing needed to match a request. We may verify ownership before discussing those records.

Send a request through the account support form and include your registered phone number or email. We may complete an identity check before providing eligible account data or explaining the response.

Yes. Under the Privacy Policy, you can ask us to correct eligible profile details through support. Describe the field that needs changing, and keep access to your registered contact method.

Cookies can maintain a mobile browser session, support security checks and remember preferences. You can manage them in browser settings, but blocking required cookies may interrupt account access.

Some records may remain for account disputes, security review or a legal requirement. We keep them only for the relevant purpose, then remove or de-identify them where suitable.

Open kotagg Privacy Policy Before Account Access

Ask kotagg About Your Privacy Policy

Account data request

Cookie question

Wallet record query

Browse kotagg Privacy Policy Controls

Account creation

Cookie handling

Payment records

Account security

Retention approach

Change requests

Find Answers About Privacy Policy

01 What does the kotagg Privacy Policy cover?

02 Why does kotagg need my phone number?

03 Does the Privacy Policy cover QRIS activity?

04 How can I request my kotagg data?

05 Can I ask kotagg to correct my data?

06 How do cookies affect Privacy Policy choices?

07 Does kotagg keep my data after account closure?

Related Pages