← To the start page

Legal

Privacy policy

This is a translation. Where it differs from the original, the German version prevails.

Last updated: October 2026

This privacy policy applies to the websites einlasshelden.de and gateheroes.events — the public information sites of Einlasshelden and its English-language brand GateHeroes, the same provider with the same services — and to the application admin.gateheroes.events (under the Einlasshelden brand: admin.einlasshelden.de), in which you manage your account, conclude contracts, pay and use the platform. Sections 1 to 6 mainly concern the websites, sections 7 to 12 the application; everything else applies to both.

Guest data — that is, the data of the people who register for your events — is processed by us on your behalf: for this data you are the controller and we are the processor. It is governed not by this policy but by the data processing agreement that you conclude in the application. For processing for our own purposes — billing, the review of published content (section 14) and the prevention of abuse at public forms (section 3) — we are ourselves the controller.

1. Controller

Einlasshelden.de
Owner: Sebastian Reinhardt
Peperkamp 2, 25451 Quickborn, Germany
Email: hello@gateheroes.events
Phone: +49 (0)4106 122744

2. General

We take the protection of your personal data seriously. The websites are pure information sites: they set no cookies, integrate no analytics or tracking services and do not load any content from third parties. The application itself only sets the cookies that are technically necessary for your sign-in (section 8), and likewise integrates no analytics or tracking services. No user profiles are created.

3. Hosting and server logs

The website and the application are operated on a server of Hetzner Online GmbH (Industriestr. 25, 91710 Gunzenhausen, Germany) in a data centre in Falkenstein/Vogtland, Germany. Files that are uploaded in the application or generated for it (such as uploads in forms and invoice receipts) are kept in the object storage of the same provider in a data centre in Nuremberg, Germany. Encrypted backup copies (backups) are kept, also at Hetzner, in a data centre in Helsinki, Finland (European Union). The data does not leave the EU.

Our servers do not keep an access log that records every page view with address, time and browser. The server's technical logs (error and protection messages) may contain your IP address — in particular when one of the protection mechanisms is triggered with which we throttle sign-in, registration, forgotten password and the waiting list form on einlasshelden.de against automated access. We likewise throttle the registration forms of your events and uploads by guests; if this throttle is triggered, the entry contains the IP address of the person making the request — including that of a guest. We do this not on your behalf but for our own purpose of preventing abuse (data processing agreement, § 2 para. 6). These entries serve solely to ensure trouble-free operation and to defend against attacks; the legal basis is our legitimate interest in a secure and functional service pursuant to Art. 6(1)(f) GDPR. We delete them after 14 days. They are not combined with other data sources or analysed for marketing purposes.

4. Fonts

The fonts used on the website and in the application are loaded locally from our own server. No connection to third-party servers (such as Google Fonts) is established in the process, and no data is transmitted to third parties.

5. Contacting us

If you contact us by email, we process the data you send us (your email address and the content of your message) in order to answer your enquiry. The legal basis is Art. 6(1)(b) GDPR if your enquiry is aimed at concluding or performing a contract, and otherwise our legitimate interest in answering enquiries pursuant to Art. 6(1)(f) GDPR. We delete this data as soon as your enquiry has been dealt with and no statutory retention obligations prevent this.

If you use the “Report content” form to report content that you consider illegal or a breach of our terms of use, we process your details (name, email address, the address of the content and your reasons) and the IP address from which you report, in order to review the report, confirm its receipt to you and inform you of our decision (Art. 16 DSA; Art. 6(1)(c) GDPR). You can report content showing the sexual abuse of children without a name and email address; in that case we do not store an IP address either. We keep a report until we have closed it, and after that until the end of the third year after the year in which it was closed; then we delete it together with the emails about it.

6. Waiting list on einlasshelden.de

On the website einlasshelden.de you can put yourself on a waiting list to be notified as soon as the platform launches. For this we store your email address, the wording of the consent you gave when doing so, and the language and time — nothing else, in particular no name. After signing up you receive a confirmation email with a link that is valid for seven days; your entry only becomes active when you click it (double opt-in). An unconfirmed entry is not used. The form is throttled per network address against automated sign-ups; if the throttle responds, a log entry with the IP address is created (section 3).

