trio.so
Templates

GDPR Compliance Checklist for IT Teams (PDF + Excel)

A GDPR compliance checklist for IT teams: 72 items by article, a ROPA template, a 72-hour breach register and device security controls. Free PDF and Excel.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

A GDPR compliance checklist turns the regulation's requirements into tasks you can assign, finish and prove. This one has 72 items in nine areas, each tied to the article it comes from, with the evidence to keep. It is written for the people who do the work: IT managers, sysadmins and MSPs, at companies in the EU and at US and other non-EU companies that sell to people there.

Most GDPR checklists stop at policies and consent. This one also covers the parts that land on IT: the record of processing activities, vendor contracts, the 72-hour breach clock, and the security of the laptops and phones where personal data actually lives.

Download it as a printable PDF and an Excel tracker with a dashboard, a ROPA template, a breach register that works out the 72-hour deadline, a rights request log with deadlines, a vendor and transfer register, and a DPIA screening sheet. Or work through it below.

Preview of the GDPR compliance checklist PDF and Excel tracker
Preview of the GDPR compliance checklist PDF and Excel tracker

TL;DR

In short

  • GDPR applies to EU-based organizations and to non-EU companies that offer goods or services to people in the EU or monitor their behavior there.
  • The core duties: know your data, have a lawful basis, tell people, honor their rights within one month, sign contracts with vendors, secure the data, and report breaches.
  • Notify the supervisory authority within 72 hours of becoming aware of a breach, unless it is unlikely to result in a risk to people.
  • A lost laptop that was encrypted, with the key kept safe and a backup, usually needs only an internal record. An unencrypted one holding personal data usually means notifying.
  • Fines reach €20 million or 4% of worldwide turnover, whichever is higher. There is no official "GDPR certified" badge to buy.

Does GDPR apply to you?

The General Data Protection Regulation has applied since 25 May 2018. Article 3 decides who it covers, and the answer depends on whose data you process and why, not only on where you are based.

Does GDPR apply to you: an EU establishment, offering goods or services to people in the EU, or monitoring their behavior there
Does GDPR apply to you: an EU establishment, offering goods or services to people in the EU, or monitoring their behavior there
  • You have an EU establishment (an office, branch or subsidiary): GDPR covers processing in the context of its activities, wherever the servers are.
  • You are outside the EU but offer goods or services to people in the EU, paid or free, or monitor their behavior there: GDPR covers that processing. The EDPB looks for intent, such as EU languages, currencies or delivery; a website people in the EU can open is not enough on its own (Guidelines 3/2018).
  • Non-EU companies in the second group must also name an EU representative in writing (Art 27), unless the processing is occasional, low-risk and not large-scale sensitive data.
  • Serving the UK? The UK has its own UK GDPR, now amended by the Data (Use and Access) Act 2025. The checklist works for both; the UK changes are under What changed in 2025 and 2026.

For US companies, the usual trigger is selling to EU customers or tracking EU visitors. If that is you, start with the scope and representative items in the first area of the checklist.

GDPR requirements in brief

The regulation has 99 articles, but the duties that drive day-to-day work fit in one table. Every item in the checklist below traces back to one of these:

RequirementArticlesWhat it means in practice
PrinciplesArt 5Process data lawfully, fairly and openly; for set purposes; only what you need; accurate; kept no longer than needed; secure. And be able to show it.
Lawful basisArt 6One of six bases for every purpose: consent, contract, legal obligation, vital interests, public task or legitimate interests.
TransparencyArt 12–14Privacy notices that say what you collect, why, on what basis, for how long, and who gets it.
Individual rightsArt 15–22Access, rectification, erasure, restriction, portability, objection and safeguards on automated decisions, answered within one month.
RecordsArt 30A written record of processing activities (ROPA).
VendorsArt 28A contract with every processor, with the terms Article 28(3) lists.
SecurityArt 32Measures that fit the risk: encryption, resilience, restore, and regular testing.
BreachesArt 33–34Authority within 72 hours where there is a risk; people affected when the risk is high; a record of every breach.
DPIAArt 35–36An impact assessment before high-risk processing.
DPOArt 37–39A Data Protection Officer for public bodies and for large-scale monitoring or sensitive data as a core activity.
TransfersArt 44–49A legal mechanism for data leaving the EEA: adequacy (including the EU-US Data Privacy Framework), SCCs, BCRs, or an Art 49 derogation.

