Security and data protection
Servers, database and files run at Hetzner in Nuremberg and Falkenstein. Every provider that processes attendee data does so in the EU/EEA — each one listed with its contracting entity and processing location in our DPA. On request we run an event with no provider that has a US parent company; that event then has no online payment and no email sending.
Last reviewed: November 15, 2026
Hosting in Germany
The live system runs in Hetzner’s data centre in Nuremberg, the backups in its data centre in Falkenstein — about 300 km apart, both in Germany. We operate the database and the file storage ourselves on this infrastructure. Hetzner Online GmbH is certified to ISO/IEC 27001:2022 for its hosting services and data centres, both sites included. Quick Event itself holds no certification of its own.
Encryption and access
- All connections use TLS; unencrypted connections are not accepted. Storage media and backups are encrypted.
- Every record belongs to exactly one event, and every query is restricted to that event. Access comes only from owning the event or an explicit invitation to it.
- Sign-in with a password (salted hash, checked against known data breaches), a passkey, or Google or Microsoft. Two-factor authentication is available to every account.
- Platform administration rights apply only in a session started with a passkey or an authenticator code.
- The application connects to the database with a role that has no administrative rights.
Backups with Object Lock
The database is backed up continuously to two separate, encrypted repositories and can be restored to any point within at least the last 30 days. One repository uses Object Lock in compliance mode: for 30 days no one can delete or overwrite a backup, not even with our own keys. Our recovery targets are at most 5 minutes of data loss (RPO) and a restored database within one hour (RTO). In our last restore drill the database was back in under a minute.
Sub-processors
For each provider we state what it does and where the data is processed. The binding list with all contract details is Annex 2 of our data processing agreement and our privacy policy; we announce any change to it in advance.
| Provider (contracting party) | Processing location | Purpose |
|---|---|---|
| Hetzner Online GmbH, Gunzenhausen, Germany | Data centres in Nuremberg and Falkenstein, Germany | Hosting, database, file storage |
| Twilio Ireland Limited (SendGrid), Dublin, Ireland | EU data centres (SendGrid EU Data Residency) | Event emails: confirmations, tickets, invitations |
| Stripe Payments Europe, Limited, Dublin, Ireland | EU/EEA | Payments, only for paid tickets |
| PostHog Cloud EU | EU instance in Frankfurt, Germany | Error monitoring and usage analysis |
| Mistral AI SAS, Paris, France | EU/EEA (France, Sweden, Norway) | All AI features: assistant in the event app, chat on the event page, support assistant, AI drafting and translation for organisers — only when used |
Stripe, Twilio (SendGrid) and PostHog process data in the EU; their parent companies are based in the United States. For events without such providers, see below.
Events without providers that have a US parent company
At the organiser’s request, we run an event in which only Hetzner in Germany processes data. We set this up per event and confirm it in the data processing agreement; it is not a self-service switch.
What such an event does without
- No online payment, so the mode is available only for events without paid tickets.
- No email: guests save their ticket (PDF, Apple Wallet, QR code) on the confirmation page and open the event app with their personal link. Invitations go out through the organiser’s own email.
- No error monitoring and no AI features.
- No organiser tracking and no CRM connection. Embedded videos (YouTube, Vimeo) appear only as links; uploaded videos are served from our own storage in Germany.
- The venue map stays, because it is served from our own domain.
Check-in that keeps working offline
Quick Scan runs in any phone browser. Installed on the phone, it keeps scanning without a connection and uploads the scans later; the first start needs a connection to load the guest list. Badges are generated locally at the print station, so a short network outage does not stop admission.
Logs without personal data
Application logs are structured and contain identifiers and yes/no flags instead of names, email addresses or credentials — a binding development rule. Server logs are deleted after 30 days. On event pages and in the event app, visits are counted with a server-side hash that changes daily: no cookie, no stored IP address.
Documents and contact
- Data processing agreement (PDF)
- Technical and organisational measures (PDF)
- Sub-processors and data location (PDF)
- Privacy policy for attendees
Questions about security, or a vulnerability to report? Write to info@quick-event.com. If a security incident affects data we process for you, we inform you without delay and at the latest within 24 hours of becoming aware of it.