Reference

Privacy Policy for Your taxi303 Account

Clear data choices start with knowing what we collect and why. taxi303 uses account, device and wallet details to verify access, record activity and respond when a payment…

Account dataCookie choicesWallet recordsAccess depends on local law
taxi303 Privacy Policy for Your taxi303 Account
CONTACT ROUTES

Privacy Help for Wallet And Login Records

A clear contact path matters when a personal detail or payment reference looks wrong. Start from the policy contact link in our footer, or use the support route shown after you sign in; include your registered phone number and the relevant date, but never send a password or one-time code. For DANA, OVO, GoPay and QRIS questions, the cashier status screen helps us locate the correct transaction record. We respond through the contact route attached to your account.

Team online

Policy contact link

Use the privacy contact link in our footer to ask what personal data we hold, why it is used, or which retention rule applies. Include your account phone number so we can confirm the request without asking you to disclose a password or one-time code.

Signed-in support path

When your request concerns login history, device access or a correction, sign in and open the support path beside your account settings. This lets us connect the request to the right account record and reduces the chance that private details are sent to the wrong person.

Wallet record check

For a DANA, OVO, GoPay or QRIS record, share the date, rail name and transaction reference from the cashier status screen. We use those details to locate the payment entry while keeping your wallet PIN, password and one-time code out of the request.

DATA PRACTICES

How taxi303 Handles Account Data

Our privacy work follows the account steps you actually take: phone verification before account access, device checks during sign-in and a record when a wallet status changes.

Account collection

We collect the phone and verification details needed to create an account and confirm access. If you contact us about a correction, we may ask for account matching details, but we do not need your password or one-time code to locate the request.

Device signals

A sign-in from a new browser or phone can create a security event containing device and session details. We use that signal to assess unusual access and protect your account; it is not a request for the contents of your device.

Cookie controls

Cookies can keep your account session available and remember basic page settings. You can clear them through your browser settings on mobile or desktop. Clearing cookies may sign you out and can remove a saved preference without deleting the account record itself.

Wallet separation

A DANA, OVO, GoPay, QRIS, bank transfer or virtual account entry contains transaction references and status details. We use those fields to match activity, while wallet PINs and banking credentials stay with the payment service or bank handling them.

Retention requests

You can ask how long a particular account, device or payment record is kept. We assess deletion or restriction requests against security, dispute and legal needs, so some entries may remain after an account access request is completed.

Change requests

To correct a phone number, ask about a device event or question a record connected with Jakarta Lucky Slots, contact us through the policy link or signed-in support path. We verify ownership before changing personal data or disclosing account details.

Privacy Policy Questions About taxi303

These answers address the searches we hear most often about the taxi303 Privacy Policy. They cover the data connected with an account, device and wallet record, along with the practical route for asking a question or requesting a change. If your situation involves a legal restriction, access depends on local law.

It covers account details, phone verification, device and browser signals, cookies, support messages and transaction records. A payment entry may identify DANA, OVO, GoPay, QRIS, bank transfer or virtual account status, while activity records can connect to your signed-in account.

No. Our records can contain a payment rail, reference, amount status and date needed for matching, but your DANA, OVO, GoPay or banking PIN is handled by the relevant wallet or bank. Never place a PIN or one-time code in a support request.

Use the privacy contact link in the footer or the signed-in support path near account settings. Give us your registered phone number and a clear request. We verify account ownership first, then explain the data held and any limits under local law.

Yes, you can ask us to correct an inaccurate phone number or clarify a device event. Send the request through the policy contact route, using the registered account details. We may retain the original security event where it is needed for protection or dispute handling.

Cookies can keep a session active and store basic page preferences on your browser. You can clear or block them through mobile or desktop browser settings. After that step, you may need to sign in again, and some account functions may not behave as expected.

Retention varies by the type of record and the reason it was created. DANA, OVO, GoPay, QRIS, bank transfer and virtual account references may remain for security, dispute or legal needs. Ask through the privacy route for the rule affecting your specific record.

Start with the Privacy Policy contact link in our footer, or sign in and use the support path beside account settings. Include the subject of your request, such as access, correction, deletion or cookie choice. Eligibility and access depend on local law.