Our guide to GDPR for small businesses explains each requirement in plain terms.

Start here: a 90-day plan

Do the groundwork first. 24 items are marked "first 30 days": scope, the data map and record, notices, the breach plan, vendor contracts and the device basics.

The GDPR checklist in three phases: the first 30 days, by day 90, and ongoing
The GDPR checklist in three phases: the first 30 days, by day 90, and ongoing

In the Excel tracker, filter the Phase column to see each list, and give every item an owner and a due date before you start.

The GDPR compliance checklist

Each item lists the article it comes from and the evidence to keep. The Excel tracker adds an owner, a frequency, a status and a due date for every row.

72 items across nine areas, by phase
72 items across nine areas, by phase

Scope and accountability (8 items)

Start by deciding whether GDPR applies, what role you play in each activity, and who owns the program. Accountability (Art 5(2)) means you must be able to show compliance, not only claim it.

IDWhat to doGDPREvidence to keep
SC-01Decide whether GDPR applies: an EU establishment, or offering goods or services to people in the EU, or monitoring their behavior there (first 30 days)Art 3Scope memo with the reasons
SC-02Decide for each activity whether you act as controller, processor or joint controller, and set out the arrangement with any joint controller (first 30 days)Art 4(7), 4(8), 26Role list per processing activity
SC-03Name one person who owns data protection, with time and budget (first 30 days)Art 24Appointment record
SC-04Check whether you need a Data Protection Officer: public body, or large-scale systematic monitoring or special-category data as a core activity (some countries require more) (first 30 days)Art 37(1), 37(4)DPO decision with the reasons
SC-05If you appoint a DPO, publish the contact details and give them to the supervisory authorityArt 37(7), 38Published contact; authority registration
SC-06Outside the EU and covered by Art 3(2)? Appoint an EU representative in writing, unless an exemption appliesArt 27Signed representative mandate
SC-07Write a data protection policy that leadership approvesArt 24(2)Signed policy with version and date
SC-08Keep a compliance file that shows how you follow each principle (accountability)Art 5(2)Index of policies, records and reports

Data mapping and records (7 items)

You can't protect or explain data you haven't found. The data map and the record of processing activities are the base for notices, rights requests, DPIAs and breach response. See the section on the ROPA below, and our data retention policy template.

IDWhat to doGDPREvidence to keep
MP-01Map the personal data you hold: what, whose, where it lives, who sees it, where it goes (first 30 days)Art 30Data map or data flow diagram
MP-02List every system, app and device that stores or reaches personal data (first 30 days)Art 30, 32System and device inventory
MP-03Write your record of processing activities (ROPA) with the Art 30(1) contents (first 30 days)Art 30(1)ROPA (the Excel tab)
MP-04If you are a processor, keep the processor record for each controllerArt 30(2)Processor record
MP-05Fewer than 250 staff? Check the Art 30(5) exemption carefully: regular processing of staff or customer data usually still needs a record (first 30 days)Art 30(5)Exemption decision
MP-06Set a retention period for each data category and delete or anonymize on scheduleArt 5(1)(e)Retention schedule; deletion logs
MP-07Describe your security measures in the record, in general termsArt 30(1)(g)Security measures summary

Lawful basis and transparency (8 items)

Every purpose needs one of the six lawful bases, chosen before you start. For staff data, avoid consent: the power imbalance means it is rarely free. Tell people what you do, including what device management sees on their laptops and phones.

IDWhat to doGDPREvidence to keep
LB-01Pick and record a lawful basis for each processing purpose (first 30 days)Art 6(1)Lawful basis per ROPA row
LB-02For legitimate interests, write and keep a balancing testArt 6(1)(f)Legitimate interests assessment
LB-03Where you rely on consent: opt-in, specific, recorded, and as easy to withdraw as to giveArt 7Consent records; withdrawal path
LB-04Avoid relying on employee consent; use another basis for staff dataArt 6, 7(4)Basis for HR processing
LB-05Find any special-category or criminal data and record the Art 9 or Art 10 conditionArt 9, 10Special-category register
LB-06Publish privacy notices with the Art 13 and Art 14 information, for customers, staff and applicants (first 30 days)Art 13, 14Published notices with dates
LB-07Tell staff what device management does: which devices, which data, and whyArt 13; WP249Staff device notice
LB-08Get consent for non-essential cookies before they are set, where the ePrivacy rules applyePrivacy Dir. Art 5(3)Cookie banner configuration

Individual rights (7 items)

