This Cookie Policy explains how CRI Ireland uses cookies and similar local-storage technologies. A cookie is a small piece of information stored by a browser. Some cookies are necessary for a website to work; others may be used for measurement or preferences.
Essential cookies
Essential cookies can support security, WordPress functions, form submissions, account sessions and saved consent preferences. Because these functions are required to provide the service requested by the visitor, the site may need them even when optional analytics are declined.
Optional analytics
Where analytics is enabled, it can help CRI understand which directory pages are useful, which searches lead to results, how pages perform and where technical improvements are needed. Optional analytics should respect the preference selected in the consent banner.
Your first visit
On a first visit, CRI displays a cookie-preference banner. Visitors can accept all available categories, choose essential cookies only, or open the settings panel. The choice is stored so the banner does not need to interrupt every page view.
Changing your choice
A Cookie settings control is displayed on the site so a visitor can reopen the preference panel. Clearing browser storage or cookies may also remove the saved preference and cause the consent banner to appear again.
Third-party services
If advertising, analytics, embedded services or other third-party functionality is added, this policy should be updated to identify the relevant purpose and consent category. CRI should not describe a third-party technology as active unless it is actually configured on the production site.
Questions
Contact CRI Ireland if you have a question about the site’s cookie categories or consent controls. For broader personal-data information, read the Privacy Policy.
How consent is recorded
The CRI consent interface records the visitor’s selected preference in browser storage and a first-party preference cookie so the website can remember whether optional categories were accepted. The consent preference itself is not intended to identify a visitor by name. If browser storage is cleared, private browsing is used or a different device is opened, the website may need to ask for a preference again.
Essential functionality
Some website functions cannot reasonably operate without essential storage. Examples can include security tokens used to prevent forged form submissions, WordPress session cookies for authenticated users, load-balancing or security cookies, and the cookie that remembers the consent choice itself. Declining optional analytics should not prevent a visitor from searching the directory or reading public pages.
Analytics configuration
If analytics is enabled on the production website, CRI should configure it to respect the consent state. Optional analytics code should not be treated as essential merely because it is useful to the site owner. The purpose of analytics is to understand aggregate site usage, improve search and navigation, identify performance problems and measure whether directory pages are useful.
Advertising and third-party cookies
If CRI later enables an advertising platform that stores or reads cookies for measurement, personalisation or advertising purposes, the cookie banner and this policy should be updated to describe the relevant category. Advertising technology should be loaded only in a way that is consistent with the applicable consent requirement and the configuration actually used on the live site.
Browser controls
Most browsers allow users to view, block or delete cookies. Blocking all cookies at browser level can affect login sessions, forms and other essential functions. CRI therefore provides its own consent interface so visitors can distinguish essential functions from optional analytics rather than relying only on a blanket browser setting.
Keeping this policy current
Cookie technology changes when the site owner adds or removes analytics, advertising, account or security services. The production site should periodically review the cookies actually set in a clean browser session and update this policy when the active configuration changes.