Skip to content

Privacy Policy

Last updated: Nov 15, 2026

Only the German version of this privacy policy is legally binding. Translations are provided for convenience only.

1. Controller

The Kölsch Crew, owner: Michael Piel · Schmiedegasse 30, 50735 Cologne, Germany · Phone: +49 221 66994069 · Email: tours@koelschcrew.com No data protection officer has been appointed, as the legal requirements are not currently met (Art. 37 GDPR).

2. Terms & legal bases

Personal data is any information relating to an identified or identifiable natural person (Art. 4(1) GDPR). Processing is any operation performed on personal data (Art. 4(2) GDPR). Legal bases: Art. 6(1)(a) (consent), (b) (contract), (c) (legal obligation), (f) (legitimate interest) GDPR. Where we store information on your device or access it and this is not strictly necessary, we ask for your consent under Section 25(1) of the German TDDDG.

3. Hosting & server logs

Our website and booking system run on our own servers at Hetzner Online GmbH in data centres in Germany (Falkenstein) and Finland (Helsinki), all within the EU. Processed automatically: IP address, date and time, referrer URL, browser type and operating system, requested resources. Purpose: operation, security, error analysis. Legal basis: Art. 6(1)(f) GDPR. Retention: 7–30 days.

4. Consent & cookie settings

On your first visit we ask which categories you agree to: statistics, marketing and external media. Without your consent we do not load Google Tag Manager, Google Analytics, Google Ads or Microsoft Clarity. Embedded videos from YouTube (privacy-enhanced mode) only load once you consent to external media.

  • Strictly necessary (Section 25(2) TDDDG): session, language, booking context and your consent choice itself.
  • Your choice is stored in your browser (cookie and local storage "tos_consent_v2") for 180 days.
  • Google Consent Mode v2: before you decide, all Google signals are set to "denied". Advertising identifiers are also removed ("ads_data_redaction").
  • Withdrawal: at any time via "Cookie settings" in the footer, as easily as you gave consent. After that we send no further data to the services concerned. You can also delete Google cookies already set in your browser settings.
  • Campaign details before you decide (tab storage): If you reach our website through an ad or a link with campaign details (Google click identifier gclid, gbraid or wbraid, or utm_source, utm_medium, utm_campaign, utm_term, utm_content) and have not yet made a choice, your browser briefly keeps these checked details in tab storage ("sessionStorage", entry "tos_landing_pending"). They stay in that tab only, disappear when you close the tab and are discarded after 24 hours at the latest. Until you decide, none of it is sent to Google or any other service. Once you decide, we delete this note: if you consent to marketing, we treat the details as described in section 7; if you consent to statistics, we pass the campaign parameters (without the click identifier) to Google Analytics so that your visit can be attributed to the campaign; if you decline, nothing remains.
  • "Do Not Track": If your browser sends the "Do Not Track" signal, we treat statistics and marketing as declined, even if you chose otherwise in the banner. Your stored choice is left unchanged. Legal basis for statistics and marketing: consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG).

5. Google Tag Manager

With your consent to statistics or marketing we load Google Tag Manager (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). It controls which of the Google services below are loaded and technically processes your IP address.

6. Google Analytics 4 (statistics)

With your consent to statistics we use Google Analytics 4 (Google Ireland Limited) to understand how our website is used.

  • For this we assign a pseudonymous identifier that is stored in your browser and contains no name. It is renewed after 13 months and deleted when you withdraw consent.
  • When you book, we send the booking number, value and currency as a "purchase" event, but no name and no contact details.
  • Event data is kept for at most 14 months.
  • Data may be transferred to the USA. The transfer is based on the EU-US Data Privacy Framework (adequacy decision of the European Commission, Art. 45 GDPR).

7. Google Ads & campaign measurement (marketing)

