Fleetorix
Request access

Data processing agreement

This is a courtesy translation. If it differs from the Dutch version, the Dutch version prevails. Read the Dutch version.

Last updated:

Article 1 – Parties and roles

This data processing agreement is an agreement between:

  • Fleetorix, we, us: ABL - The Problem Solver B.V., Sloepkade 64, 2725 EZ Zoetermeer (Chamber of Commerce number 28064282, VAT number NL804652429B01), reachable at privacy@fleetorix.com;
  • the team, you: the organisation that uses Fleetorix.

For the consents that visitors to your domains give, you are the controller and we are the processor. For your clients’ domains, Article 3 applies.

We process that data only on your instructions. Those instructions are the agreement, this data processing agreement and what you set in the dashboard. If the law requires us to do something else, we tell you beforehand, unless the law forbids that. If we believe an instruction infringes the GDPR, we say so straight away.

Article 2 – Relation to the terms and conditions

This data processing agreement is part of the agreement on the use of Fleetorix, as are our terms and conditions. You accept it when you first sign in. Where the processing of personal data is concerned, this data processing agreement takes precedence over the terms and conditions. Words such as domain, banner and consent mean the same here as there.

Article 3 – Your clients’ domains

If you use Fleetorix for your own clients’ domains, for example as an agency, your client is the controller, you are your client’s processor, and we are your sub-processor. This data processing agreement then applies between you and us, in the same way.

You make sure that your agreement with your client allows us to be a sub-processor, and you pass on to your client what they need from us. Everything goes through you: your client has no rights against us, and sends us no instructions, requests or audit questions.

Article 4 – Which data we process

We process data about the visitors to your domains, for one purpose: recording and keeping their choice in the banner, so that you can show they gave consent, and making the banner and your scripts work accordingly.

For each choice a visitor makes, we keep a consent with:

  • the cookie categories the visitor accepted;
  • the version of the banner in force at the time;
  • the hostname of the page on which the choice was made;
  • the time we received the choice;
  • a hashed visitor ID. It is made from a random code the banner stores on the visitor’s device, and isn’t derived from the IP address or a fingerprint of the device.

We also keep a snapshot for each version of your banner: the texts, the categories and the styling at the moment that version started. This lets you show what the visitor agreed to.

Each time the banner fetches its settings or sends a choice, our hosting provider sees the visitor’s IP address and browser details. We process them only in transit: they don’t go into the consent log, and stay in our hosting provider’s log files for at most 2 weeks.

We process no special categories of personal data, such as data about health or religion.

Note: anyone who reads the code on your website can use that code to send us a consent. The consent log therefore shows what came in with a domain’s code. It is no proof that every consent comes from your own website.

Article 5 – Retention and deletion

We keep each consent for 5 years, counted from the time we received it. After that we delete it permanently. That period is the same for all domains and you can’t change it: by using Fleetorix, you give us this period as an instruction. We delete a snapshot of your banner as soon as no consent can belong to it any more; the snapshot of the current version always stays.

We delete earlier in these cases:

  • If you remove a domain, we first offer the download of the consent log as a CSV. After that we delete that domain’s consents and snapshots straight away.
  • If the agreement ends, you have 30 days to download each domain’s consent log as a CSV. 30 days after the agreement ends, we delete all your domains, their banner settings, the consents and the snapshots. From then on, you keep the proof of consent yourself.

What we delete stays in our database’s backups for a short while. It disappears from them by itself, within at most 7 days.

Article 6 – Sub-processors

You authorise us to engage these sub-processors:

PartyWhat forLocationTransfer outside the EU
NeonDatabase: stores the consents and the snapshots of your bannerFrankfurt (Germany)EU-US Data Privacy Framework
VercelHosting: receives visitors’ choicesFrankfurt (Germany). Visitors’ requests pass through Vercel’s global network.EU-US Data Privacy Framework
CloudflareCDN and storage: stores each domain’s banner and delivers it to visitors. In doing so, sees visitors’ IP addresses and browser details.Storage in the EU. Visitors’ requests pass through Cloudflare’s global network.EU-US Data Privacy Framework

