Cookie notice
Version 1.1, published 22 November 2026.
Version 1.1. Last updated 22 November 2026.
This notice explains the cookies and similar technologies Engage by Elements uses, run by Elements Marketing & Communications LTD, Kilkenny, Ireland.
1. The short version
Engage sets only cookies and device storage that are strictly necessary to provide the service you ask for, such as keeping you signed in. It uses no advertising, tracking, social media or third-party analytics cookies, and loads no third-party scripts. That is why there is no cookie banner: the law does not require consent for strictly necessary cookies, and Engage has nothing else to ask you about.
Pages you visit without signing in, including the website and survey pages, set no cookies at all. The sign-in page sets a cookie only once you start to sign in: each one is short-lived and listed in section 3.
2. The law
Under Regulation 5 of the European Communities (Electronic Communications Networks and Services) (Privacy and Electronic Communications) Regulations 2011 (S.I. No. 336 of 2011), and the Privacy and Electronic Communications Regulations 2003 in the UK, storing or reading information on your device needs your consent unless it is strictly necessary to provide a service you have asked for. Everything Engage stores on your device falls into that exemption.
3. What Engage stores on your device
All cookies below are first party, set by Engage itself. Each is marked Secure, HttpOnly and SameSite=Lax, so it is sent only over HTTPS, cannot be read by scripts and is not sent when another site links to Engage. In production every sign-in cookie name starts with `__Secure-`.
| Name | Type | What it does | How long |
|---|---|---|---|
| `__Secure-engage.session_token` | Cookie | Keeps you signed in. It holds a random session reference, not your details, and is checked against our database on every request | Until you sign out, or up to 7 days after you last used Engage (each visit renews the 7 days). Elements staff sessions last at most 12 hours |
| `__Secure-engage.two_factor` | Cookie | During two-step verification, remembers that you have entered your password while you enter your code or use your passkey | 10 minutes |
| `__Secure-engage.better-auth-passkey` | Cookie | Holds the one-time challenge while you register or sign in with a passkey | 5 minutes |
| `__Secure-engage.staff_session` | Cookie | Only for Elements staff: while a staff member views a customer account to give support, keeps their own staff session so they can return to the console | 60 minutes |
| `engage_staff_refusal` | Cookie | Only for Elements staff: carries the reason a staff sign-in was refused to the sign-in page | 2 minutes |
| `__Secure-engage.state` | Cookie | When you sign in with Microsoft, Google or single sign-on: holds a one-time value that protects the sign-in against forgery while you are on the other company's page | 5 minutes |
| `__Secure-engage.relay_state` | Cookie | The same, for single sign-on that uses SAML | 5 minutes |
| `engage.respond.` followed by part of your survey link | Browser storage on your device, not a cookie | On survey pages only: saves your answers so far, so you can come back to the survey. Nothing is sent to Engage until you submit | Until you submit, or until you clear your browser's site data |
| `engage.compass.` followed by a version reference | Browser storage on your device, not a cookie | In the Culture Compass only: saves your progress in the same way | Until you submit, or until you clear your browser's site data |
When you sign in with Microsoft, Google or your organisation's single sign-on, Engage protects the sign-in against forgery with a one-time value. It is held in the short-lived cookie listed above and checked against our database when you come back.
4. What Engage doesn't use
- No advertising or retargeting cookies.
- No third-party analytics and no third-party scripts. Engage counts how its own features are used on its own servers, from events the application records when something happens, without cookies and without personal details in the records.
- No "remember this device" cookie: two-step verification is asked for on every sign-in.
- No cookies or tracking of any kind on survey pages beyond the progress storage above.
5. Other companies' pages
Some actions take you to pages run by other companies, which set their own cookies under their own notices. Engage does not load these companies' code on its own pages.
- Stripe, when you pay, buy from the shop or manage billing, on checkout.stripe.com and billing.stripe.com;
- Microsoft or Google, when you choose to sign in with them;
- your organisation's identity provider, when you sign in with single sign-on;
- Canva, if you open a kit's Canva template;
- Microsoft Teams or Zoom, when you join a live Elements event from its joining link.
Videos in Engage, including kit videos and recordings of Elements events, are stored by Elements and played in your browser by Engage itself, without a third-party video player, so they set no cookies.
6. Controlling cookies
You can block or delete cookies in your browser settings. If you block the cookies above, you won't be able to sign in to Engage. Clearing your browser's site data also clears any survey progress saved on your device.
7. Changes
If we ever want to use a cookie that isn't strictly necessary, we will update this notice and ask for your consent first.
8. Contact
Email info@elementsmarketing.ie. Our privacy notice explains how we use personal data.