This article is for founders, CEOs, and compliance officers of early‑stage Irish startups who need to meet GDPR requirements from day one.
You will gain a practical six‑step checklist that shows you how to map data flows, choose lawful bases, create required policies, manage vendors, prepare for breaches, and handle data‑subject rights requests, enabling you to build a defensible GDPR baseline for your business.
Key Takeaways
- GDPR compliance is required from day one for Irish startups, and non‑compliance can jeopardise funding and attract hefty fines.
- Start by mapping all data flows, documenting what personal data is collected, why, where it is stored, who accesses it, and any transfers outside the EEA.
- Identify the correct lawful basis for each processing activity—consent, contractual necessity, or legitimate interests—and document it, especially avoiding over‑reliance on consent.
- Implement essential policies and notices, including external and employee privacy notices, a cookie policy, and a data retention schedule, tailored to your specific processing.
- Prepare for data breaches with a response plan, breach register, and proportionate security measures, and ensure you can meet the 72‑hour DPC notification requirement.

If you're building a startup in Ireland, GDPR compliance isn't something you can push to "later." The General Data Protection Regulation applies to every company that processes personal data of EU residents, regardless of size, revenue, or how early-stage the business is. The Irish Data Protection Commission (DPC) has made that position clear through enforcement actions totalling over €4 billion in fines since 2018, largely in cross-border cases involving major tech companies.
This checklist breaks GDPR compliance into six practical steps. Each one maps to a specific obligation under the regulation, and together they form a baseline that any Irish startup can implement from day one.
Why does GDPR matter from day one?
GDPR compliance is not a growth-stage problem. It applies the moment your startup collects a customer's email address, tracks a website visitor with analytics, or stores employee records in a spreadsheet.
The DPC's expectations for early-stage companies are proportionate but real. You won't be expected to have a full-time Data Protection Officer on day one, but you will be expected to know what personal data you hold, why you hold it, and on what legal basis.
Non-compliance creates risks beyond fines. Investors routinely review data protection practices during due diligence. A startup without basic GDPR documentation raises red flags that can delay or derail a funding round.
In practice, this means: If you're processing personal data (and you almost certainly are), GDPR compliance should be part of your company setup, not an afterthought.
Building privacy into your product and operations from the start is both a legal requirement under Article 25 (data protection by design and by default) and a practical advantage. Retrofitting compliance into a product that wasn't designed with privacy in mind is far more expensive than getting it right early.
Step 1: How do you map your data flows?
A data flow map is a record of every type of personal data your startup collects, where it goes, and who can access it. Under Article 30 of the GDPR, most controllers are required to maintain a Record of Processing Activities (ROPA), because their processing is continuous rather than occasional. Even where the strict exemption might apply, the DPC expects you to understand and document your data landscape.
Start by listing the personal data you collect across three categories:
- Customers and users: names, email addresses, payment details, usage data, IP addresses, device identifiers
- Employees and contractors: names, PPS numbers, bank details, performance records, health information
- Leads and marketing contacts: email addresses, form submissions, cookie data, analytics identifiers
For each category, document:
- What personal data you collect
- Why you collect it (the purpose)
- Where it's stored (which systems and tools)
- Who has access (internal teams and external processors)
- How long you keep it
- Whether it's transferred outside the EEA
This doesn't need to be complicated. A spreadsheet works for most startups. The point is to have a single, maintained record that you can produce if the DPC asks, or when an investor requests it during due diligence preparation.
Step 2: What lawful basis applies to each processing activity?
Every processing activity needs a lawful basis under Article 6 of the GDPR. There are six options, but most Irish startups rely on the following three:
- Consent — the individual has given clear, informed, and freely given agreement. Required for marketing emails under ePrivacy rules and for non-essential cookies. Consent must be as easy to withdraw as it is to give.
- Contractual necessity — processing is necessary to perform a contract with the individual. This covers most customer data: you need their delivery address to ship a product, their email to send account notifications.
- Legitimate interests — processing is necessary for a purpose that doesn't override the individual's rights. This is the most flexible basis but requires a documented balancing test. The DPC fined LinkedIn €310 million in October 2024 partly for failing this test and partly relating to unlawful processing for targeted advertising.
Two common mistakes to avoid:
- Defaulting to consent for everything. Consent can be withdrawn at any time, which means your legal basis disappears. If contractual necessity or legitimate interests apply, use them instead.
- Using legitimate interests without documentation. If you can't produce a written Legitimate Interests Assessment showing you considered the individual's rights, the basis won't hold up under DPC scrutiny.
For special category data (health information, biometric data, political opinions), you need an additional condition under Article 9. Most startups should avoid collecting this data unless strictly necessary.
Step 3: What policies and notices do you need?
As of March 2026, every Irish startup processing personal data should have these documents in place:
External privacy notice: tells customers and website visitors what data you collect, why, on what basis, how long you keep it, and how they can exercise their rights. This must be written in clear, plain language. The DPC specifically flags overly legalistic privacy notices as a compliance failure.
Employee privacy notice: covers the same ground for your team. Even a two-person startup with employees needs one.
Cookie policy: required under the ePrivacy Regulations (S.I. No. 336 of 2011). Non-essential cookies need consent before they're placed. Analytics cookies, marketing pixels, and session replay tools all fall into this category.
Data retention policy: defines how long you keep each type of data and when it gets deleted. "We keep everything forever" is not a valid retention policy under GDPR. Your document retention obligations under Irish company law should inform the minimum periods, but GDPR requires you to delete data once the purpose for holding it has expired.
If your startup has a website, your terms and conditions should complement your privacy notice but not replace it. They serve different legal purposes.
Author's tip: Start with templates and adapt them to your actual processing activities. A generic privacy notice copied from another company's website won't satisfy the DPC's specificity requirements, and it won't protect you in a complaint.
Step 4: How do you manage vendors and processors?
If you use any third-party tool that touches personal data, whether that's a CRM, email marketing platform, analytics tool, cloud hosting provider, or payroll software, you're likely sharing personal data with a data processor. Under Article 28 of the GDPR, you need a Data Processing Agreement (DPA) with each one.
A DPA sets out:
- What data the processor handles and for what purpose
- The processor's security obligations
- What happens to the data when the contract ends
- Sub-processor arrangements and notification requirements
Most SaaS providers have a standard DPA available on request or already published on their website. We recommend that you review it, rather than just accepting it. Pay attention to sub-processor lists and international transfer mechanisms.
International transfers deserve specific attention. If your processor stores data outside the EEA, and many US-based tools do, you need an appropriate transfer mechanism in place. Standard Contractual Clauses (SCCs) are the most common solution. The EU-US Data Privacy Framework covers some US companies, but only those that have self-certified.
The DPC fined TikTok €530 million in May 2025 relating to concerns about international data transfers and access to EU user data. The rules on international transfers are actively enforced.
Step 5: Are you prepared for a data breach?
A personal data breach is any security incident that leads to the accidental or unlawful destruction, loss, alteration, or unauthorised disclosure of personal data. Under Article 33 of the GDPR, you must notify the DPC within 72 hours of becoming aware of a breach that poses a risk to individuals' rights and freedoms.
For startups, the practical requirements are:
- Know what counts as a breach. A lost laptop with unencrypted customer data is a breach. An employee emailing a spreadsheet of customer details to the wrong person is a breach. A ransomware attack is a breach.
- Have a response plan. Document who does what when a breach is discovered. Who assesses the severity? Who notifies the DPC? Who communicates with affected individuals? In a small team, this might be the same person, but write it down.
- Maintain a breach register. Record every breach, even ones you don't report to the DPC. The register should include what happened, the data affected, the timeline, and what you did about it.
- Implement proportionate security. The GDPR doesn't prescribe specific technologies, but it expects measures appropriate to the risk. For most startups, this means access controls (don't give everyone admin access to everything), encryption (at rest and in transit), regular backups, and multi-factor authentication.
Please note: The 72-hour notification clock starts when you become "aware" of the breach, not when you've finished investigating it. Report what you know to the DPC and supplement the notification later as your investigation progresses.
Step 6: How do you handle data subject rights requests?
Data subjects have specific rights under the GDPR, and your startup must be able to respond when someone exercises them. The most common requests you'll receive are:
- Right of access (Article 15): the individual wants a copy of their personal data
- Right to erasure (Article 17): the "right to be forgotten," requesting deletion of their data
- Right to data portability (Article 20): requesting their data in a machine-readable format
You have one month to respond to any rights request. That deadline can be extended by two months for complex requests, but you must tell the individual about the extension within the first month.
Build a simple process:
- Designate someone to receive and log requests
- Verify the requester's identity before disclosing any data
- Search all your systems for the individual's data (this is where your data flow map from Step 1 pays off)
- Respond within the deadline
As your startup grows, consider how your product architecture supports these rights. Can you actually find and delete all of a user's data across your systems? If not, that's a compliance gap worth addressing before it becomes a problem.
Open Forest helps Irish startups build compliance frameworks that work from day one. Talk to us about a GDPR readiness assessment tailored to your stage and sector.
Train every team member who handles personal data on the basics: what a rights request looks like, who to escalate it to, and why the deadline matters. The DPC has made clear that lack of internal awareness is not an acceptable excuse for any missed response deadlines.
Your GDPR compliance starting point
GDPR compliance for an Irish startup is not about perfection on day one. In our experience, it's about building a defensible baseline: know your data, have a lawful basis for processing it, document your decisions, and be ready to respond when something goes wrong or someone asks a question.
The six steps in this checklist cover the core obligations. They're not the entire regulation, but they address what the DPC expects from an early-stage company operating in Ireland.
If you're unsure where your startup stands, Open Forest can help you assess your current position and build a GDPR compliance framework that grows with your business.

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.