Neon, Vercel and Cloudflare are American companies. A US government can therefore in theory request data, even when it is stored in the EU. Neon, Vercel and Cloudflare participate in the EU-US Data Privacy Framework.

We impose on each sub-processor the same data protection obligations as those in this data processing agreement. If a sub-processor fails to meet them, we remain responsible to you.

For signing in, email and payments we also use Google, GitHub, Lettermint, Forward Email and Paddle. They never see your visitors’ consents, and process only the data of your account and your payments. How, is in our privacy policy.

Article 7 – New sub-processors

If we want to add or replace a sub-processor, we tell your team’s administrator by email at least 30 days in advance. If you don’t agree, you can terminate the agreement before the change takes effect. You have no right of veto. What you have already paid is not refunded, except as our refund policy describes.

Article 8 – Security

We secure the data with appropriate technical and organisational measures. In particular:

  • All connections to Fleetorix, and between Fleetorix and its sub-processors, use TLS.
  • The database is stored encrypted.
  • The dashboard shows a user only their own team’s data. Every query in the code is limited to that team.
  • Visitors’ IP addresses don’t go into the consent log, and the visitor ID is a hashed random code (see Article 4).
  • Only people at ABL - The Problem Solver B.V. who need it for their work can access the data. They are bound by confidentiality.
  • Signing in is with a Google account or with a one-time link by email. There are no passwords that can leak.
  • Our database makes backups automatically, so that we can restore data after an outage (see Article 5).

Article 9 – Data breaches

If we discover a breach of the data covered by this data processing agreement, we report it without undue delay, and at the latest within 48 hours of discovering it, by email to your team’s administrator. This gives you enough time to report it to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) within 72 hours, or to pass it on to your client if it concerns a client’s domain.

We tell you what we know at that moment: what happened, which data and how many visitors are affected, what the consequences may be and what we are doing about it. What we learn later, we send on. We don’t report a data breach to the supervisory authority or to visitors ourselves.

Article 10 – Requests from visitors

A visitor can ask you to access, port, correct, restrict or delete their data. We know a visitor only by the hashed visitor ID in the consent log. It comes from the code the banner stores on the visitor’s device. This is how we help you:

  • Access and portability you handle yourself: you find a visitor’s consents in the consent log in the dashboard, and download them as a CSV.
  • Deletion, restriction or correction: email the domain and the hashed visitor ID from the consent log to privacy@fleetorix.com. We carry out your request within 14 days and let you know it is done.

Note: if you delete a visitor’s consents, you can no longer show that this visitor gave consent. Whether that is necessary is your decision.

If a visitor’s request reaches us directly, we forward it to you. We don’t answer it ourselves.

Article 11 – Information and audit

You always have your own proof of consent at hand: each domain’s consent log, which you download as a CSV. Questions about how we process and secure the data, we answer in writing within 30 days.

In addition, at most once a year you may have an audit carried out by an independent expert bound by confidentiality. You tell us at least 30 days in advance. The audit is at your expense. For the database and the hosting, we refer to the certifications and reports of our sub-processors (see Article 6).

Article 12 – Liability

For our liability under this data processing agreement, what the terms and conditions say about it applies. This data processing agreement adds no separate arrangement to that.

Article 13 – Duration and termination

This data processing agreement runs as long as the agreement on the use of Fleetorix runs, and after that until we have deleted all data as Article 5 describes. Our duty of confidentiality continues to apply after that too.

Article 14 – Changes to this data processing agreement

We may change this data processing agreement. We tell you by email at least 30 days in advance. If you don’t agree, you can terminate before the change takes effect. The date at the top shows when the data processing agreement last changed.

Article 15 – Governing law and disputes

This data processing agreement is governed by Dutch law, as are the terms and conditions. Disputes are submitted to the District Court of The Hague.