Reference

Privacy Policy for Your aeron4d Account

Our Privacy Policy explains how aeron4d handles the data connected with your account, phone verification, device access and wallet activity.

Phone verificationMobile browser pathIndonesia data choicesWallet records
aeron4d Privacy Policy for Your aeron4d Account
CONTACT ROUTES

Get Help With a Privacy Request

A clear contact route matters when you want to question a record, change an account detail or ask how your data is used.

Account privacy request Open the support path from your account area and state whether you want access, correction or removal of a permitted record. We may ask you to confirm the phone number attached to the account before discussing personal data.
Wallet record question For a DANA, OVO, GoPay or QRIS query, include the payment rail and transaction reference without sharing a password or one-time code. We can then compare the account record with the status shown in your wallet path.
Access concern If a sign-in or phone verification step looks unfamiliar, use the account support route promptly and describe the device path involved. We review the account record before discussing changes, especially when a new browser or handset is involved.
ACCOUNT SAFEGUARDS

Your Data Choices Inside aeron4d

We treat this Privacy Policy as an operating rule for account data, not as a decorative page.

Account details

We use the details you provide during account opening and phone verification to create, identify and protect your account. Review the account area when a phone number changes so our records can be corrected through the proper request path.

Device records

A mobile browser or desktop session can create access records such as device type, sign-in time and security signals. These details help us examine an unfamiliar login without treating your game or wallet activity as a public profile.

Cookie choices

Cookies may keep a session active, remember a selected path or help identify sign-in faults. If you clear browser data, you may need to complete phone verification again when returning from a different device.

Payment matching

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to match a transaction with the correct account. We do not need your wallet password or one-time code for a privacy request.

Retention requests

We keep records only for the stated account, security, transaction or legal purpose, subject to required retention. Ask support which category applies to your record and whether correction, restriction or removal is available.

Policy contact

Our account support path is the place to ask about this Privacy Policy, including data access, correction and use. Give enough detail to locate your record, but leave out passwords, one-time codes and full wallet credentials.

Privacy Policy Questions From Indonesia

These Privacy Policy answers address the searches we expect from someone checking aeron4d before opening an account. They cover the data connected with phone verification, mobile access, wallet records, cookies and account requests. If your question is not answered here, use the account support route and describe the specific record or device path involved. Access depends on local law.

It covers account details, phone verification, sign-in and device records, cookies, support requests and payment references connected with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how you can ask about access, correction, restriction or permitted removal.

Our Privacy Policy does not require you to send a DANA, OVO, GoPay or QRIS password or one-time code for a privacy request. We use the selected payment rail, transaction reference and matching account details when checking a payment record.

Open the support path in your account area and ask for a data access request. Include the phone number linked to the account and enough detail to locate the record. We may confirm your identity before sharing personal data, and the response depends on applicable law.

Yes, you can ask for a correction when an account detail or transaction reference appears inaccurate. Use the account support route, identify the field or record and provide the corrected value. We may request phone verification before changing information connected with account access.

Cookies and similar browser records can remember a session and help us investigate sign-in faults on your phone or desktop. Clearing them may end the session or require phone verification again. This Privacy Policy lets you ask what cookie-related record is connected with your account.

The retention period depends on why the record exists, such as account security, payment matching, support handling or a legal duty. For DANA, OVO, GoPay, QRIS, bank transfer and virtual account records, ask support which category applies and whether a request can change its status.

This Privacy Policy is written for account access connected with Indonesia, including requests made from Bandung, but eligibility and access depends on local law. If local rules affect your request or account, use the support path and ask which handling rule applies to your location.