Reference

titik288 Privacy Policy For Your Account

The titik288 Privacy Policy explains what we collect when you open an account, sign in from a mobile device, or use DANA, OVO, GoPay and QRIS.

Clear data purposesWallet activity explainedAccount request pathLocal access wording

Browse Our Lobby Read FAQ

Open The Privacy Policy Before Payments

titik288 Service availability depends on jurisdiction. Users are responsible for checking local law before access.

Our Privacy Policy covers account details, phone verification, device signals, payment references, support messages and technical records created while you use titik288. We collect only what is needed for account operation, payment status checks, security checks and policy administration. A phone number can help us confirm

1
that the person requesting access matches the account record, while a transaction reference helps us trace a wallet or bank transfer question. DANA, OVO, GoPay and QRIS may provide confirmation details that appear beside a payment request. We may also record browser, device and sign-in time
2
data to identify unusual access. Where access or eligibility is discussed, it depends on local law. We keep records for the period needed for these purposes, legal duties and dispute handling, then remove or reduce identifying details when they are no longer needed. You can ask
3
us to explain a record or request a correction through the account support path.

Service availability depends on jurisdiction. Users are responsible for checking local law before access.

REQUEST HELP

Reach Support About Privacy Requests

A direct support route helps you ask about a Privacy Policy matter without sharing sensitive details in a public message.

Account support path Use the support contact displayed after account access and describe your Privacy Policy request in clear English. We may ask for an account identifier or phone confirmation before discussing personal records, so your data is not disclosed to the wrong person.

Payment record question If a DANA, OVO, GoPay or QRIS reference appears incorrect, send the transaction reference through the account support route. We use the reference and account details to check the status without asking you to reveal a PIN or password.

Access and correction For a copy, correction or removal request, tell us which account detail you mean and why it needs attention. We verify the request first, then explain what can be changed, retained or restricted under local requirements.

DATA CARE DETAILS

Explore How We Handle Account Records

Privacy work is connected to the way you sign in, move between the lobby and cashier path, and contact our team.

Account data

We may hold your contact details, phone verification result and account settings so we can identify your profile and keep sign-in records connected to the right account. We do not need your password in a support message.

Cookies and sessions

Cookies or comparable browser storage can preserve a login session, language choice and basic security state. You can manage browser permissions, but blocking necessary storage may require you to sign in again or limit account functions.

Device security

A sign-in may create records such as device type, browser details, approximate network data and time. We use these signals to spot unusual access and may request phone verification before allowing sensitive account changes.

Payment references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account activity can produce reference numbers and status details. We use those records to match a request, investigate a missing status and answer your account question.

Retention choices

We retain records only while they support account operation, security, dispute handling or a legal requirement. When a record no longer serves one of those purposes, we remove it or reduce links to your identity where practical.

Policy changes

If a material Privacy Policy change affects how account or wallet data is handled, we place the updated wording on this policy page. Check the page before opening a new account or sending a new payment request.

Browse Answers About Your Privacy Policy

These Privacy Policy answers address the searches we hear most often from Indonesian account holders. They cover the records created during sign-in, wallet status checks, cookies, correction requests and access questions. If your situation is not listed, use the support contact inside your account and describe the record or event you want us to investigate. We may need to confirm your identity before sharing personal details.

It covers account details, phone verification, device and browser signals, cookies, payment references, support messages, retention and requests about access or correction. It also explains how we use these records to protect account access and check DANA, OVO, GoPay or QRIS status.

Phone verification helps connect the person requesting account access or a sensitive change with the correct account record. It can also help us investigate unusual sign-in activity. We will not ask you to place a password or one-time code in a support message.

Yes. The Privacy Policy covers payment references and status details connected with QRIS, DANA, OVO and GoPay, along with bank transfer or virtual account references. We use these details to trace a request and answer account questions, not to request your wallet PIN.

Open the support contact shown in your account and state whether you want access to a record or correction of a specific detail. Include the account email or phone detail linked to your profile. We verify identity before discussing or changing personal data.

Cookies and similar storage can keep a mobile session active, remember selected settings and support security checks. Your browser can restrict them, but some account functions may require storage. Clearing cookies may sign you out and remove saved session preferences.

We keep personal data for the time needed to operate the account, protect access, resolve disputes or meet a legal requirement. After that period, we remove it or reduce identifying links where practical. You can ask support about the purpose of a retained record.

Yes. Account access and eligibility depend on local law. We apply the policy to records created through permitted access, but local requirements may affect what services are available, what checks are needed and how a request can be handled.

titik288 Privacy Policy For Your Account

Reach Support About Privacy Requests

Explore How We Handle Account Records

Account data

Cookies and sessions

Device security

Payment references

Retention choices

Policy changes

Browse Answers About Your Privacy Policy

01 What does the titik288 Privacy Policy cover?

02 Why does titik288 ask for phone verification?

03 Does the Privacy Policy cover QRIS and wallet data?

04 How can I request a copy or correction of my data?

05 How does the Privacy Policy handle cookies on mobile?

06 How long does titik288 keep personal data?

07 Does access under the Privacy Policy depend on local law?

Related Pages