Reference

99luck99 Privacy Policy Explained Clearly

Our Privacy Policy explains what 99luck99 collects when you open an account, sign in, use DANA or QRIS, and contact our support team.

Account dataWallet recordsCookie choicesAccess requests
99luck99 99luck99 Privacy Policy Explained Clearly
CONTACT ROUTES

Three Ways To Ask About Privacy

A clear contact route helps you control the details held under your account. Send a privacy request through our support contact path and include the account phone number or email used for sign-in, without sending a password or wallet PIN. We may ask for an account step to confirm that the request comes from you. This process applies whether your question concerns a QRIS receipt, a device record or a support conversation.

Team online

Account request

Ask us to access, correct or clarify personal details linked to your 99luck99 account. Include your sign-in contact so we can locate the right record and may request phone verification before discussing account-specific data.

Wallet record

For DANA, OVO, GoPay or QRIS references, send the transaction date, amount reference and account contact. We use those details to trace a status without asking you to disclose a wallet password or private wallet messages.

Security concern

If a device, sign-in or support message looks unfamiliar, contact us through the account help route and change your password from your account settings. We can check access records and explain the next verification step.

HANDLING DETAILS

Six Practical Privacy Safeguards

We keep this policy practical by tying each data use to an account action you recognise.

Account creation

When you open an account, we collect the contact details needed for sign-in and phone verification. We use them to connect your account activity to the correct record and to respond when you ask for access or correction.

Payment matching

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match a deposit status to your account. We do not need your wallet PIN, full wallet conversation or unrelated wallet activity for that check.

Cookie control

Cookies can keep a session active, remember basic choices and help us identify technical errors. You can clear or restrict cookies in your browser settings, although sign-in steps may appear again after that change.

Device records

We may record browser type, device signals, access time and related logs to detect unusual sign-ins. A phone and desktop can therefore create separate session records, helping us investigate account access that you do not recognise.

Retention choices

We keep personal records for account operation, security checks, support handling or legal duties for as long as that purpose requires. When a record is no longer needed, we remove it or make it unsuitable for direct identification.

Change requests

You can ask us to correct account details, explain a data use or provide available account records. Send the request through support with your sign-in contact; we may verify ownership before making a change or sharing details.

Privacy Policy Answers For Your Account

These answers address the searches we receive about account data, wallet references, cookies and access requests. They are written for Indonesian customers using the account on a phone or desktop. If your situation is not covered, contact support with your account contact and the specific record you want us to check.

The 99luck99 Privacy Policy covers account details, phone verification records, device and browser logs, cookies, support messages and payment references. It explains why we use each type of data, how we protect account access and how you can request a correction or available copy.

Yes. The Privacy Policy covers transaction references and status details connected with DANA, QRIS, OVO, GoPay, bank transfer and virtual account use. We use those records to match payment status to your account, not to access your wallet PIN or unrelated wallet content.

You can contact our support route to ask what account data is available and how it is used. Include the phone number or email used for sign-in. We may complete phone verification before discussing records, and the request process depends on local law.

We may use browser type, device signals, access time and session logs to maintain sign-in security and investigate unusual access. Phone and desktop sessions can produce different records. These details help us check an account concern without reading unrelated content on your device.

Yes, send a correction request through support and identify the account contact connected to the record. Tell us which detail is wrong and what it should say. We may verify ownership first, then explain whether the change can be made under local requirements.

We retain account, support, security and payment-reference records only while they serve an operational, security or legal purpose. After that need ends, we remove or anonymise them under our handling process, subject to retention duties that depend on local law.

Use our support contact path and describe the concern without sending your password, wallet PIN or full payment credentials. Include the account contact, approximate access time and device type if known. We can then check session records and explain the next account step.