GDPR is the personal-data law to be aware of if you serve EU users. Here are the essentials and the defensive basics in technical/operational terms — no attack steps.
Don't collect
Only the personal data you need
Don't keep
Delete once the purpose ends
Protect it
Restrict who can reach it
Detect and notify
72 hours as a rule
What it requires
Beyond the legal detail, focus on the operating practices that actually work as defense.
Don't collect or hold it (data minimization)
Collect and keep only the minimum personal data your purpose needs. Data you don't hold can't leak. That is the most effective defense. Delete it when it's no longer needed.
Protect it (encryption, access control)
Encrypt personal data and scope it to "only those who may touch it" via authorization. Keep secrets off the public surface (→ keep secrets out of public directories).
Detect and report (the 72-hour rule)
Detect a breach quickly and keep logs to trace its impact. Be ready to notify the authority within ~72 hours. With no detection, you can't meet the duty.
'Not relevant' isn't a safe assumption
GDPR can apply wherever a business is located if it offers goods/services to people in the EU or monitors their behavior. If you serve EU users or handle their personal data, "we're not an EU company" doesn't make it irrelevant. A practical start is an inventory of which personal data you hold and why.
This site's view: compliance and defense point the same way
GDPR's requirements point the same direction as the defense this site recommends: minimize personal data, encrypt it, scope it with authorization, and be able to detect and record a breach. That's not only for the law; it's the basic way to have fewer incidents. Treating regulation as "a re-check of your defenses" rather than "extra burden" is the realistic stance for a small operation.
Who it applies to
Whether GDPR applies depends not on where your company is, but on whose personal data you handle and how (Article 3).
- Businesses established in the EU: all processing in the context of that establishment
- Businesses outside the EU: in scope when they offer goods or services to people in the EU (even free ones) or monitor their behavior in the EU (tracking, profiling)
- A site aimed only at Japan that happens to get visits from the EU usually doesn't count as "offering." Selling in EU languages or currencies, or shipping to the EU, makes an intent to offer more likely
Non-EU businesses in scope generally must appoint a representative in the EU (Article 27, with exceptions for occasional, low-risk processing).
Maximum fines (Article 83)
| Type of violation | Cap |
|---|---|
| Security measures (Art. 32), breach notification (Arts. 33–34), data protection by design (Art. 25), etc. | EUR 10 million or 2% of worldwide annual turnover (higher of the two) |
| Core principles (Art. 5), lawful basis (Art. 6), data-subject rights (Arts. 12–22), transfers outside the EU (Arts. 44–49), etc. | EUR 20 million or 4% of worldwide annual turnover (higher of the two) |
The caps are sized for large companies, but authority orders (such as stopping processing) apply to small operators just the same.
GDPR vs Japan's APPI: what happens after a breach
If a Japanese business also holds data on EU users, a breach can trigger both procedures.
| Item | GDPR | Japan's APPI |
|---|---|---|
| Report to | The supervisory authority (usually where the main establishment is) | Personal Information Protection Commission |
| Deadline | Generally within 72 hours of becoming aware | Preliminary: roughly 3–5 days from discovery / Final: within 30 days (60 for improper-purpose cases) |
| Which breaches | Those posing a risk to people's rights and freedoms (none needed if the risk is unlikely) | Sensitive data, risk of financial loss (e.g. card numbers), improper purpose (e.g. unauthorized access), or over 1,000 people |
| Telling the people affected | When there is a high risk (Art. 34) | In principle required for reportable breaches |
Japan and the EU mutually recognized each other's protection as adequate in 2019, so personal data can flow from the EU to businesses in Japan without extra contractual safeguards.
Real cases
British Airways: from 22 June to 5 September 2018, information entered on the payment pages of its website was sent to a third party. About 429,612 customers and staff were affected, with names, addresses and card numbers, in most cases including the security code. BA did not detect the attack itself; it learned of it from a third party. On 16 October 2020 the UK Information Commissioner's Office (ICO) fined it GBP 20 million for failing to take appropriate security measures (GDPR Article 5(1)(f) and Article 32). The same kind of payment-page compromise happened in Japan with the APORITO online store (RIZAP) card-data exposure.
Meta: on 22 May 2023 Ireland's Data Protection Commission (DPC) fined Meta EUR 1.2 billion and ordered it to suspend transfers, finding that the way it moved EU users' personal data to the US violated GDPR. It shows that breaking the transfer rules, not only a breach, can draw a top-tier fine (Meta said at the time it would appeal).
Among EU cases covered on this site, the Dutch telecom Odido data breach and the European gym chain Basic-Fit member data breach were both reported to national data-protection authorities under GDPR.
How to check your own site or service
List your personal data
For each form, member database, support inbox, access log, analytics tool and backup, write down what you hold, why, for how long, and who can reach it. Stop collecting fields with no purpose (an unused date-of-birth field, for example).
Check what you send to third parties
Analytics, advertising and chat scripts send visitor data to other companies. Use the Site Transparency Checker to list where your pages can send data, and remove what you don't need.
Write a runbook you can follow within 72 hours
Decide who judges whether a breach occurred and who contacts the authority, and note the contact details (your supervisory authority; in Japan, the Personal Information Protection Commission). Check that logs showing who accessed which data and when are kept for at least several months.
Be ready to handle requests from individuals
Access, correction and erasure requests generally must be answered within one month (Article 12(3)). Decide in advance which databases and backups you delete from, and how you verify identity.
Read next
- Basics: authentication vs authorization (scope data to its owner) · the minimum security checklist
- Glossary: public-key crypto · PCI DSS (another standard for sensitive data)
- Related: OWASP Top 10 · the history of security (timeline)
Sources
- European Commission — GDPR (official): commission.europa.eu
- Regulation (EU) 2016/679, full text (Arts. 3, 12, 27, 33, 34, 83): eur-lex.europa.eu
- Personal Information Protection Commission (Japan) — breach reporting guidance (Japanese): ppc.go.jp
- UK ICO — British Airways Penalty Notice (16 October 2020): ico.org.uk
- Ireland DPC — "Data Protection Commission announces conclusion of inquiry into Meta Ireland" (22 May 2023): dataprotection.ie
- European Commission — Adequacy decisions (including Japan): commission.europa.eu