Cookie Policy

This policy explains how we use cookies and similar technologies on the Add to Event Platform at addtoevent.co.uk. It should be read alongside our Privacy Policy, which sets out how we handle personal data more broadly.

Cookies are small text files that websites place on your device when you visit them. They let the site recognise your device on later visits, remember your preferences, and understand how the site is being used. Similar technologies like pixels, tags, and local storage work in much the same way and are covered by this policy.

We group the cookies we use into four categories:

Strictly necessary cookies

These are needed for the Platform to work, for example to keep you logged in, remember items in a Quote Request, or protect against security risks. The Platform will not function properly without them.

Performance cookies

These help us understand how visitors use the Platform so we can improve it, for example by measuring which pages are most visited.

Functional cookies

These remember your preferences and personalise your experience.

Marketing cookies

These are used by us and our advertising partners to show you relevant ads on other sites and to measure how our marketing performs.

Our cookie banner appears when you first visit the Platform. You can withdraw your consent at any time by clicking Withdraw your consent.

You can also manage cookies through your browser settings. The exact steps vary by browser, but most browsers let you block or delete cookies. Note that blocking strictly necessary cookies may stop parts of the Platform from working.

We update this policy from time to time. The "Last updated" date at the top shows when it was most recently revised. The cookies list below updates automatically as cookies are added or removed.

If you have any questions about this policy or how we use cookies, please email our data protection team at data@addtoevent.co.uk.

The list below shows the cookies in use on the Platform, including their provider, purpose, and how long they last. It is generated automatically and updated as cookies are added or removed.

That automatic list is built by scanning our public pages, so it can't sign in and doesn't include cookies that only apply once you're logged into the supplier app (app.addtoevent.co.uk) or organiser app (organiser.addtoevent.co.uk). Those are listed here instead, under the same categories described above:

Strictly necessary (supplier and organiser apps)

• ate_uid — identifies your logged-in account. Set for about 30 days.
• authentication, firebase:authUser and firebase:host (browser storage, not cookies) — hold the sign-in token issued by Firebase, our authentication provider.

Functional (supplier and organiser apps)

• ate_uuid and ate_role — your account's unique ID and whether you're signed in as a supplier or an organiser, used for analytics and routing. Set for about 30 days.
• intercom-device-id and intercom-session — used by Intercom, our support chat widget. Set for up to about 9 months and 1 week respectively.
• pfruits_page_loaded_at and productfruits_cnt_loaded (browser storage, not cookies) — used by ProductFruits to time the onboarding tips shown to suppliers.