We advertise with Google Ads (Google Ireland Limited). With your consent to marketing we measure whether a booking or enquiry came from an ad.

  • Parameters processed when you click an ad: utm_source, utm_medium, utm_campaign, utm_id/campaignid, utm_term, utm_content, and the Google click identifiers gclid, gbraid and wbraid.
  • Where they are stored: in your browser's local storage for up to 90 days, so that a later booking, enquiry or offer acceptance can be attributed to the ad.
  • What goes to Google:
    • If you have consented, we store the campaign parameters with your booking, enquiry or offer acceptance.
    • In that case, on booking or acceptance we report the click identifier to Google together with the booking number, value and time (conversion import).
    • If the booking is cancelled, we retract the report.
    • We do not send your name or contact details.
  • Data may be transferred to the USA. The transfer is based on the EU-US Data Privacy Framework (adequacy decision of the European Commission, Art. 45 GDPR). Legal basis: consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG).

8. Microsoft Clarity (statistics)

With your consent to statistics we use Microsoft Clarity (Microsoft Ireland Operations Ltd.) to improve the usability of our website, for example through scrolling behaviour, clicks and heatmaps.

  • Form inputs are masked.
  • A data processing agreement with Microsoft is in place.
  • Data may be transferred to the USA on the basis of the EU-US Data Privacy Framework. Legal basis: consent (Art. 6(1)(a) GDPR). More information: https://clarity.microsoft.com/privacy

9. Booking system (TourOS)

We handle bookings, enquiries and offers with our own booking system TourOS, which runs on the servers in the EU named in section 3. We have not used the previous system, Recras B.V. (Netherlands), since 1 September 2026.

  • Data processed: name, contact details, booking and enquiry data, number of participants, tour and date, payment status, and the version of the terms of participation you confirmed, with time and language.
  • Purpose: handling your enquiry, processing and documenting your booking.
  • Chat on the website: TourOS processes your messages on our servers, including with a self-hosted AI language model. We do not pass them on to external AI providers.
  • Legal basis: Art. 6(1)(b) GDPR. For the record of the terms of participation, also Art. 6(1)(f) GDPR.

10. Payment service provider

Payments are processed by Mollie B.V., Netherlands. Legal basis: Art. 6(1)(b) GDPR.

11. Email & message delivery

We send booking confirmations, replies to enquiries, our newsletter including its confirmation email, and other emails via Postmark (USA). Emails you write to us are partly received and answered through our Microsoft 365 mailbox (Microsoft Ireland Operations Ltd.). A data processing agreement with Microsoft is in place. Legal basis: Art. 6(1)(b) GDPR. The transfer to Postmark in the USA is based on Standard Contractual Clauses (Art. 46(2)(c) GDPR). Inviting fellow guests by message (SMS or RCS): If you invite fellow guests to your booking in your customer portal and use delivery by message, we pass the mobile number you entered and the message text to Twilio (Twilio Inc., USA), who deliver the message. The text contains the first name of the person who booked, the name of the tour (shortened), the day and month of the tour, the name of the provider and your personal invitation link. Twilio reports back to us whether the message was delivered. This delivery method is only available when it has been switched on. Legal basis: Art. 6(1)(b) GDPR (performing your booking, inviting your fellow guests at your request). The transfer to Twilio in the USA is based on the adequacy decision for the EU-US Data Privacy Framework, to which Twilio has acceded, alternatively on Standard Contractual Clauses (Art. 46(2)(c) GDPR).

12. Sharing with service partners & independent guides

To deliver the services you book, we work with selected service partners. Where necessary to perform the contract, we pass the required personal data on to them.

  • Restaurants and brewhouses (e.g. to reserve tables)
  • Event and experience partners (e.g. providers of axe throwing or other add-on services)
  • Independent guides who run a booked tour on our behalf

We only pass on the data required to deliver the booked service, in particular:

  • name of the person who booked
  • date and time
  • number of participants
  • booked service or tour details
  • where applicable, contact details for organisational questions

Purpose of processing: pre-contractual measures and performance of the contract.

