Reference

jinhoky Privacy Policy For Your Account

The jinhoky Privacy Policy explains how we collect, use and protect the information connected to your account, device and wallet activity.

Account dataWallet recordsCookie choicesSecurity steps
jinhoky jinhoky Privacy Policy For Your Account
CONTACT PATHS

Get Privacy Help Beside Account Support

A clear contact route helps you ask about the Privacy Policy without explaining your whole account history. Start from the account help path when you need a copy request, a correction, a question about cookies or clarification about a wallet receipt. Include the phone number on your account and the relevant transaction reference, but do not send a password or one-time verification code. We use the submitted details to locate your request and keep the conversation focused on your data.

Team online

Account data request

Ask us to explain the account data connected to your phone verification or login record. Add the account phone number and a clear request so we can distinguish a data question from a general sign-in issue without asking you to disclose your password.

Wallet receipt check

For a DANA, OVO, GoPay or QRIS receipt, send the payment reference through the account help path. We compare the reference with the account record and explain what was received, what remains pending or what further verification is needed.

Privacy correction route

If your personal details are inaccurate, tell us which field needs correction and why. We may ask for an account step or phone verification before changing it, because confirming the requester protects your account from an unauthorised data change.

DATA PRACTICES

What We Do With Your Personal Data

Our handling of personal data follows the practical steps you see when using an account: phone verification before account access, device checks during sign-in and payment matching after a wallet or bank…

Account security

Phone verification links account access to a contact detail you control. We may review sign-in signals such as device type, browser session and unusual access patterns to protect the account. Never place a password or one-time code in a privacy request.

Payment matching

A payment reference helps us connect a DANA, OVO, GoPay, QRIS, bank transfer or virtual account event with the correct account. We use that record for receipt checks, status questions and account reconciliation rather than asking for unrelated personal details.

Cookies and sessions

Cookies and similar session tools can remember sign-in state, protect account steps and help us understand whether a page loads correctly on your device. You can manage cookie settings in your browser, although turning them off may interrupt account access.

Mobile device data

When you move from login to the lobby on a phone, we may receive device and browser signals needed for session security and display. These signals do not replace your account details and are handled for the access and security purposes described here.

Retention approach

We keep account, security and payment records for the period needed to provide the requested service, resolve disputes, maintain security or meet applicable duties. When a record is no longer needed for those purposes, our handling moves toward deletion or de-identification.

Your data request

You can contact us to ask what personal data we hold, request a correction, ask about processing or raise a concern about deletion. We may verify your identity through the account phone step before responding or changing a record.

Privacy Policy Answers For jinhoky

These Privacy Policy answers cover the questions we expect you to ask before opening an account or sending a wallet receipt. They explain the data connected to login, mobile browsing, cookies, payments and requests for changes. If your situation is not covered, use the account help path with the smallest amount of personal detail needed to identify your request.

It covers personal data connected to your account, phone verification, device sessions, cookies, support requests and payment references. It also explains how we use, retain and protect those records when you access the service where local law permits.

We may collect details you submit for account creation and phone verification, plus login, device and browser signals needed for session security. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity may also be recorded.

Wallet and QRIS references help us match a payment receipt to the correct account and answer a status question. We may also handle OVO, GoPay, bank transfer and virtual account records for the same account-related reconciliation purpose.

Use the account help path and state whether you want a copy, an explanation or a correction. Include your account phone number and the relevant record reference, but leave out passwords and one-time codes. We may confirm your identity first.

Cookies and session tools can support login continuity, account security and page performance when you browse on a phone or desktop. Your browser controls these settings, but disabling them may interrupt phone verification or the path from login to the lobby.

We retain records while they are needed for account access, payment matching, security, dispute handling or applicable duties. Once a record no longer serves one of those purposes, we work toward deletion or de-identification under our handling procedures.

Yes. Contact us through account help and ask which account, device or verification data relates to your access. We may request a phone verification step before sharing or changing information, so the response goes to the person connected to the account.