What data minimisation means for fulfillment
GDPR asks you to keep only the data you need. Most fulfillment stacks keep everything.
May 6, 20261 min read
The principle
Article 5 of the GDPR says personal data must be "adequate, relevant and limited to what is necessary" for the purpose it was collected for. In plain terms: collect what you need, use it for that, and do not keep it longer than you have to.
For a store, the purpose of a shipping address is delivery. That is the whole purpose. This post is not legal advice.
Where fulfillment falls short
In a typical setup, the address that was needed for one label ends up in many places:
| System | Why it has the address | Kept for |
|---|---|---|
| Store database | Order record | Forever, by default |
| 3PL warehouse system | Pick, pack and ship | Contract term, often longer |
| Packing slip | Printed with every order | Until the box is thrown away |
| Support tool | Synced for context | Until someone deletes it |
| Analytics export | Joined with order data | Unknown |
Only one row in that table is needed to deliver the parcel: the label.
How Cirdan maps to the principle
- Limited to what is necessary. The warehouse works with tokens. It never receives the address in readable form.
- Purpose limitation. The address is decrypted for one purpose, printing the label, and nothing else can do it.
- Storage limitation. The address is deleted when the carrier confirms delivery.
What it does not replace
Encryption is not a legal basis, a privacy notice or a data processing agreement. You still need all three. What it changes is the size of the problem those documents describe.