Documents

Personal data processing

The main reader of this page is a fleet owner deciding whether to trust us with their drivers' data. So this is not a retelling of the law but a description of what actually happens to the data: where it is stored, who sees it, when it leaves Kazakhstan, and which of that is recorded.

Who is who here

Driver and staff data is entered by the fleet, and the fleet controls it: it decides whom to add and what to record. We — Evgeniy Achin, hello@fleetau.com — process this data on the fleet's instructions: we store it, show it to those entitled to see it, and use it to calculate rent. No legal entity is registered yet, and we do not hide that behind wording: its details will appear here together with it.

Your own data — the email and fleet name given at registration — you hand to us directly. It is processed under the personal data legislation of the Republic of Kazakhstan.

What data and why

What we do not collect: there is no geolocation and no telematics — the product works without equipment in the vehicle. Extra data is extra liability, so the service has few required fields.

Driver: name, phone, and, if they wish, email; the terms of the rental agreement and the trail of their confirmation — the time, network address, and device from which the driver confirmed the terms, together with a snapshot of what was shown to them. This trail is what a balance due rests on in a dispute, so it is recorded at the moment of confirmation and is never created retroactively.
Document expiry dates: the expiry date of the driving licence. The expiry summary contains neither a name nor a document number: the fleet needs the answer "may the vehicle be handed over", not a copy of the licence.
Inspection photos: photos of the vehicle at handover and return. They are evidence of the vehicle's condition in a money dispute, so they are kept for at least 24 months.
Traffic fines: the ruling number, the date and time of the violation, the amount and, if the fleet attached it, a scan of the ruling. Who was driving at that moment the system determines from the rental journal — no new data about the driver is needed for that.
Fleet staff and partners: name, sign-in contact, and role. A partner sees their vehicle's income but not the fleet's people.
Fleet: email and name; the fleet's legal entities — for the cash desk. A BIN and a legal address are not required at registration.

Where the data is stored

Databases and files are in the Kazakhstan region of Yandex Cloud. Inspection photos and document scans are in the object storage of the same region. By default the data does not leave the Republic of Kazakhstan; the single exception is described below, and it works only with your explicit consent.

Who sees what

Partner who owns a vehicle: does not see the driver's personal data. The driver is shown anonymized — "Yerlan T., rating 4.8, since 12 May": no phone, no full name, no documents. This is not a setting that can be flipped by accident: such fields simply do not exist in the data sent to the partner workspace.
Driver: does not see the vehicle's owner or the fleet's economics — not the income, not the size of the payouts, not the owner's contacts.
Neighboring fleet: sees nothing. Fleets are isolated; a driver working in two fleets is two independent records. The platform does not link them to each other and builds no cross-fleet profile of a person.
We: see the data only as far as needed for the service to work and to help you in support. We do not sell it, do not pass it to advertising networks, and do not build profiles on it.

Consents: recorded so they can be produced

A consent in fleeTau is not a checkbox. What is recorded is who consented, when, and to exactly which text: the record is stored together with the edition number of the text and its cryptographic fingerprint. The text is kept by the server, not by a page in the browser, so signing one text and producing another is impossible.

A consent can be revoked at any moment in the same section of the workspace where it was given. A revoked consent is not erased — it remains as history: a consent that cannot be shown for a past period legally does not exist, and it is precisely the past period people ask about.

The consent check is closed by default. No record, a mismatched text fingerprint, a revoked consent, an unavailable check — in all these cases the answer is "no", and the action is not performed. The opposite order would mean processing data by default, and we do not allow that.

When data leaves Kazakhstan

The only such case today is the automatic recognition of traffic fine ruling scans: a copy of the image goes to a third-party recognition service for the duration of processing. This happens only with the fleet's explicit consent; without consent, fines are entered manually, and that is the only consequence of refusing.

Every transfer is written to the journal before the first byte leaves: to whom it was sent, the file's fingerprint, which person triggered it, on what basis — with the date and edition of the consent at the moment of transfer — and how it ended, including failures. The document itself is not stored in the journal: the transfer journal must not become a second store of the very data it protects.

Image storage meanwhile remains in Kazakhstan — what leaves the country is a copy for the duration of recognition. The number of transfers per fleet is capped by a daily limit, and it is counted from the same journal, not by a separate counter.

Cards and money

Card data does not pass through our services. Wherever card payment appears, the card is entered on the payment provider's page, and only tokens reach us. The danger is not only in storage: data that has once passed through a process with logs is already a problem, so we do not let it pass through.

Drivers' rental payments do not reach our accounts: the driver pays the fleet, the fleet records the payment.

How long we keep data and what we delete

Inspection photos — at least 24 months: they are evidence in money disputes, and deleting them earlier means leaving the fleet without protection.

Money records are never erased or rewritten: the ledger is built so that a retroactive edit cannot be made unnoticed. The same goes for the cross-border transfer journal and the consent history — these are evidence, and their meaning lies in their immutability.

Everything else is deleted on request. Driver data is entered by the fleet — so the first request goes to it; if the question is for us, write to hello@fleetau.com. We will delete what we are not obliged to keep as evidence, and for the rest we will say honestly what remains and why.

Status of this document

This page was written by the operator of the service — so it can be read and understood, not signed unread. Every statement here matches what the service actually does and is edited together with it.

The document acquires legal force after review by a lawyer. Until then it remains an accurate description of the data processing, and in the event of any discrepancy, a direct agreement between us and you takes priority.

Edition of 13 August 2026. Questions about data — hello@fleetau.com.

Questions

What people usually ask

Where is the data physically stored?

In the Kazakhstan region of Yandex Cloud — both the databases and the photos. By default the data does not leave Kazakhstan. The single exception is the recognition of traffic fine ruling scans, and it works only with the fleet's explicit consent, with every transfer written to the journal before it is even sent.

Does a partner see the driver's phone number?

No. The partner sees the vehicle and its income, and the driver — anonymized: "Yerlan T., rating 4.8, since 12 May". There is no phone, no full name, and no documents in the partner workspace — they are not hidden by markup, they are absent from the data that goes there. The client base belongs to the fleet.

Do you delete data on request?

What does not serve as evidence — yes. Money records, the cross-border transfer journal, and the consent history are never erased: their meaning is that they cannot be rewritten. A driver's request goes through their fleet — the fleet entered the data; if the question is for us, write to hello@fleetau.com, and we will answer what we will delete, and what we are obliged to keep and why.

Why do you keep inspection photos for two years?

Handover and return photos are evidence of the vehicle's condition in a dispute about money: damage, deposit, withholdings. A dispute can arise a year after the vehicle is returned, so 24 months is a minimum, not overcaution.