People can ask to see, correct, delete, move or restrict their data, and object to its use. You have one month to answer, extendable by two more for complex cases if you say so within the first month.

IDWhat to doGDPREvidence to keep
RT-01Set up one route for rights requests, and log every request with its date (first 30 days)Art 12Request log (the Excel tab)
RT-02Answer within one month; extend by up to two months only with reasons given within the first month (first 30 days)Art 12(3)Response dates in the log
RT-03Verify identity before you disclose anything, without asking for more than you needArt 12(6)Verification notes
RT-04Be able to find, copy, correct and delete one person's data across systemsArt 15–17Search procedure; test results
RT-05Handle restriction, portability and objection, and stop direct marketing on requestArt 18, 20, 21Request log
RT-06Tell recipients about corrections and deletionsArt 19Notification records
RT-07Identify any solely automated decisions with legal or similar effects, and offer human reviewArt 22Automated decision register

Vendors and transfers (8 items)

Most vendors that handle personal data on your behalf are processors and need an Article 28 contract. Some, such as banks or auditors, are controllers in their own right: record them, but they don't sign your DPA. Data leaving the EEA needs a transfer mechanism. MSPs are usually the processor: VT-08 covers that side. Pair this area with our vendor management policy template.

IDWhat to doGDPREvidence to keep
VT-01List every vendor that processes personal data for you (first 30 days)Art 28Vendor register (the Excel tab)
VT-02Sign a data processing agreement with each one, with all Art 28(3) terms (first 30 days)Art 28(3)Signed DPAs
VT-03Check each vendor's security before you sign, and again on renewalArt 28(1)Due diligence notes
VT-04Keep the vendors' sub-processor lists and object to changes where neededArt 28(2), 28(4)Sub-processor lists
VT-05Map transfers outside the EEA and record the mechanism: adequacy, Data Privacy Framework, SCCs or BCRs (first 30 days)Art 44–49Transfer register
VT-06For SCC transfers, assess the destination country and add measures if neededArt 46Transfer impact assessment
VT-07Watch the status of the EU-US Data Privacy Framework and have SCCs ready as a fallbackArt 45, 46Watch notes; fallback plan
VT-08If you are a processor (most MSPs): sign each client's Art 28 contract, act only on their documented instructions, get authorization before adding sub-processors and pass the same terms downArt 28(2)–(4), 29Signed client DPAs; sub-processor list

Security of processing (15 items)

Article 32 asks for security that fits the risk, and its first example is pseudonymisation and encryption. It names no product. Laptops and phones carry personal data out of the office, and a lost device is one of the most common breaches IT teams handle, so this is the largest area. Our data encryption policy template helps here.

IDWhat to doGDPREvidence to keep
SE-01Assess the risk to personal data and choose security measures that fit it (first 30 days)Art 32(1)–(2)Risk assessment
SE-02Encrypt every laptop and desktop (BitLocker, FileVault) and keep recovery keys away from the device (first 30 days)Art 32(1)(a)Encryption status per device
SE-03Encrypt phones and tablets and require a passcode (first 30 days)Art 32(1)(a)Mobile encryption and passcode report
SE-04Lock screens automatically after a short idle time (first 30 days)Art 32(1)(b)Screen lock settings report
SE-05Patch operating systems and apps on a set timeline, fastest for known-exploited flaws (first 30 days)Art 32(1)(b)Patch compliance report
SE-06Scan for vulnerabilities and fix them by riskArt 32(1)(b), (d)Vulnerability reports
SE-07Allow approved apps and block the ones that move data where it should not goArt 25, 32App allow and block lists
SE-08Block or restrict USB storage where it is not neededArt 32(1)(b)USB policy and settings report
SE-09Turn on the host firewall on every laptop and desktopArt 32(1)(b)Firewall settings report
SE-10Give each person their own account, require MFA, and limit admin rights (first 30 days)Art 32(1)(b)Access review; MFA report
SE-11Back up personal data and test that you can restore it quicklyArt 32(1)(c)Backup reports; restore tests
SE-12Wipe devices before reuse or disposal, and keep proofArt 5(1)(f), 32Wipe records
SE-13Write BYOD rules that keep work data separate and respect private data on personal devicesArt 5(1)(c), 32; WP249BYOD policy
SE-14Test and review your security measures on a scheduleArt 32(1)(d)Test results; compliance reports
SE-15Log admin actions on systems that hold personal data, and keep the logsArt 5(2), 32Admin logs; retention setting

