Reference

ink89 Privacy Policy for Your Account

The ink89 Privacy Policy explains how we handle your account details, wallet records and device access when you use our Indonesia service.

Account dataWallet recordsCookie choicesSecurity steps
ink89 ink89 Privacy Policy for Your Account
CONTACT THE POLICY TEAM

Where To Ask About Your Privacy Policy

A clear contact route helps you act on the Privacy Policy without searching through unrelated account pages.

Account access If you cannot reach the policy page after phone verification, use the support path beside your account access screen. Include your account identifier and device type so we can locate the correct record without requesting your password.
Wallet records For a DANA, OVO, GoPay or QRIS entry that looks unfamiliar, share the date, amount reference and wallet name through the account support path. We use those details to check the record while keeping your private credential out of the request.
Privacy requests To ask for a copy, correction or removal review, state the exact account detail involved and the change you want. We may verify your phone before acting, then reply with the available next step under the Privacy Policy.
SIX DATA SAFEGUARDS

What The ink89 Policy Covers

Privacy work reaches beyond a single form: it follows the account from phone verification through the lobby and cashier records.

Collected details

We may handle your account name, phone verification status, sign-in events, device information and payment references. These details help connect a session to the correct account and help us respond when a wallet record or access attempt needs checking.

Cookie controls

Cookies and similar storage can remember a session choice, protect account access and show whether a policy page has been acknowledged. Your browser settings can restrict them, although some account steps may then need to be repeated.

Account security

Phone verification is part of the access path, and we use sign-in and device signals to detect unusual account activity. Never send us a password, wallet PIN or full payment credential when asking about this policy.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can be retained to reconcile a cashier event. We use the reference for account support and status checks rather than asking for unrelated personal details.

Retention timing

We keep records only while they support account operation, security checks, dispute handling or a legal duty. When a retention purpose ends, we remove the record or change it so it no longer identifies you where that process is available.

Your requests

You can ask what personal details we hold, request a correction, ask about deletion or raise a question about processing. We may confirm account ownership first, then explain any limit that depends on local law or a legal duty.

Privacy Policy Questions From Indonesia

These Privacy Policy answers cover the account steps you are most likely to check before opening an account or contacting us. They explain what may be recorded, how wallet references are used, how to request a change and what access wording means for your location. Where a legal rule affects the answer, it depends on local law.

The ink89 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookie choices and payment references. It also explains why we use those records, how long we keep them, how we protect access and how you can ask about correction or removal.

We may store the payment reference, wallet name, status and related account event for DANA, OVO, GoPay or QRIS. We use this record to match a cashier action and investigate a receipt or status question; do not send a wallet PIN or full credential.

Use the policy contact path from your account access area and identify the records you want, such as phone verification events or wallet references. We may confirm ownership before replying, and the response available to you depends on local law and any required retention duty.

Yes. State the account detail that is wrong, explain the correction and provide the account identifier used for phone verification. We check the request against the account record before changing it, and we may keep an audit entry showing that the correction was made.

Cookies can remember a session, security setting or policy choice on the device you use. You can restrict them through your browser, but the account path may ask you to verify again or repeat a choice. We do not treat a cookie as your wallet credential.

We retain records for the period needed for account operation, security checks, payment reconciliation, dispute handling or a legal duty. The exact period can differ by record type. When the reason ends, we remove or anonymise the record where that process is available.

The Privacy Policy still explains how we handle details connected with an account or access attempt. Whether you can use a particular service or complete an account step depends on local law. Contact us with the relevant screen or request, without sending a password.