Official form guide
The WRC Form C – Cookie Policy is a template used by employers to disclose their website cookie practices to staff and the public. It is required when a workplace’s online portal or intranet uses tracking cookies.
Need help with Form C?
Open it in the AI Editor for field guidance, checks, and PDF export.
Form Overview
The WRC Form C – Cookie Policy is a template used by employers to disclose their website cookie practices to staff and the public. It is required when a workplace’s online portal or intranet uses tracking cookies.
Plain English
If your company runs a website or internal system that drops cookies on users’ browsers, you need to fill out this form. It records what cookies are used, why, and how people can opt‑out. Think of it as the official Irish version of a privacy notice for cookies.
Submission Date
AI co-pilot
Form selector
Collecting employee personal data
Required for processing sensitive data
✓ Verify if DPIA already exists
Form A – Data Protection Impact Assessment
Running a public recruitment portal
Different compliance focus
✓ Check recruitment advertising rules
Form B – Online Recruitment Notice
Introducing a new employee monitoring system
Covers surveillance, not cookies
✓ Confirm monitoring justification
File the form before the site goes live or within 14 days of adding a new cookie.
Field map
Complainant
1 items
Your name, address and contact details.
Employer
1 items
The employing entity as it appears on your contract or payslip, not a trading name.
Employment
1 items
When the employment started and ended, and what you did.
Complaint
2 items
The employment right or Act the complaint is brought under.
The events and their dates — these show the complaint is within the time limit.
Evidence
1 items
Contracts, payslips and correspondence that back up the complaint.
Almost done reviewing the fields?
Fillable formOpen in Editor->Form C is the latest version as of 2024‑2025. No major revisions have been announced for 2026.
Quick Facts
Downloads & source
Mixing up Form C with the general Data Protection Impact Assessment.
Leaving the signature block blank or using an unauthorized signatory.
Uploading a non‑PDF/A version and receiving a rejection.
Listing only the main cookie and omitting third‑party trackers.
Using an old version of the form that lacks the new manager field.
Assuming the same form covers mobile apps.
Forgetting to update the form after a minor site redesign.
Source transparency
BrieflyGo links to and explains official public form sources. We are not a government agency, and this page is for general form guidance, not legal advice.
Review risky clauses in plain English, fix the document, and keep it moving toward signature.