Data privacy is the set of rules, rights and habits that decide who may collect information about a person, what they may do with it, and what control the person keeps. This guide explains the core ideas and links to deeper pages.
It is the category hub for this section. Pandemic-era debates about tracking and consent also appear in the covid-19 hackathon hub, and the topics below branch out from the ideas on this page.
What data privacy means in practice
The European Data Protection Board (EDPB) defines personal data as any information relating to an identified or identifiable individual. That definition is wider than most people expect. A name or a phone number counts, but so do an email address, location data, a browsing history, a purchase history, and photos or recordings that show or sound like a person. The EDPB also notes that an identification number such as a booking reference can identify someone indirectly.
Privacy is therefore about more than secrecy. A person can be happy to share a delivery address with a shop and still expect the shop not to sell it, keep it forever or use it for something unrelated. Data privacy law turns that expectation into duties for organisations and rights for individuals. Security is a related but separate topic: a company can lock its databases tightly and still collect far more than it should.
Three questions run through almost every privacy debate. Who decides what is collected? What is the information used for? And how can a person see, correct, move or delete it afterwards? The sections below take each in turn, starting with the question of control and ownership.
Control and ownership of personal information
Laws rarely treat personal data like a house or a car that a person simply owns. Instead they give people a bundle of rights over information about themselves, and they give organisations obligations while they hold it. The longer discussion of that distinction sits in the guide to personal data ownership, which compares the property view with the rights view and explains why the difference matters for products and public services.
A technical response to the same problem is to move control closer to the individual. In a personal data store, a person keeps their own records in one place and grants other services access on defined terms, instead of every service holding its own copy. The idea is attractive because it changes the default: organisations ask, rather than assume.
The ownership debate is not only academic. It shapes how a product asks for permission, what a person can take with them when they switch providers, and who benefits when information is combined. A health app, a transport pass and a library card can all hold records about the same person. If each record is locked inside its own service, the individual has little say; if the person can gather and share them, the balance shifts. Privacy law approaches this through rights such as access and portability rather than through a single ownership rule.
Control also has a time dimension. Data collected today may sit in a database for years, be merged with other sources, or pass to companies the person never dealt with. For that reason many laws focus on limits on retention and on disclosure to third parties, not only on the moment of collection.

The principles behind most privacy laws
Privacy statutes differ in detail, but a common set of principles recurs. The EU’s General Data Protection Regulation (GDPR) states them in Article 5 of the regulation text on EUR-Lex. Personal data must be processed lawfully, fairly and in a transparent manner; collected for specified, explicit and legitimate purposes; and kept adequate, relevant and limited to what is necessary. It must also be accurate, kept no longer than needed, and handled securely. The EDPB’s small-business guide groups these as 6 key principles of the GDPR, and adds that an organisation must be able to demonstrate its compliance with them.
Two of those principles do most of the practical work. Purpose limitation means information gathered for one reason should not quietly be reused for another. The principle of limiting collection to what is necessary is the subject of the guide to data minimization, which shows how product teams can ask for less and still deliver a service.
Principles also carry an ethical layer that law does not always capture. An organisation can comply with every statute and still use data in ways its users would find surprising. The page on the ethical use of data looks at how organisations and cities set their own standards for fairness, transparency and accountability beyond the legal minimum.
A voluntary framework from the United States helps organisations turn these principles into routines. The National Institute of Standards and Technology (NIST) describes its Privacy Framework as a voluntary tool intended to help organizations identify and manage privacy risk while building innovative products and services. It treats privacy as a risk to be managed, in the way organisations already manage security and financial risk.
Your rights over your data
The most visible part of any privacy law is the list of rights it gives to individuals. The GDPR and California’s privacy law express many of the same ideas in different words. The table compares the rights that appear in both texts.
| Right | Under the GDPR | Under the CCPA in California |
|---|---|---|
| Learn what is held | Right of access | Right to know |
| Fix mistakes | Right to rectification | Right to correct |
| Have data removed | Right to erasure | Right to delete, with exceptions |
| Take data elsewhere | Right to data portability | Not listed as a separate right on the Attorney General’s page |
| Say no to certain uses | Right to object | Right to opt out of sale or sharing, and to limit use of sensitive information |
The table summarises the GDPR text on EUR-Lex and the California Attorney General’s CCPA page; check the current text of each law, because rights have conditions and exceptions.
Each right has limits. Under the GDPR, the right to erasure applies where one of the listed grounds applies, and the right to object concerns processing based on certain legal grounds. Under California law, the Attorney General’s page says a consumer can request that a business delete personal information, subject to certain exceptions, such as a legal duty to keep the information. The same page says a consumer can make a request to know up to twice a year, free of charge.
Rights only help when people use them. A practical request usually names the right, identifies the person making it and goes to the contact point listed in the organisation’s privacy notice. If the organisation does not respond, regulators exist to receive complaints; the California Privacy Protection Agency, for example, lists a way to file a complaint on its laws and regulations page. This guide is general information, not legal advice. Readers with a specific dispute should check the current law or speak to a qualified lawyer.

