Reference

Privacy Policy for Your Account Path

0din 4d Privacy Policy sets out how we use account, device and wallet details while you move from phone verification to the lobby.

Account clarityWallet contextDevice choicesContact route
0din 4d Privacy Policy for Your Account Path
CONTACT ROUTES

Where To Ask About Your Data

A clear contact path helps when your account record or wallet status needs attention. Use the support contact option shown after login and include the account detail that lets us locate your…

Account data request Ask us which account details we hold and why they are used. Send the request through the contact route shown in your account, and include your verified phone detail only when needed to match the correct record.
Wallet record question If a DANA, OVO, GoPay or QRIS receipt does not match your account history, tell us the reference and date. We use those details to locate the record while limiting the personal data included in the request.
Correction or deletion You can ask us to correct an inaccurate detail or explain whether deletion is possible. We first check account ownership, then assess legal, security and transaction-record duties before confirming the action available.
DATA CONTROLS

Six Controls Behind Our Data Handling

We keep privacy work close to the account steps you actually use, from phone verification to a mobile return visit.

Collection at account opening

We collect the details needed to create and verify your account, rather than asking for unrelated profile data. Phone verification supports account access, while payment references help match DANA, QRIS or bank transfer activity to the right account.

Cookies and device use

Cookies and device signals can remember a session, support security checks and show whether your mobile browser can return to the lobby. You can manage browser cookie settings, although changing them may affect login continuity or saved preferences.

Account security checks

Login events, verification status and unusual access patterns may be checked to protect your account. If a request concerns private data, we may confirm ownership before sharing details, including records connected with Aviator Mobile Play or wallet activity.

Transaction matching

Payment records are used to reconcile a wallet or transfer event, not to build unrelated marketing profiles. A QRIS receipt, virtual account reference or bank transfer detail may remain linked to your account while a transaction question is being resolved.

Retention decisions

We retain account, security and transaction records only for the period needed for service operation, dispute handling and legal duties. Retention can differ by record type and depends on local law, so we explain the reason when you ask.

Requests and changes

To request access, correction or removal, use the account contact route and describe the record involved. We may ask for phone verification or another ownership check, then confirm what we changed or why a record must remain stored.

Privacy Policy Questions Indonesian Accounts Ask

These Privacy Policy answers address the account, device and wallet questions we hear most often. They are written for your use before registration and during account support, with local payment examples such as DANA and QRIS. If your situation is unusual, send a specific request through the contact route displayed in your account.

It covers account details, phone verification, login events, device and cookie signals, support requests, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains retention, security checks and how you can request changes.

Phone verification helps us confirm account ownership before access and before discussing private records. It can also reduce mistakes when support checks a wallet reference or a login issue. We use the verification detail for those account and security purposes, subject to local law.

Yes. The Privacy Policy applies when you use a mobile browser or desktop device. We may process session cookies, browser settings and security events so your account can move from login to the lobby. You can adjust cookie controls in your browser, with possible effects on session continuity.

We use a DANA or QRIS reference, status and related receipt details to match a payment event with your account and answer a support request. We do not need unrelated wallet content for that purpose. Transaction records may be retained when legal or dispute duties require it.

Yes. Use the contact option shown in your account and state whether you want access to a record or correction of an inaccurate detail. We may confirm ownership through your verified phone detail, then respond according to the record type and local legal requirements.

You may request deletion of eligible personal data through the account contact route. We assess the request against security, transaction, dispute and legal retention duties. Where local law permits, we remove or anonymise data that no longer needs to remain connected with your account.

Describe the record or action clearly, such as a phone verification entry, cookie question, QRIS receipt or account detail needing correction. Include only enough information to locate your account, and do not send passwords or unnecessary payment credentials through a support request.