NightHall notifies an organizer thirty days before adding one, and the organizer may object and end the agreement if they cannot accept it. The list below is that notice, written once. Where a provider's own terms leave a question open, the row says so rather than resolving it in NightHall's favour.
Where: European Union.
What: Takes a buyer's money against the organizer's connected account, and collects NightHall's platform fee on the same charge.
Data: Buyer name, email address, payment instrument, order reference.
Agreement: Data processing agreement with Stripe Payments Europe, Ireland.
Where: Frankfurt, Germany.
What: Delivers every transactional message through Amazon SES, and holds the encrypted database backups and the archived write-ahead log within Amazon S3.
Data: Recipient name and address and message content for a message, including a ticket code; the whole database, as ciphertext, for a backup.
Agreement: Data processing agreement with Amazon Web Services EMEA SARL, Ireland, under the AWS GDPR terms.
Where: European Union.
What: Signs people in and holds passwords and second factors. Buyers sign in there as well as organizers, so their details reach it too.
Data: Account email address, name, and sign-in metadata.
Agreement: Data processing agreement with the identity provider, European region.
Where: European Union.
What: Runs the machines. PostgreSQL runs on the primary machine rather than on a managed database, which is why one host holds everything.
Data: Everything the platform holds.
Agreement: Data processing agreement with the hosting provider.
Where: Worldwide edge network.
What: Serves this site, resolves the domain name, terminates TLS, and applies the bot check at checkout.
Data: An address in transit at the edge. This site sets no cookie and runs no analytics.
Agreement: Data processing agreement with Cloudflare. On the free plan Cloudflare performs edge processing outside the European Union, and that is stated here rather than left for an organizer to discover.
Where: European region.
What: Receives counters, durations and trace identifiers over OTLP. Log lines are not sent there.
Data: No personal data. No contact value appears in any metric.
Agreement: Data processing agreement with Grafana Labs.
Where: Outside the European Union.
What: Polls the public status endpoints from outside and pages the on-call rotation.
Data: None. It reads a status endpoint that carries no personal data.
Agreement: Not a processor of personal data.
Where: European Union.
What: Confirms an organizer's VAT registration before NightHall starts selling for them.
Data: The organizer's VAT number and legal name. No buyer data.
Agreement: A public registry. It holds no personal data of a buyer.
Where: European Union, when enabled.
What: Drafts event text, support replies and run sheets for an organizer to approve. Not enabled for a region outside the European Union: the deployment refuses to start without one.
Data: An order summary, and a buyer's message where a support reply is drafted.
Agreement: Under review. The feature is refused at startup without a European region, and the agreement is not signed until it is.
No analytics product, no session recorder, and no customer messaging tool. Each would be a processor of buyer data for a benefit NightHall can get from its own records. Error tracking runs on NightHall's own second host rather than being bought, so a stack trace does not become somebody else's copy.
A provider that is not on this page is a deployment that refuses to start. The names the code accepts for the sending path are the ones an organizer authorises against. Anything else is not a weaker option but an option that stops the deployment.
