Legal
Privacy policy
Shadeslist is built for situations where privacy matters. That’s why we collect as little data as possible, encrypt sensitive fields and delete data after fixed periods. Here you can read in detail what we process – and what we don’t.
The essentials at a glance
- No tracking: no profiles, no advertising pixels, no social media plugins, no external fonts or CDNs and no third-party analytics services. We count visits only anonymously, without cookies and on our own server (section 2).
- No IP addresses or user agents of guests in the application.
- Data-minimal: guests only need a nickname. Email and message are optional and are stored encrypted.
- Fixed deletion periods: guest data 30 days after the event, closed support requests after 12 months.
- In your hands: guests can download and delete their data themselves at any time and receive a deletion log number for it.
- Hosting in Germany with all-inkl.com, payments via Stripe.
1. Controller
The controller for processing on this website and for the data of organizers is:
Marcel Kussin, Büskenweg 6, 45968 Gladbeck
Email: marcel@shadeslist.com
For the data of guests of an event, the respective organizer is the controller. We process this data on their behalf as a processor under Art. 28 GDPR (see section 5 and our data processing agreement).
2. Hosting and access data
The website and application are operated by ALL-INKL.COM – Neue Medien Münnich, Hauptstraße 68, 02742 Friedersdorf, Germany, on servers in Germany. When a page is requested, the web server necessarily processes connection data (including IP address, time and requested address) to deliver the page and to protect the server against attacks. The legal basis is our legitimate interest in secure operation (Art. 6(1)(f) GDPR). A data processing agreement is in place with the host.
The Shadeslist application itself stores no IP addresses or user agents of guests. To prevent abuse (e.g. mass sign-ups), we limit the number of requests; for this, a hash of the IP address is kept in the cache for no longer than the blocking period (a few minutes) and then discarded automatically.
Anonymous reach measurement
To understand how many people visit our website, where visits end and how many create an account, we count views of the public information pages and the registration page ourselves on our own server – without cookies, without third-party services and without passing data on. Not measured are the guest pages (registration, status page, code entry), door access links, the signed-in app and the back office.
- What is counted: page views (the kind of page, e.g. “Pricing”, for occasion, region and help pages also which one – no input, no search parameters), the language version of the website (German or English), the device class (smartphone, tablet or desktop, derived from the browser identifier, which itself is not stored), where a visit came from (only the host of the referring website or the campaign name from the address, never the full address), whether the registration page was opened and an account was created, and later milestones (first event, checkout, subscription) as plain daily totals not linked to any person.
- Filtering out robots: Requests by known robots (search engines, link previews, testing tools, scripts) are only counted as a number per kind, never as a visit. To detect disguised robots, we check on each request whether the usual details of a browser are sent along (e.g. a preferred language), and a small script file sends an empty notification to our server after the page has been shown briefly or on the first interaction. Nothing is read from or stored on your device for this. Only the result (confirmed, unconfirmed or suspicious) is stored with the daily check value; suspicious visits are not included in any statistic.
- How anonymous: To group the visits of one person on one day, we form a check value from the IP address and browser identifier with a random daily key. The IP address and browser identifier are processed for this only at the moment of the request and are not stored. The daily key exists only in a temporary cache and expires after 36 hours at most; after that the check value can neither be recomputed nor linked to visits on other days. The check values are deleted after the day, only counters remain permanently (24 months at most).
- Legal basis: our legitimate interest in improving our service and understanding whether it reaches people (Art. 6(1)(f) GDPR). Nothing is stored on or read from your device for this. Because the counting is anonymous, we cannot attribute individual visits to a person.
3. Cookies
Our informational pages (home page, features, pricing, help, legal) set no cookies – unless you decide otherwise when you arrive through an invitation link (referral cookie, see section 12 and the cookie settings). Only on pages with forms (contact, Have your say, guest sign-up, status page) and in the app do we set a technically necessary session cookie and a cookie that protects against forged form requests (CSRF). These cookies are strictly necessary for the service you have requested (Section 25(2) no. 2 TDDDG) and are deleted when you close your browser or when the session expires.
When you vote in a survey on the “Have your say” page, we additionally set the cookie sl_survey with a random identifier, so that your vote isn’t counted twice and you can change it (see section 11). It is only set when you vote, applies only to the Have your say pages and expires after one year.
Language
Our informational pages are also available in English at their own addresses (starting with /en/). There, the language follows from the address – no cookie is set for this.
If you switch the language on the guest pages (sign-up, status page), we store your choice in the cookie sl_locale. It contains only the value “de” or “en” and no identifier, is set only when you switch the language and expires after one year. The cookie is functional: it only makes sure the pages are shown in the language you chose (Section 25(2) no. 2 TDDDG). Without such a choice, we follow your browser’s language setting without storing it. For a registration or an organizer account, we store the language (German or English) so that emails arrive in that language.
4. Contact form and support
If you write to us using the contact form, we process your email address, optionally your name, the selected topic, subject and message in order to answer your request (Art. 6(1)(b) or (f) GDPR). This creates a support ticket with a ticket number; the email address is stored encrypted. We automatically delete closed tickets, including attachments, after 12 months.
Our support team sees no guest data. Only if an organizer explicitly grants time-limited support access for a specific problem can the team view the data concerned. Every grant and every access is logged.
5. Guests of events
What data?
When you sign up for an event, we store: nickname (required), email address (optional; not collected for anonymous sign-ups), a message to the organizers (optional), the registration status with timestamps (signed up, approved, cancelled, checked in), a check-in code and, if applicable, the invite code used. Organizers can add an internal note. Email address, message and internal note are stored encrypted. We store your personal status link only as a checksum or in encrypted form.
Who is responsible?
The controller is the organizer of the event who uses Shadeslist as a tool. We process your registration data exclusively on their behalf and according to their instructions and do not use it for our own purposes. The purpose is organizing the guest list and the door check-in; the legal basis is usually the running of the event (Art. 6(1)(b) GDPR).
Particularly sensitive information
Signing up for an event alone can allow conclusions to be drawn about particularly sensitive information. Special categories of personal data (Art. 9 GDPR) may therefore be affected. That’s why Shadeslist only requires a freely chosen nickname, there are no profiles and no public guest list, and guests only see their own registration. Guests only see the venue after they have been approved.
Emails to guests
Only if you provide an email address do we send you a confirmation with your personal link, a message as soon as you have been approved and a message if the event is cancelled. If the organizers have switched on the reminder and their plan includes this feature, you also receive, as an approved guest, one reminder before the event with the date and your personal link; the location and the event name are not in the email. The subject lines are deliberately kept neutral. The legal basis is carrying out your registration (Art. 6(1)(b) GDPR).
Plus-ones
If the organizers allow a plus-one, you can use your personal link to either state a number only (“+1”) or register a named plus-one. A number is just a figure on your registration. For a named plus-one we store their nickname, optionally an email address (encrypted, as for guests), the registration status and a check-in code of their own. That makes them a registration of their own with their own status link, treated like any other. Please only enter another person’s details if they agree. Only if you give an email address for the plus-one do we send them a message with their own link; the location and the event name are not in it. At the door the group can be let in together; for that we remember the time of the first scan until everybody has arrived. The plus-one can delete their registration themselves at any time via their own link. Purpose, legal basis, responsibility and deletion period are the same as above; the organizers decide whether and how many plus-ones are allowed, also differently for individual guests.
Wallet tickets
Approved guests can save their ticket for offline use on the status page. This is optional.
- QR code as an image: the image is saved on your device; no data is transferred to third parties.
- Apple Wallet: the pass file is stored only on your device (and in your iCloud, if you have turned on syncing yourself). If the organizers use the Pro plan, your device registers with our server for updates to the pass (e.g. a cancellation or a changed time). For this, we store a device identifier of the Wallet app and a push token; both are deleted when you remove the pass, at the latest together with your registration data.
- Google Wallet: only when you tap “Save to Google Wallet” are your nickname, check-in code and the date of the event – the event title only if the organizers have enabled this – transferred to Google and stored there. Google may also process data outside the EU. The legal basis is your consent given by tapping (Art. 6(1)(a) GDPR); you can delete the pass in Google Wallet at any time.
For how long?
All data of a registration is deleted automatically 30 days after the event. Organizers can delete registrations earlier, and you can delete your registration yourself at any time (see section 15).
6. Organizers
For your account, we process your email address, optionally your name, your password (only as a hash, if you set one), login times, your plan and the events you create (title, date, optionally venue, capacity, notes, invite codes). On the Pro plan, we also store the logo you upload. When we roll out a new feature gradually, we store whether it was enabled for your account (account number, feature, time); a fixed random value is derived from your account number for this, and your behaviour is not analysed. This information is deleted together with the account. The legal basis is the user agreement (Art. 6(1)(b) GDPR). The data is stored for as long as your account exists; deleted events stay in the trash for 30 days and are then removed permanently. If you delete your account, we delete all associated data unless statutory retention obligations (e.g. for invoices) apply.
Signing in with an email link, Google or a passkey
Besides email and password, you can sign in or sign up in these ways. Accounts created this way have no password at first; you can set one at any time.
- Sign-in link by email: We send you a link that is valid for a few minutes and works only once. For this we store your email address, a checksum of the link, when it expires and when it was used and, for a sign-up, the language you chose and a referral or voucher code from the link. Used and expired links are deleted within one day. Opening the link confirms your email address.
- Continue with Google: When you tap “Continue with Google”, we redirect you to Google. Google then tells us a fixed identifier of your Google account, your email address and whether Google has verified it. We do not take over your name or profile picture. We store the identifier and the email address to recognise you next time; we do not store access tokens from Google. Google learns that you sign in to Shadeslist and may process data outside the EU (the Google Privacy Policy applies). You can disconnect Google under “Account” and remove the connection in your Google account at myaccount.google.com/connections.
- Passkey: A passkey is a key that your device or password manager creates and protects with Face ID, a fingerprint or the device PIN. We store only the public part of the key, an identifier, a counter, the type of device (the manufacturer’s model identifier), the name you give it and timestamps. We never receive biometric data; it does not leave your device. You can delete passkeys under “Account”.
The legal basis is the user agreement (Art. 6(1)(b) GDPR); which method you use is up to you. The data is deleted together with your account.
Door access for door helpers
Organizers can give helpers at the door access without them needing an account. The access is a personal link with a random, unguessable key (token). Whoever opens the link can check guests in for exactly this event and search by nickname – nothing more. The link ends automatically shortly after the end of the event. The organizer can revoke it at any time. It also ends if the organizer’s account is locked or closed. In all of these cases, Shadeslist only shows the general message “This link is not valid.”
- What we store: a freely chosen label (visible to the organizer only), the link only as a checksum and in encrypted form (so the organizer can copy it again), timestamps (created, first opened, last used, sent by email if applicable), the number of guests checked in and, for each check-in, which access it was made through. We store no IP addresses and no device or browser identifiers of helpers and set no cookies for the access.
- Email address (optional): If the organizer sends the link by email, they enter the helper’s address. We store it in encrypted form to send the link and to show the organizer, in masked form only, whom it was sent to. The email contains neither the event name nor the organizer’s name. The address is deleted 7 days after the link expires, and immediately when the link is revoked; the entries themselves after 30 days. Neither the link nor the address appears in the email log or in error logs.
- Responsibility: Whom the organizer puts at the door and which email address they enter for that is their own decision. They are the controller in this respect and should inform the person about the processing (e.g. by pointing to this policy). We process the details on their behalf under our data processing agreement. The legal basis is the organizer’s legitimate interest in orderly admission (Art. 6(1)(f) GDPR).
- Guest data at the door: Helpers only see guests’ nicknames, status and check-in code – no email addresses, messages or notes. For offline use, the app caches this list on the helper’s device and removes it as soon as the link is no longer valid. Helpers cannot change or delete guests and cannot export lists.
Voucher codes
Organizers can redeem voucher codes (plan trial, free months or a discount on the first months of a paid plan), also right at sign-up. The conditions are in the terms (§ 13).
- What we store: for each redemption, which voucher (as an identifier) was redeemed by which account and when, what it did (type, plan, duration, percentage or amount), the value at that time (list price), how the benefit was delivered (extension of the free period, Stripe credit or discount with a Stripe reference), status and timestamps, and the name of the promotion. If a voucher belongs to an advertising partner, your account is assigned to that partner (see section 12). We store no IP addresses and no browser identifiers, and not the code you type in a failed attempt.
- Abuse protection: We count failed attempts for at most one hour as a plain number in a temporary cache, per account, at sign-up per internet address (only as a checksum, not in the database). After several failed attempts we block further entries for a while. The legal basis is our legitimate interest in protecting against guessed codes (Art. 6(1)(f) GDPR).
- Legal bases: Redemption is based on the voucher conditions and the user agreement (Art. 6(1)(b) GDPR). Redemptions are accounting records that we keep for tax reasons (Art. 6(1)(c) GDPR).
- Retention: Redemptions are kept for 10 years. If you delete your account, they lose the link to you and remain with a pseudonym only; the deletion is recorded in the deletion log (category “Voucher data”). Reserved discounts that were never applied are deleted 6 months after they lapse.
- Emails and Stripe: The confirmation and the reminder before a plan trial ends are neutral and never name the code. For discounts and credits we only pass a voucher coupon or an amount with a neutral name to Stripe (see section 7).
Conclusion of the contract, withdrawal and cancellation
For paid subscriptions we treat all organizers as consumers. The conditions are in the terms (§ 6 and § 10) and in the withdrawal instructions.
- Before the purchase: Before you take out a subscription, we store your confirmations as proof (terms and withdrawal instructions read and terms accepted, start before the end of the withdrawal period requested, knowledge that the right of withdrawal expires) with the time, plan, price including a voucher discount, the mandatory information shown, the versions of the terms, the withdrawal instructions and the privacy policy, and the language. After the purchase we add the Stripe checkout session, your acceptance of the terms in the Stripe payment form, the subscription ID, the contract number and the sending of the contract confirmation.
- Withdrawal and cancellation: If you declare a withdrawal or a cancellation (in the app, on the pages “Withdraw from contract” and “Cancel contracts here” or otherwise), we store the declaration with date and time, your name and the email address you entered (both encrypted), a contract number you entered, for a cancellation the type, the requested time and for an extraordinary cancellation the reason (encrypted), and the processing (link to your account, end of the period, status, amount paid, compensation for value, refund and the ID of the refund at Stripe). We match declarations by email address; the pages do not reveal whether an account exists for an address. We store no IP addresses and no browser identifiers.
- Purposes: concluding and performing the subscription, proving the information and consents before the contract was concluded, contract confirmation and confirmations of receipt by email, ending the subscription and refunds via Stripe. If a declaration cannot be matched automatically, we open a support ticket. Notifications to our team only contain numbers, plan, status and amounts, no names or addresses.
- Legal bases: Art. 6(1)(b) GDPR (conclusion, performance and reversal of the contract) and Art. 6(1)(c) GDPR (legal obligations, in particular under Sections 312f, 312j, 312k, 356a German Civil Code and the retention duties under commercial and tax law).
- Retention: Proof of concluded contracts as well as withdrawals and cancellations are kept as contract records for 10 years (Section 257 German Commercial Code, Section 147 German Fiscal Code). We delete the name, email address, contract number and cancellation reason of a declaration after 3 years; date, status and amounts remain. Confirmations that did not lead to a contract (payment aborted) are deleted after 6 months. If you delete your account, the records remain only with a pseudonym without a link to the account and the name and email address in your declarations are removed; the deletion is recorded in the deletion log (category “Contract data”).
7. Payments via Stripe
Subscriptions are processed by Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland. For this, Stripe receives your email address, the chosen plan and the payment details you enter in Stripe Checkout. We ourselves do not see or store any card or bank details – only a customer and subscription ID and the subscription status. Refunds after a withdrawal are also issued via Stripe to the original means of payment. Guest data is never transferred to Stripe. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR) and legal obligations (Art. 6(1)(c) GDPR). Stripe may transfer data to the USA; this takes place on the basis of the EU-US Data Privacy Framework or EU standard contractual clauses. We keep billing-related data in accordance with the retention periods under tax and commercial law (up to 10 years).
8. Sending emails
We send system emails (e.g. confirmations, password resets, replies to support requests) via the mail servers of all-inkl.com in Germany. For troubleshooting, we only log which type of email was sent when and with which result – without the recipient address and without content. This log is deleted after 90 days.
9. Internal notifications
Our team is notified about certain events (e.g. a new support ticket, a new subscription) by email or via the messenger Telegram. These notifications contain no personal data – only technical IDs, the plan or amounts. Telegram therefore receives no data about guests or organizers.
10. Error logs
If a technical error occurs, we store an error message with an error ID, the time, the affected function and the app version so that we can fix the error. Email addresses, long identifiers and phone numbers are automatically masked. For each error, we only keep the most recent occurrences.
11. Surveys & feature suggestions (Have your say)
On the “Have your say” page and in the app, you can vote on which feature we should build next and suggest your own ideas. Taking part is voluntary.
- Voting without an account: we only store which options you chose. So that nobody votes twice and you can change your choice, we set the technically necessary cookie
sl_surveywith a random identifier when you vote. The database only contains a hash of it, which cannot be traced back to you. We do not store IP addresses. - Voting as an organizer (in the app): your vote is linked to your account and your plan, so that we can weight our customers’ wishes.
- Suggestions: we store the title and description of your idea. Suggestions by organizers are linked to the account and are part of the data export in the app.
- Email for status updates: only if you voluntarily provide an email address and want to be notified do we inform you about status changes of your suggestion. We first send you a neutral email with a confirmation link (double opt-in); only after confirming do you receive status updates. We automatically delete unconfirmed addresses after 7 days. The address is stored encrypted and deleted automatically 12 months after the last status change; every deletion is recorded in the deletion log.
- Account deletion: if you delete your account, your votes and suggestions are anonymized – they still count in the statistics but can no longer be attributed to anyone.
The legal basis is our legitimate interest in developing Shadeslist according to the needs of its users (Art. 6(1)(f) GDPR); for status updates by email, your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time, e.g. via the contact form.
12. Referral and partner program
With the referral program, organizers can recommend Shadeslist (“customer refers customer”); advertising partners can bring in new customers through their own links (partner program). Both programs are voluntary.
What we store
- Referral code and clicks: every organizer has a random referral code with no personal reference. We only count clicks on the link as a number – no IP address, no user agent, no record per visitor.
- Attribution at sign-up: who referred (account or partner), the time, the progress (e.g. the number of redeemed QR codes as a number, a paid subscription) and the rules that applied at sign-up. We do not show names or email addresses of the other party to those involved. Guest data is not part of it.
- Credits: an accounting record of the months credited (time, months, value, type of credit) with a pseudonym instead of a name.
- Partner program: commission bookings per paid invoice (amount, Stripe invoice number, period); the referred customer only appears as a pseudonym. We store partners’ contact details encrypted. A voucher code can also belong to a partner: redeeming it assigns your account to that partner unless it is already assigned to one.
Legal bases
The program is carried out on the basis of the participation conditions (Art. 6(1)(b) GDPR, see terms). We keep accounting records for tax reasons (Art. 6(1)(c) GDPR). Protection against abuse, for example through a waiting period, caps and the rejection of self-referrals, rests on our legitimate interest (Art. 6(1)(f) GDPR).
Retention
Accounting records (credits and commission bookings) are kept for 10 years. We delete rejected or expired referrals after 6 months. If you delete your account, attributions lose their link to you; accounting records remain with a pseudonym only, and the deletion is entered in the deletion log.
Cookies on referral links
If you open a page through an invitation link (addresses with ?ref=, short /r/…), we do not set a cookie at first. Instead, a notice asks whether we may remember the referral code in a cookie for 30 days (for partners up to 90 days depending on the agreement), so that the referral counts when you sign up. “Yes” and “No” are equal choices.
sl_ref(only on “Yes”): referral code and time, signed – without any information about you and without an IP address. The cookie isSecure,HttpOnlyandSameSite=Lax. We only read it when you sign up and delete it right afterwards. A new link with your consent replaces the old code.sl_consent(on “Yes” and “No”): remembers your decision for 365 days so that the notice does not appear on every visit (Section 25(2) no. 2 TDDDG).
The legal basis for sl_ref is your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). Signing up works just the same without a cookie: the code is then passed on through the address of the sign-up link. You can withdraw your consent at any time with effect for the future on the cookie settings page, which also lists all cookies with purpose, content and lifetime. We count anonymously per day how often consent was given, declined or withdrawn – with no link to a person.
13. Business outreach (acquisition)
We introduce Shadeslist to organizers, venues, clubs and service providers it may be useful for – by letter, message, email or in person. For this we keep an internal contact list. If we contacted you this way, this section informs you (Art. 13 and 14 GDPR).
- What data: name of the business or club, website or profile address, contact person, business email address, where the contact details come from, country and broad target group (e.g. “venue”), the history of the outreach (date, type, template used, your reply) and short factual notes. We store nothing about the kind of your events, your private life or special categories of data, and no postal addresses of private individuals. Name, email address and notes are stored encrypted.
- Sources: publicly available business information (legal notice, contact or about page, public profile, organizer pages), your own inquiry, a personal conversation or an introduction by a partner. We name the specific source in our first message. Researched contact details are used for this first message within one month or deleted.
- Purpose and legal basis: presenting our offer and initiating a business relationship. The legal basis is our legitimate interest in direct marketing (Art. 6(1)(f) GDPR); if you contacted us yourself, Art. 6(1)(b) GDPR.
- Email: If we email you without prior contact, we do so individually, name the source and follow up at most once. We do not send bulk emails. A short “no” in reply to any message is enough and we will not contact you again.
- Who has access: only our sales team and the administration. We do not pass the list on. It is stored on our servers in Germany (section 2); we write emails from our own mailbox.
- Retention: We delete your data 6 months after the first contact or after your last reply. If you answer “no” or do not react to our follow-up, we remove names, contact details and notes immediately; only anonymous information remains for our statistics (date, channel, outcome).
- Suppression list: So that we do not contact you again after an objection, we keep your email address and website only as a check value (a hash computed with a secret key from which the address cannot be recovered) for 3 years (Art. 6(1)(f), Art. 21(3) GDPR).
- Objection: You can object to the use of your data for marketing at any time without giving reasons (Art. 21(2) GDPR). A short “no” or an email to marcel@shadeslist.com is enough. Your other rights are listed in section 15.
14. Our social media profiles (Instagram and YouTube)
We run an Instagram profile (@shadeslist) and a YouTube channel (“Shadeslist”). We create the posts ourselves and publish them from our internal back office through the platforms’ interfaces. There are no social media plugins on our website for this; no data of website visitors, guests or organizers is transmitted to Instagram or YouTube.
YouTube API Services
Our back office uses Google’s YouTube API Services to upload videos to our own channel and to retrieve the view counts of our own videos. It connects exclusively to our own Google account; we do not retrieve any data of other YouTube users.
- What we store: the access credentials (tokens) of our own account in encrypted form, the channel and video IDs, the upload status and daily figures per video (e.g. views, likes) without reference to individual persons.
- Who has access: only our social media team and the administration. We do not pass this data on.
- Deletion and revocation: When we disconnect the account in the back office, the tokens are deleted immediately. The account holder can also revoke access at any time in the Google security settings: security.google.com/settings/security/permissions.
- The YouTube Terms of Service and the Google Privacy Policy apply.
For Instagram, we use Meta’s Instagram interface (Meta Platforms Ireland Limited, Merrion Road, Dublin 4, Ireland), signed in with our own business account. As with YouTube, we only store the encrypted token, the IDs of our posts, the publishing status and daily figures per post (e.g. views, reach, saves) without reference to individual persons. For the images and videos of a post, we create a time-limited, signed address from which Instagram fetches the file. Instagram’s Terms of Use and Privacy Policy apply.
When you visit our profiles
If you visit our Instagram profile or our YouTube channel, Meta or Google process your data under their own privacy policies. From Instagram and YouTube we only receive aggregated statistics, no information about individual persons. For the statistics on our Instagram profile (Insights), we are joint controllers with Meta (Art. 26 GDPR); under the joint controller addendum, Meta assumes primary responsibility, including for your data subject rights. We answer messages you send us there on the respective platform. Links in our posts carry the public ID of the post (e.g. utm_campaign=sp_…) so that we can count visits per post anonymously (section 2).
The legal basis is our legitimate interest in making Shadeslist known and communicating with interested people (Art. 6(1)(f) GDPR).
15. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). You can withdraw any consent you have given at any time with effect for the future (Art. 7(3)). You can also lodge a complaint with a data protection supervisory authority (Art. 77 GDPR).
Self-service for guests
- Export: on your personal status page, “Download my data” downloads all stored data of your registration as a JSON file.
- Deletion: “Delete my data” removes your registration immediately and permanently, including the check-in log.
- Please direct requests about organizers’ internal notes to the organizers as controllers. If such requests reach us, we forward them.
Self-service for organizers
In the app under “Privacy”, you can export all data of your account, view the deletion log and delete your account.
Deletion log
Every deletion (by you, by organizers or by the automatic deletion period) is recorded in a deletion log with a reference number (e.g. “DEL-2026-7QF4MZ2K”). The log contains no personal data of the person concerned, only the time, the trigger, the type and number of deleted records and the data categories. With the reference number, you can prove the deletion later.
For all other matters, you can reach us at marcel@shadeslist.com or via the contact form.
16. Data security
All connections are TLS-encrypted. Sensitive fields are encrypted in the database, and passwords are only stored as hashes. Our team’s access is limited to what is necessary and protected with two-factor authentication. There is no automated decision-making and no profiling.
17. Recipients and processors
- ALL-INKL.COM – Neue Medien Münnich, Germany: hosting, database, sending emails
- Stripe Payments Europe, Ltd., Ireland: payment processing (organizer data only)
- Telegram: internal team notifications (without personal data)
- Google: Google Wallet – only if you save your ticket there yourself (see section 5, “Wallet tickets”)
- Google: “Continue with Google” – only if you sign in that way yourself (see section 6, “Signing in”)
- Apple: push service for updates to Apple Wallet passes (only a push token, no content)
- Google (YouTube) and Meta (Instagram): publishing our own posts (see section 14, without data of visitors, guests or organizers)
Data is not passed on to any other third parties unless we are legally obliged to do so.
18. Changes
We adapt this policy when Shadeslist or the legal situation changes. The version published here applies.
Version 2026-11-17.1 · Last updated November 17, 2026