Reference

Privacy Policy for Your taxi555 Account

Your taxi555 Privacy Policy sets out what we collect when you open an account, verify your phone, browse on a mobile browser or use DANA, OVO, GoPay and…

Account dataCookie choicesWallet recordsPhone verification
taxi555 Privacy Policy for Your taxi555 Account
CONTACT ROUTES

Privacy Help Beside Account Support

A clear contact route helps when a privacy request and a wallet question arrive together.

Account support area Use the support path attached to your account for a Privacy Policy request. Include your verified contact detail and the record you want checked, such as a sign-in event or QRIS status, so we can route the matter accurately.
Wallet status request If your question concerns DANA, OVO or GoPay data, name the payment rail and approximate transaction point rather than sharing a password. We use that reference to separate wallet status records from unrelated account activity.
Access change request Ask us to access, correct or clarify personal data through the available support contact. We may ask for account verification before disclosure, helping prevent a third party from receiving your phone or device records.
DATA PRACTICES

How We Handle Your Account Records

Privacy choices work best when each data path is easy to identify. We separate account details from payment references, use device signals to investigate unusual access, and keep cookie controls close to…

Account data

We use the details needed to create and maintain your account, including contact data and phone verification status. If you ask us to correct a detail, we compare the request with the account record before applying a change.

Cookie controls

Cookies and similar browser storage can remember access preferences or help us understand a session. You can manage browser permissions on your mobile or desktop device, though clearing them may require another sign-in step.

Device signals

A mobile browser or desktop browser may send technical signals such as session details and device type. We use these signals to support account security and investigate access concerns, not to request your wallet password.

Payment references

For DANA, QRIS, bank transfer and virtual account activity, we may retain rail, amount-status and reference details needed to trace a request. Wallet credentials remain with the payment service rather than forming part of our account record.

Security checks

Phone verification helps us connect a privacy request to the right account before we disclose or change data. If a request comes from a new device, we may ask for another account check before proceeding.

Retention requests

We keep records only for the period required for account operation, dispute handling or applicable obligations. You can ask what remains connected to your account, and we will explain available action where local law permits.

Privacy Policy Answers for taxi555

These Privacy Policy answers address the account questions you are most likely to have before opening access or asking us to change a record. They cover phone checks, mobile browsing, cookies, local wallets and requests from Indonesia. If your situation is not listed, use the account support path and describe the specific data concern without sending a password.

It covers account and contact details, phone verification, browser and device signals, cookies, payment references and support requests. It also explains retention, security checks and how to ask for access or correction, with availability depending on local law.

Phone verification helps connect account access and a privacy request to the correct person. It can also reduce the risk of disclosing records to someone using another device. We do not ask you to provide a wallet password during this check.

Yes. The policy covers payment rail, status and reference data connected with DANA, OVO, GoPay and QRIS. It can also cover bank transfer and virtual account references, while wallet credentials remain with the relevant payment service.

A mobile or desktop browser may provide session and device-type signals linked to account access. We use them to support security, troubleshoot sign-in and assess unusual activity. The exact handling and retention of these records depends on local law.

Use the account support path and state whether you want access, correction or clarification. Include the verified contact detail attached to your account and describe the record, such as phone status or a QRIS reference. We may verify identity first.

Yes. Your mobile browser normally provides controls for cookies and similar storage. Removing them can clear preferences and may lead to another sign-in. The Privacy Policy explains why these records may be used and which choices are available where local law permits.

Retention varies by the record, its account purpose, dispute needs and applicable obligations. Payment references may need a different period from browser signals. Ask support which category applies to you, and we will explain available access or change options.