---
title: "What is GDPR? A plain-English guide"
description: "GDPR is the General Data Protection Regulation, a European law that sets rules for handling personal information and gives individuals rights over its use."
published: "2026-09-03T22:00:00.000Z"
updated: "2026-09-03T22:00:00.000Z"
url: "https://getdosya.com/what-is-gdpr-a-plain-english-guide"
canonical: "https://getdosya.com/what-is-gdpr-a-plain-english-guide"
site: "Get dosya"
---

# What is GDPR? A plain-English guide

GDPR is the General Data Protection Regulation, a European law that sets rules for handling personal information and gives individuals rights over its use.

## Key takeaways

- GDPR has applied since May 25, 2018, and can cover organizations outside the EEA that offer goods or services to people there or monitor them.
- Consent is only one of six lawful bases, and each processing purpose needs its own documented basis rather than a blanket request for consent.
- Organizations must generally respond to individual rights requests without undue delay and within one month, with a possible extension if the person is told.
- Controllers must notify the supervisory authority of a breach within 72 hours where feasible, unless it is unlikely to create a risk to individuals.

GDPR is the General Data Protection Regulation, a European law that sets rules for handling personal information and gives individuals rights over its use. For organizations, it means having a valid reason to use data, protecting it, and being able to explain those decisions. This GDPR overview covers the essentials, common misunderstandings, and practical steps toward compliance. ([eur-lex.europa.eu](https://eur-lex.europa.eu/EN/legal-content/summary/general-data-protection-regulation-gdpr.html))

## What is GDPR, and why does it matter?

GDPR is the European Union’s main data protection regulation. Applicable since May 25, 2018, it governs how organizations collect, use, store, share, and otherwise process personal data. Its purpose is to protect people, not simply to require privacy policies or cookie banners. ([consilium.europa.eu](https://www.consilium.europa.eu/en/policies/data-protection-regulation/))

For someone running a business, the central question is straightforward: can you justify what you do with people’s information? A useful answer covers why you need it, what permits you to use it, who can access it, and when you will delete it. GDPR makes those responsibilities part of everyday operations rather than an afterthought. ([dataprotection.ie](https://www.dataprotection.ie/en/dpc-guidance/guidance-for-smes))

## Who does GDPR apply to?

GDPR generally applies to personal-data processing connected with an organization’s establishment in the European Economic Area, or EEA, which includes EU countries, Iceland, Liechtenstein, and Norway. It can also apply to organizations outside the EEA when they offer goods or services to people there or monitor their behavior there. Small businesses are not automatically exempt. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/learn-the-basics/data-protection-basics_en))

For example, a US company deliberately selling subscriptions to customers in France may fall within its scope. Simply having a website that someone in Europe can visit does not, by itself, establish that the business targets that market. The assessment concerns the organization’s activities, not just a customer’s citizenship. ([eur-lex.europa.eu](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng))

Some obligations depend on the nature, scale, and risk of processing. A small retailer and a large health-data platform therefore need different compliance arrangements, even though both may be covered. Do not confuse a limited exemption from a particular duty with an exemption from GDPR altogether. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/application-gdpr_en?prefLang=nl))

## Personal data and processing, explained

Personal data is information relating to an identified or identifiable living person. Names, customer email addresses, location information, photographs, and purchase histories can qualify. Processing is equally broad: collecting information, storing it, looking it up, sharing it, or deleting it all count. Organized paper filing systems can fall within the rules too. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/learn-the-basics/data-protection-basics_en))

Business information is not necessarily outside GDPR. A named employee’s work email address can identify an individual, even when it is used only for professional communication. By contrast, information solely about a legal entity is not personal data unless it also relates to an identifiable person. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/application-gdpr_en))

### Sensitive information needs additional protection

Special-category data includes information about health, racial or ethnic origin, political opinions, religious beliefs, trade-union membership, and certain other sensitive matters. Using it generally requires both an ordinary lawful basis and an additional condition permitting that processing. Criminal-conviction information is subject to separate restrictions. Treat these categories as a signal to obtain more specific advice before proceeding. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/find-practical-info/faq_en?page=1))

## The seven principles behind the rules

Much of what people call “GDPR regulations” follows seven principles. Together, they explain what responsible processing should look like, regardless of the software or filing system involved. ([eur-lex.europa.eu](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng))

| Principle | Practical meaning |
| --- | --- |
| Lawfulness, fairness, and transparency | Have a lawful basis, avoid unfair uses, and explain what happens to information. |
| Purpose limitation | Collect data for clear purposes; do not reuse it for incompatible purposes. |
| Data minimization | Collect only what the purpose actually requires. |
| Accuracy | Take reasonable steps to correct inaccurate information. |
| Storage limitation | Keep identifiable information only as long as necessary. |
| Integrity and confidentiality | Protect data against unauthorized use, loss, destruction, or damage. |
| Accountability | Be able to demonstrate compliance, not merely claim it. |

These principles come from Article 5 of GDPR. ([eur-lex.europa.eu](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng))

