Reference

teko4d Privacy Policy For Your Account

Our Privacy Policy explains how teko4d handles the details connected with your account, device, cookies and wallet activity before you open the lobby.

Clear data purposesWallet activity contextAccount access choicesIndonesia policy path
teko4d teko4d Privacy Policy For Your Account
CONTACT ROUTES

Ask About Data Near Your Cashier

A clear contact route matters when your account record or payment reference needs attention.

Account access If phone verification blocks access, contact us through the account help path beside the…
Wallet status For DANA, OVO, GoPay or QRIS questions, share the payment reference and its date…
Policy requests To ask for access, correction or deletion under the Privacy Policy, describe the request…
DATA HANDLING

Explore How We Protect Policy Choices

The Privacy Policy is practical: it connects each data category with an account action you can recognise.

Account details

We use the contact details you submit to create and protect your account, including the clear phone verification step before account access. If your name or phone detail changes, ask us to correct the record through the account support path.

Device signals

A phone or desktop session can create technical information such as browser type, operating system and access time. We use these signals to maintain a usable session and investigate unusual sign-in activity, not to request your device password.

Cookies

Cookies can remember settings that help the Privacy Policy page and account path load consistently. Your browser controls many cookie choices. Removing them may require you to repeat a sign-in or preference step, while the policy still explains the data purpose.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce references, timestamps and status records. We use these details to reconcile a receipt or wallet state; we do not need your wallet PIN to check that request.

Security records

Sign-in, verification and account-change events help us identify when a request may not come from you. Keep your password private and contact us if a device path looks unfamiliar so we can explain the available account-protection step.

Retention requests

We keep information only for the period needed for the stated account, security, payment or legal purpose, subject to applicable requirements. Ask us what remains on your record, why it is retained and whether correction or deletion can be applied.

Browse Privacy Policy Answers For teko4d

These Privacy Policy questions reflect the account decisions you are most likely to make before opening access. We answer them in plain English and keep the examples close to the Indonesian account path, including phone verification, mobile sessions and local wallet references. If your situation is not covered, use the policy contact route with the smallest amount of account detail needed to identify your request.

It covers account details, phone verification, sign-in events, device signals, cookies and payment references linked with DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. It also explains how to ask about access, correction, deletion and the period information remains stored.

We use your phone number for account creation and the verification step required before account access. It helps connect the right person with the right account and lets us investigate a sign-in request. If the number is wrong, contact us through the account support path.

Yes. A mobile or desktop session may create records such as browser type, operating system, access time and security events. We use these details to keep the session working and identify unusual access. Your device password is not needed for this purpose.

The Privacy Policy covers payment references, timestamps and status information linked with DANA and QRIS, as well as OVO, GoPay, bank transfer and virtual account steps. We use those records to trace receipts or status questions, and we do not ask for your wallet PIN.

You can ask what account information we hold, why it is used and whether an inaccurate detail can be corrected. Send the request through the policy contact route and identify your account with the requested verification step. Do not include your password or full wallet credentials.

You may request deletion or ask whether deletion applies to a particular record. We assess the request against the account, security, payment and legal purposes described in the Privacy Policy. Some records may need to remain for an applicable requirement, and we will explain that outcome.

Access and eligibility depend on local law. Where local law permits, the Privacy Policy applies to the account and device activity created through the available service path. If your location or legal position changes, contact us before continuing so we can explain the relevant access position.