Privacy & legal notices

Imprint (Swiss LCD art. 3), zero-tracking static architecture, licence payment and activation data, and responsibility boundaries under the Swiss FADP.

  • Zero cookies · Zero trackers
  • Swiss FADP and imprint

Reviewed: 2026-11-11

Who is responsible

The publisher, postal address, contact address and VAT note are shown in the legal details at the top of this page.

What this website collects

This website is built as pure static HTML, CSS, and minimal progressive enhancement scripts:

  • No cookies and no analytics: The site sets no cookies and has no analytics or advertising scripts. Fonts are self-hosted with the site bundle.
  • No user accounts, and no runtime calls (D8): Customer EmDash sites never call this website. Eventual RSVP – Tickets checks its licence key offline with Web Crypto on each site itself; it contacts our licence service only when an administrator activates, refreshes or deactivates the licence (see below).
  • Hosting logs: Whoever hosts these static files may keep transient web-server logs (IP address, request path, status code) for reliability and abuse prevention.

Buying a licence

  • The site itself: The page you are on sets no cookies. The Pricing page loads a script from Paddle only when you start a purchase, by focusing the licence form or pressing its button.
  • Paddle handles the payment: Paddle is our reseller and merchant of record. It takes the payment as an independent controller under Paddle’s privacy policy and may set cookies inside its payment window.
  • What we receive from Paddle: the buyer’s name, email address and country, the business name if you buy as a business, and the licence bought. We use them to email your licence code, answer support questions and send a renewal reminder.
  • Activating a site: when an administrator clicks Activate, Refresh or Deactivate on the Tickets page, the site sends our licence service (licences.vermeulen.solutions, a Cloudflare Worker) the licence code and the site’s hostname, and nothing else. We record which hostnames are active on each licence, to count sites and moves. We store a one-way hash of each code, not the code itself.
  • Retention: the licence record (purchase, email address, name, activated hostnames) is kept for the period shown in the legal details at the top of this page.
  • The plugins report nothing to us: Eventual RSVP – Core, Eventual RSVP – Registrations and Eventual RSVP – Tickets run on your own EmDash site. Core and Registrations never contact us; Tickets contacts the licence service only on the administrator clicks described above, never about visitors, attendees or orders.

Visitor and attendee data on customer EmDash sites

Eventual RSVP – Core, Eventual RSVP – Registrations, and Eventual RSVP – Tickets run inside your own EmDash installation:

  • Data stays on your host: Event registrations, custom question answers, waiting lists, ticket orders, and QR check-ins stay in your EmDash SQLite/D1/Turso database, never on Vermeulen Solutions infrastructure.
  • Your role as organiser / controller: When you collect registrations or sell tickets, your organisation is the data controller vis-à-vis visitors and attendees under the Swiss FADP, EU GDPR, or your local data protection law.
  • Built-in FADP/GDPR tools: Both Registrations and Tickets include configurable retentionDays (30–3650 days, 365 default), hourly anonymisation sweeps that preserve anonymised place counts and statutory order bookkeeping amounts, IP-rate-limit hashing (ipHash), and admin email lookup and erasure controls.
  • Open-source components: Eventual RSVP – Core, Eventual RSVP – Registrations, and eventual-capacity are published under the MIT License without warranty.