Consider an event registration form. Asking for contact details may support event administration; asking for unrelated personal information needs a separate justification. Applying the principles means questioning each field before launch, deciding who needs access, and setting a retention period tied to the purpose. ([dataprotection.ie](https://www.dataprotection.ie/en/dpc-guidance/guidance-for-smes))

## Lawful bases: consent is only one option

Every processing purpose needs an appropriate lawful basis. GDPR provides six, and the correct choice depends on what you are doing and why. Asking everyone to consent is not a substitute for examining whether another basis is more appropriate. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/be-compliant/process-personal-data-lawfully_en))

- **Consent:** The person freely agrees to a specific, clearly explained use.
- **Contract:** Processing is necessary to fulfill a contract with the person or take requested steps before entering one.
- **Legal obligation:** Applicable EU or national law requires the processing.
- **Vital interests:** Processing is necessary to protect someone’s life or another vital interest.
- **Public task:** Processing is necessary for a legally grounded public-interest task or official authority.
- **Legitimate interests:** A legitimate purpose requires the processing, and the person’s interests or fundamental rights do not override it. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/find-practical-info/faq_en?page=1))

For example, a delivery address may be necessary to fulfill an online order. That does not automatically justify using the address for unrelated promotions. Assess purposes separately and document the reasoning behind each basis. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/be-compliant/process-personal-data-lawfully_en))

Where you rely on consent, it must be freely given, specific, informed, and unambiguous. People must be able to withdraw it, and you must be able to demonstrate that it was obtained. Legitimate interests also needs a real assessment; “this would help our business” is not enough on its own. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/be-compliant/process-personal-data-lawfully_en))

## Individual rights and your response process

GDPR gives people rights over their information, although not every right applies in every situation. Your organization needs a way to recognize requests, assess them, and respond appropriately. Rights include: ([edpb.europa.eu](https://www.edpb.europa.eu/sme/be-compliant/respect-individuals-rights_en?trk=article-ssr-frontend-pulse_little-text-block))

- **Information and access:** Understand how data is used and obtain access to personal data.
- **Correction:** Have inaccurate personal information corrected.
- **Erasure and restriction:** Request deletion or limits on processing in qualifying circumstances.
- **Portability:** Receive certain data in a reusable format and, where applicable, transfer it.
- **Objection:** Challenge certain processing, including an unconditional right to object to direct marketing.
- **Automated-decision safeguards:** Receive protection against certain solely automated decisions with significant effects. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/be-compliant/respect-individuals-rights_en?trk=article-ssr-frontend-pulse_little-text-block))

Generally, organizations must respond without undue delay and within one month. A permitted extension may apply to complex or numerous requests, but the individual must be told within the initial month. Erasure is not absolute: a legal retention obligation, for instance, may justify keeping particular records. ([eur-lex.europa.eu](https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1529595055951&uri=CELEX%3A32016R0679))

Practically, make sure staff know where to send requests, including ones received outside a dedicated form. Confirm identity proportionately, track deadlines, and explain any refusal clearly. A process that works only when someone uses the “right” terminology is not a reliable process. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/be-compliant/respect-individuals-rights_en?trk=article-ssr-frontend-pulse_little-text-block))

## A practical GDPR checklist for organizations

