Reference

tekno88 Privacy Policy For Indonesia

Our Privacy Policy explains how tekno88 handles the account, device and wallet details connected with your access.

Account dataWallet recordsDevice sessionsPolicy access
tekno88 tekno88 Privacy Policy For Indonesia
CONTACT PATH

Where Privacy Questions Reach Our Team

A privacy question should reach the same support route that helps with a stalled login or wallet status. Sign in, open the account help area, and send a message with the email or phone number linked to your account; do not include a wallet password or full payment credentials. If you cannot sign in, use the support contact shown on the access page and describe the issue without sending sensitive material. We use the details you provide only to locate the relevant request and respond to your policy concern.

Team online

Account help

Use the account support chat when you want to ask how your phone number, login record or verification detail is used. Include the request type and your registered contact route so we can locate the correct account without asking you to share a password.

Wallet status

For a DANA, OVO, GoPay or QRIS privacy query, send the transaction reference and date rather than a wallet PIN. Our support route can connect the payment event to your account record while keeping secret wallet credentials out of the message.

Policy request

If you want a copy, correction or removal request considered, state the exact account detail involved and use your registered contact route. We may ask for a verification step before changing or releasing personal data linked to your account.

SECURITY PRACTICE

What We Do With Your Account Data

Privacy depends on practical handling at each account step, from phone verification to the mobile session that opens the lobby.

Account records

We may hold your name or contact details, phone verification result, login history and account preferences.

Payment references

A cashier event may carry a DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference.

Cookies and devices

Our browser session may store cookies or device signals that keep you signed in, remember a security choice or help…

Account security

Phone verification, session checks and account contact matching help us reduce unauthorised access.

Retention period

We keep account, payment and support records only for as long as needed for the stated purpose, account security, dispute…

Your requests

You can ask us to access, correct or delete personal data, or ask why a detail is being used.

Privacy Policy Answers For Your Account

These Privacy Policy answers focus on the account actions you are most likely to check before opening access. We cover wallet references, phone verification, cookies, device sessions, deletion requests and the support path for Indonesia. If your situation involves eligibility or account access, the outcome depends on local law. For a case-specific response, use the contact route shown in the support section and write from your registered account contact where possible.

It covers personal data connected with your account, phone verification, device sessions, cookies, support messages and payment references. It also explains why we use those records, how we protect them, how retention works and how you can request access, correction or deletion.

Yes. When DANA or QRIS is used, we may receive a transaction reference, amount, time and status needed to match the event with your account. We do not need your wallet PIN, and you should not include it in a support message.

Phone verification helps us connect an account to the correct contact route and check ownership before an access or data-change request. The result can be stored as an account security record. Your access remains subject to local law.

Send a request through account support using the phone number or email linked to your profile. Name the record you want copied or corrected, such as a contact detail or payment reference. We may complete an ownership check before responding.

You can request deletion through the support contact route. We will assess the request against account security, dispute handling and legal retention duties. If some records must remain, we will explain the reason and remove identifying links where practical.

Cookies or similar storage can maintain your login session, remember a security choice and help diagnose access errors. Clearing them may sign you out or remove a saved setting. Your mobile browser controls whether stored site data remains on the device.

Sign in and use the account help route, or use the support contact displayed on the access page if login is unavailable. Describe the privacy concern and provide your registered contact route, but leave out passwords, wallet PINs and complete bank credentials.