LEGAL REFERENCE

How taxi4d Handles Your Account Data

This is the taxi4d privacy policy — the document that tells you exactly what we collect when you open an account, why we hold it, and how long...

Plain EnglishIndonesia ScopeAccount DataWallet PrivacyLast Updated
taxi4d How taxi4d Handles Your Account Data

Policy Posture and Jurisdiction Scope

Service availability is jurisdiction-dependent. Users are responsible for checking local law before access.

HELP CHANNELS

Privacy Contact Paths

If you need to raise a data question, exercise your rights, or flag something unusual on your account, these are the channels...

Privacy Inbox Send data access, correction or deletion requests to...
In-App Chat Open the chat bubble from your account menu...
Data Officer For formal complaints or regulator-facing correspondence, our designated...
REVIEW SIGNALS

How We Review This Policy

Quarterly Review

Our legal and product leads sit down every quarter to read the policy line by line, checking that what we wrote still matches how the taxi4d account flow and lobby actually behave today.

Indonesian Counsel

We brief Indonesian privacy counsel before any material change ships, so the wording you read reflects current local interpretation rather than a generic template lifted from another market.

Processor Audits

Every payment and analytics processor that touches DANA, OVO, GoPay or QRIS data is audited against our data-processing agreement, and the list of sub-processors is refreshed on this page.

Engineering Sign-Off

No clause goes live until our engineering lead confirms the described data flow matches production. If code and policy disagree, we hold the release and fix the gap first.

Version History

Each revision carries a date stamp and a short note describing what moved. You can ask our privacy desk for the previous wording if you signed up under an earlier version.

Reader Feedback

When account holders flag a confusing sentence, we log it and rewrite in the next cycle. The policy improves because you tell us where the language gets in the way.

Consistency Across Our Policy Pages

Terms of Service
Definitions used here — account, wallet, session, device — match the Terms of Service word for word so there is no drift between the two documents.
Cookie Notice
Tracking technologies are summarised in this policy and detailed in the cookie notice; both files share the same category labels and retention windows.
AML Statement
Identity verification data referenced here lines up with the checks described in our AML statement, including how long we keep KYC artefacts on file.
Payments Policy
References to DANA, OVO, GoPay and QRIS handling appear identically in the payments policy, so settlement language never contradicts privacy language.
Security Notice
Encryption, storage location and breach-response timing stated here match the security notice, keeping technical and legal pages in step.
Complaints Policy
The contact ladder for privacy complaints mirrors the general complaints policy, with the same acknowledgement and resolution windows applied.
Account Closure
Deletion and retention clauses in this policy match the account-closure flow described in our help centre, including what survives after closure.

What This Policy Page Includes

Scope Section

A clear opening that names which taxi4d services the policy covers, written so you can confirm in one read whether your account activity falls inside the document.

Data Categories

A labelled breakdown of identity, transactional and device data, with examples drawn from the real account flow rather than abstract legal categories that leave you guessing.

Retention Table

Plain rows showing how long each data class stays on file, tied to the Indonesian financial record-keeping periods we operate under and reviewed every quarter.

Your Rights

A short, readable rights section covering access, correction, export and deletion, with the exact contact path you should use for each request type.

Sub-Processor List

The third parties that handle slices of your data are named, grouped by purpose, and refreshed when we add or retire a vendor in the taxi4d stack.

Change Log

A dated history of revisions sits at the foot of the page so you can see what shifted between the version you signed up under and the one live today.

Privacy Policy Questions

At sign-up we collect your name, contact details and the identity fields required for verification. Once you fund the wallet, we add transaction records tied to DANA, OVO, GoPay or QRIS, plus device signals used for security.

Payment processors receive only what they need to settle each transaction. We do not pass DANA, OVO, GoPay or QRIS details to marketing partners, and we never sell account data to third parties under this policy.

Retention follows Indonesian financial record-keeping periods. Identity and transaction records sit on file for the statutory window, while device signals used for fraud checks roll off on a shorter schedule defined in the retention table.

Yes. Send a deletion request through the privacy inbox or in-app chat. We honour it for everything outside the statutory retention window, and we tell you exactly which records must remain and why.

Account and transactional data sits in infrastructure aligned with our supported regions across Indonesia. Storage locations and the providers behind them are listed in the sub-processor section and refreshed when the stack changes.

Material changes are announced on the account dashboard before they take effect, and the change log at the foot of this page records every revision date alongside a short note describing what moved.

Address formal complaints to our data officer through the contact path listed in the support section. We acknowledge within two business days and reply substantively inside the window set by Indonesian privacy rules.