GDPR (the General Data Protection Regulation) is a European Union law that governs how organizations collect, use, and protect the personal data of people in the EU and European Economic Area. It applies to any business worldwide that handles that data, and it backs its rules with fines of up to 20 million euros or 4% of global annual revenue.
You do not have to operate in Europe for GDPR to reach your business. If people in the EU can buy from your website, sign up for your newsletter, or simply get tracked by your analytics, the regulation can apply to you, no matter where your servers or your offices sit. That surprises a lot of American business owners, and it is exactly why GDPR matters far beyond the EU. This guide explains what GDPR actually is, who it covers, the core rules it sets, the rights it gives individuals, and what the penalties really look like, in plain English rather than legal code.

The General Data Protection Regulation is the European Union’s comprehensive law for protecting personal data and privacy. It was adopted by the European Parliament and Council in 2016 and became enforceable on 25 May 2018, replacing a patchwork of older national rules with a single standard that applies across every EU member state. You can read the full law in the official EU regulation text on EUR-Lex, and the European Data Protection Board’s official guidance explains how regulators interpret it.
At its heart, GDPR is about “personal data,” which it defines broadly as any information relating to an identifiable person. That is more than a name and email. It includes IP addresses, location data, device identifiers, cookies, and online behavior, so the regulation touches almost every company that runs a website or markets online. Whenever your business collects or uses that kind of information, GDPR calls the activity “processing,” and processing is only allowed when you have a valid legal reason for it.
A useful way to picture GDPR is as a set of rules of the road for personal data. It does not stop you from driving, in other words from using data to run and grow your business. What it does is set the speed limits, require a license, and hold you responsible if you cause harm. The regulation assumes the individual, not the company, ultimately owns their personal information, and that your business is only borrowing it under conditions the person can see and control. That single shift in ownership is what drives every rule that follows.
Source: Regulation (EU) 2016/679, EUR-Lex | European Data Protection Board
GDPR is long, but its core sits in seven principles that every use of personal data must satisfy. If you understand these, you understand what the regulation is actually asking for. They come directly from Article 5 of the law.
That last principle, accountability, is what trips up most businesses. GDPR does not just want you to be compliant; it wants you to hold the records, policies, and evidence that show you are compliant, because that is what a regulator asks for first. Good data governance is what produces that evidence as a byproduct of daily operations rather than a last-minute scramble.

Source: GDPR Article 5, principles of processing | UK Information Commissioner’s Office, data protection principles
This is the question that matters most for a US business, and the answer is wider than most people expect. GDPR is not limited to companies headquartered in Europe. Its reach, defined in Article 3, follows the people it protects, not the location of the company. Your business can fall under GDPR in three common situations.
GDPR also splits responsibility between two roles. A data controller decides why and how personal data is used, and a data processor handles data on the controller’s behalf, such as a cloud provider or an email platform. If you run the business collecting the data, you are usually the controller and carry the primary legal responsibility, even when a vendor does the actual processing. That makes your vendor contracts part of your compliance.
Myth: GDPR only applies to companies in Europe. This is the single most expensive misconception about the regulation. GDPR is deliberately extraterritorial. A Houston e-commerce store that ships to a customer in Germany, or a Texas SaaS company whose app is used by someone in France, is processing the personal data of people in the EU, and the regulation can apply. “We are a US business” is not a defense. Whether GDPR reaches you depends on whose data you handle, not on where your headquarters sits.
Source: GDPR Article 3, territorial scope | European Commission, rules for business and organisations
GDPR is most often confused with the California Consumer Privacy Act, or CCPA, and its amendment the CPRA. Both are landmark privacy laws that give people rights over their data, and a business subject to one is often close to the other. But they are not the same, and treating GDPR like CCPA leaves real gaps. The biggest difference is the consent model: GDPR generally requires people to opt in before you use their data, while CCPA lets you use it unless they opt out.
| Attribute | GDPR | CCPA / CPRA |
|---|---|---|
| Who it protects | People in the EU and EEA | Residents of California |
| Consent model | Opt-in before most data use | Opt-out of the sale or sharing of data |
| Who must comply | Any organization handling EU residents’ data | Businesses over set revenue or data-volume thresholds |
| Scope of “personal data” | Very broad, including online identifiers | Broad, with some business-context carve-outs |
| Maximum penalty | Up to 20M euros or 4% of global revenue | Per-violation civil penalties, plus consumer lawsuits |
The practical takeaway: GDPR is generally the higher bar. A business built to meet GDPR, with opt-in consent, documented purposes, and a way to honor individual rights, is usually well positioned for CCPA and the growing list of US state privacy laws. Building only to CCPA and assuming it covers Europe is the mistake that gets companies fined.
Source: California Attorney General, CCPA | General Data Protection Regulation, full text
GDPR shifts control of personal data to the individual, and it does that through eight specific rights. For your business, these are not abstract, because you are legally required to have a process to honor each one, usually within one month of a request. Ignoring a request is itself a violation.
Behind each right sits a practical requirement: you have to be able to find a specific person’s data across every system you run. A business that cannot locate all copies of one customer’s information cannot honor an access or erasure request, which is why these rights push companies toward better data organization whether they intended to improve it or not.

