How NAIAQ uses cookies and similar technologies.
This Cookie Policy explains how NAIAQ uses cookies, local storage, session storage and similar technologies on our website, dashboards and future app-related services.
Introduction
This Cookie Policy should be read together with our Privacy Policy. The Privacy Policy explains how NAIAQ collects, uses, stores and protects personal data.
Cookies and similar technologies can be used to keep the platform secure, keep users signed in, remember preferences, process payments through third-party services, understand how the website is used and support future marketing or analytics features.
What cookies and similar technologies are
A cookie is a small text file placed on a device when someone visits a website. Similar technologies include local storage, session storage, pixels, SDK storage, device identifiers and browser-based tokens.
Some technologies are required to provide a secure online service that the user has requested. Others, such as analytics or marketing technologies, may require consent before they are used.
Does NAIAQ use cookies?
Yes. NAIAQ uses cookies, local storage and similar technologies for essential platform functions and, on public pages, consent-gated analytics.
Even if a specific browser item is stored as local storage rather than a traditional cookie, Irish/EU cookie rules can still be relevant where information is stored on or accessed from a user’s device. For example, NAIAQ uses authentication sessions, security checks, Stripe checkout, support/contact flows and cookie preferences. Google Analytics 4 is loaded on supported public pages only after analytics consent is granted.
Strictly necessary or security-related technologies support sign-in, account access, MFA, staff/admin/provider dashboards, form protection, payment redirects and user preferences. The analytics consent choice is stored in the browser until it is withdrawn, browser storage is cleared or the policy version changes.
Types of cookies and similar technologies we may use
| Category | Purpose | Examples | Consent position |
|---|---|---|---|
| Strictly necessary | Needed for the website, dashboards, account access, security, fraud prevention, form submission, MFA and core platform functions. | Supabase authentication/session storage, CSRF/security tokens where used, cookie preference storage, staff/admin/provider dashboard session handling. | May be used without consent, but users must be told about them. |
| Payment and checkout | Needed to start, complete, secure and verify payment or subscription flows. | Stripe checkout/session and fraud-prevention technologies. | Strictly necessary where used to provide payment checkout requested by the user. Stripe may also set its own cookies under its own policies. |
| Preference and functional | Used to remember choices such as cookie preferences, interface preferences or user-selected settings. | Cookie consent choices, saved UI preferences, dashboard display preferences where implemented. | Consent may be required unless the storage is strictly necessary for a requested setting or service. |
| Analytics | Used to understand traffic, page usage, feature use, errors and platform performance. | Google Analytics 4 on supported public pages after consent; Google may set identifiers such as _ga and _ga_* when analytics is accepted. | Used only with consent where required. |
| Marketing | Used to measure campaigns, understand referrals or show relevant advertising. | Marketing pixels, ad conversion tags or retargeting pixels if enabled later. | Used only with consent where required. |
Third-party services
NAIAQ may use trusted third-party services to operate the platform. These providers may use cookies or similar technologies when their services are loaded or used.
- Supabase: authentication, account sessions, database, storage and Edge Function infrastructure.
- Stripe: provider subscriptions, checkout, payment security and fraud prevention.
- Email providers: transactional emails, admin/staff invites, MFA codes and service notifications.
- Google Analytics: public-site usage measurement, loaded only after analytics consent. Marketing/advertising storage remains disabled in the current consent configuration.
- Content delivery networks: delivery of scripts, fonts, styling, icons or static assets where used.
Third-party providers may process data under their own terms and privacy/cookie policies. NAIAQ reviews third-party tools before use and aims to avoid unnecessary tracking.
Your cookie choices
Where non-essential cookies or similar technologies are used, NAIAQ will ask for consent before using them where required. You should be able to accept, reject or manage non-essential cookies without losing access to the core platform.
You can also control cookies through your browser settings. Blocking strictly necessary cookies or storage may stop parts of NAIAQ from working, including login, dashboards, MFA, checkout, job posting, job tracking and account security features.
You can reopen Cookie settings from the public-site footer to accept or withdraw analytics consent. Withdrawing consent stops future analytics loading and attempts to remove NAIAQ-domain Google Analytics cookies. Marketing cookies are not enabled by the current public-site consent configuration.
Changes to this Cookie Policy
We may update this Cookie Policy when we add or remove cookies, introduce new platform features, change third-party services or need to respond to legal or technical developments.
When changes are material, we may notify users through the website, dashboard, email or another appropriate method.
Contact
Questions about this Cookie Policy or NAIAQ’s use of cookies and similar technologies can be sent to support@naiaq.ie.