Reference

Open tigelon Privacy Policy Clearly

tigelon Privacy Policy explains what we collect when you open an account, verify your phone and use DANA, OVO, GoPay or QRIS.

Clear collection purposesWallet record controlsPhone access security
Explore Our Lobby Read FAQ
tigelon Open tigelon Privacy Policy Clearly
CONTACT PATHS

Find Privacy Help Near Wallet Support

A clear contact route matters when you want to ask about the Privacy Policy or correct an account record.

Policy questions Use the account help path for questions about Privacy Policy wording, collected account details or the reason a particular record is needed. Include your registered contact detail so we can match the request to your account without requesting your password.
Wallet record request For a DANA, OVO, GoPay or QRIS record, provide the payment reference and approximate date rather than sharing a PIN. We can use that operational detail to check which account record the request concerns and explain the next privacy step.
Login access concern If phone verification or a sign-in session appears unusual, contact account help before opening another account. Tell us the device path you used, such as mobile browser or desktop browser, so we can assess the access event.
DATA PRACTICE

Explore How tigelon Handles Your Records

We keep the Privacy Policy practical by linking each data category to an account action. Account details support sign-in and phone verification; device and session signals help us review unusual access; payment…

Account details

We use the contact details you submit to create and protect your account, complete phone verification and respond to a privacy request. If a detail changes, ask through account help so the record and future contact route stay aligned.

Device and sessions

When you sign in from a mobile browser or desktop browser, we may record session and device signals linked to security checks. These signals help us examine unfamiliar access without treating the device itself as your identity.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can create reference data. We use the reference, amount status and timing to match a receipt or investigate a missing account update, not to request your wallet PIN.

Cookies and storage

Browser cookies or similar storage can keep a session active, remember a selected setting or support security checks. You can manage browser storage through your device settings, although clearing it may require you to sign in again.

Retention choices

We retain records for the account, security, payment reconciliation or support purpose that requires them, subject to applicable rules. A retention question should identify the account detail or payment reference involved so we can assess it precisely.

Changes and requests

You can ask for access to account data, correction of an inaccurate detail, clarification of a collection purpose or a deletion assessment through account help. We may verify your account contact before changing records or disclosing account data.

Browse Privacy Policy Questions

These Privacy Policy answers address the account and wallet questions you are most likely to raise before opening access. They explain what to prepare, where a request starts and how local payment references fit into data handling. If your situation is not covered, use the signed-in account help path and describe the exact record or access event.

The tigelon Privacy Policy covers account details, phone verification, sign-in sessions, device signals, cookies, support messages and payment references. It applies when you use the site through a mobile or desktop browser, with access and eligibility depending on local law.

We use phone verification to confirm the contact route attached to your account and help protect sign-in access. If you want to ask about that record or correct it, start through account help using the phone or email already connected to your account.

DANA and QRIS can create payment references showing a receipt status, timing and account match. We use those details to reconcile an account update or investigate a stalled wallet status. Do not send a wallet PIN when asking about a payment record.

You can request access to account data through the signed-in account help path. State which category you mean, such as phone verification, device session or payment reference. We may verify your registered contact before discussing or releasing account-linked records.

Send a correction request through account help and identify the inaccurate field, such as an email, phone detail or account reference. We may ask for account verification before making a change, so another person cannot alter your account record.

Retention depends on why the record exists, such as account security, payment reconciliation or a support request, together with applicable local rules. Ask through account help with the relevant DANA, OVO, GoPay, QRIS or bank reference for a specific assessment.

Use account help to ask which cookie or device signal relates to your session. You can also manage browser storage in your mobile or desktop settings. Clearing cookies may end the session and require phone verification or sign-in again.

Related Pages

tigelon Indonesia FAQ La Liga Over Under Access guide Account information