Driveosplatform catalogue

How the data is protected

Sign-in, roles, isolation between companies, audit, documents and a passenger’s rights over their own data — without a technical dictionary.

Taxi work means holding other people’s data: where someone was, when, how much they paid and where they were going. That is not only a matter of regulation — it is what a passenger expects when getting into the vehicle. That is why the rules are built into the system, not left to good will.

Sign-in and session

  • Sign-in issues a short-lived pass and a refresh key; the key changes on every use, so a stolen copy soon stops working.
  • Two-factor sign-in asks for a code beside the password. It is optional and recommended for anyone touching money or data.
  • A password is stored as a fingerprint, not as text — not even we can read it. The owner’s first password is temporary and must be changed.
  • A session is not transferred between devices; signing out on one phone does not sign out another.

Roles: everyone sees their own

RoleWhat they may doWhat they do not see
OWNEREverything in the company, including brand, users and releaseOther companies
DISPATCHERRides, board, map, assignment, fleetPrices, settlement, users
OPERATORPhone bookings and the call centrePrices, settlement, fleet
ACCOUNTANTReports, payments, settlementThe dispatch board
Hiding is not only in the interfaceWhen something is not allowed, it is not merely “not shown” — the server refuses the request even if it is sent directly. That is why rights cannot be bypassed by knowing an address.

Isolation between companies

All companies use the same system, yet none can reach another’s data. The rule is doubled: in the software and in the database itself. Even a mistake in the software stays inside the company.

  • A request for another company’s ride returns “not found” (404), not “not allowed” — because that is data too.
  • An API key belongs to one company; the request has no field that selects a company.
  • Isolation is measured by dedicated checks, not assumptions — an attempt to read another company’s record must fail.

Audit: who changed what

Every change touching money, documents or rights is recorded — with the user, the time and the address it came from. That is not watching people, but the answer to “why is this like this”, which always comes up later.

  • A price change, a module enabled, a receipt issued and a role change are all visible.
  • The record cannot be edited or deleted from the interface.
  • When someone leaves, the account is deactivated, not deleted — otherwise the audit log would lose the name.

Documents and photos

  • Documents (registration, insurance, permits) and driver photos are not in a public area — they are reached only through a protected link valid for a short time.
  • Files have a size limit and a type check, so nothing that is not a document can be uploaded.
  • Deleting a document removes its content too; the database keeps only the trace that it existed.

A passenger’s rights over their own data

  • Data export: the passenger requests a copy of their rides and account data from the app.
  • Account deletion: deletion is irreversible and removes personal data; rides stay in settlement without personal data, because the law requires them.
  • Consent: marketing messages only with consent, which can be withdrawn at any time.
  • The company’s legal texts (terms, privacy) sit on its address and are linked from both apps.