GDPR: the obligations that apply wherever you process EU personal data
The General Data Protection Regulation applies to organisations anywhere in the world that offer goods or services to people in the EU or monitor their behaviour, which is why a software company in Sydney or Austin has GDPR obligations. This guide sets out what the regulation requires, the documents and processes regulators ask for first, and how to evidence them.
GDPR is built on seven principles in Article 5: lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality; and accountability. The last one is the operative principle. Regulators do not only ask whether you comply; they ask you to demonstrate it, which is why documented records, assessments and decisions matter as much as the controls themselves.
Every processing activity needs a lawful basis under Article 6 (consent, contract, legal obligation, vital interests, public task or legitimate interests) and, for special categories such as health or biometric data, an additional condition under Article 9. Choosing the basis, recording it and telling people about it in a privacy notice is the foundation of everything else.
What a GDPR programme contains
Records of processing activities (Article 30)
A register of every processing activity: purpose, categories of data and data subjects, recipients, transfers, retention and security measures. The first document a supervisory authority asks for.
Privacy notices and transparency (Articles 12–14)
Clear information to individuals at the point of collection about who you are, why and on what basis you process their data, who receives it, how long you keep it and their rights.
Data subject rights (Articles 15–22)
Access, rectification, erasure, restriction, portability, objection and rights relating to automated decision-making, handled within one month with a documented process.
Processor contracts (Article 28)
Written terms with every processor covering instructions, confidentiality, security, sub-processors, assistance, deletion and audit rights.
Security of processing (Article 32)
Appropriate technical and organisational measures given the risk, including encryption, resilience, restoration and regular testing. ISO 27001 is the usual way to evidence this.
Data protection impact assessments (Article 35)
Required before high-risk processing such as large-scale monitoring, profiling or special-category data; consultation with the authority where residual risk stays high.
Data protection officer (Articles 37–39)
Mandatory for public bodies and for organisations whose core activities involve large-scale monitoring or special-category processing.
International transfers (Chapter V)
Transfers outside the EU need an adequacy decision, standard contractual clauses with a transfer impact assessment, binding corporate rules, or, for the US, certification under the EU-US Data Privacy Framework.
Breach management (Articles 33–34)
Detect, assess, document every breach, notify the authority within 72 hours where there is a risk to individuals, and notify individuals where the risk is high.
Who it applies to
Any organisation established in the EU, and any organisation elsewhere that sells to or monitors people in the EU. In practice this covers almost every SaaS vendor, e-commerce business, marketplace and multinational employer. Processors are directly liable for their own obligations, not only controllers. UK organisations follow the near-identical UK GDPR, and many other regimes, including Saudi Arabia’s PDPL and Australia’s Privacy Act reforms, borrow its structure.
From scope to evidence, in one system
Records of processing as a living register
Processing activities are recorded with purposes, lawful bases, data categories, recipients, retention and transfers, linked to the systems and vendors involved, so the Article 30 register is a report that stays current.
DPIAs and risk in one place
Impact assessments run in the Risk & Quantification module with the GDPR criteria, the mitigations and the residual-risk decision, with a history the authority can review.
Vendor and processor register
Processors are tiered, Article 28 terms and sub-processor lists held against each, transfer mechanisms recorded, and review dates tracked.
Article 32 evidenced through ISO 27001
Security of processing is demonstrated by the same controls and automated evidence that support ISO 27001 and SOC 2, mapped through the crosswalk.
Rights requests and breach clocks
Data subject requests are tracked against the one-month deadline, and incidents carry the 72-hour assessment and notification record.
Policies and notices
The AI Policy Builder generates the privacy policy set and notices scoped to your processing, versioned and acknowledged.
Frequently asked questions
We are outside the EU. Does GDPR really apply?
If you offer goods or services to people in the EU, even free ones, or monitor their behaviour, yes, and you may need to appoint an EU representative under Article 27. Supervisory authorities have fined non-EU companies.
Is ISO 27001 enough for GDPR?
It covers Article 32 security well and is the evidence regulators expect for it, but GDPR is mostly about lawful basis, transparency, rights, records and transfers, which ISO 27001 does not address. ISO 27701 extends 27001 into privacy management for that reason.
Do we need a DPO?
Only if you are a public body, or your core activities involve regular and systematic large-scale monitoring or large-scale special-category processing. Many organisations appoint one voluntarily or name a privacy lead instead; the decision should be documented.
What happens after a breach?
Assess within hours whether there is a risk to individuals. If so, notify the supervisory authority within 72 hours, even with incomplete information, and individuals where the risk is high. Record every breach, notified or not.
Related frameworks
Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.