Which laws apply, and where
There is no single global privacy law. Which rules apply depends on where the person lives and where the organisation operates. The GDPR is the best-known example because of its reach. The EDPB explains that it may apply to organisations established in the EU or the European Economic Area, and also to an organisation outside the EEA when its products or services are offered to individuals who are in the EEA. The article on gdpr explained walks through lawful bases, consent, controllers and processors in plain language.
The GDPR also sets out how seriously regulators can treat breaches. The regulation’s fines provision allows fines of up to 20 million euros, or in the case of an undertaking, up to 4% of the total worldwide annual turnover of the preceding financial year, whichever is higher, for the most serious infringements, including breaches of the basic principles and of data subjects’ rights. The regulation also requires that a controller must notify the supervisory authority of a personal data breach not later than 72 hours after having become aware of it, where feasible, unless the breach is unlikely to result in a risk to people’s rights and freedoms.
The United States has no single comprehensive federal privacy statute of the GDPR kind, so individual states have filled the gap. California led. According to the California Privacy Protection Agency, in November 2020, California voters passed Proposition 24, which amended the California Consumer Privacy Act and created the agency that now enforces it. The agency lists the statute and its regulations as effective January 1, 2026 on the same page, and the Attorney General’s office notes that the CPRA amends the CCPA rather than creating a separate law.
The California law does not apply to everyone. The Attorney General’s page says it covers for-profit businesses that do business in California and meet any of three tests: annual gross revenue above a set threshold; buying, selling or sharing the personal information of 100,000 or more California residents or households; or deriving 50% or more of annual revenue from selling California residents’ personal information. It adds that the law generally does not apply to nonprofit organizations or government agencies. The revenue threshold is not fixed: the California Privacy Protection Agency adjusts it for inflation every odd-numbered year, and its page on updated monetary thresholds lists $26,625,000, up from $25,000,000, effective January 1, 2025. Readers should check that page for the current figure.
Other states have passed their own statutes, and the details change often. The International Association of Privacy Professionals (IAPP) maintains a tracker of comprehensive state bills that it says was last updated 8 Sept. 2026. The guide to us state privacy laws explains how the California model spread and how the later statutes differ.
Everyday risks: cities, apps and brokers
Most people meet privacy risk through ordinary services rather than through courtrooms. A shopping app builds a purchase history. A phone shares location data. A loyalty card links visits across stores. Each piece looks harmless alone; combined, they can describe a routine, a health condition or a set of beliefs. The EDPB’s list of special categories shows why: information that reveals health, sexual orientation, ethnic origin, political opinions, religious or philosophical beliefs, or biometric data is usually prohibited from processing unless a specific justification such as explicit consent applies.
Public spaces raise a different problem, because a resident cannot easily decline a camera on a street corner. Cities that deploy sensors, cameras and open data platforms have to decide what to collect, who can see it and how long it is kept. The page on smart city privacy explains how consent works, or fails to work, when the data collector is the local government.
Local examples make the issue concrete. Readers who want a place-based case can start with the hub on Elyria Ohio, which looks at one small US city’s history, economy and civic technology work, and which gives context for how data questions look at city scale.
The pandemic brought the same tension to a national scale. Health authorities wanted fast, accurate information on who had been exposed; privacy advocates wanted limits on what apps could collect and keep. The guide to contact tracing app privacy reviews the design choices that apps made, and what they showed about trust, voluntary use and data deletion.
Data brokers add a further layer. The California Attorney General’s page explains that the CCPA applies to many businesses, including data brokers, and the California Privacy Protection Agency’s page describes a Delete Act that creates additional requirements unique to data brokers, along with a registry and a deletion mechanism. These are the companies that gather information from many sources and sell it on, often without any direct relationship with the person concerned.
Practical steps for individuals and organisations
Individuals can reduce exposure without becoming experts. The first habit is to share less: give an organisation the details it needs for the service, and no more. The second is to use the controls that already exist, such as account privacy settings, permissions on a phone and, where a law provides it, opt-out and deletion requests. The third is to review accounts that are no longer used and close them. A fuller list of everyday measures, from account hygiene to browser settings, sits in the guide on how to protect your privacy online.
Organisations have a matching checklist. The EDPB’s good-practice list for small businesses asks whether the purpose for collecting personal data is justified, whether only the necessary data is collected, whether individuals are informed about purposes, whether there is a legal basis, whether data is handled securely and kept accurate, and whether it is deleted when no longer necessary. It also reminds readers that national legislation may require some data to be kept, for example for tax reasons.
Design choices matter before any data is collected. Article 25 of the GDPR requires controllers to implement appropriate technical and organisational measures, such as pseudonymisation, when they decide how processing will work and while it runs. In plain terms, privacy should be built into a product from the first sketch, not added after launch. Teams that follow the NIST approach record what data flows exist, assess the risk to people, and then choose controls in proportion.
Developers and community groups that build tools with personal data face the same questions on a small scale. Before writing code, a team can list each field it plans to collect, write down the reason for each, decide how long it will be kept and name who can see it. Fields without a clear reason are dropped. Test data should be invented rather than copied from real people, and any dataset shared for a project should have identifying details removed or replaced. Habits like these cost little at the start and are far harder to retrofit once a service has users.
It also helps to plan for the person on the other side of the screen. A reader opening a sign-up form should be able to tell, in a few lines, what happens to their answers. If a form needs a date of birth, it should say why. If a feature needs location, it should work without it when the person declines. Defaults matter: most people never change them, so a default that shares less protects more people than a long menu of options.
Good practice also includes honest communication. A clear privacy notice states what is collected, why, for how long and who receives it. A request-handling process names a person or team responsible for answering. A breach plan sets out who decides, who notifies the regulator and how affected people are told. None of these steps requires a large budget, but each requires a decision to treat personal information as something held on behalf of people, not simply as an asset.

