Reference

ink743 Privacy Policy For Your Account

Your account details, wallet status and device choices stay connected to one clear Privacy Policy at ink743.

Account data explainedWallet records clarifiedMobile access coveredPolicy contact path
ink743 ink743 Privacy Policy For Your Account
HELP WITH PRIVACY

Get Clear Answers About Your Data

A direct support path matters when a Privacy Policy question meets a real account problem. We connect your request to the relevant account record instead of asking you to repeat the same details across separate messages. Use the support route inside your account when a phone check, wallet status or receipt needs clarification. You can also refer to the policy before contacting us, which helps you describe whether your request concerns access, correction, deletion or retention. We handle each request against the account details and payment context you provide.

Team online

Account privacy request

Open the account support path and state whether you want to access, correct or remove personal details. Include the phone verification context when relevant, so we can match the request to the right ink743 account without asking you to send payment credentials.

Wallet record question

If DANA, OVO, GoPay or QRIS shows an unclear status, tell us which wallet appears and the date of the account activity. We use that detail to separate a Privacy Policy request from a payment receipt check.

Device access concern

When your mobile login looks unfamiliar, contact us through the account support path and describe the device change. We can review the account access record, explain the related data use and guide the next phone verification step.

HOW WE HANDLE DATA

Privacy Choices Across Account Use

We treat Privacy Policy work as an operating task, not a footer link. Account creation, phone verification, wallet activity and device access create different records, so we explain each purpose separately.

Account details

We use the details you enter to create and maintain your account, connect your phone verification and respond to account requests. If a detail changes, request a correction through support so the account record and related Privacy Policy response refer to the same identity.

Wallet activity

A DANA, OVO, GoPay or QRIS action can create a payment reference linked to your account. We use that reference to show wallet status and check a receipt, while keeping the request focused on the transaction details needed for the issue.

Cookies and sessions

Cookies can keep a signed-in session working as you move from mobile login to the lobby. We describe their role in the Privacy Policy so you can distinguish session support from account details and raise a specific request if a cookie concern affects access.

Device signals

We may record device and connection signals around account access to identify an unusual login or protect a phone verification step. These signals help us investigate access concerns; they do not replace your account request or change the policy purpose.

Retention choices

We retain records only for the account, payment, support or legal purpose described in the policy. A deletion request can be limited when a transaction record or legal check must remain, and we explain that reason rather than marking the request complete without context.

Policy contact

For a Privacy Policy question, contact us through the support route attached to your account. Tell us whether you need access, correction, deletion, retention details or a purpose explanation, and we will use that wording to direct the request.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the questions you are most likely to have before opening or using an ink743 account in Indonesia. We cover the account step, wallet records, mobile access, cookies, retention and the route for requesting changes. If your situation is unusual, use the account support path with the specific detail you want us to check. Access remains subject to local law, and we will explain when that affects a request.

It covers account details, phone verification, wallet references, device signals, cookies, support requests and retention. The Privacy Policy explains why each type is used and how to ask for access, correction or deletion. It applies to your account activity where local law permits.

Phone verification helps connect the person opening an account with the account record and helps us investigate an unfamiliar login. We use the verification detail for that account purpose, not as a reason to request unrelated wallet credentials. The policy explains the related handling.

Yes. DANA and QRIS activity can create a reference linked to your account so we can show status and check a receipt. OVO, GoPay, bank transfer and virtual account references follow the same policy approach when those payment routes are used.

You can ask for access through the account support path. Describe the account detail or record you want checked, such as phone verification, device access or a wallet reference. We may confirm account ownership before sharing personal data connected with the request.

Send a correction request through account support and identify the detail that appears wrong. If the change affects phone verification or a DANA, OVO, GoPay or QRIS reference, include that context without sending a password or full payment credential.

Retention depends on the record's purpose. Account, payment, support or legal checks may require different periods, and the Privacy Policy explains the reason for keeping each category. Ask support for the retention detail connected to your specific account or transaction reference.

Use the account support path and clearly request deletion of the data you want reviewed. Where local law permits, we assess the request against the account record. Some payment or legal records may need to remain, and we explain that limitation.