Reference

Privacy Policy for Your ltd66 Account

Our Privacy Policy explains how ltd66 handles the details connected with your account, including phone verification, wallet activity and access from your device.

Clear data purposesWallet record contextAccount access choicesPolicy contact path
Browse Home Lobby Read FAQ
ltd66 Privacy Policy for Your ltd66 Account
CONTACT ROUTES

Ask About Your Privacy Policy

A direct request is the quickest way to resolve a question about the Privacy Policy or the data connected with your account.

Account data request Ask us to identify the personal data linked to your ltd66 account and explain why it is held. For account matching, we may request your registered phone number and a recent sign-in detail, but never your password or one-time security code.
Wallet record question If a DANA, OVO, GoPay or QRIS record looks unfamiliar, send the receipt reference and approximate transaction time through our account help path. We use those details to check the account record without asking you to disclose an unnecessary wallet password.
Correction or removal You can contact us when a profile detail needs correction or when you want to ask whether removal is available. We first verify the request, then explain any account, security or legal reason that requires a particular record to remain.
DATA PRACTICE

How ltd66 Handles Account Data

Privacy work is part of the account path, from the first phone check to a later wallet-status question.

Phone verification

Phone verification connects the account to a contact route we can use for access checks. If your number changes, contact us before trying repeated sign-ins. We may compare account details with the verification record to reduce mistaken access to your data.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create references such as amount, time and status. We use these records to trace a receipt or payment state, while wallet credentials remain outside the message you send us.

Cookies and sessions

Cookies and session markers help us remember an active sign-in and protect the route between your device and account. You can clear browser data, but doing so may sign you out and require phone verification again before account access returns.

Device security

We may record device and browser signals around login, failed access attempts and session changes. These signals help us investigate unusual activity. If you see an unfamiliar session, change your account password and contact support without sharing the replacement password.

Retention choices

We keep account and payment records only while they serve an account, security, dispute or legal purpose. When a record no longer has a valid purpose, we remove it or separate it from direct account identifiers where that process is available.

Request handling

A Privacy Policy request should state the action you want, such as access, correction or removal. We verify ownership, assess the request under applicable local rules and reply with the next step, including any reason a record cannot yet be changed.

Privacy Policy Questions About ltd66

These answers address the Privacy Policy questions that usually arise before account access or after a wallet-status check. We keep the wording practical so you know what to send, what may be retained and when local rules affect a request. If your case involves a specific account record, use the contact route rather than posting personal details in an open channel.

The ltd66 Privacy Policy covers account details, phone verification, login and device signals, support messages, cookies, and payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains why we use those records and how you can ask about them.

Yes. The Privacy Policy explains that we may use payment references, receipt details, timestamps and status values to match activity with your account or investigate a question. We do not need your wallet password for that check, so do not include it in a support message.

Contact our account help route and state that you want access to the data linked with your ltd66 account. Include your registered phone number and enough recent account context for ownership checks. We may ask for further verification before releasing personal data.

You can request a correction when a profile or account detail is inaccurate. Explain which field is wrong and provide the updated value through support. We verify the request first, then confirm whether the change can be made under the Privacy Policy and local rules.

We retain payment records while they are needed for account administration, security checks, disputes or a legal purpose. A DANA receipt, QRIS reference or bank-transfer record may therefore remain after the related account step. We remove or separate records when that purpose ends.

You may ask whether deletion is available for a particular record or account detail. Where local law permits, we assess the request after verifying ownership. Some records may need to remain for security, dispute handling or another valid legal purpose, and we will explain that outcome.

Yes. Account access and any related data request depend on local law and are handled where local law permits. If your location or account status limits access, support can explain the available route without asking you to bypass a regional restriction.

Related Pages

ltd66 Indonesia Komodo Gold Reels FAQ Access guide Account information