Protection means evidence and privacy together
A useful log helps you remember what happened and prove your own consistency — without creating a honeypot of other people's personal data. That balance is why MyTaxi keeps trips on the device and asks for notes, not identity documents.
Riders gain a record of spend and corridors. Drivers gain operational truth. Both gain a contemporaneous note if a dispute appears days later. None of that requires a social graph.
The minimum viable trip record
Timestamp. Role (rider/driver). Kilometres. Waiting minutes. Total. One sentence note. That is the whole religion. Optional extras: toll flag, weather word, flight number for airport runs. If you add twenty fields, you will stop logging by Thursday.
Consistency beats perfection. A messy note that exists outperforms a beautiful template you never fill.
What not to store
Avoid ID numbers, full card details, home alarm codes, and gossip. If a note would embarrass you on a projector, rewrite it. Local storage reduces breach blast radius; it does not make you immortal to phone theft. Use device passcodes. Clear old trips if you sell a handset.
For company reimbursement, export summaries deliberately rather than forwarding raw logs with unrelated personal trips mixed in.
Habits that make the log trustworthy
Log within five minutes of parking. Do not edit totals weeks later without a reason note. If you correct a mistake, add "corrected because...". Future you is a hostile witness to vague edits.
Weekly, skim for anomalies. Monthly, archive screenshots of totals if you need external records. The tool is the capture layer; your judgment is the archive policy.
How this ties to the product
The map and fare estimate create the numbers. The log captures them. The driver trial exists for people who want that loop as a paid habit. Riders keep the free path. Privacy policy explains the boundaries in plain language.
Award-level here means editorial clarity plus technical restraint: fewer trackers, fewer forced accounts, more useful text in the first HTML response.
Device loss and export discipline
Local-first means a stolen phone can take the log with it. Mitigate with device encryption, a passcode, and periodic exports of non-sensitive summaries to a place you control. You do not need automatic cloud sync of every GPS crumb to achieve backup.
If you change browsers or clear site data, understand you may wipe IndexedDB. Read prompts carefully. Before a big clear, export what you need.
Shared phones and household boundaries
Do not keep detailed trip logs on a shared household profile if privacy matters. Use a separate browser profile or stick to high-level notes. Drivers who share a handset with family should assume relatives can open the browser.
Riders logging late-night trips may prefer minimal notes for the same reason. Protection includes social privacy, not only cybersecurity theatre.
Aligning with the privacy page
Read the privacy policy on this site. It explains what we intend not to collect. A trip log that stays on-device matches that promise. If our practices ever change, the policy should change first — and you should re-evaluate whether the product still fits your threat model.
Good privacy writing is part of award-level product work. So is refusing features that demand surveillance to function.
From private log to personal policy
Write three rules for yourself. Example: I log within five minutes. I do not store other people's ID numbers. I export a monthly spend summary for reimbursement. Stick the rules in a note titled "trip log policy". It sounds formal; it prevents drift.
Review the rules when your life changes — new city, new partner sharing a phone, new kind of corporate client. Privacy is contextual. A policy makes the context explicit.
Technologists love syncing everything. Resist by default. Sync summaries, not intimate trails, unless you have a strong reason and a secured destination. Local-first tools like this one exist so ordinary people can have memory without joining a surveillance product.
If you ever need to show a pattern to a platform support agent, export only the relevant slice. Oversharing creates new risks. Precision is protective.
Teaching teens and first-time riders to log
A simple family practice: after a night ride, the young rider sends themselves a one-line note with amount and suburb pair. It builds money awareness and creates a breadcrumb if something felt off. Keep it light. The goal is literacy, not surveillance of their social life.
Parents should model the same. Hypocrisy kills the habit. Show your own log occasionally. Explain why wait matters. Over time the household argues less about "taxis are so expensive" because the arithmetic is visible.
Why editorial sites still matter here
A trip log without explanation becomes another abandoned app screen. That is why this site pairs the tool with long guides: so the why sits in the first HTML, readable by humans and crawlers, without depending on client-side content injection. Server-rendered guidance plus local-first data is the architecture. Your privacy stays wider when the product does not need your identity to teach you.
One last practical tip
Before you sell or reset a phone, export or screenshot the trips you still need for reimbursement or disputes. Then clear site data deliberately. A local-first product respects you enough to let you leave cleanly — use that door consciously so your protection does not evaporate by accident during a hurried upgrade.
FAQ
Does MyTaxi upload my trips?
Trip data is stored in your browser's IndexedDB on-device. See the privacy page for the full picture.
What fields are enough?
Time, role, kilometres, wait, total, and a short note. More fields die of neglect.
Should I log passenger names?
Prefer minimal data. Corridor and code are often enough. Avoid storing sensitive IDs.