Breach response (8 items)

Write the plan before you need it. The clock is 72 hours from awareness to the authority. Our data breach notification policy template gives you the wording.

IDWhat to doGDPREvidence to keep
BR-01Write a breach response plan: who decides, who notifies, and within what time (first 30 days)Art 33, 34Plan; test report
BR-02Teach staff to report a lost device or a suspected breach at once (first 30 days)Art 33Training records; reporting route
BR-03When a device is lost, lock it, locate it if company-owned, and wipe it if neededArt 33, 34(3)(b)Incident record with actions and times
BR-04Assess the risk fast: what data, how many people, was it encryptedArt 33(1), 34(1)Risk assessment in the breach record
BR-05Notify the supervisory authority within 72 hours of becoming aware, unless the breach is unlikely to result in a risk (no EU establishment? notify each authority where affected people live)Art 33(1), 33(3)Notification copy with timestamp
BR-06Tell the people affected without undue delay when the risk to them is high, unless an Art 34(3) exemption appliesArt 34Communication copy
BR-07Record every breach, reported or not, with facts, effects and actions (first 30 days)Art 33(5)Breach register (the Excel tab)
BR-08Processors: tell the controller without undue delayArt 33(2)Notice to controller

DPIA and privacy by design (6 items)

High-risk processing needs a data protection impact assessment before it starts. Monitoring staff devices is a common trigger, so run one on your device management too. See our guide to the data protection impact assessment (DPIA).

IDWhat to doGDPREvidence to keep
DP-01Screen every new project, system or vendor for high risk before it startsArt 35(1)Screening record (the Excel tab)
DP-02Run a DPIA when the processing is on your authority's list, and usually when two or more WP248 criteria applyArt 35(1), 35(3)–(4)DPIA with the Art 35(7) contents
DP-03Run a DPIA on your device management itself: monitoring staff devices is a common triggerArt 35; WP249DPIA for device management
DP-04Ask your DPO's advice on each DPIA, where you have oneArt 35(2)DPO advice on file
DP-05Consult the authority before processing if high risk remains after your measuresArt 36Consultation record
DP-06Build data protection into new systems: collect the minimum and set privacy-friendly defaultsArt 25Design notes; default settings

People and training (5 items)

People cause and catch most incidents. Train them, bind them to confidentiality, limit admin access, and close the gaps when they leave.

IDWhat to doGDPREvidence to keep
PE-01Train everyone who handles personal data at hire and every yearArt 24, 32(4)Training records
PE-02Bind staff and contractors to confidentialityArt 29, 32(4)Signed agreements
PE-03Limit who can see device and user data in admin consolesArt 5(1)(f), 25(2)Admin role list
PE-04Remove access and recover or wipe company devices when people leaveArt 32Leaver records with times
PE-05Review the program yearly and report to leadershipArt 24(1)Annual review report

Data mapping and the record of processing activities (ROPA)

Data mapping is the work; the ROPA is the document that comes out of it. Article 30(1) lists what a controller's record must contain:

  1. Your name and contact details, and those of any joint controller, EU representative and DPO.
  2. The purposes of the processing.
  3. The categories of people and of personal data.
  4. The categories of recipients, including any outside the EEA.
  5. Transfers outside the EEA and the safeguards used.
  6. Where possible, how long you keep each category.
  7. Where possible, a general description of your security measures.

Processors keep a shorter record for each controller they work for (Art 30(2)). Keep it in writing, electronic is fine, and be ready to hand it to the supervisory authority on request.

The under-250 exemption is narrower than it looks. Article 30(5) exempts organizations with fewer than 250 staff only if the processing is occasional, unlikely to result in a risk, and includes no special-category or criminal data. Payroll and customer records are processed regularly, so most small businesses still need a record for those. An EU proposal to widen the exemption has been agreed with the Council and goes to a Parliament vote, expected in November 2026; until it is adopted, the 250 rule applies.

To map data quickly, start from systems, not departments. List each app, database and device type, then ask what personal data it holds, whose, where it goes and how long it stays. The device inventory from your device management tool gives you the endpoint rows. The Excel tracker's ROPA tab has the Article 30(1) columns and four worked examples: payroll, customer accounts, device management and marketing email.

Breach response: the 72-hour clock and the lost laptop

