FADP vs UK GDPR
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 2 of 9 topics. Each verdict names what it rests on; read the wording before relying on it.
- FADP Asks more on 0 topics Alone on 1 topic More detailed on 0 topics
- UK GDPR Asks more on 0 topics Alone on 1 topic More detailed on 0 topics
| Topic | FADP | UK GDPR | Verdict |
|---|---|---|---|
| Protection | |||
| Data security | FADP: 1 | UK GDPR: 1 | Both cover itread the wording below |
| Third parties and supply chain | |||
| Contract requirements | FADP: – | UK GDPR: 1 | Only UK GDPRno specific requirement on the other side in the acts covered |
| Privacy and data protection | |||
| Lawful processing | FADP: 1 | UK GDPR: 2 | Both cover itread the wording below |
| Transparency | FADP: 1 | UK GDPR: 1 | Both cover itread the wording below |
| Rights of individuals | FADP: 1 | UK GDPR: 1 | Both cover itread the wording below |
| Privacy by design and by default | FADP: 1 | UK GDPR: – | Only FADPno specific requirement on the other side in the acts covered |
| Impact assessment | FADP: 1 | UK GDPR: 1 | Both cover itread the wording below |
| Records of processing | FADP: 1 | UK GDPR: 1 | Both cover itread the wording below |
| International transfers | FADP: 1 | UK GDPR: 1 | Both cover itread the wording below |
What This Covers
The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.
Included
- FADP Federal Act on Data Protection of 25 September 2020, SR 235.1; Data Protection Ordinance, SR 235.11
Status
Reviewed against the official texts.
Included
- UK GDPR Regulation (EU) 2016/679 as it forms part of UK law; Data Protection Act 2018 (c. 12); Data (Use and Access) Act 2025 (c. 18)
Status
Reviewed against the official texts.
Protection
Data security
Both cover it read the wording below
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12
Data security
Security appropriate to the risk.
Security
Appropriate technical and organisational security, tested regularly.
Third parties and supply chain
Contract requirements
Only UK GDPR no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20
Nothing in the acts covered.
Processors
Contracts with processors setting out their duties.
Privacy and data protection
Lawful processing
Both cover it read the wording below
NIST Privacy Framework CT.PO-P
Principles
Lawful, good faith, proportionate processing for purposes that are recognisable, with accurate data kept only as long as needed.
Principles and accountability
Process personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. lawfully, fairly and transparently, for specified purposes, minimised, accurate, kept no longer than needed and secure, and be able to show it.
Lawful bases
Each processing has a lawful basis, including the recognised legitimate interestsA UK GDPR lawful basis for using personal information when this is necessary for a specified public-interest purpose listed in Annex 1. The purposes include safeguarding, emergencies, crime prevention, national security and certain disclosures supporting public tasks. Organisations must meet the relevant conditions and show that the use is necessary. Under ordinary legitimate interests, they must also check whether the affected person's interests, rights or freedoms outweigh their own interests. That additional check is not required for recognised legitimate interests. Other data protection duties still apply. added in 2025.
Transparency
Both cover it read the wording below
NIST Privacy Framework CM.AW-P
Duty to inform
Inform people when collecting their data, including about automated individual decisions.
Transparency
Tell people what you do with their data, when you collect it.
Rights of individuals
Both cover it read the wording below
NIST Privacy Framework CT.DM-P
Rights of the people concerned
Access, delivery or transfer of data, and the right to have data corrected or deleted.
Individuals' rights
Access, rectification, erasure, restriction, portability, objection and rights on automated decisions, answered within a month.
Privacy by design and by default
Only FADP no specific requirement on the other side in the acts covered
NIST Privacy Framework CT.DP-P
Privacy by design and by default
Technical and organisational measures built in from the start, with data-protection-friendly defaults.
Nothing in the acts covered.
Impact assessment
Both cover it read the wording below
NIST Privacy Framework ID.RA-P
Impact assessments
A data protection impact assessmentAn assessment of the impact of planned processing on the protection of personal data, carried out before processing that is likely to result in a high risk to people's rights and freedoms. Article 35 of the GDPR makes it mandatory in those cases. for processing likely to lead to a high risk.
Impact assessments
A data protection impact assessmentAn assessment of the impact of planned processing on the protection of personal data, carried out before processing that is likely to result in a high risk to people's rights and freedoms. Article 35 of the GDPR makes it mandatory in those cases. before high-risk processing.
Records of processing
Both cover it read the wording below
NIST Privacy Framework ID.IM-P
Records of processing
A record of processing activities, with an exemption for smaller companies.
Records of processing
A record of processing activitiesA written inventory of an organisation's activities involving personal data, used to understand and demonstrate how that information is handled. Under Article 30 of the EU GDPR and UK GDPR, controllers and processors have different record requirements. A controller's record covers matters such as purposes, data and recipient categories, retention and security; a processor's record focuses on processing performed for its clients., with limited exemptions for small organisations.
International transfers
Both cover it read the wording below
Transfers abroad
Transfers to countries on the Federal Council's list, under appropriate safeguards, or under exceptions.
International transfers
Transfers outside the UK under adequacy regulationsUK Adequacy Regulations, appropriate safeguards such as the International Data Transfer Agreement, or exceptions.
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.