Reference

ts138 Privacy Policy for Your Account

Our Privacy Policy explains what we collect when you open a ts138 account, sign in from mobile or desktop, and use DANA, OVO, GoPay or QRIS.

Account dataWallet recordsDevice controlsPolicy requests
ts138 ts138 Privacy Policy for Your Account
REQUEST A CHECK

Get Privacy Policy Help Through Your Account

A clear account route helps when you need to ask about a Privacy Policy matter. Sign in, open the account support path, and include the email or phone detail linked to your profile plus the relevant payment reference. We use that information to locate the correct record, while a request about DANA, OVO, GoPay or QRIS can be checked against the matching transaction status.

Team online

Data access request

Ask which account, device or payment records we hold about you. Include your registered contact detail so we can check identity before sending a response through the account support path.

Correction request

If your contact detail or account record is inaccurate, tell us what needs changing and why. We may compare the request with your account step and related wallet reference before updating it.

Privacy concern

For a concern about cookies, sign-in security or a DANA, OVO, GoPay or QRIS record, send the relevant date and reference. We will route the request for a focused policy check.

SIX CONTROL POINTS

How We Apply This Privacy Policy

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

Data handling

We use contact, verification and access details to maintain your account and protect sign-in activity. Payment references from DANA, OVO, GoPay, QRIS, bank transfer or virtual account are used for reconciliation.

Cookies and signals

Cookies and similar device signals help keep a session working, remember selected settings and identify unusual access. You can manage browser cookie controls, though some account steps may then need to be repeated.

Account security

Before account access, we may check contact or verification details and compare device events with recent sign-in activity. This helps us investigate an unfamiliar session without exposing wallet credentials.

Retention

We retain account, support and payment records only for the period needed for service administration, dispute handling, security checks or legal duties that apply to the relevant record.

Change requests

You can request a correction to your profile or ask how a record is used. Include your registered contact detail and the exact field or transaction reference so we can assess the request.

Contact route

Use the account support path for Privacy Policy questions rather than sending wallet passwords or full payment credentials. A DANA, OVO, GoPay or QRIS reference is enough to locate a status check.

Privacy Policy Answers For ts138 Accounts

These Privacy Policy answers address the searches we hear most often before an account is opened. They explain the records connected with sign-in, mobile use, local payment references and policy requests, while access remains subject to local requirements. If your case is not covered, use the account support path with the smallest useful set of details.

The ts138 Privacy Policy covers contact details, verification information, sign-in events, device signals and support records supplied or created during account use. We use them for access, security, service administration and applicable legal duties.

Yes. The Privacy Policy covers payment references and status data connected with DANA, OVO, GoPay, QRIS, bank transfer and virtual account steps. We use those references to match activity, not to request wallet passwords.

Sign in, open the account support path and ask for a data access check. Include the contact detail linked to your profile. We may verify account ownership before explaining the records associated with you.

You can request a correction for an inaccurate contact or account field. State the existing detail, the proposed change and your registered contact route. We may compare it with verification records before making an update.

Cookies and device signals may support sessions, settings and unusual-access checks on mobile browsers and desktop browsers. Browser controls can restrict them, but you may need to repeat an account step or sign in again.

We retain payment and account records for the period needed for reconciliation, support, security, disputes or legal duties that apply. A retention question can be sent through the account support path with its reference.

Use the account support path and label the request as a Privacy Policy concern. Mention whether it relates to sign-in, cookies, retention or a payment reference; do not include wallet passwords or full credentials.