Under Article 33, you notify your supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a personal data breach, unless it is unlikely to result in a risk to people. You become aware when you are reasonably certain personal data was compromised. If you can't give every detail in time, send what you have and follow up in phases. No EU establishment? There is no lead authority for you, so notify each authority where affected people live.

The GDPR 72-hour breach clock: the authority within 72 hours, people affected when the risk is high, and a record of every breach
The GDPR 72-hour breach clock: the authority within 72 hours, people affected when the risk is high, and a record of every breach

You tell the people affected without undue delay only when the risk to them is high (Art 34). And you record every breach, reported or not, with the facts, the effects and what you did (Art 33(5)).

The most common breach for IT teams is a lost or stolen device. The EDPB's own examples show how much encryption changes the outcome:

Lost laptop or phone under GDPR: encrypted with a safe key and a backup usually means a record only; unencrypted usually means notifying
Lost laptop or phone under GDPR: encrypted with a safe key and a backup usually means a record only; unencrypted usually means notifying
  • Encrypted tablets stolen, strong passwords, backups available, a remote wipe sent: unlikely to result in a risk. No notification; record it (EDPB Case 10).
  • Unencrypted notebook stolen with customer data on it: notify the authority and the people affected (EDPB Case 11).
  • Encryption only helps if the key is safe. The key must stay in your possession and not be compromised. If the device held the only copy of the data, the loss can still be an availability breach to assess (Guidelines 9/2022).

So the evidence you need on day one is simple: which device it was, whether it was encrypted, where the recovery key is, and when it was locked or wiped. Have that ready before a device goes missing. Our data breach response plan covers the full process.

GDPR Article 32 and your devices

Article 32 asks controllers and processors for security appropriate to the risk, and lists four measures "as appropriate": pseudonymisation and encryption; the ongoing confidentiality, integrity, availability and resilience of systems; the ability to restore data quickly after an incident; and regular testing of the measures. It names no product, standard or algorithm.

Device controls such as encryption, screen lock, OS updates and remote wipe, mapped to the GDPR articles they support
Device controls such as encryption, screen lock, OS updates and remote wipe, mapped to the GDPR articles they support

On a mixed fleet of Windows, Mac, iPhone and Android devices, those measures come down to a short list of settings: full-disk encryption with the recovery key kept off the device, a passcode and screen lock, OS updates on a timeline, controlled apps and USB storage, and the ability to lock or wipe a lost device. The encryption guidance from the Information Commission (formerly known as the ICO) gives the same advice on encryption for UK organizations. Our guide to full disk encryption explains the options per platform.

Device management needs its own GDPR check. The EU's data protection authorities said in their opinion on data processing at work (WP249) that employers should run a DPIA before rolling out mobile device management, tell staff what it does, and keep location tracking for lost devices from turning into ongoing monitoring. On personal devices (BYOD), keep work and private use apart. Our BYOD policy template is a starting point.

What changed in 2025 and 2026

  • The EU Digital Omnibus is still a proposal. In November 2025 the European Commission proposed changes that would notify authorities only of high-risk breaches, within 96 hours through a single EU entry point, and set EU-wide DPIA lists. As of October 2026 it has not been adopted, so the 72-hour rule applies.
  • The EU-US Data Privacy Framework is still in force. It is valid at the time of writing, but under legal challenge: the General Court rejected a challenge in September 2025, an appeal followed, and in July 2026 the EDPB Chair asked the Commission to assess a US Supreme Court ruling on FTC independence. Keep SCCs ready as a fallback (EDPB note on transfers to the US).
  • UK changes are in force. The Data (Use and Access) Act 2025 adds recognised legitimate interests, "reasonable and proportionate" searches for access requests, and a duty to handle complaints, all in force by 19 June 2026 (Information Commission summary). The UK keeps the 72-hour breach rule, and the EU renewed the UK's adequacy decision in December 2025, until 2031.
  • Cross-border enforcement gets new procedures. Regulation (EU) 2025/2518 applies from April 2027. It changes how authorities handle cross-border complaints, not what companies must do.
  • Fines keep coming. Recent examples include TikTok (€530 million, 2025, mostly for transfers to China), Uber (about €825 million from the Dutch authority, 2026, automated decisions) and Google (€403 million, 2026, location data). The Irish DPC's list tracks the largest ones; many are under appeal.

Evidence: what a GDPR audit checklist looks for

Accountability means showing your work. Whether the question comes from a customer's security review, an internal audit or a supervisory authority after a complaint, the answer is dated records collected over time.

