Reference

gilahoki Privacy Policy for Indonesia Accounts

gilahoki Privacy Policy explains how we collect, use and protect the details connected with your account, device and wallet activity.

Account clarityWallet recordsCookie choicesPrivacy requests
gilahoki gilahoki Privacy Policy for Indonesia Accounts
PRIVACY HELP ROUTE

Ask Us About Your Account Records

A clear support path helps when a privacy question is connected to a login, wallet receipt or device session.

Privacy request Use our support contact route to ask which account details we hold, why they…
Wallet record If a DANA, OVO, GoPay or QRIS entry looks unfamiliar, send the receipt reference…
Access concern For an unexpected login or device session, tell us the device type and last…
DATA HANDLING DETAILS

Browse How We Handle Privacy Requests

We separate useful account records from details that are not needed for the stated purpose.

Account data

We may use your phone number, verification result and account activity to create access, recover the account and connect requests…

Payment references

A wallet or bank entry can show a method label, amount reference, status and time so we can match the…

Device signals

Browser type, operating system, approximate session details and security events may be recorded when you sign in.

Cookies

Cookies can remember a session choice or help us understand which privacy page section is being opened.

Retention period

We keep records for as long as they support account operation, payment reconciliation, security checks or a legal requirement.

Change request

To request access, correction or a change to personal details, contact support with your registered phone number and the specific…

Find Privacy Policy Answers Before Joining

These Privacy Policy answers cover the practical questions we hear before an account is opened or when a wallet record needs checking. They explain the data connected with phone verification, mobile access, cookies and local payment references. If your question concerns a particular account event, support can use the registered phone number and receipt details to locate the relevant record.

The gilahoki Privacy Policy covers account details, phone verification, login and device events, cookies, support messages and payment references. It also explains why we use those records, how long they may be retained, and how you can request access or correction where local law permits.

We may collect your registered phone number, verification result, login activity, device signals and messages sent to support. We use these details to provide account access, connect a request to the correct account and investigate unusual sessions. We do not need your password in a support message.

Yes. The Privacy Policy covers payment references linked to DANA, OVO, GoPay, QRIS, virtual account and bank transfer activity. These may include a method label, status, time and receipt reference. The relevant payment provider handles its own processing under its separate terms.

Contact our support route using the phone number registered to your account and name the exact detail you believe is incorrect. We may complete an account check before changing anything. This prevents another person from altering your records and lets us explain any retention requirement.

When you access the account from a phone or desktop browser, we may record device and session signals such as browser type, operating system and security events. These details help identify a familiar login path and investigate access that does not match your account.

You can contact us to discuss deletion or removal of direct links to your account data. We first check the request and may retain some records for account security, payment reconciliation or a legal requirement. Any action depends on local law and the purpose still attached to the record.

Send support the registered phone number, the record type and any safe reference available, such as a QRIS receipt time or device session date. Do not include a wallet PIN or password. We can then check the account trail and explain the relevant Privacy Policy handling.