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 only where they are essential: keeping your session secure, completing checkout, remembering a few interface preferences, and preventing abuse. Our analytics are cookieless (see below), so no cookie is set to measure usage. We do not use cookies for advertising, we do not track you across other websites, and we never sell cookie data. Because we set no tracking or advertising cookies, no cookie consent banner is required.

Cookie Categories

EventLinqs sets only the following first-party cookies. There is no advertising, cross-site tracking, or analytics cookie category.

• 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.

Analytics is handled cookielessly by Plausible (see below), so no analytics cookie is set on your device. Payment fraud screening on the checkout page is performed by Stripe under its own cookies, described under Third-Party Cookies.

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.