Reference

nagahoki Privacy Policy For Your Account

nagahoki Privacy Policy explains how we handle the details you provide during account creation, phone verification and wallet activity.

Account dataWallet recordsCookie choicesPhone verification
nagahoki nagahoki Privacy Policy For Your Account
HELP WITH PRIVACY

Three Ways To Ask About Your Data

A clear contact path matters when your account record or wallet status needs attention. Use the privacy contact route linked with this policy and include the email or phone detail connected with…

Account access If your phone verification or sign-in record looks incorrect, tell us which account step stopped. We use the registered contact detail and recent device context to locate the issue before discussing account data with you.
Wallet records For a DANA, OVO, GoPay or QRIS reference, send the payment date, selected rail and receipt number through the stated contact path. We use those details to match status records without asking for your wallet password.
Privacy requests To request access, correction or deletion of personal details, identify the account and describe the change clearly. We may ask for a verification step so another person cannot request changes to your nagahoki record.
HOW WE HANDLE DATA

Six Practical Privacy Safeguards

Our privacy process follows the same account path you see on mobile or desktop: identify the account, check the relevant event and respond through the stated contact route.

Account data

We collect details needed to create and maintain your account, including contact information and the phone verification result requested before account access. We use these details to identify your account and respond to account-related privacy requests.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references such as amount, date, status and selected rail. We use those references to reconcile a record, not to request your wallet password.

Cookies

Cookies and similar browser storage can keep your session connected and help us understand whether a sign-in attempt is unusual. You can manage browser cookie settings, although changing them may affect account access and saved preferences.

Device security

When you move from login to the lobby on a phone, tablet or desktop browser, we may record device and browser signals for security checks. These signals help us examine unfamiliar access without treating a device name as your identity.

Retention periods

We retain account, security and payment references only for as long as needed for the stated purpose, account administration, dispute handling or legal duties. When a record is no longer needed, we remove it or separate it from direct account identifiers.

Change requests

You can ask us to correct account details, provide a copy of relevant personal data or remove eligible records through the privacy contact route. We confirm your identity first and explain any legal or operational reason a record must remain.

Privacy Policy Answers For Indonesia

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. They cover what we collect, how the mobile browser path works, what happens when a wallet reference needs checking and how to request a change. If your question is not listed, use the privacy contact route with your registered account detail.

The nagahoki Privacy Policy covers account details, phone verification, sign-in and device signals, cookies, payment references and privacy requests. It explains why we use each category, how we retain it and how you can ask for access or correction where local law permits.

We may collect the contact details you submit, the phone verification result required before account access, sign-in events and device or browser signals. If you use DANA, OVO, GoPay or QRIS, we may also receive payment status and reference details.

Yes. The Privacy Policy covers payment references connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity. These can include the selected rail, date, status and receipt reference used to match your account record.

Use the privacy contact route shown with this policy and identify the account using its registered phone or email detail. State whether you want access to a record or a correction. We verify the request before sharing or changing account data.

Cookies can maintain your sign-in session and preserve selected preferences while you move through the mobile browser path. You can change cookie settings in your browser, but blocking some cookies may interrupt account access or require another sign-in.

We keep account, security and payment references for the period needed to provide account administration, investigate disputes, meet legal duties or answer a valid request. After that need ends, we remove the record or separate it from direct identifiers.

You can submit a deletion request through the privacy contact route. We first verify that you control the account, then assess which records can be removed. Some account, payment or security records may need to remain where local law permits or requires.