Traceability data security: what a supplier must guarantee
Who can see your data, where it is hosted, what happens in the event of a breach — the security guarantees to check before entrusting your traceability to a third-party tool, in non-technical language.

Entrusting your traceability to a third-party tool means entrusting it with data that is sometimes sensitive — production volumes, customers, suppliers, sometimes strategic commercial information. This guide sets out, in non-technical language, what a tool supplier should guarantee, without requiring IT security skills to ask the right questions.

Where the data is hosted
The hosting location determines which legal framework applies to data protection. Hosting within the European Union offers, by default, the guarantees of the GDPR; hosting outside the EU may require specific contractual clauses to offer an equivalent level of protection. The question to ask: where, precisely, is the data stored, and under which legal regime?
Who can access the data, and how that is controlled
- Access control within your own business — a good tool lets you restrict who, within the organisation, sees which data (an employee does not necessarily need to see all of the commercial data).
- Access by the vendor's employees — an often-overlooked point: who, at the tool supplier, can view customers' data, and in what circumstances (technical support, maintenance)?
- Sharing with third parties — is the data sold on, shared with commercial partners, or used for purposes other than the service provided?
The 72-hour deadline, and what it means for your contract
The figure to remember above all others. In the event of a personal data breach, the controller notifies the supervisory authority — in France, the CNIL (the French data protection authority) — without undue delay and, where feasible, not later than 72 hours after having become aware of it (Article 33 of the GDPR). After that deadline, the notification must be accompanied by the reasons for the delay. Without a legitimate reason, the failure is liable to a fine of up to €10 million or 2% of turnover.
Two practical consequences, rarely drawn:
- The deadline runs from when YOU become aware, not from the incident. Hence the importance of the alert deadline you impose contractually on your supplier: it determines whether you have 70 hours left to act, or 2.
- Notification can be provided in phases. The GDPR accepts that you will not have all the information within 72 hours. Waiting until you have understood everything before notifying is therefore a mistake: you notify what you know, then you add to it.
Encryption: what it actually protects
Data encryption protects against unauthorised access in the event of an intrusion or theft — but its effectiveness depends on its scope. Encryption "at rest" (stored data) protects differently from encryption "in transit" (data exchanged between systems). A serious tool covers both, and you do not need to understand the technical details to ask for confirmation that this is the case.
What happens in the event of a breach
A security incident can happen to any supplier, however serious — the relevant question is not "can it happen" but "what happens if it does":
- Does the supplier commit contractually to notifying its customers in the event of a breach, and within what deadline? This is not a matter of convenience: Article 33 of the GDPR requires the controller to notify the breach to the CNIL without undue delay and, where feasible, not later than 72 hours after having become aware of it. If your supplier takes a week to warn you, your own deadline has already passed — it is you, not them, who is in breach.
- Is there a documented incident response plan, not just a verbal promise?
- Do the backups allow rapid restoration in the event of data loss or corruption?
Common mistakes
- Never asking where the data is located before signing, when that determines the applicable legal framework.
- Relying on a marketing claim ("secure", "encrypted") without checking its exact scope.
- Ignoring internal access by the vendor's employees by focusing solely on the risk of external intrusion.
Checklist
- Ask for the precise location where the data is hosted.
- Check access control within your own organisation.
- Ask which of the supplier's employees can access the data, and under what conditions.
- Check that there is a contractual commitment to notification in the event of a breach.
- Check the frequency and reliability of backups.
Sources
- Notifier une violation de données personnelles (Notifying a personal data breach) and Violations de données personnelles : les règles à suivre (Personal data breaches: the rules to follow), CNIL — 72-hour deadline, phased notification, reasons for delay.
Verified 17 August 2026.
Hvad det betyder for dig
Den samme tankegang udspiller sig forskelligt, afhængigt af hvor du står i kæden.
Du er producent
Your traceability data often includes commercially sensitive information (volumes, customers, prices) — this guide gives the questions to ask without needing any technical IT security skills.
VeraTrace til producenter →Du forarbejder, du er et brand
Uncontrolled access to your data by a third-party vendor’s employees poses a risk distinct from a technical breach — the section on access control covers this often-overlooked point.
VeraTrace til forarbejdningsvirksomheder →Du er distributør eller indkøbscentral
Requiring traceability from your suppliers means trusting them on the security of their own tools — this guide, written from the user’s side, also helps assess what a supplier should be able to guarantee.
VeraTrace til detailhandlen →