Reference

teo288 Privacy Policy And Your Account

teo288 Privacy Policy explains how we collect, use and protect the details you provide when opening an account or contacting us.

Clear data purposesPhone verificationWallet activity recordsCookie choices
teo288 teo288 Privacy Policy And Your Account
CONTACT PATHS

Privacy Policy Help Near Account Support

A clear contact route helps you act on the Privacy Policy without guessing where to send a request. Use the account support path when you need to ask about stored details, a phone verification record or a wallet status linked to your account. Include your registered contact detail and the subject of your request, but do not send a wallet password or full payment credentials. We may ask you to confirm ownership before discussing private account data.

Team online

Account request

Use our account support path for a copy request, correction request or question about the personal details held with your teo288 account. We compare the request with your registered contact detail before sharing account-specific material.

Payment privacy

For a DANA, OVO, GoPay or QRIS question, provide the transaction reference, date and wallet name. We use those details to trace status without asking you to disclose a wallet PIN, password or complete payment credential.

Security concern

If you notice an unfamiliar login, device session or phone verification event, contact account support promptly and describe what you saw. We can check the related access record and explain the next account-security step.

DATA PRACTICES

What We Keep And Why It Matters

We handle Privacy Policy requests through practical account controls rather than broad promises.

Account details

We use your registered contact detail and verification status to provide account access and identify the correct person when you…

Device sessions

A mobile browser or desktop session may create technical records such as device type, browser signals and login time.

Cookie settings

Cookies can keep your session connected and help us measure whether a policy page loads correctly.

Payment records

A deposit or withdrawal record may include a rail name, reference, amount, status and time.

Retention checks

We keep selected records for the period needed to address account security, payment disputes, technical faults or legal requests that…

Your requests

You can ask what personal data we hold, request a correction, ask about deletion eligibility or question a processing purpose.

Privacy Policy Questions About teo288

These Privacy Policy answers address the account and device questions you may have before opening access. We keep each answer tied to a real process, from phone verification and cookies to DANA, OVO, GoPay and QRIS records. If your situation is specific, contact account support with your registered contact detail and the relevant reference.

The teo288 Privacy Policy covers account details, phone verification, device session data, cookies, support messages and payment references. It explains why we use each category, how long selected records may remain, and how you can ask about access, correction or deletion where local law permits.

We do not need your wallet password to match a transaction. Our payment record may contain the selected rail, reference, status, timestamp and account connection for DANA, OVO, GoPay or QRIS. Never send a wallet PIN or password in a support message.

Phone verification helps us connect an account request to the person who created the account and reduces confusion when access or wallet status needs checking. The verification result can be retained as an account-security record, subject to the retention rules in our Privacy Policy.

Yes. Send a correction request through account support and identify the account detail that needs changing. We may ask you to confirm account ownership before making the change. If a record must remain for a payment or security reason, we will explain that limitation.

Cookies may keep your session active or help us see whether a Privacy Policy page loads correctly. Your browser controls can remove or block them. Some account access steps may appear again after removal, because the browser no longer retains the related session setting.

Retention depends on the reason for holding a record, such as account security, payment matching, dispute handling or a legal request that applies where you are located. We do not describe one fixed period for every record; support can explain the category relevant to your request.

Use the account support path and state whether you want access, correction, deletion eligibility or an explanation of processing. Include your registered contact detail and any relevant payment reference, but exclude passwords and wallet PINs. We may verify ownership before giving account-specific details.