Reference

sihoki Privacy Policy: Your Data Explained

Our Privacy Policy shows how sihoki handles the details you provide when opening an account, signing in, checking wallet status or contacting support.

Account clarityWallet referencesCookie choicesContact path
sihoki sihoki Privacy Policy: Your Data Explained
CONTACT OPTIONS

How To Ask About Your Privacy

A clear contact route helps you act on this Privacy Policy without guessing which team to reach.

Account request Use the support chat to ask for a copy, correction or deletion review involving…
Wallet query For DANA, OVO, GoPay or QRIS records, send the payment reference and date through…
Access concern If a new phone, browser or login alert looks unfamiliar, contact support through the…
HANDLING DETAILS

How We Manage Your Privacy Choices

We keep this Privacy Policy practical by tying each data use to an account action you can recognise.

Account data

We may hold your name, contact details, verification result and account timestamps so we can create access, recover the account…

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records are used to match payment status.

Cookies

Cookies and similar device markers can keep a session active, remember a selected language and help identify unusual sign-in behaviour.

Security steps

Before discussing account data, we may compare your contact detail, recent sign-in signal or verification status.

Retention period

We keep records for account operation, security checks or legal needs.

Change request

Ask us to correct inaccurate details through support chat or the contact form.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the searches we hear most often before an account is opened. They cover account data, cookies, payment references, device access and the steps needed to contact us. If your question is not listed, use the support route above and refer to the specific record or account action involved.

We collect the contact and verification details needed to create account access, plus sign-in timestamps and device signals used for security. We explain any additional request before it is needed.

No. We use payment references, status details and receipts to match a DANA, OVO, GoPay or QRIS request. Do not send a wallet password or one-time code to support.

Contact us through support chat or the contact form and ask for an account-data copy. Include your connected email or phone number; we complete an account check before responding.

Yes. Tell support which account field is inaccurate and what it should say. We may request verification before changing contact, identity or account-access details.

Cookies can retain a session, remember language settings and flag unusual sign-in behaviour. Your browser controls let you manage cookies, though restricting them may affect account access.

We retain records while they support account operation, security checks or legal needs. After that period, we remove them or restrict access according to our internal retention process.

Yes. Account access and data handling can depend on local law. Where local law permits, we provide the account and support steps described here for Indonesian customers.