Driver data requests

Which data belongs to a driver

Filodos stores most data against the vehicle, not the driver. A row belongs to a driver when the vehicle was linked to that driver at that time. The assignment history gives these time ranges.

If two drivers were linked to the same vehicle at the same time, the data of that time range belongs to both. An erasure for one driver keeps that range.

Export the data of a driver

1. Open Organization → Data protection and go to Driver data export.
2. Select the driver.
3. Click Download export. Your browser saves a ZIP file.

The ZIP file holds:

• CSV files for the driver, the assignments, trips, events, stops, positions, telemetry summaries, notifications, and the lists of alarm photos and clips.
• The still images in the photos folder, up to 200 MB.
• The video in the video folder, up to 1 GB. One MP4 file for each recording.
• A README.txt file. It lists the time ranges, the row counts, and anything that did not fit.

The file does not hold safety scores or daily totals. These are figures of the vehicle, not of one driver.

Filodos builds the file for your request and keeps no copy. Each export writes a row to the audit log. The row holds counts only.

Erase the data of a driver

An erasure cannot be undone. Download the export first if you need a copy.

1. Open Organization → Data protection and go to Erase driver data.
2. Select the driver.
3. Click Preview erasure. The page shows how many rows and files the erasure removes. Nothing changes yet.
4. Read the list. Check the number of time ranges that stay because another driver shared them.
5. Type the name of the driver in the box.
6. Click Erase for good.

The erasure deletes, for the time ranges of the driver:

• positions, Traccar events, trips, stops, driving events, telemetry, notifications, and alarm photo and clip records;
• still images, video files, and raw telemetry files;
• the safety scores and daily totals of those days.

It also:

• deletes the driver login and the record that the driver read the notice;
• deletes the driver record in Traccar;
• revokes the share links that show the data of the driver;
• clears the stored bodies of webhook deliveries about those times;
• renames the driver in the assignment history to "Erased driver". The time ranges stay, so vehicle totals stay correct.

Rules and limits

• Only administrators can export or erase.
• The erasure keeps a time range that another driver shared on the same vehicle.
• A trip that is still open stays until it closes. Run the erasure again after it closes.
• The erasure does not remove these copies: Traccar frame logs (kept 14 days), backups (kept up to 35 days), and data that your ERP system or a webhook receiver already received.
• Each erasure writes a row to the audit log with counts only. The row does not hold the name of the driver.

For developers: the same functions are available at POST /gdpr/drivers/{id}/export and POST /gdpr/drivers/{id}/erase, with an administrator sign-in token. API keys cannot call them. The erase call takes confirm_name (the driver name) and dry_run (true counts the rows and changes nothing). Error codes: 404 when the driver has no assignment in your organization, 422 when confirm_name is wrong, 403 for a sign-in that is not an administrator.