Legal basis: Art. 6(1)(b) GDPR.

Independent guides act either as separate controllers or, where agreed by contract, as service providers bound by our instructions. Any further use of the data for their own marketing purposes is not permitted.

13. Mobile app "Kölsch Catch"

In addition to our website, we offer the free mobile game app "Kölsch Catch" for Android and iOS (available on Google Play and the Apple App Store).

Data processed: The app requires no registration and no user account, no password and no email address. Scores, statistics and settings (e.g. language, volume) are initially stored only locally on your device.

Online leaderboard. The app also offers a worldwide online leaderboard. Finished runs are entered there automatically. Before this happens for the first time, the app asks for a nickname and expressly points out the automatic entry; if you cancel this prompt, nothing is transmitted. You can switch off automatic entry at any time in the app's settings — a run is then transmitted only when you trigger it yourself. The following is transmitted to our own server infrastructure:

  • a nickname you choose (2 to 16 characters)
  • score, level reached, number of objects caught, best streak and duration of the run
  • your device's timestamp at the time of submission
  • a one-time identifier that prevents the same run from being entered twice by mistake
  • a pseudonymised device identifier (a randomly generated UUID). It contains no information about you, is not linked to any account, and serves only to combine several runs from the same device (only your best run appears in the ranking) and to limit how often submissions can be made. If you delete and reinstall the app, you will usually receive a new identifier that cannot be linked to the previous one. One exception is Android's automatic backup ("Backup & restore"): if it is active in your device settings, Android can back up the app data, including this identifier, in your own Google account and restore it on reinstallation or on a new device — the identifier then stays the same. Whether this happens is controlled in the settings of your device or your Google account; we have no influence on it and no access to this backup.

Your IP address is not stored by the leaderboard application itself — neither in plain text nor hashed, salted or otherwise shortened. It is used there only for the duration of the individual request, to technically limit the frequency of submissions (at most 60 submissions per hour per IP address), and is then discarded immediately; the leaderboard's application logs do not contain it either. As with every request to our website, however, our web server receives the request first, and its access log contains the IP address for purposes of operational security and error analysis — in this respect section 3 applies, with the retention period stated there.

Every submission is technically signed; a plausibility-checked but in principle not forgery-proof mechanism reduces abuse of the leaderboard but cannot rule it out completely.

The leaderboard itself (nickname, score, level reached, time of the run) is publicly visible — for "all time", for the last seven days and for the last thirty days. Only this information is displayed, never a device identifier.

Retention and deletion. Submitted scores are not deleted — the leaderboard remains complete. After 24 months an entry is automatically anonymised: the device identifier is replaced by a new random identifier that can no longer be attributed; nickname, score, level and time remain in the leaderboard. As long as your entry has not yet been anonymised, you can request its deletion via the contact below, stating your device identifier — which the app shows you in the settings.

Data that exists only locally on your device (e.g. the on-device leaderboard, game statistics, settings) is unaffected and stored without limit until you delete it yourself or uninstall the app.

Weekly raffle. Among the ten best runs of a raffle week (each running from Sunday 18:00 to Sunday 18:00), we raffle a voucher for a free place on one of our brewery tours. Participation results automatically from a submitted run — no additional information is required, in particular no name, no address and no email address. You can switch off participation at any time in the app's settings; your runs then still appear in the leaderboard but no longer take part in any draw. To make this effective, we store your device identifier with the time you opted out until you switch participation back on. The terms and conditions of participation apply.

