Reference

Privacy Policy for DANA and QRIS Data

tibet Privacy Policy shows what we collect when you open an account, check wallet status or move from your phone into the lobby.

Account recordsWallet referencesCookie choicesPolicy requests
tibet Privacy Policy for DANA and QRIS Data
HELP WITH PRIVACY

Privacy Policy Help for Account Access

A clear contact path matters when your account record or wallet reference needs checking.

Account access If you cannot reach your account after phone verification, use the account help path and provide the contact detail linked to your profile. We use that step to confirm ownership before discussing data connected with your login.
Wallet status For DANA, OVO, GoPay, QRIS, bank transfer or virtual account questions, send the transaction reference and displayed status through account support. We can then match the record without asking for a wallet password or private security code.
Policy requests To ask for a copy, correction or removal review under the Privacy Policy, contact us through the policy support route from your account. Include the request type and preferred contact detail so we can reply about the next step.
DATA HANDLING

Device Security Inside tibet Privacy Policy

We keep the Privacy Policy practical by describing the points where information enters the service and what happens afterward.

Account details

We use the contact details and verification outcome supplied during account setup to identify your profile and support account access. We do not need your DANA, OVO, GoPay or QRIS wallet password to match a payment record.

Payment references

A payment reference can show the rail used, such as QRIS, DANA or bank transfer, together with status and time. This lets support investigate a receipt or pending state while keeping the request tied to your account.

Device signals

When you move from mobile login into the lobby, we may process browser, device and connection signals for account protection. These signals help us notice unusual access patterns and are not treated as your wallet credentials.

Cookie choices

Cookies can retain session settings and your selected preferences on the device you use. You can manage available cookie choices through the browser controls or the setting shown with our policy notice.

Retention checks

We retain records only while they support the stated account, payment, security or legal purpose, then assess whether they are still needed. A request about a particular record can be sent through policy support for checking.

Correction route

If your account detail is inaccurate, contact us from the linked account and describe the field that needs attention. We may ask for an ownership check before changing or disclosing personal information.

tibet Privacy Policy Questions

These answers cover the searches we hear most often about the Privacy Policy, from wallet records to phone verification and device access. They are written for Indonesian account holders and point you back to the policy support route when a request needs a profile-specific check. Access remains where local law permits.

The tibet Privacy Policy covers account details, phone verification, payment references, device and browser signals, cookies, retention and requests for access or correction. It applies when you open an account, sign in, check wallet status or contact support about a transaction.

No. Our Privacy Policy explains that we use transaction references and displayed status for DANA, OVO, GoPay and QRIS checks. We do not need your wallet password or private security code to match a receipt with your tibet account.

Phone verification links an account to a contact detail before access is provided and helps us investigate an account request safely. We retain the verification result and related account record according to the Privacy Policy, with access depending on local law.

The Privacy Policy mentions browser, device and connection signals used to identify unusual account access. When you move from a mobile login to the lobby, these signals can support security checks. They are separate from DANA, OVO, GoPay and QRIS credentials.

Use the policy support route from your linked account and state whether you want access to a record or a correction. Include the relevant contact detail and account context. We may confirm ownership before sending, changing or discussing personal data.

Our Privacy Policy explains that cookies may retain session settings and selected preferences on your device. You can manage available choices through browser controls or the setting shown with the policy notice, depending on the device and browser you use.

Yes. Contact account support with the displayed transaction reference, rail and status for an OVO, GoPay, DANA, QRIS, bank transfer or virtual account entry. We use those details to locate the record without requesting your wallet password.