LiveEvent

Subprocessors

The technical providers involved in running the service, what they do, and where they are established.

Why this page exists

A customer of the platform is responsible for their participants' data; the publisher is their processor. The regulation therefore requires their authorisation before engaging other providers, and information about any change. This page is that information: any modification appears in the repository's public history.

What they are allowed to do

Each acts only on instruction, for the stated purpose alone, and may not use this data for its own purposes. None has access to all the data: each sees only what its function requires.

Objecting to a change

If a new provider is added, customers are informed before it goes live. A customer who objects on reasonable grounds may terminate without charge before the effective date.

The list, as of today

  • Supabasetheir policy

    Database, authentication and file storage.

    United Kingdom (London) - adequacy decision

  • Hosting for the application and the public sites.

    United States and European Union

  • Sending transactional emails and campaigns.

    United States

  • Cloudflaretheir policy

    Anti-bot protection on the registration form (Turnstile), video delivery of live streams and replays (Stream), relay for Studio and Meeting video calls (TURN and STUN).

    United States

  • OpenStreetMap Foundation (Nominatim)their policy

    Geocoding for the participant map: only receives a place name - “city, country” - on the organiser’s gesture, never an address nor a person.

    United Kingdom (London) - adequacy decision