Use this GDPR compliance guide as a starting framework, not proof that every requirement has been met. Work through actual data flows and keep evidence of your decisions. That approach connects written policies with how your organization operates. ([dataprotection.ie](https://www.dataprotection.ie/en/dpc-guidance/guidance-for-smes))

### Map information and assign responsibility

1. **Create a data inventory.** Record what you collect, whose information it is, where it comes from, why you use it, who receives it, and how long you keep it.
2. **Identify your role.** A controller decides the purposes and means of processing. A processor handles information on a controller’s behalf; one business can hold different roles for different activities.
3. **Assign ownership.** Give someone responsibility for coordinating privacy work and establish whether a formal data protection officer is required. Not every organization needs one. ([dataprotection.ie](https://www.dataprotection.ie/en/dpc-guidance/guidance-for-smes))

### Match explanations and contracts to reality

1. **Record lawful bases.** Connect each purpose to its justification and any additional conditions for sensitive data.
2. **Review privacy notices.** Explain your identity, purposes, lawful bases, retention approach, recipients, relevant transfers, and individual rights in accessible language. Avoid copying a policy that describes someone else’s operations.
3. **Check processor agreements.** Contracts should address instructions, confidentiality, security, assistance with rights and breaches, subcontractors, and what happens to data when the service ends. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/be-compliant/process-personal-data-lawfully_en))

### Build safeguards into everyday work

1. **Set retention rules.** Choose periods based on purpose and applicable legal requirements, then implement deletion or anonymization rather than keeping everything indefinitely.
2. **Apply proportionate security.** Consider access controls, staff training, backups, and encryption according to the risks. Review access when people change roles or leave.
3. **Assess risky projects early.** Build privacy into design and default settings. Carry out a data protection impact assessment before processing likely to create high risks for individuals. ([dataprotection.ie](https://www.dataprotection.ie/en/dpc-guidance/guidance-for-smes))

### Check international transfers

1. **Identify overseas recipients.** Where data goes to another organization outside the EEA, check whether GDPR’s international-transfer requirements apply. An adequacy decision or appropriate safeguards, such as standard contractual clauses, may provide a route, subject to applicable conditions. A supplier’s general promise to be “GDPR compliant” does not replace this assessment. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/be-compliant/international-data-transfers_en))

Keep the checklist live. Revisit it when adding suppliers, launching services, changing collection forms, or introducing a new use for existing information. Record what changed and who approved the decision so accountability survives staff turnover. ([dataprotection.ie](https://www.dataprotection.ie/en/dpc-guidance/guidance-for-smes))

## Personal data breaches require a prepared response

A personal data breach is not limited to hacking. It can involve lost information, accidental disclosure, unauthorized alteration, or loss of availability. An email sent to the wrong recipient can therefore require assessment, even when no attacker is involved. ([commission.europa.eu](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/obligations_en))

Controllers must notify the relevant supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a breach, unless it is unlikely to create a risk to individuals’ rights and freedoms. High-risk breaches generally also require informing affected people without undue delay, subject to exceptions. Processors must notify the controller without undue delay. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/assess-the-risks/data-breaches_en?trk=article-ssr-frontend-pulse_little-text-block))

Prepare a response plan before an incident: identify reporting contacts, contain the problem, assess consequences, and document decisions. Keep records of breaches even when notification is unnecessary. If information is incomplete, reporting in stages may be appropriate; do not assume you can wait until every detail is known. ([edpb.europa.eu](https://www.edpb.europa.eu/sme/assess-the-risks/data-breaches_en?trk=article-ssr-frontend-pulse_little-text-block))

## Enforcement and the next practical step

Supervisory authorities can investigate, order corrective action, restrict processing, and impose fines. For certain infringements, the maximum can reach €20 million or 4% of an undertaking’s total worldwide annual turnover for the preceding financial year, whichever is higher. These are ceilings, not automatic penalties for every mistake. ([eur-lex.europa.eu](https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1529595055951&uri=CELEX%3A32016R0679))

The most useful takeaway from this GDPR quick guide is to start with your real information-handling practices. Map one process, such as customer onboarding, and follow its data from collection to deletion. Identify the gaps, assign responsibility, and keep improving; a published privacy policy alone cannot demonstrate compliance. ([dataprotection.ie](https://www.dataprotection.ie/en/dpc-guidance/guidance-for-smes))

*This guide provides general information about EU GDPR, not legal advice. Seek tailored advice where your activities, jurisdiction, or risk profile require it.*

## Related guides

- [How to remove a password from a PDF](/how-to-remove-a-password-from-a-pdf)
- [Malware vs ransomware: what is the difference?](/malware-vs-ransomware-what-is-the-difference)

## Sources

1. [General data protection regulation (GDPR) | EUR-Lex](https://eur-lex.europa.eu/EN/legal-content/summary/general-data-protection-regulation-gdpr.html)
2. [consilium.europa.eu: Data protection regulation](https://www.consilium.europa.eu/en/policies/data-protection-regulation/)
3. [Guidance for SMEs | Data Protection Commission](https://www.dataprotection.ie/en/dpc-guidance/guidance-for-smes)
4. [Data protection basics | Data protection guide for small business | European Data Protection Board](https://www.edpb.europa.eu/sme/learn-the-basics/data-protection-basics_en)
5. [Regulation - 2016/679 - EN - gdpr - EUR-Lex](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng)
6. [Application of the GDPR - European Commission](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/application-gdpr_en?prefLang=nl)
7. [Application of the GDPR - European Commission](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/application-gdpr_en)
8. [FAQ | Data protection guide for small business | European Data Protection Board](https://www.edpb.europa.eu/sme/find-practical-info/faq_en?page=1)
9. [Process personal data lawfully | Data protection guide for small business | European Data Protection Board](https://www.edpb.europa.eu/sme/be-compliant/process-personal-data-lawfully_en)
10. [Respect individuals’ rights | Data protection guide for small business | European Data Protection Board](https://www.edpb.europa.eu/sme/be-compliant/respect-individuals-rights_en?trk=article-ssr-frontend-pulse_little-text-block)
11. [Regulation - 2016/679 - EN - gdpr - EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1529595055951&uri=CELEX%3A32016R0679)
12. [International data transfers | Data protection guide for small business | European Data Protection Board](https://www.edpb.europa.eu/sme/be-compliant/international-data-transfers_en)
13. [Obligations - European Commission](https://commission.europa.eu/law/law-topic/data-protection/information-business-and-organisations/obligations_en)
14. [Data breaches | Data protection guide for small business | European Data Protection Board](https://www.edpb.europa.eu/sme/assess-the-risks/data-breaches_en?trk=article-ssr-frontend-pulse_little-text-block)