How to keep up with a changing field
Privacy law moves quickly. Regulations are amended, regulators issue guidance and new state statutes appear. The California Privacy Protection Agency’s page, for example, lists current rulemaking activities and says it is gathering input on topics such as data broker audits; as of November 2026, its entry on that topic says the preliminary comment period closed on May 7, 2026. Readers who depend on a rule, whether as a business owner, a developer or a resident, should go to the regulator’s own pages for the current text: EUR-Lex and the EDPB for the GDPR, the California Attorney General and the California Privacy Protection Agency for the CCPA, and a state attorney general or legislature for other US statutes.
Three habits keep a reader oriented. Read the definitions first, because who counts as a controller, a business or a consumer decides whether a law applies at all. Note the dates, because a summary written years ago may describe a repealed or amended rule. And separate law from good practice: a voluntary framework such as NIST’s is not a legal requirement, but it often describes what regulators and customers expect an organisation to be able to show.
Frequently asked questions
What is data privacy in simple terms?
Data privacy is about control over personal information: what organisations may collect, how they may use it, and what rights people have to see, correct, move or delete it. The EDPB describes personal data as any information relating to an identified or identifiable person.
Does the GDPR apply to organisations outside Europe?
It can. The EDPB says the GDPR may apply to an organisation outside the EEA if its products or services are offered to individuals in the EEA, or if it monitors their behaviour. The exact test is in the regulation’s territorial scope provision.
Can people sue under the California privacy law?
The California Attorney General’s page says consumers cannot sue businesses for most CCPA violations. A lawsuit is possible if non-encrypted and non-redacted personal information was stolen in a data breach caused by a failure to maintain reasonable security, and then only in limited circumstances.
Is the NIST Privacy Framework a law?
No. NIST describes it as a voluntary tool that helps organizations identify and manage privacy risk. Organisations adopt it to structure their own privacy programmes.
Where can the current text of these laws be found?
The GDPR is published on EUR-Lex, and the California statute and regulations are listed on the California Privacy Protection Agency’s website. For a specific legal question, a qualified lawyer can advise on how the current law applies.
