Reference

jakartahoki Privacy Policy For Your Account

jakartahoki Privacy Policy explains what we collect when you open an account, use the lobby, or check DANA, OVO, GoPay and QRIS status.

Clear data purposesWallet activity contextAccount request stepsIndonesia access wording
jakartahoki jakartahoki Privacy Policy For Your Account
CONTACT YOUR WAY

Privacy Policy Help Beside Account Support

A direct account request gives us the clearest route for Privacy Policy questions. Use the support path shown inside your account when you need to ask about a phone number, login record, wallet reference, cookie choice, or stored contact detail. Include the email or phone detail linked to your account, but do not send a password, one-time code, or complete wallet credential. We can then check the request against the account before discussing private data.

Team online

Account request

When your question concerns a phone number, login record, or stored profile detail, send it through the account support path. We check the account identity first, then explain which data the Privacy Policy covers and what change or access step we can take.

Wallet query

A DANA, OVO, GoPay, QRIS, bank transfer, or virtual account reference can help us locate a payment-status question without exposing your full wallet credentials. Share the date, amount reference shown in your account, and the issue you want us to check.

Access concern

If a login alert or unfamiliar device signal appears, contact us through the account support route before continuing. We can ask for the account step needed to confirm you, explain the relevant security record, and help separate your activity from an unexpected access attempt.

DATA HANDLING

Aviator Access And Your Privacy Choices

Privacy controls work best when they match the way you use the service. We separate account details, device signals, cookie settings, payment references, and support messages by purpose rather than treating every…

Collected account details

During account creation and phone verification, we collect the details needed to identify your account and send account messages. Login activity, device type, and access time can help us recognise a normal return to Aviator or another lobby area without asking you to repeat every account step.

Cookies and browser use

Cookies can keep a selected page, session state, or security check working while you move from login to the lobby on mobile or desktop. Your browser settings can restrict cookies, although some account functions may then ask you to repeat a sign-in or verification step.

Payment references

We handle a payment reference rather than requesting your complete DANA, OVO, GoPay, or QRIS secret. Bank transfer and virtual account records can be matched with the account and status you selected, helping us investigate a pending result while limiting unnecessary wallet detail.

Account security checks

Phone verification, login signals, and account-session checks help us identify whether a request is coming from you. Never place a password or one-time code in a message. If a device looks unfamiliar, pause the account step and use the support route shown after login.

Retention of records

We retain account, security, payment, and support records for as long as needed for the purpose described in this Privacy Policy, including resolving disputes and meeting applicable duties. When a record is no longer needed, our handling follows the deletion or anonymisation process available to us.

Changes and questions

You may ask what personal data we hold, request a correction, or ask why a record is used by sending a clear request through account support. We may need to confirm your identity before acting, and access or eligibility depends on local law where local law permits.

Privacy Policy Answers For jakartahoki

These Privacy Policy answers address the searches we hear most often before an account is opened or checked. We keep the wording practical: what is collected, why a payment reference appears, how to request a correction, and what happens when you use a different device. If your situation is not covered, send the account detail and question through the support path so we can check it directly.

The jakartahoki Privacy Policy covers account details, phone verification, login and device signals, cookie use, payment references, support messages, and records connected with account security. It explains why we use each category, how we confirm a request, and which local-law conditions may affect access.

These wallet names appear because a status check may need an account reference, payment timestamp, or transaction result. Our Privacy Policy explains that we use the minimum practical detail to connect DANA, OVO, GoPay, or QRIS activity with your account, rather than asking for a wallet password.

Yes. Send a correction request through the account support path and identify the detail you believe is wrong, such as a phone number or contact address. We confirm that you control the account before changing it, then explain the result under the Privacy Policy and applicable local law.

A new phone or browser may create a different device signal, so we may ask for phone verification before account access continues. The Privacy Policy allows us to use that signal for security checks. Use the support route if the device is yours but the account step does not clear.

We may retain transaction references and status details for bank transfer or virtual account activity when they are connected with your account. The Privacy Policy does not require you to send a banking password. We use the reference to resolve account questions, security matters, and applicable record duties.

Retention depends on the purpose of the record, including account operation, security checks, payment questions, support history, dispute handling, and applicable duties. When information is no longer needed for that purpose, our process may delete or anonymise it, subject to requirements that apply where local law permits.

Start with the support path inside your account and state whether you want access, correction, deletion, or an explanation of use. Include the contact detail linked to the account, but not a password or one-time code. We may confirm your identity before replying to the request.