Skip to content
Shadeslist

Client (controller): the organizer who uses a Shadeslist account.
Contractor (processor): Marcel Kussin, Büskenweg 6, 45968 Gladbeck.

§ 1 Subject matter and duration

(1) The subject matter is the processing of personal data of guests by the contractor when providing the Shadeslist software (guest list management and door check-in) in accordance with the terms and conditions.

(2) This agreement applies for the duration of the user agreement. It ends when the client’s account is deleted.

§ 2 Nature and purpose of the processing

Collecting, storing, displaying, changing, exporting and deleting registration data so that the client can manage the guest list, approve guests, send confirmation emails to guests (only if an email address was provided) and check guests in at the door. The contractor does not process the data for its own purposes.

§ 3 Type of data and categories of data subjects

Data subjects: guests who sign up for the client’s events, and door helpers to whom the client gives door access.

Data categories:

  • Nickname (required, freely chosen)
  • Email address (optional; not collected for anonymous sign-ups)
  • Message to the organizer (optional)
  • Registration status with timestamps (signed up, approved, cancelled, checked in)
  • Check-in code, check-in log and, if applicable, the invite code used
  • The client’s internal notes on individual guests
  • Door helpers (door access): label chosen by the client, optionally an email address (only when the access link is sent by email; deleted 7 days after the access expires), times of use of the access and the access link (only as a checksum or in encrypted form)

Depending on the type of event, special categories of personal data (Art. 9 GDPR) may be affected. The parties take this into account in the scope of data collection and in the protective measures. IP addresses and browser identifiers of guests are not stored.

§ 4 Instructions

(1) The contractor processes the data exclusively on documented instructions from the client. The client gives instructions primarily by using the functions of the software (e.g. approving, deleting, exporting); supplementary instructions are given in text form.

(2) If the contractor considers an instruction to be unlawful, it informs the client without undue delay.

(3) If the client enters the email address of a door helper, the client decides on the purpose and means of this processing. The client is responsible for ensuring that passing on the address is permitted and informs the person concerned. The contractor processes the address only to send the access link and to show it to the client in masked form.

§ 5 Obligations of the contractor

  • Persons with access to data are bound to confidentiality.
  • The contractor’s support team generally has no access to guest data. Access is only possible if the client explicitly grants it in the app for a limited time; every grant and every access is logged.
  • The contractor supports the client in fulfilling data subjects’ rights. Guests can export and delete their data themselves via their personal status page.
  • The contractor reports personal data breaches to the client without undue delay, at the latest within 48 hours of becoming aware of them.
  • The contractor supports the client with data protection impact assessments and provides the information necessary to demonstrate compliance with its obligations.

§ 6 Technical and organizational measures

  • Encryption: transmission exclusively via TLS; email addresses, messages and internal notes are stored encrypted in the database. Personal status links are only stored as a checksum or in encrypted form.
  • Hosting in Germany: application, database and email delivery with a host whose data center is located in Germany.
  • Access control: accounts with passwords (stored as hashes), a role and permission concept for the contractor’s team, two-factor authentication for team accounts, limits on login and form attempts.
  • Data minimization: no storage of IP addresses or user agents of guests, no tracking, no external services on guest pages.
  • Deletion periods: automatic deletion of all guest data 30 days after the event; deleted events are removed permanently after 30 days.
  • Deletion log: every deletion is logged with a reference number, time, trigger and data categories – without personal data of the data subjects.
  • Notifications to the team contain no personal data.

§ 7 Sub-processors

The client agrees to the use of the following sub-processors:

  • ALL-INKL.COM – Neue Medien Münnich, Hauptstraße 68, 02742 Friedersdorf, Germany: hosting, database, sending emails.
  • Stripe Payments Europe, Ltd., Dublin, Ireland: payment processing. Processes exclusively data of the client, no guest data.
  • Telegram: internal team notifications. No personal data is transferred.

The contractor informs the client about intended changes by email at least four weeks in advance. The client may object for an important reason under data protection law and in this case terminate the contract.

§ 8 Audit rights

The client may verify compliance with this agreement, primarily through information and documentation provided by the contractor. On-site audits are possible after timely notice during normal business hours, insofar as they are proportionate.

§ 9 Deletion and return

After the end of the agreement, the contractor deletes all guest data of the client unless there is a legal obligation to retain it. Before deletion, the client can export the guest lists as CSV and their account data in the app under “Privacy” at any time. The deletion is recorded in the deletion log.

§ 10 Final provisions

In the event of contradictions between this agreement and the terms and conditions, this agreement takes precedence in matters of data protection. In all other respects, the final provisions of the terms and conditions apply.

Version 2026-10-05.2 · Last updated October 5, 2026