Reference

cina788 Privacy Policy for Your Account

cina788 Privacy Policy explains how we handle your account details, phone verification, device activity and wallet records when you use our Indonesia service.

Clear data purposesWallet record controlPhone verification contextPolicy request path
cina788 cina788 Privacy Policy for Your Account
HELP WITH PRIVACY

Ask About Your Account Data

A direct request helps us locate the right record without guesswork. Use the account help route while signed in, describe the Privacy Policy question clearly, and include the relevant wallet rail or device path only when it relates to your request. We use your account details to verify the requester before discussing or changing personal data.

Team online

Account help route

Send a Privacy Policy question from the signed-in account help path. We can connect the request to your phone verification record without asking you to post personal details in a public message.

Wallet record check

If your request concerns DANA, OVO, GoPay or QRIS data, name the rail and approximate account action. We use the matching reference to investigate the record while limiting unrelated account disclosure.

Device access query

Tell us whether the request began on a mobile browser or desktop session. Device and login signals help us confirm the account path before we respond to a Privacy Policy request.

DATA HANDLING

How We Apply Privacy Controls

We treat Privacy Policy requests as account matters rather than general lobby questions. Our handling follows the data purpose involved, the account step that created the record and the access context shown…

Account data

We may handle your account name, contact details and phone verification result to create access, confirm ownership and answer a Privacy Policy request. We use only the details relevant to that account purpose.

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account records can show a transaction reference or status. We use those references to reconcile account actions, not as a reason to expose unrelated records.

Cookies and devices

Cookies and device signals can support sign-in continuity, fraud checks and session security. A mobile browser may create different session data from desktop, so we assess the relevant device path during account requests.

Security checks

Before discussing personal data or changing an account record, we may ask for account and phone verification details. Never send a password or wallet PIN through a support request.

Retention period

We retain account, transaction and support records only for the period needed for the stated service, security, dispute handling or legal requirement. The applicable period can differ by record type and local rule.

Change requests

You can ask us to correct account details, explain a data use or address a Privacy Policy concern through the signed-in account help route. Include the specific record so we can assess the request.

Privacy Policy Answers for Indonesia

These Privacy Policy answers address the account questions we expect before you open access or send a wallet request. They explain the practical route for checking data, correcting details and asking how cookies, device signals or payment references are handled. Where eligibility is involved, access depends on local law.

It covers account details, phone verification, cookies, device and login signals, wallet references, support messages, retention and requests to correct or explain personal data.

Phone verification helps us confirm account ownership before access or a data request is handled. It also helps connect the correct account when a wallet status needs checking.

Yes. The policy covers transaction references and status details linked to DANA, QRIS, OVO, GoPay, bank transfer and virtual account actions connected with your account.

You can send a correction request through the signed-in account help route. Tell us which detail is incorrect and complete the account check needed to protect your data.

Cookies can help maintain a sign-in session and support security checks. A mobile browser and desktop session may produce different device signals, which can affect how we confirm a request.

Retention depends on the record and the reason it was created. We may keep wallet, account or support records for service, security, dispute handling or legal needs.

Use the signed-in account help route and describe the specific data, device or payment reference involved. We use account verification before discussing personal records or processing changes.