The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time with effect for the future — via the unsubscribe link in every email or by sending us a message. We send the waiting list confirmation email via the email service provider Mailjet (Mailjet SAS, France), which processes the message on our behalf and bound by our instructions within the EU (section 13).

7. Account and contract in the application

When you register in the application, we create your account. For this we process the account name, your email address and your password (only as a hash, section 8) and assign a customer number. You confirm your email address via a link in the welcome email.

Before the platform processes guest data for you or you buy paid services, we record your account's contract and billing details: company (optional), VAT ID (optional, companies only), contact person, address including country, contact email address and phone number. These details are the contracting party of the data processing agreement, appear on your invoices and determine the available payment methods and the VAT.

When you accept the data processing agreement or agree to the order terms (at checkout or under “Account”), we record as proof who agreed to which version and when, including the IP address from which this was done. We likewise record, with the time and IP address, who agreed to the terms of use (when registering or on first sign-in), cancelled the contract, cancelled a purchased contract (such as your own domain) or withdrew from a purchase; when a purchased contract is cancelled, also which contract, as of when and — if you state it — for what reason. Invoices cannot be changed once issued. For every purchase in the application we record which person in your account triggered it; the account admins see this on the invoice.

If you buy as a consumer, you can ask us to start the service before the withdrawal period has ended. We then record this request with the time, the wording shown to you and your IP address, so that we can prove that you made it; and, if we create a purchase for you, who created it and when (Art. 6(1)(b) and (f) GDPR). We keep these records like the other contract records until the end of the third year after the year in which the contract ended.

We keep the record of the dispatch of the order confirmation (time, recipient address, reference to the order), like the records of your consents and declarations (time, version of the text, IP address), until the end of the third year after the year in which your last contract with us ends, and then delete them. We do this in order to be able to establish or defend claims. The legal basis for the dispatch record is Art. 6(1)(c) and (f) GDPR, and for the records of your consents and declarations Art. 6(1)(f) GDPR.

If you invite further people to your account, we store their email address and the invitation link (valid for seven days). If an account admin removes an access, it is deleted as soon as it no longer belongs to any account; where an action by this person must remain documented (such as who triggered a purchase or stored a payment method), the entry remains and continues to name the email address under which the person acted at the time, together with the date of deletion. For this purpose we keep their last login address, their earlier login addresses and the date of deletion until, for every account in which the person acted, the contract has ended and the records of it have been deleted — that is, usually until the end of the third year after the year in which the last of these contracts ended. If the person left nothing that must remain documented, we delete this information within two days after the access was deleted. After that, an entry only states that the access was deleted.

Files you upload for notices (media storage) are kept as long as your account exists. If a workspace has no event for two years, its notices are no longer publicly accessible; if your whole account has none for three years, we delete the files after two advance warnings by email (60 and 14 days before). A new event prevents this.

The legal basis is the performance of the contract with you (Art. 6(1)(b) GDPR). We keep account and contract data for the duration of the contractual relationship, and billing data beyond that for as long as commercial and tax retention periods require (Art. 6(1)(c) GDPR). We keep the records of your agreement to the data processing agreement, the order terms and the terms of use and of the cancellation, each with the IP address, until the end of the third year after the year in which the contract ended, and then delete them; of the cancellation, the account then records when it was declared, when the contract ended, under which version of the terms of use and, where applicable, when the contract was continued — without the IP address and without who cancelled. We keep a withdrawal for as long, but at least until the end of the third year after the year in which we received it. We keep a withdrawal that we cannot assign to an account until it is assigned. We keep the cancellation of a purchased contract in the same way as a withdrawal. Until then, claims under the contract can still be asserted (regular limitation period, §§ 195, 199 BGB), and we must be able to prove what was agreed (Art. 6(1)(f), Art. 17(3)(e) GDPR). Once the account has been deleted, we delete the contact email address and phone number on the account together with these records; where we sent a notice or a payment request remains recorded with that notice or request and in our log. We keep the account name, company, VAT ID, contact person, address and a separate invoice recipient for as long as an invoice or other receipt for your account has to be retained, and delete them then; after that, the account remains without these details, for example with its customer number and the end of the contract. We back up the database daily and keep these backups on the server for up to eight weeks. Backup copies stored elsewhere are encrypted; their keys are renewed at regular intervals and old keys are destroyed.

