Reference

tayo4d Privacy Policy For Your Account

Our Privacy Policy explains what tayo4d collects when you open an account, use the mobile lobby, contact support, or check a wallet status.

Account detailsDevice securityWallet recordsAccess requests
tayo4d tayo4d Privacy Policy For Your Account
CONTACT PATHS

Where To Ask About Your Privacy Policy

A clear contact path helps you ask what we hold, why we use it, or how to correct an account detail. Start from the support area after signing in, then include the phone number linked to your account and the relevant wallet reference when your question concerns DANA, QRIS, OVO, or GoPay. We use those details to locate the right record without asking you to send a full password or secret code.

Team online

Account data request

Use the signed-in support path to ask for a copy of account details linked to your phone verification. We may ask you to confirm the account step before releasing personal records, so the request reaches the correct account.

Wallet record question

For a DANA, OVO, GoPay, or QRIS question, include the transaction reference and status shown in your cashier history. We use that reference to check the payment record while avoiding unnecessary wallet credentials.

Correction request

If your phone number, name, or account detail needs correction, contact support through the account help area. Tell us which field is wrong and why; we may request phone verification before making a change.

DATA PRACTICES

Six Privacy Checks Inside tayo4d

Our handling process follows the journey of an account rather than treating every visit alike.

Account creation

When you open an account, we record the details needed to create your login and complete phone verification. This lets us connect your account activity with the correct profile instead of relying on a shared device name or an incomplete sign-in.

Device signals

A mobile browser may provide device and session signals such as browser type, login time, and security events. We use these details to identify unusual access and keep the phone-to-account path clear when you move from login to the lobby.

Cookie choices

Cookies can keep a session active, remember basic page settings, and help us understand whether an account page loads correctly. You can manage cookie controls in your browser, although restricting them may affect login continuity or saved preferences.

Wallet matching

Payment records are matched to the account using references from DANA, OVO, GoPay, QRIS, bank transfer, or virtual account steps. We use the match to show a status and investigate a receipt question without storing your wallet password.

Retention period

We retain account, security, and transaction records only for as long as needed for the stated service, dispute handling, security checks, and legal duties. When a record is no longer needed, we remove it or keep it in a form that does not identify you.

Policy changes

If this Privacy Policy changes in a way that affects how account or device data is used, we will place the updated wording on this page. Check the policy before opening a new account or continuing after a material change.

Privacy Policy Answers For tayo4d

These Privacy Policy answers cover the questions we expect before you open an account or send a data request. They explain the practical route for account access, mobile sessions, wallet references, cookies, and corrections. If your situation is not covered, use the signed-in support path and identify the account step or transaction reference involved.

It covers account details, phone verification, login and device signals, cookies, support messages, and records connected with DANA, OVO, GoPay, QRIS, bank transfer, or virtual account activity. It also explains retention, correction requests, security handling, and how access depends on local law.

We use your phone number to create and protect the account, complete the required verification step, and help support locate the right record. It can also help us identify unusual login activity. Do not send a password or private wallet code in a support message.

Yes. The policy covers browser type, session events, login time, and related device signals when you use the mobile path. These details help maintain account security and diagnose access issues, whether you open the lobby from a phone in Denpasar or from a desktop.

We use the transaction reference, status, and related account details needed to match a QRIS or DANA action with your account. The same approach applies to OVO, GoPay, bank transfer, and virtual account records. We do not need your wallet password for this check.

Yes. Contact us through the signed-in account help path and state whether you want a copy, correction, or explanation of a record. Include the relevant phone number or transaction reference, but not a password. We may verify account ownership before responding.

We keep personal data for the period needed to provide account access, investigate disputes, protect the service, and meet legal duties. Retention can differ by record type. When the purpose ends, we delete the record or remove identifying details where practical.

Yes. Where local law permits, you can ask how an access decision relates to the data held on your account. Send the request through support with the account step or message involved. We will explain the applicable process without asking for unnecessary wallet credentials.