Reference

agito4d Privacy Policy For Indonesia

Our Privacy Policy explains how agito4d handles the details you provide when opening an account, confirming your phone, entering the lobby or checking wallet status through DANA and…

Clear data purposesWallet record contextRequest path includedMobile access explained
agito4d agito4d Privacy Policy For Indonesia
HELP WITH REQUESTS

Privacy Help Beside Your Account

A clear contact route matters when you want to ask what we hold, correct an account detail or question a wallet record. Start from the account help path while signed in, or use the support route beside the cashier area if login or payment status prevents normal access. Tell us the account identifier, the issue and the date of the relevant event; do not send a password or full payment credentials. We use those details to locate the right record without asking you to repeat sensitive information.

Team online

Account help

Use the signed-in account help path for a Privacy Policy request about your name, phone verification, login record or stored account details. We can match your message to the account step involved and explain what action is available without asking you to share your password.

Cashier status

If your request concerns DANA, OVO, GoPay, QRIS, bank transfer or a virtual account reference, contact us through the cashier support path. Include the transaction date and visible reference so we can check the payment record while keeping your full wallet credentials private.

Access route

When login stalls on a mobile browser or desktop device, use the available support contact before sending personal documents. We first check the account and security event linked to your access attempt, and eligibility or access depends on local law where that question applies.

DATA HANDLING DETAILS

What We Keep And Why

We separate account information from the activity needed to operate a secure session. For example, a phone verification event helps us recognise an account access step, while a QRIS reference helps us…

Account records

We may hold the name, phone number, login details and verification outcome you submit during account creation. These records help us connect your account with the correct wallet status and support request. We do not need your phone contents or unrelated contacts for this account step.

Payment references

A DANA, OVO, GoPay or QRIS transaction reference can appear in our operational records when you ask us to check a deposit or account balance status. Bank transfer and virtual account references serve the same matching purpose. We use the reference, not your wallet password.

Cookies

Cookies and similar browser storage can keep a login session, remember a selected language or help us understand whether a page is working. On a mobile browser, you can clear site data through browser settings; clearing it may require you to verify your account again.

Account security

We use phone verification, login event checks and device signals to help protect account access. If a sign-in from a new device needs another check, that extra step is connected to the account security process. Never place a password or complete wallet credential in a support message.

Retention choices

We keep information only for as long as it serves the stated account, security, support or legal purpose. A payment record may need to remain available after a wallet question is closed, while an unused support detail can be removed when it no longer serves that purpose.

Changes and contact

You can ask us to correct an inaccurate phone number, account name or contact detail through account help. For a broader Privacy Policy request, describe the record and action you seek. We may ask for an account check before changing information so another person cannot alter your details.

Privacy Policy Questions For agito4d

These answers focus on the questions you may have before opening an account or contacting us about stored information. They cover the account path, local wallets, mobile browsing, cookies, corrections and access requests. If your situation is not listed, use account help with the smallest useful set of details, and remember that account access depends on local law.

The Privacy Policy covers information connected with account creation, phone verification, login, wallet status, payment references, support messages, cookies and security events. It explains why we use each category and how you can ask about, correct or otherwise request action on information linked to your account.

We use your phone number for the account path and phone verification before account access. It helps us connect a login or support request to the right account. We do not ask for access to your phone contacts, messages or unrelated device content as part of that check.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use a visible reference, date or status detail to match a payment question to your account; we do not need your wallet password or full credential.

We may record device type, browser details, login time and security signals related to your session. These details help us investigate a new-device check or an unusual login. On a mobile browser, clearing cookies can remove session storage and may require another phone verification step.

Use the signed-in account help path and identify the detail that needs correction, such as your account name or phone number. We may ask you to confirm account ownership before making a change. This protects your record from an unauthorised alteration.

Send a request through account help and describe the categories you want us to check, such as login events, cookies or payment references. Include the relevant date when possible, but do not send passwords or complete wallet credentials. We will use an account check before responding.

Yes. Use account help for a general Privacy Policy question, or the cashier support path when the concern involves DANA, OVO, GoPay, QRIS, bank transfer or a virtual account record. Explain the issue in English and include only details needed to locate the account event.