Reference

shiokambing Privacy Policy for Your Account Data

Our shiokambing Privacy Policy explains what we collect when you open an account, sign in from a phone, or use DANA and QRIS for account payments.

Account dataCookie choicesPayment recordsSecurity requests
shiokambing shiokambing Privacy Policy for Your Account Data
REQUEST A CHECK

How to Ask About Your Account Data

A clear support path helps you ask about the Privacy Policy without sharing sensitive details in the wrong place.

Data access request Ask us which account details and payment references are associated with your profile.
Correction request If your contact detail or account record needs changing, send the specific field through…
Payment privacy help For DANA, OVO, GoPay or QRIS questions, include the transaction reference rather than a…
HANDLING YOUR DATA

How shiokambing Handles Device And Cookie Data

We separate account, device and transaction details so each data use has a practical purpose.

Account details

We use the contact and verification details you enter to create your account, confirm ownership and respond to account requests.

Device signals

When you sign in from a mobile browser or desktop, we may record device and browser signals for security checks.

Cookie choices

Cookies can retain a sign-in preference and help pages load with the right account context.

Account security

We may compare sign-in activity with your usual account pattern and pause a questionable step for verification.

Record retention

Account, payment and security records stay available only as long as needed for account operation, payment matching, dispute handling or…

Changes and contact

You can request access, correction or removal by using the account support path.

Privacy Policy Questions About Your Data

These Privacy Policy answers address the account and payment questions you are most likely to have before opening access. We keep the process practical: identify the relevant record, use the account support path and provide only the details needed for a secure response.

It covers account details, verification activity, device signals, cookie use, payment references and support requests. It also explains retention, security checks and the steps for asking about your personal data.

We record transaction references so a DANA or QRIS payment can be matched with the correct account and status question. We do not need your wallet password or verification code for that check.

Yes. Use the account support path, identify the account concerned and ask for a data copy. We confirm ownership before sharing records, and the available response depends on local law.

Send a correction request through account support and name the specific field, such as a contact detail. We verify that you control the account before changing the record.

Cookies may retain sign-in preferences and account context when you use a mobile browser. Your browser controls can limit them, but you may need to sign in again after changing those settings.

We retain each record only for account operation, payment matching, security checks, dispute handling or a legal request. The period may differ by record type and applicable local requirement.

You can request removal through the account support path. We first verify ownership and assess the request against account, payment, security and legal needs; processing is available where local law permits.