Skip to main content

Legal

Privacy policy

Last updated September 2026

What we collect

When you register for an event, subscribe to the newsletter, apply to sponsor, or contact us, we collect the details you provide: name, email, organization, job title, and anything you write in a message field.

How we use it

  • To run the event you registered for, including confirmations and logistics.
  • To share registered attendee details (such as name, organization, role, and contact information) with sponsors of that event, as part of running the event and the sponsorship arrangement. You confirm this when you register.
  • To send newsletter and other marketing emails about Multiomics Mixer events and related community updates. You can unsubscribe from any marketing email via the link in the message.
  • To respond to sponsorship and contact enquiries.
  • To understand aggregate community composition for planning and reporting.
  • To measure how the public site is used in aggregate (popular pages, buttons, and sponsor profile interest), so we can improve events and the website. This is not used to tell sponsors which individual viewed their page.
  • To measure engagement with marketing emails we send (such as whether a message was opened or a link was clicked), so we can improve content and see who is interacting with our outreach. This is tied to the email address on the message, not sold to third parties.

What we do not do

We do not sell attendee lists as a product, and we do not share your details with unrelated third parties for their own marketing outside the event sponsorship context described above.

Legal basis

We process registration data to fulfill your request to attend an event and, where required, based on the consent you give at registration for sponsor sharing. Marketing emails may go to people who registered for an event, subscribed to the newsletter, applied to sponsor, or contacted us; every marketing message includes an unsubscribe link. Transactional emails (RSVP confirmations, password resets, and similar) are separate. You may withdraw consent or ask us to stop certain uses by contacting us or using unsubscribe; withdrawing does not affect processing already completed for a past event.

Retention and your choices

You can unsubscribe from marketing emails via the link in any campaign message, or ask us to delete or correct your details by contacting us. We keep registration records for as long as needed to run and account for the events you attended.

Cookies and analytics

We use first-party, cookieless analytics stored in our own database: page views, button clicks, and outbound sponsor-link clicks. Events are tagged as anonymous, attendee, or sponsor when you are signed in, using your account role — not your name or email. A temporary random session id lives in the browser only for that tab, so we can count unique visits without identifying you. Admin pages are not recorded. You can use the site fully if this insert fails; it is not required to register or apply.

We also use Google Analytics 4 (GA4) on public pages to understand aggregate traffic and engagement. GA4 may set cookies or use similar storage and receive technical signals such as page URL, approximate location derived from IP, device, and browser information. We do not use advertising pixels or session replay. Admin and auth pages are excluded from GA4, same as our first-party analytics. See Google’s Privacy Policy (opens in a new tab) for how Google processes this data.

Sponsors and hosts may share short first-party campaign links (for example /r/…). Opening one records an opaque click against that campaign and may store a first-touch campaign id in your browser for about 30 days so a later RSVP can be counted toward that link. Sponsors see aggregate click and RSVP counts only — not who clicked or who registered through their link. Named guest lists remain under separate attendee-list delivery rules.

Public contact, mixer RSVP, and email/password account signup use Google reCAPTCHA v3 (an invisible spam check) when it is configured. That loads a Google script on those pages only and may send technical signals such as IP address and browser data to Google to score the submission. It is not used for advertising. Google/Apple sign-in is not scored by this check. See Google’s Privacy Policy (opens in a new tab) and Terms (opens in a new tab).

Contact

Questions about your data? Use the contact form and choose "Something else".