GDPR and the DPC, for Irish businesses

Data protection

A data protection policy for a small firm: what it's for and what goes in

A data protection policy is the internal rulebook for how your firm handles personal data. Article 24(2) of the GDPR expects one where it's proportionate to what you do, and the DPC expects you to be able to show your rules in writing.

By FourWindsCurrent as at 4 minute read3 sources

The short answer

Article 24(1) of the GDPR makes you put appropriate technical and organisational measures in place and be able to show them. Article 24(2) adds that, where proportionate, those measures include appropriate data protection policies.

For a firm that handles client files, payroll or health information, a written policy is proportionate. It tells staff what to do, and it's the first document a client, an insurer or the DPC asks to see.

Policy, notice and record: three different documents

These three are easy to confuse, and each has a different reader.

DocumentWho reads itWhere the duty comes from
Data protection policyYour staffGDPR Article 24(2)
Privacy noticeClients, website visitors, job applicantsGDPR Articles 13 and 14
Record of processingYou, and the DPC on requestGDPR Article 30

What the DPC looks for

The DPC's guidance on accountability says organisations, not the regulator, have to show they comply. It names documented processes and procedures, and asks you to work out for each kind of data why you hold it, how you got it, how long you keep it, how secure it is and who you share it with.

Your policy is where the answers become rules. The NCSC also lists a data protection policy among the policies an Irish business should adopt, alongside its security and remote access policies.

What goes in it

Keep it short enough that people read it. These sections cover a firm of up to forty people:

  1. 1Who's responsible: the partner or director who owns data protection, and how to reach them.
  2. 2The principles in Article 5, in a sentence each: lawful, limited to its purpose, minimal, accurate, kept no longer than needed, secure.
  3. 3Where personal data may be kept and which tools are approved, including AI tools.
  4. 4How long each kind of record is kept, in a short retention table.
  5. 5Security rules: two-step sign-in, locked screens, encrypted laptops, sharing files safely.
  6. 6Requests from individuals: how to recognise an access or erasure request and who handles it.
  7. 7Breaches: what counts, and that it's reported internally at once so the 72-hour clock can be met.
  8. 8Suppliers: that any processor has a contract before it gets data.
  9. 9Training, and when the policy is next reviewed.

Write rules your firm follows

A policy copied from a template that describes systems you don't use is worse than none, because it shows a gap between the rules and the practice.

An insurance broker, worked through

Take a twelve-person insurance broker. It holds client names, addresses, claims histories and some health details for life and income protection cover.

Its policy runs to three pages. It names the compliance director as owner, sets out where client files live, and treats health details as special category data with access limited to the advisers who need it. It has a retention table that matches the broker's record of processing, and a line saying no client data goes into public AI tools.

Every new starter reads it in their first week and signs to say so, and it's reviewed each January alongside the staff GDPR training. When an insurer partner asks for the broker's data protection arrangements, the policy and the training record go back together.

Keep it alive

A policy is only as good as the date on it. Review it when you add a system, a supplier or a kind of client, and at least once a year. Eurus keeps each check result it records with a SHA-256 fingerprint chained to the one before, so anyone holding an export can confirm at eurus.ie/verify that the evidence behind your policy wasn't changed afterwards.

Questions

Is a data protection policy a legal requirement?
Article 24(2) of the GDPR requires appropriate data protection policies where that's proportionate to your processing. For a firm handling client or employee data, it usually is.
Is a data protection policy the same as a privacy policy?
No. A privacy notice, often called a privacy policy, tells people outside the firm how you use their data (Articles 13 and 14). A data protection policy tells your own staff how to handle it.
Does a small business with under 250 employees need one?
The under-250 exemption in Article 30(5) relates to the record of processing, and it has conditions. It doesn't apply to Article 24, so the size of the firm doesn't remove the need for proportionate policies.
How often should we review the policy?
When something changes, such as a new system or supplier, and at least once a year. Record the date of each review.

Sources

  1. 1.General Data Protection Regulation, Articles 5, 13, 24, 30 and 32 · EUR-Lex
  2. 2.Accountability obligation · Data Protection Commission
  3. 3.12 Steps to Cyber Security: Guidance on Cyber Security for Irish Business · National Cyber Security Centre

See where you stand, in Eurus

Connect your systems once, and Eurus does the talking. It works out which laws apply, finds your AI tools, suppliers and people, and keeps the proof itself. If there is a gap you can't close yourself, FourWinds reviews it and sends a fixed quote.

Try Eurus live

Who wrote this

FourWinds · Compliance experts, and the makers of Eurus

FourWinds writes and maintains the legal explainers on this site, and does the compliance work behind them. Every date and article number here is checked against the legislation itself before it is published, and each article shows the date it was last checked.

Questions and corrections go to support@fourwinds.ie.

More about how we work →

Read next

More on GDPR and the DPC, for Irish businesses

Written on 14 November 2026; it describes the law as FourWinds read it on that date. How we check the law.