Reference

tali123 Privacy Policy For Your Account Data

The tali123 Privacy Policy explains what we collect when you open an account, use the mobile browser lobby and move through wallet checks.

Account detailsWallet referencesDevice choicesPolicy access
tali123 tali123 Privacy Policy For Your Account Data
CONTACT PATHS

Get Privacy Policy Help Beside Account Support

A clear contact path matters when you want to ask what data we hold or why a wallet reference appears in your account record.

Account access questions If your phone verification or sign-in record looks wrong, contact us through the policy support route with your account identifier. We first confirm that you control the account, then explain which record needs correction without exposing private details in an open message.
Wallet record checks For a DANA, OVO, GoPay or QRIS reference, send the payment receipt or status detail through the account support path. We use the reference to locate the transaction record, clarify its purpose and avoid asking you to share a wallet password.
Privacy requests You can ask how to access, correct or remove eligible personal data through the same support route. Include the request type and account contact detail; we may ask for another verification step before changing records connected with your account.
DATA HANDLING PRACTICE

How tali123 Handles Device And Account Records

We separate the records needed to operate an account from information used to understand device access and policy security.

Account collection

When you open an account, we collect the details required for account creation and phone verification. We do not need your wallet password for DANA, OVO, GoPay or QRIS. Payment references are used to match account activity, receipt status and related support questions.

Mobile browser signals

On an Android phone, iPhone or computer browser, we may record browser family, operating system, language, approximate session time and security events. These details help us identify unusual access and keep a repeated login from looking like an unknown account request.

Cookie choices

Cookies can keep your session open, remember basic preferences and support security checks. You can manage cookie settings through your browser. Turning some cookies off may remove saved choices or require another account step before the lobby opens.

Security checks

Phone verification connects an account to a confirmed contact route before sensitive access is discussed. We may compare sign-in details with device signals and request an additional check when an account action, receipt query or record request appears unusual.

Retention decisions

We keep account, support and payment-reference records for as long as they are needed for security, reconciliation or legal duties. For example, a BCA or Mandiri transfer reference may remain while a receipt question is being resolved, then follow our removal process.

Change requests

To request access, correction or removal of eligible data, use the policy support route and describe the record involved. We verify the request against your account, explain any restriction, and tell you when a correction or deletion action has been completed.

Privacy Policy Answers For tali123 Accounts

These Privacy Policy answers cover the questions we expect before you open an account or connect an Indonesian wallet. They explain the practical path for account data, device records, cookies, payment references and requests for access. If your question is not covered, use the support route linked beside this policy and include only the account detail needed to identify your request.

The tali123 Privacy Policy covers account details, phone verification, sign-in events, device signals, cookies, support messages and payment references. It also explains how we use, retain, protect and respond to requests involving records connected with DANA, OVO, GoPay, QRIS or bank transfer.

No. Our Privacy Policy does not require us to store your DANA or GoPay wallet password. We may receive a transaction reference, status and related receipt detail so we can match an account request, investigate a missing record or answer a support question.

We collect limited device and browser signals to protect account access and recognise unusual sign-in behaviour. On a mobile browser, this can include operating system, browser family, language and session time. These details support security checks; they are not a copy of your private device content.

Use the support route linked from the Privacy Policy and ask for access to your account data. Include your account contact detail, but do not send a wallet password. We verify that you control the account, locate eligible records and explain any legal or security restriction.

Yes. Send a correction request through the policy support path and identify the inaccurate field, such as a phone detail or account contact. We may ask for phone verification before changing it, then confirm the result or explain why a record must remain unchanged.

We retain records only while they serve account security, payment reconciliation, support handling or legal duties. A QRIS receipt reference or BNI transfer record may remain during a status question. When the purpose ends, we remove or anonymise the record under our retention process.

Yes. Access and eligibility depend on local law. The Privacy Policy explains how we handle data for an account, but it does not override Indonesian requirements or restrictions that may apply to your location, account activity or payment route.