Reference

Privacy Policy for agustoto Indonesia Accounts

Our Privacy Policy explains how agustoto handles the account, device and wallet data you share when you open an account or enter the lobby.

Clear collection purposesWallet data contextAccount access controlsCookie choices
agustoto Privacy Policy for agustoto Indonesia Accounts
PRIVACY HELP

Privacy Help Through Your Account Path

A clear contact route helps you ask about the Privacy Policy without searching through unrelated pages. Start from your signed-in account area and include the email or phone detail linked to your account, the device path you used and the nature of your request. We use those details to locate the correct record while limiting what is disclosed. Bandung and Medan customers follow the same route, subject to local law.

Team online

Account contact

Use the support contact route after signing in and identify your account with its linked phone or email. We can then address a Privacy Policy question without asking you to send a full payment credential.

Wallet status query

For a DANA, OVO, GoPay or QRIS record, share the visible receipt reference and date rather than a wallet PIN. This lets us check the privacy-related account trail while reducing unnecessary exposure.

Access request

If you cannot sign in, state the device path and the account detail you can verify. We may ask for a phone confirmation before discussing stored records or changing the contact route.

DATA CONTROL

Six Data Handling Checks We Apply

Our handling process follows the purpose stated in this Privacy Policy rather than treating every record as open-ended.

Account details

When you open an account, we collect the contact details needed for phone verification and account access. We use them to identify your account, send account-related replies and handle a requested correction.

Device signals

A mobile browser and a desktop browser can create different sign-in records, including session time and basic device signals. These help us review an access question without collecting unrelated files from your device.

Cookie controls

Cookies can keep your selected session path and help us understand whether a page loads correctly. You can manage cookie settings through your browser, although restricting them may interrupt sign-in or saved account choices.

Wallet references

For DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity, we may retain a reference, amount status and time. We do not need your wallet PIN to address a Privacy Policy request.

Account security

Phone verification before account access helps us distinguish an account holder from an unverified request. Never place a password, one-time code or wallet PIN in a support message about privacy.

Retention requests

You can ask what personal data is held, request a correction or ask about deletion. We assess the request against account security, transaction records and any retention duty that depends on local law.

Questions About agustoto Privacy Policy

These Privacy Policy answers address the account steps you are most likely to search before opening an account or asking for a data change. We keep the route practical: identify your account, describe the record involved and avoid sending passwords, one-time codes or wallet PINs. Requests from Indonesia are handled under the applicable local rules, and access depends on local law.

It covers account details, phone verification, sign-in activity, device signals, cookies, support messages and wallet references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account use.

We use the phone number linked to your account for verification, account access checks and replies about a privacy request. We do not need your wallet PIN to identify that account.

Yes. The Privacy Policy covers data created when you use a mobile browser or desktop browser, including session and basic device signals used to review access and security questions.

Sign in where possible, use the account support route and state the field that needs correction. Include your linked phone or email, but never send a password or one-time code.

You can request a description or copy of stored personal data through the account contact route. We first verify the request and may limit disclosure where account security or local law requires it.

Retention depends on the record type and any operational or legal duty that applies. A wallet reference may remain for status checks or required records, then be removed or restricted when allowed.

Use the support contact route and explain that you cannot sign in, name your device path and provide the account detail you can verify. We may require phone confirmation before discussing stored data.