For the draw we process only the information that already exists for the leaderboard (nickname, score, duration, time, pseudonymised device identifier). If you win, we additionally store the voucher code issued for you together with its assignment to your device identifier — this is the only way the app can show you the prize the next time it starts and — if you have allowed notifications — notify you by push notification (see "Win notification by push"). A prize must be collected in the app within 14 days of the draw; after that it lapses. The voucher code is then no longer shown to you and is raffled again in the next draw, i.e. assigned to another winner. The assignment of the lapsed prize to your device identifier remains stored, marked as "lapsed" — it records that the voucher has become free and may be raffled again. As soon as the voucher has expired (twelve months after issue), we detach the assignment of a prize — collected or lapsed — from your device identifier by the following day at the latest: it is replaced by a new random identifier that can no longer be attributed; nickname, score and time of the draw remain for the list of winners. Until then you can request its deletion at any time via the contact below, stating your device identifier (shown in the app's settings). A winner's nickname may be displayed in the app together with the time of the draw so that draws can be traced; it is self-chosen and appears in the public leaderboard anyway.

Voucher by email — voluntary. On request you can additionally have the voucher sent to you by email. The address you enter is transmitted solely for this dispatch to our booking system TourOS (see section 9), which sends the email via Postmark (see section 11). Neither the app on your device nor the app's server infrastructure stores the address. TourOS does, however, keep it in its dispatch queue and records the dispatch with the recipient address and time in its dispatch log so that delivery can be proven; no automatic deletion period is currently set up for this. We will delete these entries at your request. If you want the voucher sent again, you enter the address again. The legal basis is Art. 6(1)(b) GDPR (conduct of the prize draw at your request).

The legal basis for conducting the raffle itself is Art. 6(1)(f) GDPR — legitimate interest in a customer-loyalty measure around our brewery tours. You can object at any time by switching off participation in the app.

Hosting. The online leaderboard runs on the same own server infrastructure (dedicated server at Hetzner Online GmbH, Falkenstein, Germany) as our website and "Schocken" (see sections 3 and 14). For the leaderboard itself there is no third-party provider, no crash reporting and no user account; its data goes exclusively to us. For the separate usage statistics and the win notification, see the following paragraphs.

Usage statistics — only with your consent. The app can collect pseudonymised usage statistics via Google Analytics for Firebase (provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). This happens only if you expressly consent at first launch. Until then, collection is already switched off in the delivered app; nothing is collected and nothing is sent. You can withdraw your decision at any time in the settings; the withdrawal takes effect immediately.

After consent, the following is transmitted:

  • four events from the game: level reached, end of a run (with reason, level reached and score), an entry in the leaderboard (only with its outcome, e.g. "successful" or "will be sent later") and an explicit language choice
  • the information Google collects automatically: app start, session duration, screens viewed, app and operating system version, device model
  • an app instance identifier assigned by Firebase. It is device-related, not linked to any account and is reassigned when the app is deleted.
  • Google derives an approximate location (country, region) from your IP address. The IP address itself is truncated by Google and not stored.

Expressly not transmitted are your nickname, the leaderboard device identifier and your IP address. The advertising ID of your device (Advertising ID) and the Android device-internal identifier (SSAID) are also switched off — there is no recognition across other apps, no advertising, no personalisation and no linking with Google Ads.

Google processes this data as our processor; a transfer to the USA may take place, secured by the EU Commission's standard contractual clauses and the EU-US Data Privacy Framework. Retention at Google is at most 14 months.

Win notification by push — only with your permission. As soon as you have submitted a run in a raffle week or a prize is waiting for you, the app asks once in the main menu, via your device's system prompt, whether it may send you notifications. On Android up to version 12 there is no such system prompt: notifications are permitted by the system from installation; there you can object by switching off notifications for this app in the system settings or by opting out of the raffle. Once this occasion has arisen and notifications are permitted, the app transmits the following to our server for as long as you take part in the raffle:

  • a push token (a device identifier assigned by the operating system or the push service, through which a notification can be delivered),
  • the platform (iOS or Android) and
  • the app language (German or English).

We store this information together with your pseudonymised leaderboard device identifier. If the token or the app language changes, the app reports this immediately; otherwise it refreshes the information at most every seven days.

Purpose, exclusively: to tell you that you have won a raffle ("You won!" with a note on the 14-day collection period). There is no advertising, no marketing messages and no other notifications. After a draw we send one notification per prize; if delivery fails, we try again until the end of the collection period, so in exceptional cases it may arrive twice.

Delivery via third parties. We hand the notification to the Expo Push Service (650 Industries, Inc., USA, "Expo"), which forwards it to Google Firebase Cloud Messaging (Google Ireland Limited, Ireland / Google LLC, USA) for Android devices or to the Apple Push Notification service (Apple Distribution International Ltd., Ireland / Apple Inc., USA) for iOS devices. For this purpose these services receive the push token and the content of the notification and process them on our behalf solely for delivery. A transfer to the USA may take place, secured by the EU Commission's standard contractual clauses or the EU-US Data Privacy Framework. Already when the push token is created, the app exchanges technical device data for this purpose directly with Expo and your operating system's push service. No linking with advertising data takes place.

The legal basis is Art. 6(1)(a) GDPR (your consent in the system prompt) in conjunction with Section 25(1) TDDDG. On Android up to version 12, where there is no system prompt, we base the win notification on Art. 6(1)(f) GDPR — our legitimate interest in informing you about a prize before it lapses; you can object at any time by switching off notifications for this app in the system settings or by opting out of the raffle. You can withdraw your consent at any time — in your device's system settings under "Notifications" for this app. After such a withdrawal, the app deregisters your device with our server the next time it is opened, and we delete the token; if the app cannot reach the server, the token is deleted at the latest 180 days after the last refresh. If you switch off participation in the raffle in the app's settings, we delete the token immediately and do not accept a new one unless you take part again. Without permission or after withdrawal, you will still learn of a win when you open the app.

Retention: until you opt out of the raffle, until the app deregisters the device after a withdrawal, until the operating system or push service reports the token as invalid (e.g. after uninstallation), or until 180 days after the last refresh — whichever comes first.

Permissions: For technical reasons (the app framework used and the online leaderboard), the app requests internet access. In addition — only once the win notification becomes relevant, and only once — it asks for permission to send notifications (on Android 13 and later: "Notifications"). You can decline; the app then remains fully usable.

Distribution via app stores: When you download and install the app, Google (Google Ireland Ltd., for Google Play) or Apple (Apple Distribution International, for the App Store) process data such as device and payment information under their own responsibility. Their respective privacy policies apply.

Legal basis: For the online leaderboard, Art. 6(1)(f) GDPR — legitimate interest in operating a worldwide leaderboard as the core of this feature. Because finished runs are entered automatically, we no longer base it on Art. 6(1)(b) GDPR alone; you are informed before the first transmission and can object at any time by switching off automatic entry in the settings. Also based on Art. 6(1)(f) GDPR are the purely technical, tightly time-limited use of your IP address for rate limiting and its logging in the web server for operational security and error analysis (see section 3).

For the usage statistics, the basis is Art. 6(1)(a) GDPR (your consent) in conjunction with Section 25(1) TDDDG for access to information on your device. Without this consent, no collection takes place.

The legal basis of the win notification is, as described above, your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG), and on Android up to version 12 our legitimate interest (Art. 6(1)(f) GDPR).

