
ISO 277017 min read
ISO 27701 and GDPR: how the two relate
ISO 27701 is not a GDPR certificate. It is a privacy management system that helps you organise and prove the work the GDPR requires.
By Fabio Sestito, Managing Director SICE, expert and auditor for ISO 27001, 9001 and 20000-1
ISO 27701 is not a GDPR certificate. It is a management system standard for privacy that helps you organise, document and prove the work the GDPR asks of you.
The two documents do different jobs. The GDPR is a regulation: it says what you must do with personal data and what rights people have. ISO 27701 is a standard: it describes how to build a management system that makes those duties routine instead of a one-off project. A supplier questionnaire from a customer in Germany or France will often ask for evidence of the second, because the first cannot be "certified" by a business itself.
What ISO 27701 requires
ISO 27701:2025 specifies requirements for a privacy information management system, abbreviated PIMS. The official description is on the ISO page for ISO/IEC 27701. The 2025 edition is a standalone standard. Earlier editions were an add-on to ISO 27001, which meant you needed an information security system first. That dependency is gone.
Like other management system standards, it follows the high level structure:
- Clause 4, Context of the organization: which personal data you process, in which role, and which laws apply.
- Clause 5, Leadership: management takes responsibility and assigns privacy roles.
- Clause 6, Planning: you assess privacy risks and set objectives.
- Clause 7, Support: resources, competence, awareness and documented information.
- Clause 8, Operation: the processes that actually handle personal data.
- Clause 9, Performance evaluation: monitoring, internal audit and management review.
- Clause 10, Improvement: handling incidents and nonconformities, and correcting them.
The standard also contains control sets for organisations acting as controllers and for those acting as processors. Which set applies depends on your role for each processing activity. Many agencies and software providers are processors for their clients and controllers for their own staff and marketing data, so both sets can be relevant.
How ISO 27701 supports GDPR duties
The overlap is large, because both documents deal with the same practical questions. The standard does not copy the regulation article by article, but it asks you to run processes that cover the same ground.
Records and accountability
Article 30 of the GDPR requires records of processing activities. ISO 27701 expects you to know which personal data you hold, why, where it goes and how long you keep it. A working PIMS produces this inventory as a by-product, and keeps it current.
Processors and sub-processors
Article 28 requires a contract with every processor and rules for sub-processors. The standard asks for the same discipline: documented agreements, a list of the parties involved, and a way to check that they do what the contract says. If your customers send you a data processing agreement, a PIMS gives you a consistent answer instead of a new negotiation each time.
Data subject requests
People can ask for access, correction, deletion or a copy of their data. The GDPR sets a time limit for the answer. A PIMS defines who receives the request, who verifies the identity of the person, who finds the data and who signs off the reply. That is the part most small businesses have not written down.
Risk, privacy by design and impact assessments
Article 25 asks for data protection by design and by default. Article 35 requires a data protection impact assessment for high-risk processing. Clause 6 of the standard builds privacy risk assessment into planning, so the question "does this new tool need an impact assessment?" gets asked before you sign up for it.
Security and breaches
Article 32 requires appropriate security measures. Articles 33 and 34 set out notification to the supervisory authority and, in some cases, to the people affected. The standard expects an incident procedure with clear roles. When a laptop is lost or a mailing goes to the wrong list, the team knows who decides whether it is a reportable breach.
What ISO 27701 does not do
The limits matter, especially when you write them into a tender response.
- It is not a GDPR certification in the sense of Articles 42 and 43. Those articles describe certification mechanisms approved under the regulation. An ISO 27701 certificate is a statement about your management system, not a finding that you comply with the GDPR.
- It does not decide your legal questions. Whether you have a lawful basis for a given newsletter, or whether a transfer to a provider outside the EU or Switzerland is permitted, remains a legal judgement. The system makes sure someone examines these questions. It does not answer them for you.
- It does not replace a data protection officer or an EU representative where the GDPR requires one. Article 37 sets the conditions for appointing an officer.
- It does not protect you from a complaint or a fine. A functioning PIMS is good evidence of accountability. It is not immunity.
Put plainly: ISO 27701 shows that you have a system. Compliance with the GDPR is shown by what that system does in practice, case by case.
Why this matters for businesses in Switzerland
The GDPR applies outside the EU when you offer goods or services to people in the EU or monitor their behaviour (Article 3). A Swiss agency with clients in Germany, or an online shop shipping to Austria, can fall under it. The revised Swiss Federal Act on Data Protection has been in force since 1 September 2023, and it overlaps with the GDPR in many areas, though not in all. One management system can cover both, as long as you note where the two differ.
In practice the trigger is rarely a regulator. It is a procurement team. A German customer sends a security and privacy questionnaire, a public tender asks for evidence of a privacy management system, or an enterprise client wants proof before it shares customer data with you. A certificate with a verification page answers that request faster than a forty-page questionnaire.
Smaller companies sometimes assume this is only for large firms. The standard scales with the amount and sensitivity of the data you handle, and our guide to ISO certification for small and medium businesses explains what that means for a team of ten or fifty.
Checklist: are you ready to claim ISO 27701 alignment?
If you can tick most of these, a certificate will mainly confirm and document what exists. If you can tick few, the checklist is your work plan.
Where Zertify fits in
Zertify issues ISO certificates based on an online self-assessment, without an on-site audit. For privacy, that means the ISO 27701 assessment, which asks you to describe how your organisation handles personal data against the requirements of the standard. A member of the SICE Certification Board reviews every assessment. The certificate is issued by Zertify under licence from SICE, and it is publicly verifiable: the PDF carries a QR code that leads to a verification page your customer can open.
After a passed assessment and payment, the certificate is issued within 4 hours. It is valid for three years and confirmed each year with a short online re-audit, which is a yearly subscription. The pricing page shows what that costs. If you want to see the questions first, you can start the assessment and judge how close your organisation already is.
A self-assessment is a different route from the classic one, where a certification body sends auditors to your premises. If you want to understand the difference before you decide, read our guide on ISO certification without an audit.
A sensible order of work
Start with the inventory. Without a list of what personal data you hold and who receives it, every other step rests on guesses. Then fix the contracts with processors, because that is what customers and authorities look at first. Write down the request and incident procedures next, even if they are one page each. Only then take on the formal assessment, with documents you can actually point to.
Keep your legal adviser or data protection officer involved for the questions the standard cannot answer. The management system is the frame. The legal judgement inside it stays with people who know your processing.
Frequently asked questions
Does ISO 27701 make me GDPR compliant?
No. ISO 27701 certifies that you run a privacy management system. It supports GDPR compliance because it covers similar ground, but it is not a finding that you comply with the regulation, and it does not settle legal questions such as lawful basis or international transfers.
Do I need ISO 27001 before ISO 27701?
Not with the 2025 edition. ISO 27701:2025 is a standalone standard, whereas earlier editions were an extension to ISO 27001. If you already run an information security system, much of its documentation will still be useful.
Is ISO 27701 the same as a certification under GDPR Article 42?
No. Article 42 describes certification mechanisms set up under the GDPR itself. An ISO 27701 certificate refers to an international management system standard and is a separate thing.
Does a Swiss company need to care about the GDPR?
Yes, if it offers goods or services to people in the EU or monitors their behaviour there. The Swiss data protection act also applies to Swiss businesses. One privacy management system can serve both, if you note where the requirements differ.


