What is GDPR (General Data Protection Regulation)?
Last updated: July 29, 2026
Definition
The General Data Protection Regulation (GDPR) is a European Union privacy law that establishes protections for personal data of individuals in the European Economic Area. It applies to any organization worldwide that processes EU resident data, requiring consent-based data collection, transparent processing practices, documented security controls, and 72-hour breach notifications to supervisory authorities.
Key Facts
- Also known as: EU Regulation 2016/679, EU GDPR
- Category: Compliance & Risk
- Effective date: May 25, 2018
- Jurisdiction: European Union member states, EEA, extraterritorial application to non-EU organizations
- Related standards: ISO/IEC 27701 (Privacy Information Management), NIST Privacy Framework
- Maximum penalties: €20 million or 4% annual worldwide turnover (whichever is greater)
- Breach notification: 72 hours to supervisory authority
How GDPR Works
GDPR operates through seven core data protection principles that govern all personal data processing. Controllers must process data lawfully, fairly, and transparently, collect only what is necessary for stated purposes, maintain accuracy, store data no longer than needed, and implement appropriate security measures. Organizations must demonstrate accountability through documentation, staff training, Data Processing Agreements with third-party processors, and in many cases, appointment of a Data Protection Officer who reports to senior management and serves as the supervisory authority contact point.
Processing personal data requires one of six lawful bases. Consent requires explicit, informed, freely-given agreement that can be withdrawn at any time. Contract basis applies when processing is necessary to fulfill agreements with data subjects. Legal obligation covers compliance with laws. Vital interests protect someone's life. Public tasks apply to official functions. Legitimate interests allow processing that serves the organization's needs when not overridden by individual rights, requiring a balancing test before use.
Data subjects hold eight enforceable rights. They can request information about collection and processing, obtain copies of their personal data, correct inaccuracies, demand erasure under specific grounds, restrict processing, transfer data between service providers, object to marketing or non-service processing, and challenge automated decision-making. Organizations must implement processes to respond to these requests, conduct data protection impact assessments for high-risk processing, maintain records of all processing activities, and report personal data breaches to supervisory authorities within 72 hours unless the breach poses minimal risk to individuals. Organizations rely on security monitoring and breach detection capabilities to meet these breach notification obligations.
Why GDPR Matters
GDPR establishes the strictest data protection enforcement globally. Non-compliance triggers administrative fines reaching €20 million or 4% of annual worldwide turnover, whichever produces the greater penalty. Organizations face these fines for serious violations including inadequate security, failure to obtain proper consent, ignoring data subject rights, missing the 72-hour breach notification deadline, or processing without a valid lawful basis. Data subjects retain the right to seek compensation for damages beyond regulatory fines, creating dual financial exposure for organizations that fail compliance requirements.
The regulation's extraterritorial reach captures any organization worldwide offering goods or services to EU residents or monitoring their behavior within the EU, regardless of where the organization is based or where data processing occurs. This Brussels effect has driven worldwide adoption of GDPR-style regulations. Brazil enacted LGPD, California passed CCPA, and China implemented PIPL, all following GDPR's consent-based, rights-driven framework. For organizations processing EU resident data, GDPR compliance is not optional. It determines market access, shapes vendor selection, and defines baseline security standards that extend beyond European borders. Texas-based SMBs implementing compliance frameworks for SMBs often address GDPR alongside HIPAA and SOC 2 requirements when serving clients with European operations.
GDPR vs. CCPA
| Aspect | GDPR | CCPA |
| Primary function | Protects personal data privacy for EU residents | Protects consumer privacy for California residents |
| Scope | Extraterritorial (applies globally if processing EU data) | California businesses meeting revenue or data thresholds |
| Used by | Any organization processing EU resident data | California businesses with $25M+ revenue or large data volumes |
| Key difference | Requires affirmative consent for many processing activities | Allows opt-out model for data sales |
| When to use | When offering goods/services to EU or monitoring EU behavior | When operating business in California or processing California resident data |
The key difference is GDPR requires organizations to obtain affirmative consent before processing personal data for many purposes, while CCPA allows businesses to process and sell consumer data unless the consumer opts out.
Common Misconceptions
GDPR is not limited to companies based in the European Union. Any organization worldwide that processes personal data of individuals located in the EU, whether offering goods and services to them or monitoring their behavior within the EU, must comply with GDPR regardless of where the organization is headquartered or where data processing occurs.
GDPR does not make organizations compliant simply by obtaining user consent. Consent is one of six lawful bases for processing, and organizations still must implement data protection by design, maintain processing records, conduct impact assessments for high-risk activities, appoint Data Protection Officers when required, respond to data subject rights requests, and report breaches within 72 hours.
Frequently Asked Questions
The six bases are consent (explicit agreement), contract (fulfilling service agreements), legal obligation (complying with laws), vital interests (protecting life), public tasks (official functions), and legitimate interests (balancing organizational needs against individual rights). Organizations select based on processing purpose and context. Once selected, the basis must be documented, communicated transparently, and cannot easily change later.
DPO appointment is mandatory when processing is conducted by public authorities, when core activities require regular systematic large-scale monitoring, or when processing special category data or criminal conviction data at scale. DPOs must have expert knowledge of data protection law, maintain independence without conflicts of interest, report to highest management, and cannot be dismissed for performing DPO duties.
GDPR applies to non-EU organizations if they offer goods or services to EU data subjects or monitor EU resident behavior, regardless of where processing occurs or where the organization is based. Non-EU establishments must designate EU Representatives serving as contact points for supervisory authorities unless processing is occasional, small-scale, and excludes special categories.