Reference

taysen Privacy Policy For Your Account

The taysen Privacy Policy explains what we collect when you open an account, verify your phone, enter the lobby, or use DANA, OVO, GoPay and QRIS.

Clear collection rulesWallet record contextPhone access controlsCookie choices
taysen taysen Privacy Policy For Your Account
HELP WITH PRIVACY

Ask About Data Beside Your Account

A direct support route helps you ask what a record means before you request a change. From your signed-in account, use the account help path beside the cashier area and describe the phone, device, wallet reference or cookie concern involved. We may ask for account details to confirm that the request comes from you, but we will not ask you to send a wallet password. This process applies whether your question follows QRIS use or a lobby session.

Team online

Account help route

Use the signed-in account help path beside the cashier area for Privacy Policy questions. Include the relevant date, phone number ending or payment reference so we can locate the correct record without asking you to repeat unrelated account details.

Wallet record check

If a DANA, OVO, GoPay or QRIS reference looks unfamiliar, send its visible reference and time through account help. We compare it with our account record and explain the status without requesting your wallet password or full wallet login details.

Access request

For a copy, correction or eligible removal request, tell us which data category you mean and which account step created it. We first confirm account ownership, then explain what can be changed and what must remain for a stated legal or dispute reason.

DATA HANDLING

How We Protect Your Policy Rights

Privacy choices work best when each account action has a clear data reason. We separate sign-in checks from wallet references, keep cookie controls available in the browser path, and use session signals…

Account details

We use your phone number and verification result to create and protect your account access. If you change a permitted detail, we may retain the earlier value in a restricted history so we can trace an access dispute or explain a previous account action.

Payment references

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account reference helps us match an account event. We keep the reference needed for reconciliation and support, while treating wallet credentials as outside the details we request from you.

Cookies and sessions

Cookies can remember a session choice and help the account path load correctly. You can manage browser cookie settings, though removing essential cookies may sign you out or prevent the phone verification step from working until they are allowed.

Device signals

We may read device type, browser version, access time and security signals when you sign in. These details help us compare a mobile session with a desktop session and flag unusual access; they are not used to read private files on your device.

Retention decisions

We keep records for the period needed for account operation, payment matching, dispute handling or a legal duty. When a category no longer needs retention, we remove it or separate it from direct account details according to our internal process.

Requesting changes

Ask for access, correction or eligible removal through account help, naming the exact category and account step. We verify your identity before responding, explain any limit clearly, and use the same route if you need to ask why a request was declined.

Privacy Policy Answers For taysen

These Privacy Policy answers focus on the searches we hear most often from Indonesian account holders. They explain phone verification, wallet references, cookies, device access, retention and request handling without turning the policy into a general lobby description. If your question concerns a specific account event, include its date and visible reference through the account help route.

We use your phone number to open and protect your account and to complete the clear verification step before access. We do not treat phone verification as permission to view unrelated device content. Ask through account help if the number on your account needs correction.

No. We may keep a payment reference, amount context and processing time needed to match DANA, OVO, GoPay, QRIS, bank transfer or virtual account activity. We do not ask you to send a wallet password, and you should not include one in a support request.

Cookies help remember a session and browser choice, including the path from sign-in to the lobby. You can manage them in your browser. Removing essential cookies may sign you out or interrupt phone verification, so the account path may not work until required cookies are enabled.

Yes, you can request access to eligible account details through the signed-in account help route. Name the category and the account step involved, such as phone verification or a QRIS reference. We confirm account ownership first and explain any record that cannot be supplied.

The period depends on why the record exists. We keep details for account operation, payment matching, dispute handling or a legal duty, then remove them or separate them from direct account details when that reason ends. Support can explain the category-specific basis for a retention decision.

You can ask us to correct an eligible phone, account or contact detail through account help. Include the inaccurate value and the correct value, but not a wallet password. We verify your request, update the record where permitted, and tell you if a history record must remain.

Yes. We may process device type, browser version, access time and security signals on mobile or desktop to protect your session. We do not read private files. If you switch devices while using the lobby, those signals can help us investigate an unusual account access event.