For all other functions of the app (game, local leaderboard, settings), no processing on our part is relevant under data protection law, as this data does not leave your device.

14. Online game "Schocken"

At schocken.koelschcrew.de and as an Android app, we offer the online multiplayer dice game "Schocken" (public matchmaking, private game rooms, single player against the computer, local multiplayer mode).

Data processed: You take part without registration, using a guest nickname of your choice (max. 20 characters). No password, no email address and no permanent user account are collected. When you play, we process:

  • nickname (pseudonym)
  • game and room data (e.g. points/lid count, game history)
  • chat messages sent within a game
  • IP address (technically to establish the connection and to protect against misuse/overload, e.g. rate limiting)

Purpose: providing the game features (matchmaking, real-time synchronisation of moves, chat within a game) and protecting the server infrastructure against misuse.

Note: Please do not share personal data in the chat (e.g. your real name or contact details).

Retention: Room and game data are kept only for the duration of the game session and are then deleted automatically. IP addresses are processed as part of the server logs in accordance with section 3.

Hosting: "Schocken" runs on one of our own servers at Hetzner Online GmbH in Falkenstein, Germany (see section 3). The server is located in the EU.

Legal basis: Art. 6(1)(b) GDPR (providing the game feature you use) and Art. 6(1)(f) GDPR (legitimate interest in protection against misuse and operational security with regard to IP processing).

