Reference

tayo4d Privacy Policy For Clear Account Access

Our Privacy Policy explains how tayo4d handles your account details, wallet records and device signals when you open the lobby in Indonesia.

Account dataWallet recordsCookie choicesAccess requests
tayo4d tayo4d Privacy Policy For Clear Account Access
CONTACT YOUR WAY

Get Policy Help Beside Account Support

A clear contact path matters when a wallet reference or account detail needs checking. If you have a Privacy Policy question, use the support route shown in your account area and include the email or phone detail linked to your profile. We can then locate the relevant record without asking you to send a full wallet password or security code.

Team online

Policy questions

Ask how we collect, use or retain a particular account detail through the support path displayed in your account area.

Wallet record check

Share the DANA, OVO, GoPay or QRIS reference and its status, while keeping your wallet PIN and one-time code private.

Change request

Request a correction or access copy using your verified account contact so we can match the request to the right profile.

CONTROL YOUR DETAILS

See What We Keep And Why

We handle this policy area through defined account and device checks rather than broad collection.

Account details

We use your registration and verified phone details to open the correct account, respond to requests and prevent another person…

Wallet references

DANA, OVO, GoPay, QRIS, bank transfer and virtual account references help us match a status check without storing your wallet…

Cookies

Cookies can keep sign-in preferences and policy choices available on your browser; you can adjust cookie controls through your device…

Device security

We may record device type, browser details, IP address and sign-in events to identify unusual sessions and protect account access.

Retention

We keep records for the period needed for account service, security checks or legal duties, then remove or anonymise them…

Your requests

Contact us through the account support route to ask for access, correction or a privacy explanation; use your verified contact…

Privacy Policy Questions Before Account Access

These answers address the Privacy Policy points you are most likely to check before opening an account. They cover wallet records, cookies, device checks, retention and the practical route for requesting changes.

It covers account and phone verification details, wallet references, device and browser signals, cookies, support requests, security events, retention and requests to access or correct your records.

Yes. We may handle a DANA or QRIS reference, status, amount and time to match account activity. The same approach can apply to OVO, GoPay, bank transfer and virtual account records.

Device type, browser settings, IP address and sign-in events help us recognise unusual access, connect your session to the right account and investigate a security concern without requesting your wallet PIN.

You can ask for access through the support route shown in your account area. Include your verified phone or email detail so we can match the request and explain any lawful restriction.

Send a correction request through account support and identify the record that appears wrong. We may ask for a verified account detail before changing registration or wallet-related data.

Retention varies by the reason for collection. We keep data while it supports account service, security or a legal duty, then remove or anonymise it when that need ends.

Use the support path connected to your account and write the Privacy Policy topic clearly. We can explain collection, cookies, retention or a requested change after verifying your account contact.