Irish business owners and website operators collecting personal data via forms, cookies, analytics, or accounts. Ideal for startups and SMEs building GDPR compliance without legal expertise.
Readers will learn exact requirements under Articles 13/14, plain language drafting tips, cookie handling, update strategies, and pitfalls to avoid, ensuring DPC-compliant policies that foster customer trust.
Key Takeaways
- Irish websites collecting personal data must have a privacy policy per GDPR Articles 13/14 and ePrivacy Regulations to inform users and ensure transparency.
- Required elements include data controller details, purposes, legal bases, retention periods, recipients, transfers, and data subject rights.
- Write in plain language with summaries, tables for processing activities, and layered access; avoid US templates.
- Address cookies by category, require informed consent, avoid invalid practices like pre-ticked boxes.
- Update policy for changes, notify users, maintain version history, and review annually for ongoing compliance.

Privacy Policy for Your Website: Irish Legal Requirements
If you are an Irish business owner with a website that collects personal data, GDPR requires you to provide privacy information, typically through a prominently accessible privacy policy. Under GDPR Articles 13 and 14, you must tell people what personal data you collect, why you collect it, and what you do with it. A privacy policy for your website in Ireland is not optional, and a poorly written one can expose your business to complaints and regulatory action from the Data Protection Commission (DPC). This guide covers what your privacy policy must include, how to write it in plain language, and the common mistakes Irish businesses make.
Why does every Irish website need a privacy policy?
A privacy policy is a legal obligation under the General Data Protection Regulation (GDPR). Articles 13 and 14 require data controllers to provide specific information to individuals when collecting their personal data. If your website collects any personal data, whether through contact forms, analytics, cookies, or account creation, you need a privacy policy.
The Irish ePrivacy Regulations (SI 336/2011) add further requirements for websites using cookies or similar tracking technologies. These work alongside the GDPR to create a comprehensive transparency framework.
Beyond legal compliance, a clear privacy policy builds trust. Customers and clients increasingly check how businesses handle their data before engaging with them. A missing or vague policy signals carelessness, while a well-drafted one signals professionalism.
The consequences of not having a compliant privacy policy range from DPC complaints to administrative fines. The DPC fined TikTok €530 million in May 2025 for unlawful transfers and for failing to meet transparency obligations, a reminder that these obligations are actively enforced.
What must your privacy policy include?
Under GDPR Article 13, your privacy policy must provide the following information at the point of data collection:
- The identity and contact details of the data controller (your business)
- Contact details of your Data Protection Officer, if you have one
- The purposes of processing and the legal basis for each purpose
- The categories of personal data you collect
- Any recipients or categories of recipients who receive the data
- Details of international data transfers and the safeguards in place
- Retention periods for each category of data, or the criteria used to determine them
- The data subject's rights: access, rectification, erasure, restriction, portability, and objection
- The right to withdraw consent at any time, where consent is the legal basis
- The right to lodge a complaint with the DPC
If you collect data indirectly (not from the individual themselves), Article 14 requires you to provide additional information, including the source of the data and the categories of personal data concerned.
Each legal basis you rely on must be stated clearly. Saying "we process your data for legitimate business purposes" is not enough. You need to specify the purpose and match it to the correct legal basis under Article 6.
Author's tip: List your processing activities in a simple table: purpose, data collected, legal basis, retention period. In our experience, it makes the policy easier to write and easier for readers to scan.
How do you write a privacy policy in plain language?
The GDPR's transparency principle (Article 12) requires that information is provided in a "concise, transparent, intelligible and easily accessible form, using clear and plain language." Your privacy policy cannot read like a legal contract.
Start with a summary layer at the top of the policy: a few sentences explaining who you are, what data you collect, and why. Readers who need more detail can scroll to the full sections below.
Use short sentences and simple vocabulary. Explain technical terms the first time you use them. "Data controller" should be followed by something like "(that is us, the company that decides how your data is used)."
Avoid copy-pasting template policies from other jurisdictions. It is important to be aware that a US-style privacy policy will not meet Irish GDPR requirements. It will reference the wrong legislation, miss required disclosures, and confuse your readers.
If your website serves different audiences, consider a layered approach: a short summary for casual visitors and a full policy for those who want the detail. Both layers must be easily accessible from every page, typically through a footer link.
What about cookies and tracking disclosures?
Cookie disclosures are a common stumbling block for Irish businesses. The ePrivacy Regulations require informed consent before placing non-essential cookies on a user's device.
Your privacy policy should address cookies, but many businesses choose to maintain a separate cookie policy linked from the main privacy policy. Either approach works, as long as the information is clear and complete.
For each type of cookie you use, explain:
- What the cookie does
- Whether it is first-party or third-party
- How long it persists
- Whether it requires consent
Group cookies by category: strictly necessary, analytics, functional, and marketing. Your consent management tool should align with these categories and allow users to accept or reject each one independently.
The DPC has flagged common cookie consent problems: pre-ticked boxes, toggles set to "on" by default, and hidden settings beneath toggles that appear to be off. All of these invalidate consent.
If you are already managing your website's terms and conditions, your cookie disclosures should sit alongside them as part of a coherent legal framework.
How do you keep your privacy policy up to date?
A privacy policy is not a set-and-forget document. You must update it whenever your data processing activities change.
Common triggers for an update include:
- Adding new services or features that collect personal data
- Changing third-party processors or analytics tools
- Expanding into new markets or adding international data transfers
- Changes to retention periods or legal bases
- Regulatory updates that affect your obligations
When you make material changes, notify your users. A banner on your website, an email to registered users, or a notification in your app are all acceptable methods. The key is that the notification is visible and timely.
Maintain a version history with dates. This shows the DPC (and your users) that you actively manage your privacy obligations. An annual review is good practice even if nothing has changed, as it demonstrates accountability.
If your business has a data processing agreement with third-party processors, review those agreements alongside your privacy policy to ensure consistency.
Please note: Updating your privacy policy without notifying users of material changes can itself be a transparency violation under the GDPR.
What are the most common privacy policy mistakes?
Irish businesses, especially smaller ones, tend to make the same privacy policy errors:
- Copy-pasting a US-style policy: American privacy policies reference state laws and omit GDPR requirements. They will not protect you.
- Missing legal bases: Stating that you process data without specifying the legal basis for each purpose is a breach of Article 13.
- Failing to list third-party processors: If you use Google Analytics, Mailchimp, Stripe, or any external service that handles personal data, your policy must reference them.
- Hiding the policy: Your privacy policy must be easily accessible. A link buried three clicks deep in a submenu does not meet the "easily accessible" standard.
- No retention periods: Saying "we keep your data as long as necessary" is too vague. Specify periods or the criteria you use to determine them.
- Ignoring cookie consent: Relying on implied consent or "by continuing to browse" notices has not been valid since the GDPR came into force.
If your business is building its GDPR compliance framework, fixing your privacy policy is one of the most visible and impactful first steps.
Ready to get your website legally compliant? Open Forest helps Irish businesses draft privacy policies, cookie policies, and terms and conditions that meet GDPR requirements. Get in touch to get your legal pages in order.
Getting your privacy policy right
Your website's privacy policy is one of the most public-facing parts of your GDPR compliance. It tells your customers and the DPC exactly how seriously you take data protection.
We recommend that you start with the required disclosures under Articles 13 and 14, write them in plain language, and keep the policy updated as your business evolves. If you are unsure where to begin, Open Forest can help you build a privacy policy that meets Irish legal requirements and earns your customers' trust.

Laura Ryan is a practising Barrister at the Bar of Ireland. She graduated from the Honourable Society of King’s Inns in 2024, having previously qualified and practised as a Chartered Accountant in a big four accounting firm.













