Privacy Policy

Last updated : 2026-11-19

Status of this text

Text to be reviewed by a lawyer before going live.

1. Who is responsible

[Company name], [Address] (“we”) is the controller for the data of our website visitors and of the people who create an account and buy from us. For the data our customers enter about their fleet, drivers and staff, the customer is the controller and we act as its processor under our data processing agreement. You can contact us about privacy at contact@flotalog.com.

2. Data we collect as controller

Account data: name, email address, password (stored only as a hash) or Google sign-in identifier, language and time zone, organization name, country and role. Billing data: company name, address, VAT number and payment history; card details are handled by Stripe and never reach us. Communications: messages you send us.

Website analytics: we use Umami, self-hosted in the European Union, which measures visits without cookies and without building individual profiles. Technical logs, including a salted hash of the IP address, are used for security and rate limiting; IP hashes are deleted after 90 days.

3. Data we process for our customers

Customers enter data about their assets, maintenance and deadlines, and may enter data about people: names of usual drivers, assignment history, person deadlines such as a licence expiry date, and the content entered by drivers through the QR code (optional first name, readings, fuel entries, defects, inspections and photos). Flotalog does not collect location: location metadata is removed from photos in the browser before upload. Drivers are informed by a notice that the customer completes from our template.

4. Purposes and legal bases

We use account and billing data to provide the service and perform our contract, to send service emails such as reminders and account notices, and to meet our accounting and tax obligations. We use analytics and security logs on the basis of our legitimate interest in running a secure and useful website. We do not sell personal data and do not use advertising cookies.

5. Where data is stored

Customer data is stored in the European Union: the database (Cloudflare D1) and the files (Cloudflare R2) are both stored under the EU jurisdiction. Requests are handled on Cloudflare’s global network, so some processing may take place outside the EU while data at rest remains stored in the EU.

6. Subprocessors

We use the following subprocessors. Where data is transferred outside the European Economic Area or the United Kingdom, the transfer is covered by the European Commission’s standard contractual clauses, with the UK addendum where relevant.

7. Retention

Account and customer data are kept as long as the account exists. When an account is closed at the customer’s request, an export is offered and the data is deleted within 30 days, and from backups within 35 days. Invoices are kept for the period required by accounting law. IP hashes are deleted after 90 days.

For driver data, the default periods, which each customer can change, are 3 years for assignments, first names attached to readings and photos, and at least 15 months for defects and inspections. Customers can also anonymize driver first names.

8. Cookies and local storage

We use only cookies needed to keep you signed in and to protect forms against abuse. On the driver QR page, the optional first name is remembered in the phone’s browser storage so it does not have to be typed again; it can be cleared from the browser at any time.

9. Your rights

Under the GDPR and the UK GDPR, you have the right to access, correct and delete your data, to restrict or object to its processing, and to receive it in a portable format. If you are a driver or employee of one of our customers, please contact that organization first, as it is the controller; we will help it answer. You can also lodge a complaint with your data protection authority, such as the Information Commissioner’s Office in the United Kingdom.

10. Security

Data is encrypted in transit, each customer’s data is isolated by organization in every request, QR codes use random tokens stored only as hashes and can be replaced in one click, and access to the service is limited by roles. Security events and actions are logged.