8. Sign-in and session

We store your password exclusively as a hash (scrypt with a random salt); it cannot be recovered from it. After you sign in, the application sets the technically necessary cookie eh_session: it carries a random session identifier whose session expires on our server after seven days. As soon as you choose an account or workspace, eh_account and eh_workspace are added; they remember where you are currently working. All three are inaccessible to scripts (HttpOnly), are only transmitted over encrypted connections and are not sent to third parties. They are deleted when you sign out.

Optionally, you can set up two-factor sign-in. We store the secret required for this in encrypted form (AES-256-GCM); we store the recovery codes only as a hash, and each can be used once.

To protect sign-in, registration and forgotten password against automated attacks, the application counts attempts per network address and target address in its working memory and slows down when something looks suspicious; these counters are not stored in the database. If a protection mechanism responds, a log entry with the IP address is created (section 3). How many invitations, delivery tests and confirmations for test addresses an access can trigger per hour is also limited; this counter is tied to the access, not to your network address. The legal basis is Art. 6(1)(b) GDPR (session, two-factor) and our legitimate interest in secure operation pursuant to Art. 6(1)(f) GDPR (defence against attacks).

So that misuse of a user access or an account is noticed and can be investigated, the application keeps two kinds of entries. For every person with user access: successful and failed sign-ins (a wrong password only if a user access exists for the email address entered), correct and wrong two-factor codes, signing in with a recovery code, signing out, changing and resetting the password, and turning two-factor sign-in on and off as well as its reset by an account administrator or our support team. Only the person themselves sees these entries, under “My sign-ins”, and a platform supporter during support access (section 10); no account administrator sees them. For every account: who opened the account and when (at most once per session) and who, as an account administrator there, reset a person's two-factor sign-in. The account administrators of the account see these entries under “Security — sign-ins”. Each entry contains the time, the email address the person signs in with, the IP address and the browser identifier (user agent); when two-factor sign-in is reset, we store no IP address and no browser, and for an account administrator their email address instead. We combine several failed attempts of the same kind from the same IP address within 10 minutes into one entry. The legal basis is our legitimate interest and that of the account holder in protecting accounts and user access and in detecting and investigating misuse and data breaches (Art. 6(1)(f) GDPR). We delete each entry after 90 days. If a user access is deleted, the personal entries of that person go with it; an account's entries remain until the 90 days are up, even if the person leaves the account or their user access is deleted. If the account is deleted, its entries go with it.

9. Emails to account holders

The application sends you emails that are part of running your account: the welcome and confirmation email, invitations, messages about forgotten passwords and password changes, invoice receipts and notices when something needs your attention (such as an upcoming deletion after a deadline expires, storage running low or an expiring domain). We send these emails via the email server of domainfactory GmbH, Munich, Germany, as our processor (Art. 28 GDPR) — not via the waiting list's email service provider. Only these emails themselves pass through domainfactory: your email address, your name and the content of the email, and for invoices the invoice document. Your account, your events and all of your guests' data are stored exclusively with Hetzner in the EU (section 3). According to its own information, domainfactory may from time to time transfer data to affiliated companies or service providers outside the EU, including the USA, and relies primarily on the EU-U.S. Data Privacy Framework, otherwise on the European Commission's Standard Contractual Clauses. Only when you have the application check whether your guest emails arrive (delivery test to your own address) does this one email — like every guest email — go via Mailjet (section 13); a template's preview email, by contrast, goes via our mailbox. The legal basis is Art. 6(1)(b) GDPR. There are no promotional emails to account holders.

10. Support access

So that we can help you with a problem, a platform supporter of ours can look into your account — read-only, never acting, always with a reason that they must state, and only for one hour; after that the access expires by itself. Particularly sensitive details of your guests (Art. 9 GDPR) remain masked during this access. Every look is logged, and you can see in your account when a platform supporter looked into it and for what reason. During support access, the platform supporter also sees the personal sign-in entries of the account's members (section 8). The legal basis is the performance of the contract with you (Art. 6(1)(b) GDPR) and our legitimate interest in trouble-free operation (Art. 6(1)(f) GDPR).