AreaEvidenceRefresh
Scope and rolesScope memo; controller or processor per activity; DPO decisionYearly
RecordsROPA with Art 30(1) contents; data mapOn change
NoticesPrivacy notices with dates; staff device noticeYearly
RightsRequest log with response datesEach request
VendorsSigned DPAs; transfer register; transfer assessmentsEach contract
SecurityEncryption status per device; patch reports; access reviewsMonthly
BreachesBreach register, including the ones you did not reportEach incident
DPIAsScreening records; DPIAs; DPO adviceEach project
TrainingTraining records; confidentiality agreementsYearly

Common mistakes

  • Calling yourself "GDPR certified". There is no general GDPR certificate. Article 42 allows approved certification schemes, which cover specific processing operations, not a whole company.
  • Relying on staff consent. Employees can rarely refuse freely, so use another lawful basis for HR and device data.
  • Assuming the under-250 exemption covers you. Regular processing still needs a record.
  • Starting the 72 hours too late. The clock runs from awareness, not from the end of your investigation.
  • Encryption you can't prove. If you can't show the lost laptop was encrypted, plan to treat it as if it wasn't.
  • Forgetting device management in the DPIA. Location tracking and remote wipe on staff devices are processing too.

How trio.so helps with the device items

GDPR compliance stays your organization's program: the lawful bases, notices, contracts, DPIAs and notification decisions are yours. trio.so covers many of the device items in this checklist from one console, across Windows, Mac, iOS and Android:

  • Encryption: enforce BitLocker on Windows and FileVault on Mac, with FileVault recovery key escrow, enforce encryption and passcode rules on iOS and Android phones, and see encryption status per device (SE-02, SE-03).
  • Baseline settings: inactivity screen lock, USB storage and firewall settings (SE-04, SE-08, SE-09).
  • Patching and vulnerabilities: enforce OS updates on Windows, macOS, iOS and Android, with vulnerability findings scored by CVSS, EPSS and CISA KEV (SE-05, SE-06).
  • Apps: allow approved apps and block the ones you don't want near personal data (SE-07).
  • Lost devices: lock a lost Mac, iPhone or Android device and wipe company-owned devices (BR-03, SE-12).
  • Inventory and evidence: hardware and software inventory for every enrolled device, admin event logs with export, and compliance evidence export for your records (MP-02, SE-15, SC-08).

Comparing tools? Our guide to GDPR compliance software covers what automation can and can't do.

trio.so's compliance engine includes GDPR among its frameworks, covering the technical controls a device management tool can enforce. Learn more about GDPR compliance in trio.so and compliance automation.

Start free trial Book a demo

14-day free trial. No credit card required.

Sources. Last reviewed October 2026. This article is guidance, not legal advice. The mapping of device controls to GDPR articles is ours.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

It is a list of the tasks GDPR requires, each tied to the article it comes from and the evidence that shows it is done. This one has 72 items in nine areas, from scope and records to breach response and device security.

Follow the seven principles in Article 5, have a lawful basis for each purpose, give clear privacy notices, answer rights requests within one month, keep a record of processing, sign Article 28 contracts with vendors, secure the data under Article 32, report breaches, run DPIAs for high-risk processing, appoint a DPO where required, and use a legal mechanism for transfers outside the EEA.

Yes, if the company has an EU establishment, or offers goods or services to people in the EU, or monitors their behavior there (Article 3). A US company caught by the second or third case usually also needs an EU representative under Article 27.

Notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to people. Tell the people affected without undue delay if the risk to them is high. The UK GDPR has the same 72-hour rule.

It depends on the risk. In the EDPB's examples, stolen encrypted devices with a safe key and a backup needed no notification, only an internal record, while a stolen unencrypted notebook with customer data had to be reported to the authority and the customers. Record every case either way.

It is the written record Article 30 requires: your purposes, the categories of people and data, recipients, transfers, retention periods and a general description of your security measures. Organizations with fewer than 250 staff are exempt only for occasional, low-risk processing without sensitive data.

There is no general GDPR certification for a company. Article 42 allows certification schemes approved by authorities, which cover specific processing operations, not a whole company. Treat any 'GDPR certified' badge with care.

Up to €10 million or 2% of worldwide annual turnover for breaches of duties such as security, records and breach notification, and up to €20 million or 4% for breaches of the principles, lawful basis, individual rights or transfer rules, whichever is higher.

Related

From the blog

The related industry news, interviews, technologies, and resources.