Sub-processors

What this list is

heer(ish) processes attendee data for organisers, and engages the companies below to do it. Under the data processing agreement at heerish.app/dpa this list is Annex III to the standard contractual clauses, and your general authorisation covers exactly the recipients named here.

Each is bound by contract to obligations no weaker than the ones heer(ish) owes you, and heer(ish) stays liable to you for what they do.

There are no analytics, advertising or tag-management providers, on any page, so none appear below. Mollie sees organiser billing data only and never touches attendee data.

The sign-in providers an organiser offers on an event (Google, LinkedIn, Apple, or the organiser's own community on Mighty Networks) are not on this list either: heer(ish) does not engage them to process attendee data, and passes them nothing from an event page. An attendee who picks one signs in with them directly, and heer(ish) receives the result. A Mighty Networks community is the organiser's own tool, used under the organiser's own agreement with Mighty Networks.

Nor are the push services that deliver notifications to an attendee's device (Apple's, Google's, Mozilla's or Microsoft's, whichever made the attendee's browser): the attendee's browser chooses that service when they switch notifications on, and heer(ish) does not engage it. What heer(ish) hands it is encrypted for that one device, so the service learns only that a notification was sent to it, and when.

Cloudflare, Inc.

Purpose: hosting and running the application, the databases (D1), photo storage (R2) and outbound email (Email Sending). Everything on an event page passes through Cloudflare.

Personal data: all of it — cards, photos, meetups, uploaded invitee lists, sign-in identifiers, consent records and change logs.

Where it is processed: events on the EU setting are stored in the European Union under a jurisdiction restriction that keeps them there; events on the US setting are stored in the United States, in a database and photo storage created in Cloudflare's eastern North America location, with no jurisdiction restriction behind it. Organiser accounts and organisations are stored in the European Union. Email goes out through the Cloudflare network worldwide, the United States included.

Safeguard: Cloudflare is an American company. Transfers to the United States run on the European Commission's standard contractual clauses (GDPR Article 46(2)(c)), with Cloudflare's EU-US Data Privacy Framework certification as an additional safeguard beside them.

Plus Five Five, Inc. (Resend)

Purpose: the fallback for outbound email. When Cloudflare cannot send a message, because the daily sending limit is reached, sending is rate-limited or Cloudflare reports an internal error, the same message goes out through Resend from mail.heerish.app instead.

Personal data: what that one message carries — the recipient's email address, and their name on an invitation to an event; an invitation to become an organisation's admin names the colleague who sent it, with their email address; the sender name shown on it; the subject and the message itself, sign-in and unsubscribe links included. No card or photo is sent to Resend, and of an uploaded list only the name and address the message is for.

Where it is processed: the United States, where Resend stores message content, delivery logs and account records. Like Cloudflare's email, it is outside the storage region chosen for an event. Resend keeps message content and delivery logs for 30 days after sending, and its backups for 7 days more, so an email sent shortly before an event's deletion date outlives that date by up to 37 days.

Safeguard: Resend is an American company. Transfers to the United States run on the European Commission's standard contractual clauses (GDPR Article 46(2)(c)), incorporated in Resend's data processing addendum, with Resend's EU-US Data Privacy Framework certification as an additional safeguard beside them.

Google LLC and Google Ireland Limited

Purpose: the map on an event page, and the place search behind the lodging field.

Personal data: the text an attendee types into the place search, and the IP address their browser reveals to Google by fetching the map, which on the EU and UK settings happens only once the attendee has agreed to load it. Place searches are proxied through the heer(ish) server, so Google does not see the attendee's device for those. No card data, no photo and no email address is ever sent to Google.

Where it is processed: the European Union and the United States.

Safeguard: standard contractual clauses under the Google Maps Platform terms, with Google's EU-US Data Privacy Framework certification as an additional safeguard beside them. On the EU and UK settings the map does not load at all until the attendee agrees to it.

Mollie B.V.

Purpose: taking payment when an organiser buys a plan.

Personal data: organiser billing data only — the name and address of the organisation, the billing email address, the VAT number where one is given, and the amount. Mollie handles the card or bank details itself; they never reach heer(ish). No attendee data of any kind is sent to Mollie.

Where it is processed: the Netherlands.

Safeguard: none needed. Mollie is a Dutch company and the data stays in the European Union.

How you are told about a change

heer(ish) emails every organiser at least 30 days before adding or replacing a recipient on this list, and the date at the top of this page changes with it.

If you object within those 30 days you can close the events affected before the change takes effect. The refund rule in the terms applies to an event that has not opened.

Questions about this list go to privacy@heerish.app.