15. Recipients

  • Hetzner Online GmbH (hosting of the website, booking system and "Schocken", Germany and Finland)
  • Google Ireland Limited (Tag Manager, Analytics, Ads, only with consent; Google Play for "Kölsch Catch"; in the "Kölsch Catch" app, only with consent or permission, also Google Analytics for Firebase and Firebase Cloud Messaging for push notifications to Android devices)
  • Microsoft Ireland Operations Ltd. (Clarity, only with consent)
  • Microsoft Ireland Operations Ltd. (Microsoft 365 mailbox)
  • Postmark (email delivery, USA)
  • Twilio Inc. (SMS/RCS delivery of fellow-guest invitations, USA; only if you use this delivery method)
  • Google Ireland Limited (YouTube, embedded videos, only with consent to external media)
  • Mollie B.V. (payments, Netherlands)
  • Apple (App Store for "Kölsch Catch"; only if permission is granted, also the Apple Push Notification service for notifications to iOS devices)
  • 650 Industries, Inc. ("Expo", USA; delivery of the win notification of the "Kölsch Catch" app, only if permission is granted, see section 13)
  • Service partners and independent guides (see section 12)

16. Retention

  • Server logs: 7–30 days
  • Consent choice in your browser: 180 days
  • Analytics event data: up to 14 months. Pseudonymous identifier: 13 months.
  • Campaign parameters in your browser: up to 90 days. Stored with a booking, enquiry or acceptance: as long as the booking data.
  • Campaign details in tab storage before you decide: until the tab is closed, 24 hours at most.
  • Fellow-guest invitations (contact details entered, including the mobile number): 14 days after the tour, or 14 days after cancellation if the booking is cancelled. We then delete them.
  • Contract data: in line with commercial and tax retention periods
  • "Kölsch Catch" — local data (progress, settings): without limit, until you delete it yourself or uninstall; no server-side storage
  • "Kölsch Catch" — online leaderboard: scores are not deleted, anonymised after 24 months (see section 13); the leaderboard application itself does not store the IP address, not even hashed — for the web server's access log, the retention period for server logs stated above applies
  • "Kölsch Catch" — weekly raffle: the assignment of a voucher code to a device identifier until the voucher expires (twelve months after issue), after which the device identifier is replaced by a random identifier by the following day at the latest (see section 13); an opt-out from the raffle (device identifier and time) until you take part again; an email address entered for dispatch is not stored in the app or the app's server infrastructure, and is kept in our booking system's dispatch queue and dispatch log without an automatic deletion period (deletion on request, see section 13)
  • "Kölsch Catch" — usage statistics (only with consent): at most 14 months at Google
  • "Kölsch Catch" — win notification (only if permission is granted): push token, platform and app language until you opt out of the raffle, until the app deregisters the device after permission is withdrawn, until the push service reports the token as invalid, or until 180 days after the last refresh (see section 13)
  • "Schocken": only for the duration of the game session.

17. Your rights

You have the right to access, rectification, erasure, restriction of processing, data portability, objection, and withdrawal of consent with effect for the future.

Right to object (Art. 21 GDPR): where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR, for example server logs or the record of the terms of participation), you may object at any time on grounds relating to your particular situation. You may also lodge a complaint with a data protection supervisory authority. Contact: tours@koelschcrew.com

18. Changes

We update this privacy policy when our services or the legal situation change.