Reference

Privacy Policy For Your tyara88 Account

tyara88 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or check wallet status through DANA, OVO, GoPay and QRIS.

Account dataCookie choicesWallet recordsAccess requests
tyara88 Privacy Policy For Your tyara88 Account
PRIVACY HELP

Where To Ask About Your Data

A clear contact route matters when you need a copy, correction or explanation of personal data held for your account. Use the privacy contact path linked on our site and include the account phone number or email connected to your request. We may ask for account details before acting, so we do not disclose records to the wrong person. When your question concerns a wallet status, mention whether the reference came from DANA, OVO, GoPay, QRIS, bank transfer or a virtual account.

Team online

Privacy contact

Use the privacy contact path on our site for access, correction, deletion or processing questions. Include the account detail needed to locate your record, but do not send a password, one-time code or full payment credential. We may request an account step to confirm that the request is yours.

Account access help

If a sign-in or phone verification step blocks a privacy request, use the account support route connected to the cashier area. Tell us whether the issue appeared on mobile or desktop and identify the related DANA, OVO, GoPay or QRIS reference without sharing secret codes.

Payment record check

For a data question about bank transfer or virtual account activity, send the date, reference label and account contact used at the time. We compare those details with our records before responding, helping separate your request from another account with a similar payment description.

DATA HANDLING

What We Do With Account Records

We keep the Privacy Policy practical by connecting each data use to an account task you can recognise.

Account details

We use the contact and verification details you provide to create, secure and maintain your account. Phone verification can connect a sign-in attempt with the correct account before access is granted. Keep your contact details current so a privacy response reaches the right account holder.

Payment references

A DANA, OVO, GoPay or QRIS reference can show that a wallet event belongs to your account, while bank transfer and virtual account records help us reconcile a matching request. We use these references for account records and support checks, not as a replacement for your secret credentials.

Device activity

When you sign in from a phone, tablet or desktop browser, we may record device and session signals linked to that access. These details help us identify unusual activity and protect account records. They do not give us access to files, photos or other unrelated device content.

Cookies

Cookies can remember a session, language choice or privacy preference so the policy page and account path behave consistently. Browser controls let you remove or restrict them, although some account functions may need a session cookie to recognise your signed-in state.

Retention checks

We review stored account, support and payment-reference records against the reason they were collected. A record may remain while needed for security, dispute handling or a lawful requirement. When that reason ends, we assess deletion or further restriction instead of keeping data without a purpose.

Your requests

You can ask what personal data we hold, request a correction, ask about processing or seek deletion where local law permits. Send the request through our privacy contact path and provide enough account detail for identity checking. We may retain a minimal request record to show how it was handled.

Privacy Policy Questions About tyara88

These Privacy Policy answers address the account and access questions we expect from Indonesian customers before they open an account. They cover the data connected with phone verification, mobile sessions, cookies, wallet references and privacy requests. For a situation that is not covered here, use the privacy contact path and describe the account step or payment reference involved. Access and eligibility depend on local law.

The tyara88 Privacy Policy covers personal data connected with your account, phone verification, sign-in sessions, device signals, cookies, support messages and payment references. It explains why we use those records, how we protect them, how long they may remain stored and how you can request access or correction.

We may collect the account contact details you submit, phone verification results, sign-in activity, device and browser signals, support messages and records linked to account actions. If you use DANA, OVO, GoPay, QRIS, bank transfer or a virtual account, related references may also be recorded.

Yes. The Privacy Policy covers device and session signals created when you sign in from a phone, tablet or desktop browser. We use them to recognise account activity and identify unusual access. We do not use this process to read unrelated files, photos or other private device content.

Use the privacy contact path linked on our site and state that you are making a personal data request. Include the account phone number or email needed to locate your record. We may ask for an account verification step before sharing data, so another person cannot obtain it.

You can ask us to correct inaccurate account data or request deletion where local law permits. Send the request through the privacy contact path with the relevant account detail and a clear description of the change. Some records may remain when needed for security, disputes or a lawful requirement.

Our Privacy Policy treats DANA, OVO, GoPay and QRIS references as payment-related account records. We use them to match a wallet event with the correct account and investigate a status question. We may also handle bank transfer and virtual account references for the same reconciliation purpose.

We keep records while they serve the account, security, support, dispute or legal purpose for which they were collected. Retention depends on the record and applicable requirements. Once the purpose ends, we assess deletion or restriction rather than retaining the data without a current reason.