Reference

Privacy Policy for Your ink66 Account

Your Privacy Policy page explains how ink66 handles the details you provide before you enter the lobby, including your account identity, phone verification, wallet status and device signals.

Account clarityWallet recordsCookie choicesRequest steps
Browse the lobby Read FAQ
ink66 Privacy Policy for Your ink66 Account
HELP WITH REQUESTS

Where to Ask About Privacy

A clear request route matters when your account data needs attention, so we keep privacy questions close to the account help path. Tell us whether you need a copy, correction, deletion request or explanation of a cookie or payment record. Include the email or phone detail attached to your account, but do not send a password or full wallet credentials. We will use the account step needed to confirm that the request comes from you before discussing private records.

Team online

Account request

Use the account help path when you want to ask how your phone verification, sign-in record or profile detail is used. We may ask you to confirm an account identifier before discussing the request, so private details are not disclosed to another person.

Wallet question

For a DANA, OVO, GoPay or QRIS privacy question, share the payment reference and approximate date rather than a wallet password. We can explain why a receipt or status check was retained without asking you to place sensitive credentials in a support message.

Cookie request

If a mobile browser keeps a cookie you would rather remove, tell us the device path and browser session involved. We can explain the setting, the effect on sign-in preferences and the account checks that may still apply after cookie removal.

DATA HANDLING

What We Keep And Why

Privacy works best when each record has a clear reason, so our policy separates account operation from payment reconciliation and security checks.

Account details

We use your account and phone details to create the right sign-in path, complete phone verification and connect your account activity to the requested service. Keeping these records accurate helps us respond to a data request without confusing your profile with another account.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference can help us match a receipt with the correct account. Our policy treats that reference as a transaction record, not as permission to view your wallet password or unrelated financial details.

Cookies

Cookies can remember a sign-in preference, language setting or device session so the privacy controls you select remain understandable. You can manage cookies through your browser, although removing them may require another account check when you return to the lobby.

Account security

Phone verification and sign-in records help us examine unusual account access. We may retain relevant security events for the period needed to investigate or protect an account, and we will not ask you to place a password in a privacy request.

Retention

We keep account, payment and security records only for the operational, legal or dispute-handling reason described in this policy. When a record no longer serves that reason, our retention process can remove it or separate it from direct account identification.

Changes and contact

You can ask us to correct account data, explain a processing purpose or address a deletion request through the account help path. We may verify your identity first, then confirm what we changed, what must remain and why the policy requires it.

Privacy Policy Answers For Indonesia

These Privacy Policy answers focus on the searches you may make before opening an ink66 account or asking about an existing record. We cover the data connected to sign-in, phone verification, mobile cookies, local wallet references and requests for correction or removal. If a question depends on your location or eligibility, the answer remains subject to local law.

The ink66 Privacy Policy covers account details, phone verification, sign-in and device records, cookies, support requests, payment references and security events. It explains why we use each category, how long it may remain connected to your account and how you can ask about it.

DANA and QRIS can create payment references that help us match a receipt or status check to your account. Our Privacy Policy explains that we use those references for reconciliation and account protection, not to request or store your wallet password.

Yes. Send a correction request through the account help path and identify the profile detail that needs attention. We may ask you to confirm the phone or account detail attached to the profile, then we will explain the result of the request.

The Privacy Policy treats mobile cookies as session and preference records. They can help remember sign-in settings or browser choices, while your browser controls whether they remain. Removing cookies may lead to another phone or account check when you return.

You can ask about deletion through the account help path. We first verify the requester and identify the records involved. Some account, payment or security details may need to remain for an operational, legal or dispute-handling reason described in the Privacy Policy.

Yes. OVO and GoPay status checks can produce a reference used to confirm whether an account payment request was received. Our Privacy Policy limits that use to the relevant payment and security purpose, without treating the reference as access to your wallet.

Use the account help path and state whether your request concerns access, correction, deletion, cookies or a payment reference. Include only the account detail needed to locate the record. We may verify your identity before sharing private account or security details.

Related Pages

ink66 Indonesia FAQ Access guide Account information ularnagaslot