Reference

Privacy Policy for Your ink555 Account

Our Privacy Policy explains what ink555 collects when you open an account, verify your phone, enter the lobby and use wallet options such as DANA, OVO, GoPay or…

Clear data purposesWallet records explainedDirect privacy requests
Explore Our Lobby Read FAQ
ink555 Privacy Policy for Your ink555 Account
CONTACT ROUTES

Get Privacy Help Near Your Account

A privacy question should not require you to search through unrelated pages. We keep the contact path close to the account and cashier areas, where you can identify the record or wallet event you are asking about. Include your account contact details, the relevant date and a short description, but do not send a password or one-time verification code. We use those details to locate the request, confirm that it comes from you and provide a focused reply.

Team online

Account contact route

Use the contact route shown after account access when you need to ask about a profile record, phone verification detail or stored contact address. We may ask you to confirm account ownership before discussing private data.

Wallet record question

For a DANA, OVO, GoPay or QRIS record, include the wallet name, date and status shown in your account. We can then separate a privacy request from a payment-status question without asking you to reveal your wallet password.

Security concern

If you notice an unfamiliar login or device event, contact us through the account help path and change your password from your account settings. Do not share a verification code; we use account checks to protect the request.

DATA PRACTICES

How ink555 Handles Privacy Requests

We handle this policy area as an operating process, not as a statement hidden from your account journey.

Account data

When you create an account, we record the details needed to identify it and complete phone verification before access.

Wallet records

DANA, OVO, GoPay and QRIS references help us connect a wallet event with the correct account and status.

Cookies and browser signals

Cookies and similar browser signals can remember session choices, support account security and show whether a login pattern needs checking.

Account protection

We use phone verification, login events and device signals to help identify unusual access.

Retention approach

We keep records only for the period needed for the purpose described in the Privacy Policy, account operation, security checks…

Changes and requests

You can ask us to correct an inaccurate contact detail, explain a data use or provide the route for a…

Privacy Policy Answers for ink555

These answers address the questions we expect you to ask before opening an account or checking the lobby. They focus on data collection, local wallet records, device access, cookies, retention and contact steps. If your situation is not covered, use the privacy contact route connected with your account and describe the specific record you want us to check.

It covers account details, phone verification, login and device signals, cookies, wallet and transaction references, support messages, retention and privacy requests. It also explains the purposes for using each category and the checks we make before discussing information linked to your account.

Phone verification helps connect the account to the person opening it and reduces mistaken or unauthorised access. We may use the verification record when checking a privacy request. Access and eligibility depends on local law, and we do not ask you to send your verification code.

Yes. The policy covers references created when you use DANA, OVO, GoPay or QRIS, including status and matching details connected with your account. Bank transfer and virtual account records may also be included, while wallet passwords and private codes should remain with you.

When you move from login to the lobby, we may receive browser type, operating system, language settings, device signals and security events. These details help maintain a session and check unusual access. They do not replace the account and phone verification information used for identity checks.

Use the account contact route and state which detail is inaccurate, such as a contact address or phone record. Add the account identifier and a short explanation. We confirm account ownership before changing a record, then use the available contact path to respond.

The period depends on the type of record and the reason it was collected. We retain data for account operation, security checks, service handling or legal duties described in the Privacy Policy. Ask us about a specific category, such as a QRIS reference or support message.

You can ask us to explain the categories connected with your account, the purpose for using them and the route for a specific access request. Include enough detail for us to locate the record, but never send your password, wallet PIN or phone verification code.

Related Pages

ink555 Indonesia Super Sic Bo FAQ Account information Access guide