Reference

tanjung 899 Privacy Policy

tanjung 899 Privacy Policy explains what we collect when you open an account, sign in, use Speed Blackjack or check wallet status through DANA and QRIS.

Clear data purposesCookie choicesAccount access rightsContact steps
tanjung 899 tanjung 899 Privacy Policy
PRIVACY CONTACTS

Get Help With A Data Request

A clear contact path matters when your account data needs attention. Use the support link shown inside your account area and describe the Privacy Policy request in plain English, including the sign-in detail we can use to locate your record. We may ask for an account confirmation before discussing personal data. For a wallet question, include the relevant DANA, OVO, GoPay or QRIS reference without sending your password or full security code.

Team online

Account access check

If you cannot open the account area, use the support route displayed on the sign-in page. Tell us whether the issue concerns a data copy, correction or deletion request, and we will first confirm that the request comes from the account owner.

Wallet record query

For a Privacy Policy question involving DANA, OVO, GoPay or QRIS, share the transaction reference and date rather than private wallet credentials. We can then match the record to the correct account and explain the data purpose connected with that event.

Policy clarification

When a sentence in this policy is unclear, contact us through the account support channel and quote the relevant heading. We will respond about data use, cookies, retention or access eligibility, which depends on local law.

DATA CONTROL ROOM

Six Practical Privacy Safeguards

Privacy work is tied to ordinary account actions, so we describe the controls in practical terms.

Data collection

We may collect your name, contact detail, account credentials, verification result, device information and activity records. These details support sign-in, security checks, wallet matching and support replies; we do not ask for unrelated personal details just to browse this policy.

Cookie controls

Cookies can keep a sign-in session active, remember a language choice and help identify repeated security events. You can adjust cookie settings in your browser, although disabling required cookies may prevent account access or remove session continuity on a phone.

Account security

Keep your password private and complete phone verification before account access when requested. We may compare device and sign-in signals when activity looks unusual. Never send a password, one-time code or wallet PIN through the support channel.

Record retention

We keep account, security and payment records only for the period needed for service operation, dispute handling, fraud checks or legal duties. When a record is no longer needed, it is removed, anonymised or placed beyond routine account access.

Your requests

You can ask for access to your personal data, correction of an inaccurate detail, an explanation of a processing purpose or deletion where applicable. We may request account confirmation first, and some records may remain when a legal or security duty applies.

Policy changes

If our data practices change, we update this Privacy Policy and show the revised date or notice where practical. Check this page before changing account details or connecting a wallet, especially when access is discussed for Indonesia.

Privacy Policy Questions From Indonesia

These Privacy Policy answers focus on the questions you may have before opening an account or linking a local wallet. We keep the wording direct: your data request should identify the account, your payment query should name the relevant rail, and any access decision depends on local law. If your question is not covered, use the support route displayed in the account area.

The Privacy Policy covers account details, phone verification, device signals, cookies, game activity records, wallet references and support messages. It also explains why we use those details, how we restrict access, how retention works and how you can request a copy or correction.

Phone verification helps confirm that the person requesting account access controls the contact detail attached to the account. It can also help us respond safely to a data request. We do not ask you to send the verification code to support.

Yes. The Privacy Policy covers payment references created when you use DANA, OVO, GoPay or QRIS. We use a reference, amount and time marker to match a transaction event with the correct account, while wallet credentials remain with the relevant payment service.

You can request access to personal data connected with your account through the support path shown after sign-in. Include the account contact detail and state that you want a data copy. We confirm ownership first and explain any record that cannot be released.

Use the account settings path when the field is editable. If a verification detail or payment record cannot be changed there, contact support and identify the inaccurate field. We may request account confirmation before updating it, and transaction history may require a separate explanation.

Retention depends on the type of record and the reason it was created. Sign-in, security, support and payment records may be kept for service, dispute or legal needs. When the reason ends, we remove, anonymise or restrict the record under our retention process.

Access eligibility depends on local law and the checks applied to your account location. This Privacy Policy does not change those requirements. If access is unavailable, contact support through the displayed account route to ask how your data request can still be handled.