11. Payment processing

This section applies to purchases by customers based in Germany: there we are the seller, and Stripe processes the payment on our behalf. If you buy from outside Germany, Link (Stripe) is the seller; section 12 applies to that.

When you buy paid services in the application and pay online (for example by card), we process the payment via the payment service provider Stripe Payments Europe, Limited, Dublin, Ireland (“Stripe”). You enter your payment details directly into the payment form provided by Stripe. Full card numbers, account numbers or security codes never reach our servers and are never stored by us.

Besides cards, you can pay in Stripe's payment form, where offered, with Amazon Pay, Apple Pay, Google Pay or Link. If you pay with Amazon Pay, you give your payment details directly to Amazon Payments Europe S.C.A., 38 avenue John F. Kennedy, L-1855 Luxembourg, which is a controller in its own right for this; we receive only the confirmation of the payment. The same applies to Apple Pay (Apple Distribution International Ltd., Ireland), Google Pay (Google Ireland Ltd.) and Link (Stripe; here as a payment method in the payment form — for Link as the seller, see section 12). These providers process your payment data according to their own privacy policies. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR).

You can buy on invoice only if your account is based in Germany and we have enabled it for this. We issue the invoice ourselves and send it electronically to your account's contact email address; you pay by bank transfer, and we match the incoming payment to your invoice. If you have a payment charged back, we receive details of the chargeback (amount, time, status) from Stripe or your bank and record them on your account in order to withhold the service concerned provisionally and to clarify the case (Art. 6(1)(b) and (f) GDPR).

On your first purchase we create a customer record for your account at Stripe that carries only your account's identifier and your customer number. In connection with a payment, Stripe also receives from us:

  • the invoice amount and the currency,
  • an internal identifier of the payment transaction — not your name, your email address or your address,
  • the details you enter yourself in the payment form (such as name or billing address, where the chosen payment method requires them).

Stripe tells us whether a payment was successful and sends us an identifier of the payment and — if you save your payment method — an identifier of the saved payment method. We hold only this identifier, no card data. We retrieve its type and a shortened display (for example “Visa •••• 4242”) from Stripe when we show it to you in your account, and do not store them.

As soon as you trigger a purchase and the payment form appears, your browser loads it from Stripe's servers. In the process Stripe receives your IP address and technical details about your device and browser, which Stripe also uses to detect and prevent fraud; Stripe may set cookies for this. This concerns only the payment page in the application — nothing from Stripe is loaded on the website.

Saving a payment method: When paying, you can choose to have Stripe save your payment method for future purchases. This only happens if you tick the corresponding box; it is only charged when someone triggers a purchase themselves — never automatically. A saved payment method belongs to your account, not to you alone: every account admin can pay with it. We record who stored it and who triggered a payment, and show both to the account admins of your account with email address and date. You can remove saved payment methods in your account at any time; they are then detached from your account at Stripe.

The legal basis is the performance of the contract with you (Art. 6(1)(b) GDPR); for fraud prevention it is additionally our legitimate interest in secure payments (Art. 6(1)(f) GDPR). Stripe processes the payment data as a payment service provider under its own responsibility, insofar as this is necessary to execute the payment, prevent fraud and fulfil its own legal obligations. In doing so, Stripe may transfer data to affiliated companies in the USA, in particular to Stripe, Inc. According to its own information, Stripe bases this transfer on the EU-U.S. Data Privacy Framework and additionally on the standard contractual clauses of the European Commission. You can find details in Stripe's privacy policy.

We keep the data belonging to an invoice (amount, invoice number, billing address with contact person and VAT ID, payment status, time, payment identifier and who triggered the purchase) on our servers (section 3) for as long as commercial and tax retention periods require. A saved payment method remains stored at Stripe until you remove it or your account ends; the customer record at Stripe exists until your account ends.

Customers based outside Germany do not buy paid services in the application from us but via Stripe Managed Payments: the seller is then Link, a service of Stripe. According to Stripe, the payment is processed by Stripe Payments Company (USA) or Stripe Technology Europe, Limited (Dublin, Ireland). For the data that reaches them for the purchase and the payment, Link or Stripe is an independent controller — not our processor.

