Reference

tikus4d Privacy Policy Explained

tikus4d Privacy Policy shows how we collect, use, protect and remove data connected with your account, device and wallet activity.

Account dataWallet recordsCookie choicesPrivacy requests
tikus4d tikus4d Privacy Policy Explained
REQUEST PATHS

Get Privacy Help Near Account Access

A clear request path matters when you want a copy, correction or removal of personal data.

Account request Use the support route inside your account to ask what personal data we hold. We will first match your request with the verified phone detail attached to your account.
Wallet record For a DANA, OVO, GoPay or QRIS query, include the transaction reference and approximate date. We use those details to locate the relevant record without asking for your wallet password.
Access concern If a new phone or browser shows an unfamiliar session, tell support through the account path. We can review the sign-in context and explain the next identity check.
HANDLING DETAILS

How We Handle Your Data

We keep this policy practical by separating account, payment-reference and device records instead of treating every event as the same data.

Account records

When you open an account, we use your submitted contact detail and phone verification status to connect sign-in activity with the correct account and respond to requests about access.

Device signals

A mobile browser, desktop browser or tablet may create session and security signals. These help us recognise unusual access without requiring us to store the full contents of your device.

Cookie choices

Cookies can support sign-in continuity and saved preferences. You can clear or restrict them through browser controls, although some account access steps may then need to be repeated.

Payment references

DANA, OVO, GoPay, QRIS, BCA, BRI, Mandiri and BNI references may appear in service records. We use the reference for matching status, not as a request for your wallet password.

Retention period

We retain records only for the operational, security or legal purpose that requires them. When that purpose ends, data is deleted, anonymised or placed beyond routine account access.

Change requests

Ask us to correct account data, explain its use or remove eligible records through support. We may request phone verification before making a change that affects account security.

Privacy Policy Answers For Your Account

These Privacy Policy answers address the account steps that create the most practical questions: phone verification, mobile sessions, cookies, payment references and requests for access or correction. Read them before opening an account, then contact support if your situation needs a direct response.

The tikus4d Privacy Policy covers account contact details, phone verification, device sessions, cookie choices and payment references connected with DANA, OVO, GoPay, QRIS or bank transfer activity.

We use phone verification to connect the correct person with an account, reduce mistaken access and confirm ownership before discussing records or changing security details. Access depends on local law.

Yes. The Privacy Policy covers relevant browser and device signals created when you sign in on a phone, tablet or desktop, such as session details used to identify unusual access.

We may retain payment references, status details and dates for DANA or QRIS activity so support can match a receipt. We do not need your wallet password for that check.

You can contact support through your account path and request a copy of eligible personal data. We may confirm your phone detail first so records are not disclosed to another person.

Send a correction request through support with the account detail you believe is wrong. After ownership is confirmed, we can explain the change, update eligible records or state why a record must remain.

Retention varies by the record’s purpose, security needs and applicable legal duties. Account, device and payment-reference records are removed, anonymised or restricted when the relevant purpose ends.