
Privacy by design: what IT sets by default, and why the default is the real decision
Privacy by design is written into data protection law as a duty of the organisation, but in practice IT is the one who fills it in: which fields a form asks for, who can see a folder, how long a mailbox keeps mail and what a sharing link does by default. This article is about that part, the settings, not the legal judgement behind them.
Privacy by design means protection of personal data is built into the system itself, and privacy by default means the default setting is the most restrictive one. Hardly anyone changes a default, so that value is the real decision.
Translated into IT it is concrete: fewer fields, role-based access, sharing links that do not go to everyone, retention periods that technically delete and no live data in test environments.
The duty sits with the controller and the judgement is a legal one. IT provides the settings and the evidence that they are in place; we are not lawyers and not a data protection officer.
What privacy by design means in IT
Article 25 of the GDPR, kept in the UK GDPR, is headed “data protection by design and by default”. It asks the controller to put appropriate technical and organisational measures in place when a processing activity is designed, not after the fact. The law does not list the measures; they have to fit the state of the art, the cost and the risk to the people whose data it is. The ICO’s guidance follows the same line.
For an IT team that is less abstract than it sounds. Every setting is a decision about personal data: a mandatory field, a default sharing permission, a retention period set to “never delete”, an integration that sends every field because that was easier. Privacy by design is the habit of making those decisions deliberately, with the most restrictive option as the starting point.
The duty sits with the organisation that decides on the processing, not with the software vendor. But whoever chooses a system also chooses the settings it allows. A package that cannot switch off fields or cannot truly delete a record makes privacy by design hard for that processing, however good the intentions are.
Privacy by default: the default value is the decision
The second half of Article 25 is the sharpest: by default, only the personal data necessary for the purpose may be processed. That applies to how much you collect, how far you process it, how long you keep it and who can reach it. And data must not be accessible by default to an indefinite number of people.
This is where IT makes the difference, because users rarely change a default. Go through these settings:
- Sharing links. Is the default link type in SharePoint and OneDrive “anyone with the link”, or specific people? One setting, a large effect.
- Form fields. Which fields are mandatory, and why? Date of birth, phone number or address that are “handy” but not needed are off by default.
- Visibility inside the organisation. New teams, groups and folders private by default, not open to the whole organisation.
- Retention. A retention policy on mail, chat and documents, instead of keeping everything forever.
- Telemetry and tracking. Optional diagnostic data and analytics features off where they are not needed.
For every deviation from the most restrictive value, record who decided and why. That is not paperwork: it is the answer to the question that comes later.
Fewer fields, fewer permissions, shorter retention
Most privacy by design measures are not new technology but three habits that come back in every system.
- Fewer fields. What you do not collect cannot leak and does not need protecting. Watch free-text fields in particular: health details, disputes and other sensitive data end up there without anyone designing it that way.
- Fewer permissions. Access by role rather than by person, admin rights separate and time-limited, and a regular review of who still has access. Otherwise someone who moves department takes their old rights along. How to set that up is covered under identity and access management.
- Shorter retention. A retention period that only exists in a policy document keeps nothing for less time. It has to be a setting that actually deletes records, including the copies in exports, log files and backups, with a period that matches the backup.
A fourth belongs with them as soon as anything is tested or analysed: no real personal data where it is not needed. A test environment with a copy of live data is a second live environment with less security.
With a new system: the questions before you buy
Privacy by design starts with choosing the system, because afterwards you can only configure what the package allows. Ask the vendor, preferably in writing and before the contract:
- can fields be switched off or made optional, including in standard forms and reports;
- can a record really be deleted, or is it only hidden, and what happens in the backups;
- can retention periods be set per type of data, so that deletion happens automatically;
- how granular are the roles, and is it logged who viewed which record;
- can data be exported in a usable format, for a subject access request and at the end of the contract;
- what is switched on by default that you have to switch off yourself.
If the system is likely to result in a high risk to individuals, a data protection impact assessment comes with it. What IT contributes to that is in our article on the DPIA for a new IT system; the answers to the questions above make up a large part of it.
An existing environment: where to start
Most organisations do not start with a new system but with an estate that has grown over years. An order that works:
- First the defaults that affect everyone. Sharing links, guest access, visibility of new teams and groups. A handful of settings with the widest reach.
- Then the places where data piles up. Old exports on a network drive, shared mailboxes with no retention, folders with copies of HR files.
- Then test environments and integrations. Which environments run on a copy of live data, and which integrations pass on more fields than the receiving system uses.
- Last, the systems themselves. Per package, check what is on by default, and take it into the next replacement if it cannot be changed.
Change settings with notice. A sharing link that suddenly stops working for a client, or a folder that disappears from someone’s view, generates tickets that undermine the change.
Showing that it is in place
Data protection law does not only ask you to take measures but to be able to demonstrate that you have. For IT that means three things:
- Record what is configured. An export or overview of the relevant settings, with a date. Not a description of how it should be, but of how it is.
- Changes through a fixed route. A setting changed through a ticket or change request, with a reason, can be accounted for later. A setting someone flipped on a Friday afternoon cannot.
- Review regularly. Updates to a cloud service sometimes bring new features with their own defaults. A review every quarter or after each major update stops a new feature quietly being switched on.
If you work with ISO/IEC 27001 you will recognise this: the standard has controls for the protection of personal data and for data masking. A certificate does not make a processing activity compliant, but the habit of recording and reviewing is the same.
Where our work stops
What we do. In the environments we supply, configure or manage, we put in place the settings that make privacy by design real: defaults for sharing and visibility, role-based access, retention policies that technically delete, test environments without live data. We record how things are set, review them regularly and answer the technical questions of your privacy lead or data protection officer. We work under ISO/IEC 27001; that describes how we work, not a judgement on your processing.
What we do not do. We are not lawyers and not a data protection officer. We do not assess whether processing is lawful, which data is necessary for a purpose or which retention period the law requires, and we do not declare that an organisation complies with data protection law. That judgement belongs to the controller, with advice from a privacy lawyer or data protection officer. We configure what follows from it.
Questions we get about this
The five that come up most often.
What is privacy by design?
Privacy by design means the protection of personal data is part of a system or process from the design stage, rather than added afterwards. It is set out in Article 25 of the GDPR and the UK GDPR. In IT it comes down to concrete choices: which fields exist, who can access them, how long data is kept and what is switched on by default.
What is the difference between privacy by design and privacy by default?
Privacy by design is about the design: measures built into the system from the start. Privacy by default is about the default settings: without anyone changing anything, only the data that is needed is processed and it is not openly accessible to everyone. Because users rarely change defaults, the second is often the most important in practice.
Is privacy by design a legal requirement?
Yes, the GDPR and the UK GDPR require the controller to apply data protection by design and by default. The law does not prescribe a fixed list of measures; they must fit the risk, the state of the art and the cost. Which measures are appropriate for your processing is a judgement to make with a privacy lawyer or data protection officer.
Is the software vendor responsible for privacy by design?
The duty sits with the organisation that decides why and how data is processed, not with the software vendor. But by choosing a system you also choose which settings are possible. So ask before you buy whether fields can be switched off, records truly deleted and retention periods configured.
Can you tell us whether we comply with the GDPR?
No. We are not lawyers and not a data protection officer, and we do not give an opinion on whether processing is lawful. What we do is configure and record the settings that follow from your privacy policy, and answer the technical questions of your privacy lead.
Further reading
What privacy by design connects to.
Shall we go through your default settings?
We review the settings for sharing, visibility, permissions and retention in your environment and record how they stand. The legal judgement stays with your privacy lead.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.