Link receives:

  • from us: the contact email address of your account, the purchased services with name, quantity and price, and an internal identifier of the payment transaction,
  • from you on the payment page: your name, your billing address and your payment details.

Your browser loads the payment page from Stripe's servers; in the process Stripe receives your IP address and technical details about your device and browser, also to detect and prevent fraud. You receive the invoice and the receipt from Link, not from us; your bank statement shows “LINK.COM*”. Questions about payment, invoice or refund are answered by Link's support. Stripe tells us whether the payment was successful and sends us identifiers of the payment, the amount and, for a refund or chargeback, its status. This notification technically also contains the name, email address and billing address you entered on the payment page; we do not evaluate or store this information. We do not receive your payment details.

The legal basis is the performance of the contract (Art. 6(1)(b) GDPR). You can find details of the processing by Link and Stripe, including transfers to the USA, in Link's privacy policy and in Stripe's privacy policy.

13. Disclosure of data

Your data is not transferred to third parties — with the exception of the service providers who process data on our behalf and bound by our instructions on the basis of a data processing agreement pursuant to Art. 28 GDPR: the hosting provider named above, domainfactory GmbH as the provider of our email mailbox for account emails (section 9) and the email service provider Mailjet for the waiting list (section 6) and for the delivery test of your guest emails to yourself (section 9) and Amazon Web Services EMEA SARL (Luxembourg) for the AI review of published content (section 14) — as well as the payment service provider Stripe for a payment in the application (section 11), which processes the payment data under its own responsibility, and Link (Stripe) as the seller for a purchase from outside Germany (section 12), likewise under its own responsibility.

14. Review of published content

What you show publicly on our platforms — Landingpages including the legal texts you store there, notice-board items and the pages a notice-board item links to — we review for unlawful content, phishing and malware. We do this because we are obliged to as a hosting provider (Regulation (EU) 2022/2065, Digital Services Act; Art. 6(1)(c) GDPR) and because we have a legitimate interest in secure operation (Art. 6(1)(f) GDPR). We are responsible for this ourselves, not as your processor (Art. 28(10) GDPR). We do not review emails or mailings to your guests.

The review is automated. Once a night an AI service reviews the published content; we retrieve the pages a notice-board item links to once a week ourselves and review them in the same way. Uploaded files go through a virus scan on our own server before they are published; no third party receives the file in the process. We use the AI service (a language model from Anthropic) through Amazon Bedrock of Amazon Web Services EMEA SARL, 38 avenue John F. Kennedy, L-1855 Luxembourg (“AWS”); we use the EU inference profile with the source region Stockholm, the requests are processed exclusively in regions of the European Union, and your content is not used for training. AWS is our processor in this.

The AI only flags suspected cases; a person decides on any measure. An exception applies to clear phishing: then the system blocks the individual content immediately itself, a person reviews the block no later than the next working day, and you are informed without delay. This is an automated decision based on the contract (Art. 22(2)(a) GDPR); you can lodge an objection at any time and ask for a person to review it again. We store an unremarkable result only with the time and a checksum, without any text. We keep a suspected case until it is closed and after that until the end of the third year after the year in which it was closed, because otherwise we could not prove why we acted (Art. 6(1)(f), Art. 17(3)(e) GDPR).

15. Your rights

Under the GDPR you have the following rights:

  • access to the data stored about you (Art. 15 GDPR),
  • rectification of inaccurate data (Art. 16 GDPR),
  • erasure (Art. 17 GDPR),
  • restriction of processing (Art. 18 GDPR),
  • data portability (Art. 20 GDPR),
  • objection to processing (Art. 21 GDPR),
  • withdrawal of consent given, with effect for the future (Art. 7(3) GDPR).

An informal message to the contact details given above is sufficient to exercise your rights.

16. Right to lodge a complaint with the supervisory authority

Without prejudice to other legal remedies, you have the right to lodge a complaint with a data protection supervisory authority. The supervisory authority responsible for us is:

Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein (ULD)
Holstenstraße 98, 24103 Kiel, Germany
www.datenschutzzentrum.de