Privacy, in computing, is control over what is collected about you, who can see it and what it is used for. It is a technical property as much as a legal one: a system either gathers and exposes data or it does not. Good design collects less, keeps it shorter and protects what remains.
Key concepts
- Data minimisation: do not collect what you do not need; data never stored cannot leak.
- Metadata: who talked to whom, when and from where often reveals more than content, and encryption alone does not hide it.
- Tracking and fingerprinting: cookies, identifiers and device characteristics link activity across sites and apps.
- Anonymisation limits: removing names rarely makes data anonymous; combining records can re-identify people.
- Privacy by design: defaults, retention limits, access controls and purpose limitation built in from the start.
Vocabulary
- PII: personally identifiable information.
- End-to-end encryption: only the communicating parties hold the keys, not the service between them.
- Differential privacy: adding calibrated noise so results reveal little about any one person.
- Data subject: the person the data is about; rights over data differ by country, so check your local law.
What to study, in order
- Audit your own digital footprint: accounts, app permissions, what each one stores.
- Watch the network traffic of one app or site you use, in your own browser's developer tools, and list what it sends and to whom.
- Set up end-to-end encrypted messaging and full-disk encryption on your own devices.
- Design a small database with minimal fields, retention limits and per-role access.
- Learn k-anonymity and differential privacy by trying to re-identify a toy dataset you built.