Reference

ink79 Privacy Policy For Your Account

Our Privacy Policy explains what account details we collect, why wallet records are checked, and how you can ask about your data before opening an account.

Account dataWallet recordsCookie choicesSecurity checks
Explore Our Lobby Read FAQ
ink79 ink79 Privacy Policy For Your Account
ACCOUNT HELP ROUTE

Get Privacy Help Near Your Wallet

Privacy questions are easier to resolve when we can match them to the right account event. Use the support contact available inside your signed-in account and include the phone number on file, the relevant date and the payment reference when your question concerns DANA, OVO, GoPay, QRIS or a bank transfer. We use those details to reduce back-and-forth while keeping requests tied to the person who controls the account.

Team online

Data questions

Ask which personal details we hold, why a field is needed, or how a specific login event appears in your record. Our support path in the signed-in account lets us check your request against the phone verification already attached to your ink79 access.

Wallet receipts

For a DANA, OVO, GoPay or QRIS privacy question, send the payment reference shown in your receipt and the date of the event. We can then separate wallet status data from account data without asking you to post sensitive details in a public channel.

Access concerns

If an unfamiliar device appears in your login history, contact support through your account area and describe the device path. We may ask you to complete phone verification before discussing records or changing account contact details.

DATA CONTROL POINTS

Keep Control Of Your ink79 Records

We handle Privacy Policy requests through identifiable account steps rather than broad, unverified instructions.

Collected account details

We may hold your phone number, verification result, login history, device signals and support messages. These details help us connect a request to the correct account and explain why access to a casino page or wallet record was recorded.

Payment data

A payment record can include a DANA, OVO, GoPay or QRIS reference, or a bank transfer and virtual account identifier. We use this data to reconcile status and investigate a mismatch, not to replace your account identity.

Cookie controls

Cookies can preserve sign-in state, remember device behaviour and support page security. Ask us which cookie category relates to your visit and what changing that setting may mean for account access on your mobile browser.

Security protection

Phone verification is required before account access is fully discussed, especially when a request concerns a new device or contact change. We compare the request with login events so private records are not disclosed to the wrong person.

Retention questions

Some records remain available for account security, payment reconciliation or legal duties after an event ends. You can ask what category a record belongs to, why it is retained and whether a shorter period applies to your request.

Change or deletion request

Send a clear request through the signed-in account support path, naming the data field or record you want corrected or removed. We confirm your account step first, then explain any limit created by security, payment matching or local law.

Answers About Your ink79 Privacy Policy

These Privacy Policy answers address the questions we expect before an Indonesian account is opened or used. They explain the data connected to login, local wallet payments, cookies, device checks and requests for access or correction. When a question depends on eligibility or regional access, the answer uses the same policy wording: where local law permits.

It covers account details, phone verification, login and device records, cookie activity, support messages, and payment references linked to DANA, OVO, GoPay, QRIS, bank transfer or virtual account events. It also explains retention, security, access requests and correction steps where local law permits.

We use your phone number to create an account link, complete phone verification and help confirm that a privacy request comes from the account owner. It can also help us investigate an unfamiliar login or a wallet status question without exposing your records to another person.

Yes. The Privacy Policy includes payment references and status data connected with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account activity. We use these records to match an account event, check a receipt and investigate a payment mismatch.

Sign in through the device path you normally use, open the support contact shown in your account area and state which data category you want to access. Include the relevant date or payment reference where useful. We may complete phone verification before sharing account-linked records.

Yes. Send the correction request through the signed-in account support path and identify the field that is wrong, such as a phone detail or payment reference. We confirm the account step, review the record and explain any restriction connected to security or local law.

The period depends on the record type and its purpose. Login events, payment matching details and support messages may be retained for security, reconciliation or legal duties. Ask through your account support path for the category, reason and applicable retention position for your request.

Cookies can support sign-in, remember device behaviour and protect account pages. You can ask us which cookie category was used and what changing it may affect on your mobile browser. A cookie request is handled separately from requests to access or correct account data.

Related Pages

ink79 Indonesia ink79 Casino Account information About Us Pontianak Casino Lobby