Reference

Open astogel Privacy Policy With Clarity

astogel Privacy Policy explains what we collect when you open an account, use DANA or QRIS, and move between the lobby on mobile or desktop.

Account dataWallet recordsDevice securityPolicy requests
Explore Our Lobby Read FAQ
astogel Open astogel Privacy Policy With Clarity
CONTACT YOUR WAY

Open A Privacy Request Through Support

A clear support route helps you act on the Privacy Policy instead of searching through unrelated account screens.

Account help Use the account help path when you want to ask about stored contact details, a verification record or access to your Privacy Policy rights. Include the account identifier you use for login, but never send your password, one-time code or complete wallet security details in a support message.
Wallet evidence For a payment-data question, attach only the useful reference from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We can compare that reference with the account record while you keep your PIN, password and one-time code private.
Access concern If a privacy request follows an unexpected login or device change, tell us which device path you used and when the event appeared. We can direct the concern to account security and explain what action is available under the Privacy Policy.
HOW WE HANDLE IT

Explore astogel Data Handling In Six Steps

The Privacy Policy is practical: it connects each data purpose to an account action you can recognise.

Collection

We collect account details when you create or update your access path, then use them to connect verification with the correct account. A clear phone verification step can help distinguish your account from another person using the same device or network.

Payment records

A DANA, OVO, GoPay or QRIS reference can appear in our operational records when you use that rail. Bank transfer and virtual account references serve the same matching purpose, helping us investigate a wallet status question without requesting your PIN.

Cookies

Cookies may support the session needed to move from login to the lobby and keep a selected account state available. Your browser controls whether some cookies remain, and changing those controls can require another login or remove stored session preferences.

Security

We use account and device signals to assess unusual access, such as a new browser appearing after your normal mobile path. If a check is needed, we may ask you to complete the account verification step rather than share your password or one-time code.

Retention

We retain records for the period needed to operate the account, reconcile wallet activity, address disputes and meet applicable legal duties. The period can differ by record type, so a request about a QRIS receipt may follow a different retention path from a login event.

Changes and contact

You can ask us to correct account details, explain a data use or remove information where the Privacy Policy and local law allow. Send the request through account help with enough context to locate the record, while keeping passwords, PINs and codes out of the message.

Check Privacy Policy Questions Before Opening

These Privacy Policy answers focus on the account decisions you are most likely to make before opening access from Indonesia. We explain the records connected with wallets, devices, verification and support, without turning this page into a general lobby description. Where an answer involves eligibility or access, the position is direct: it depends on local law. Use the account help path when you need a record-specific answer about your own details.

It covers account details, phone verification, login and device signals, cookies, wallet references, support requests and retention. We use these records to operate access, check payment status, protect sessions and respond to your questions. Availability and any related request depend on local law.

We collect the details needed to create and maintain your account, including contact information and verification records. Login events and device signals may also be recorded for security. We do not need your password, PIN or one-time code in a support request, so keep those private.

Yes. The policy covers transaction references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These references help us match a wallet event with your account and investigate a status question, while your PIN and other security credentials stay out of support messages.

Use the signed-in account help path and identify the detail you want corrected, such as a contact record or verification entry. We may ask for an account check before changing it. Send only the context needed to locate the record, never your password or one-time code.

Cookies can support the session that takes you from login to the lobby and remembers necessary browser choices. Your browser settings can limit or remove them, although that may require another login. The policy explains their operational purpose rather than treating cookies as a separate account.

We keep each record for the period needed for account operation, security checks, wallet reconciliation, dispute handling and applicable legal duties. Retention can vary between a login event and a QRIS or bank transfer reference. Ask support about the record type connected with your request.

You can ask us to explain a data use, provide access to a relevant record, correct details or remove information where the policy and local law allow. Start through account help and describe the record. We will explain the available action after confirming the account context.

Related Pages

astogel Indonesia FAQ About Us MotoGP Race Bet Account information