Cookie Policy

What Cookies Are

Cookies are small text files that a website stores on your device when you visit. They let us remember preferences, keep you signed in, and understand how the platform is being used so we can make it better. This policy also covers local storage, session storage, and similar technologies that behave like cookies.

How We Use Cookies

EventLinqs (operated by Lawal Adams trading as EventLinqs, ABN 30 837 447 587, PO Box 141, Newcomb VIC 3219, Australia) sets cookies where they are essential: keeping your session secure, completing checkout, remembering a few interface preferences, and preventing abuse. Our own traffic measurement is cookieless (see below), so no cookie is set to count a page view. We never sell cookie data.

We also ask, once, whether you are willing to let us load two further kinds of measurement: product analytics, which show us where people give up on a form so we can fix it, and advertising measurement, which tells us which of our own adverts brought an organiser here. Neither loads until you say yes.If you say no, nothing is requested, nothing is stored, and the platform works identically: buying a ticket and running an event are unaffected either way. Your answer is remembered in a first-party cookie (el_consent) that records the choice and nothing else, so we do not have to keep asking.

Cookie Categories

EventLinqs sets the following first-party cookies. The last two categories are set only if you agree to them.

• Strictly necessary. Authentication, checkout session, CSRF protection, and abuse prevention such as rate limiting. These cannot be disabled because login, ticket purchase, and basic security will not work without them. Examples: sb-access-token, sb-refresh-token.
• Preferences. A small number of first-party cookies that remember interface choices, such as your chosen browsing city (el_city), currency, or list-vs-map view. Clearing them only resets those choices; everything still works.
• Product analytics, only if you agree. PostHog, which records which steps of a form people reach so we can see where the platform is failing them. It is not loaded at all until you accept, and saying no leaves nothing behind.
• Advertising measurement, only if you agree.Google Analytics 4, Google Ads and the Meta pixel, which tell us which of our own adverts brought an organiser to the platform. These are the ones that can recognise you on other sites, which is why they are in their own category and why they are off until you say otherwise. None is loaded until you accept.

Our own traffic measurement is handled cookielessly by Plausible (see below), so no cookie is set for it and it is outside the question above: it stores nothing on your device and cannot recognise you anywhere else. Payment fraud screening on the checkout page is performed by Stripe under its own cookies, described under Third-Party Cookies.

You can change your mind at any time by clearing theel_consent cookie in your browser, which brings the question back on your next visit.

Third-Party Cookies

A small number of our partners set their own cookies when their features are used on EventLinqs:

• Stripe sets cookies on the checkout page for payment security and fraud screening. These are required for card payments to complete.
• Supabase sets session cookies when you are signed in. These are first-party to .eventlinqs.com.
• Plausible Analytics (see the next section for the full details) is cookieless by design - no cookies are set on your device for analytics.

Analytics (Plausible)

EventLinqs uses Plausible Analytics, a privacy-friendly analytics service based in the European Union, to understand which pages people visit and how features are used. We chose Plausible specifically because it respects our attendees and organisers.

• Plausible does NOT use cookies and does NOT track you across websites. No fingerprinting, no shadow profile.
• Plausible only counts aggregated, anonymised page views and events on eventlinqs.com. We see counts and trends, not individual people.
• Data is processed in the European Union under GDPR compliance. No data is sold, shared with advertisers, or used to build an advertising profile.
• Plausible's public privacy statement is at plausible.io/privacy and their data policy at plausible.io/data-policy.

Alongside page views, we track a small set of named conversion events: viewing an event, starting checkout, completing a purchase, saving an event, searching, and organisers signing up. These events let us improve the product. They carry only non-identifying metadata (e.g. event id, category, city, price range). They never carry your name, email, or payment details.

Your Choices

You can clear or block cookies in your browser at any time. Clearing them will sign you out and reset your preferences. Blocking strictly-necessary cookies will prevent login and checkout from working. Browser help pages:

• Chrome, Firefox, Safari, Edge.

Changes to this Policy

We'll update this page when our cookie use changes. The “last updated” date at the top will always reflect the most recent revision. Material changes will also be announced in-app.

Contact

Questions about cookies or how we handle your data? hello@eventlinqs.com.