Source: European Commission, rights of citizens | UK Information Commissioner’s Office, individual rights
GDPR gets attention for one reason above all others: the size of its fines. The regulation uses a two-tier structure, and both tiers are calculated as the higher of a fixed cap or a percentage of the company’s global annual revenue, which is what makes them so serious for large businesses.
GDPR’s Two Fine Tiers (Maximum Caps)
Each tier is the higher of the fixed cap or the percentage of worldwide annual revenue. Source: GDPR Article 83.
The lower tier, up to 10 million euros or 2% of global revenue, covers more procedural failures like poor record-keeping or not appointing a required data protection officer. The higher tier, up to 20 million euros or 4% of global revenue, covers the serious violations: ignoring the core principles, breaking the rules on consent, or violating individuals’ rights. Regulators also weigh how severe and how negligent the violation was when setting the actual figure.
These are not theoretical numbers. The largest single GDPR fine to date was issued in May 2023, when Ireland’s Data Protection Commission penalized Meta 1.2 billion euros over unlawful transfers of EU user data to the United States. Enforcement has also broadened well beyond big tech.
Across all of Europe, GDPR fines totaled roughly 5.88 billion euros between the law taking effect in 2018 and early 2025, with about 1.2 billion euros issued in the most recent survey year alone, according to law firm DLA Piper’s annual survey. Beyond the headline penalties, a serious violation often triggers a breach: under Article 33, a personal data breach must generally be reported to the regulator within 72 hours of discovery, a deadline that catches unprepared companies off guard. For a fuller picture of enforcement trends, see our cybersecurity compliance statistics.
Explore Managed Cybersecurity Services
See Backup and Recovery Options
Source: GDPR Article 83, conditions for imposing fines | Irish Data Protection Commission, Meta decision | DLA Piper GDPR Fines and Data Breach Survey, January 2025
You do not become GDPR compliant by buying a single tool or posting a privacy policy. It is a program that combines legal decisions, documented processes, and real technical controls. For a small or midsize business, a workable path follows five steps.
The hardest part is rarely the technology. It is sustaining the accountability, which is why many businesses assign GDPR oversight to a CIO, an outsourced Virtual CIO, or a data protection lead who can translate the regulation into practical rules and keep them enforced. Pairing that leadership with a broader IT compliance program and a formal cybersecurity risk assessment gives you a prioritized starting point instead of a blank page. If GDPR is only one of several regulations you face, treating them together as a single governance effort is far more efficient than chasing each one separately.
Definitions and rules in this guide are grounded in the text of the General Data Protection Regulation, Regulation (EU) 2016/679, and the official guidance of the European Commission and the European Data Protection Board. The seven principles are from Article 5, territorial scope from Article 3, the fine tiers from Article 83, and the 72-hour breach reporting rule from Article 33. Enforcement figures, including the roughly 5.88 billion euros in total fines since 2018 and about 1.2 billion euros in the most recent survey year, are from DLA Piper’s GDPR Fines and Data Breach Survey (January 2025); the record 1.2 billion euro fine against Meta is from the Irish Data Protection Commission’s May 2023 decision. Figures are cited to their original sources and used to illustrate GDPR’s scope and enforcement, not as legal advice for any specific organization.
Sources: Regulation (EU) 2016/679, EUR-Lex | European Data Protection Board | European Commission, data protection | UK Information Commissioner’s Office | DLA Piper GDPR Fines and Data Breach Survey 2025
Infrastructure security is the practice of protecting the core technology systems a business runs on: its…
Infrastructure as Code (IaC) is the practice of managing and provisioning IT infrastructure, such as servers,…
Homomorphic encryption is a form of encryption that lets you perform calculations directly on encrypted data…
FinOps is an operational framework and cultural practice for managing and optimizing cloud costs by bringing…