Privacy Policy for your customer account, the app and online ordering

1.1 Overview

• The app and the order portal are operated by Nhas Food 1993 GmbH. Each “City Chicken” restaurant is run by its own company, the operating company; in Cologne, this is MOG Gastro GmbH. You make the contract for your booking with this company, whether you book in the app or in the order portal, and we take care of your booking together with it. You can contact us with any questions about data protection.
• We use your data for your customer account, your bookings, your requests and the security of the app and the order portal. We do not sell it.
• When you check in at the restaurant, we pass your order with your first name to the restaurant’s point-of-sale system so that the kitchen can prepare it and the till can record it. It remains stored there for as long as the operating company has to keep its till records, usually ten years, even if you delete your customer account (section 5.7). We then show you the till receipt in the app and in the order portal (section 5.8).
• The app does not show advertising from other companies, does not read any advertising identifier and does not analyse how you use it. In the order portal, we do not use any analytics or advertising services; your browser only stores there what is needed for the functions you use (section 12.4). However, Stripe’s payment module, in the app Google’s services for push notifications and the map, and in older app versions also for checking the internet connection, and on the iPhone Apple’s map collect technical data about your device or browser themselves (sections 6 to 8 and 12.6).
• The app only loads the map showing the restaurants if you agree and confirm that you are at least 16 years old (section 8).
• We do not receive your location.
• You can delete your customer account in the app and in the order portal, export your data there, ask for information about your data and complain to a data protection authority (section 17).

Your right to object: Where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you have the right to object, on grounds relating to your particular situation, at any time to this processing. You can find the details in section 17.

2.1 Nhas Food 1993 GmbH

The app and the order portal are operated by Nhas Food 1993 GmbH, Südwestkorso 14, 12161 Berlin, represented by its managing director, Nesrin Nhas, e-mail media@citychicken-nhas.de, phone +49 30 62904952. We alone are responsible for registration and sign-in, your customer account and your profile, push notifications, the restaurant map, the contact form, protection against misuse, showing that you are signed in in the header of our website (section 13.2) and the addresses at nhascitychicken.app (section 13.1).

2.2 Operating companies of the restaurants

Each “City Chicken” restaurant is operated by its own company (the operating company), with which you conclude the booking contract. The restaurant in Cologne, Breite Straße 29, is operated by MOG Gastro GmbH, Torstraße 125, 10119 Berlin, represented by its managing director, Adel Khalaf, e-mail mog@citychicken1993.de, phone +49 1525 7378706. If another restaurant becomes bookable in the app or in the order portal, we name its operating company here before you can book there.

2.3 Joint responsibility for bookings

We and the operating company of the booked restaurant are jointly responsible (Art. 26 GDPR) for the hold, the booking, the order and the payment, for the QR ticket and the check-in, including passing your order to the restaurant’s point-of-sale system and the status reported back, for providing your till receipt, for cancellations and refunds, for the booking confirmation, for ratings of your visit and for your requests about a booking, including after your visit. This applies equally to bookings in the app and in the order portal. The operating company uses your booking data to serve you, to receive your payment and to reach you if anything changes, and your rating to improve its restaurant. Other operating companies do not receive your booking. The operating company alone is responsible for the data in its point-of-sale system (section 5.7).

2.4 The essence of our arrangement

In an arrangement under Art. 26 GDPR, we and the operating company have set out who fulfils which obligation:

• We inform you and are your central point of contact for all data protection matters. The operating company forwards any requests it receives to us without undue delay.
• We operate and secure the app, the order portal and the systems behind them, decide which data is collected and what your device or browser stores for this, and conclude the contracts with the technical service providers. The operating company concludes the contracts with Stripe and with the provider of its point-of-sale system itself and also decides which payment methods it offers.
• At check-in, we pass your order to the operating company’s point-of-sale system. We decide together which data goes there. In the point-of-sale system, the operating company decides who has access to your data, how long it is kept and when it is deleted; it provides information about this data through us. In your customer account, we provide you, on behalf of the operating company, with the till receipt that the point-of-sale system sends us.
• We only collect and store ratings of your visit so that the operating company can improve its restaurant; we do not use them for our own purposes.
• The operating company only gives access to your booking to the staff who need it and obliges them to keep it confidential.
• The companies inform each other of data breaches without undue delay. We report incidents involving the app, the order portal or our systems to the supervisory authority and tell you about them if the law requires this; the operating company deals with incidents in the restaurant.

Even so, you can exercise your rights against each of the companies involved.

2.5 After your booking is completed

We show you your bookings in your customer account for as long as it exists; we alone are responsible for this. After your visit, a cancellation or the expiry of your booking, the operating company alone is responsible insofar as it stores booking and payment data because the law requires it to keep this data, and uses the data for its accounting (Art. 6(1)(c) GDPR), or asserts or defends claims under the booking contract (Art. 6(1)(f) GDPR; its legitimate interest is to resolve such claims). In doing so, we act only on its behalf and on its instructions.

2.6 Data protection officer

Nhas Food 1993 GmbH and MOG Gastro GmbH have appointed the same data protection officer. You can reach him at the address of Nhas Food 1993 GmbH, marked “Datenschutzbeauftragter” (data protection officer), or by e-mail to r.heyne@citychicken-nhas.de.

3.1 Which data

You need a customer account to book in the app or in the order portal. The same account works for both, and you sign in to the app and the order portal with the same details. For this, we process:

• your e-mail address,
• your first and last name,
• your mobile number,
• in the app, your country,
• the language of your customer account, German or English; in the app, you choose it yourself, and in the order portal we take German when you register if you use the pages in German, and English otherwise,
• the time and version of your agreement to the Terms and Conditions, the version of this Privacy Policy that we pointed you to at that time, and the time at which you took note of a new version, each with the kind of event and, where the app or the order portal sends them, the channel (app for iOS or Android, or order portal), its version, the language of the text and of the screen, the identifier of the wording shown and the checksum of the text.

Your e-mail address, name and mobile number are required, and in the app also your country; without them, you cannot create a customer account or book. A profile picture and, in the app, links are optional (section 4).

3.2 Sign-in with codes

There is no password. When you register, you receive a code by e-mail, and you confirm your mobile number with a code sent by text message (SMS). After that, you sign in with a code sent by text message; as long as your number has not been confirmed, you receive the code by e-mail. Supabase manages the customer accounts for us, and Twilio sends the text messages. The e-mails with codes are created by a function at Supabase and sent via Cloudflare’s e-mail service (Cloudflare Email Service).

In the order portal, your browser connects directly to Supabase for the codes sent by e-mail and for confirming your mobile number, just like the app. If you sign in there with a code sent by text message, our server at Vercel (section 11.5) checks the code through our interface. Our server then stores your sign-in in a cookie in your browser (section 12.4). When you sign in or register, you can tick the box “Stay signed in”. If you do not tick it, your sign-in ends when you close your browser, unless your browser restores your last session. If you tick it, you remain signed in until you sign out or have not used the order portal for 30 days.

3.3 Legal basis

The legal basis is Art. 6(1)(b) GDPR, because the processing is necessary for the user agreement for the platform, that is, for your customer account in the app and the order portal. We need your confirmed mobile number so that the restaurant can reach you if anything changes and so that nobody blocks time slots with many customer accounts. We store the record of your agreement to the Terms and Conditions so that we can prove that the contract was concluded; to that extent, the legal basis is also our legitimate interest in keeping this record (Art. 6(1)(f) GDPR). When you sign in, we also process your IP address to detect and fend off misuse (section 11).

4.1 Profile picture and links

In your profile, you can choose to add a profile picture and, in the app, links to your Instagram or TikTok profile. We show these details to you in the app and the order portal and, as long as you are signed in to the order portal, also show your profile picture or your initials in the header of our website (section 13.2); we do not use them for anything else. Other users do not see your profile details; on our side, only authorised persons can see them.

The app only accesses your camera and photo library when you start this yourself; if your device requires permission for this, it asks you first. From your photo library, the app only takes the picture you select. In the order portal, you select the picture through your browser’s file dialog and choose the section to use. Our server at Vercel (section 11.5) checks the picture, removes metadata such as the location, time and camera details, reduces it to no more than 1024 × 1024 pixels and stores only this cleaned picture with our service provider Supabase.

4.2 Legal basis and changes

The legal basis is Art. 6(1)(b) GDPR, because the profile is a function of the user agreement that you can choose to use. You can change your name in the app and in the order portal, and your links in the app. You can replace a profile picture in the app, and replace or remove it in the order portal; if you want to remove it in the app, write to us at media@citychicken-nhas.de. When a profile picture is replaced or removed, we delete the previous file immediately. If, after a new picture has been uploaded, it cannot be added to your profile, the uploaded file remains stored until your customer account is deleted (section 16.1).

5.1 Which data

When you book a time slot, we process the following together with the operating company (section 2.3):

• the restaurant, the number of people and the time slot, including during the hold while you order,
• the food and drinks ordered with your choices, and prices and taxes,
• the payment status and Stripe’s payment reference,
• the time at which you confirmed the rules on cancellation and check-in, with the check-in window, the cancellation deadline, the refund share and the version of the Terms and Conditions that apply to your booking,
• your QR ticket with the booking code, the time of your check-in and the person who checked you in or, if the staff do not let you in after your time slot, the time of that decision and the person who made it,
• after check-in, your pickup number, the status of your order in the point-of-sale system, a copy of the receipt data, the till receipt as a PDF file and, where applicable, the refund of a difference (sections 5.7 and 5.8),
• where applicable, cancellations, refunds and the expiry of a booking.

A booking is not possible without these details. In the order portal, your browser stores your basket until you order, for no more than seven days (section 12.4).

5.2 Who can see the booking

On the business day of your time slot, the staff at the restaurant’s door can see the following in a list of bookings, even before you check in:

• your first name and the first letter of your last name,
• the number of people and the time slot,
• your order with the total amount and our order number,
• the status of your booking, for example whether you have checked in, and after check-in the status of your order in the point-of-sale system and your pickup number.

After check-in, the staff at the till and the kitchen see your first name, your order, our order number, the time slot, the number of people and your pickup number, on the kitchen screen or on a kitchen ticket. The staff at the door can then also open your till receipt in order to reconcile it with the till and to clarify queries (section 5.8).

Authorised persons at the operating company and in our administration see bookings with your name and contact details, insofar as they need them for running the restaurant, for queries, refunds and accounting. If someone opens or edits bookings or other guest data in our management system, for example when checking you in at the door, we record who opened or edited which bookings or customer accounts, when, and what was changed. Our legitimate interest in this is being able to trace who has accessed your data and to investigate unauthorised or improper access (Art. 6(1)(f) GDPR). We delete these records after one year, unless we need individual records for longer to investigate a specific incident.

5.3 Booking confirmation by e-mail

After your booking, you receive a booking confirmation by e-mail. We send it in the name of the operating company via Cloudflare’s e-mail service; replies go to the operating company’s mailbox. We use the same route to let you know when we refund a difference because the till charged less than you paid (section 5.7).

5.4 No note on your order

You cannot add a note for the restaurant to your order, so we do not pass any note on to the point-of-sale system either. Please raise allergies and intolerances directly at check-in.

5.5 Rating of your visit

Once the restaurant has marked your booking as completed, the app asks you on the home screen to rate your visit; the order portal does not ask for ratings. It is up to you whether you do so; if you do, you give stars and can add a comment. The rating belongs to your booking: the operating company uses it to improve the food and service in its restaurant. For this purpose, we collect and store it within our joint responsibility for your booking (section 2.3) with your order, your customer number and the time, and we do not use it for our own purposes. Authorised persons at the operating company and in our administration see it with your first name; other users do not see it. The legal basis is the operating company’s legitimate interest in improving its restaurant (Art. 6(1)(f) GDPR). We delete the rating together with your customer account (section 16.1).

5.6 Legal basis

The legal basis is Art. 6(1)(b) GDPR, because the processing is necessary for your booking contract with the operating company and for your user agreement with us. The booking confirmation is also required by law (Art. 6(1)(c) GDPR in conjunction with § 312f Abs. 2 BGB (German Civil Code)). Section 16 explains how long booking and payment data is kept. Section 5.7 applies to passing your order to the restaurant’s point-of-sale system.

5.7 Passing your order to the restaurant’s point-of-sale system

When you check in at the restaurant, our server passes your paid order to the operating company’s point-of-sale system (Lightspeed Restaurant). This way, the kitchen receives your order on its screen or as a kitchen ticket, and the till records it as paid and creates the till receipt. For this, we transmit:

• your first name, or the word “Gast” (German for “guest”) if there is no first name,
• the food and drinks ordered with item number, quantity and your choices; if an item is now more expensive at the till than what you paid, a discount equal to the difference,
• the amount charged by the till, marked as paid through the platform,
• a pickup number under which the restaurant calls your order,
• an order note with our order number, the time slot and the number of people,
• instead of your e-mail address, an e-mail address of ours to which the point-of-sale system sends the till receipt (section 5.8).

We do not transmit your last name, your e-mail address, your mobile number, your customer number or payment data such as Stripe’s payment reference. For bookings that you paid for before 6 a.m. on 4 October 2026, we only transmit the word “Gast” instead of your first name. If the transfer fails, the staff enter your order at the till.

If the till charges less for your order than you paid, we automatically refund the difference to your payment method through Stripe on behalf of the operating company and let you know by e-mail (section 5.3).

The point-of-sale system tells us the status of your order, for example whether it has been accepted, is ready or has been cancelled at the till, together with the identifier of the transaction in the till. Once the transaction has been completed, we retrieve the receipt data, and the point-of-sale system sends us the till receipt (section 5.8). With your booking, we store, in addition to the till receipt, the status with the times, the pickup number, the identifier of the transaction in the till, a copy of the receipt data with the receipt number, times, till device, items, taxes and payments without the names of guests or staff, and the result of our price check between the app and the till. This way, the staff at the door can see whether your order has reached the till, and your booking, your payment and the till entry can be matched.

The operating company alone is responsible for your data in the point-of-sale system; Lightspeed processes it there as its processor (sections 14.1 and 15.3). The till records your order and protects the record with its technical security device. The operating company must keep the record and must not alter it in a way that means its original content can no longer be determined (§ 146 Abs. 4 and § 147 AO (German Fiscal Code)). The record therefore remains stored in the point-of-sale system together with your first name even if you delete your customer account; your right to erasure does not apply to this extent (Art. 17(3)(b) GDPR). After your visit, the operating company only uses the record for its accounting and for audits by the tax office; once the retention period has ended, it has it deleted (section 16.1).

The legal basis for passing on your order is Art. 6(1)(b) GDPR, because the restaurant needs your order to fulfil your booking contract. We transmit your first name so that the kitchen and the till can match your order to you; tax law does not require it, but it becomes part of the record. When the operating company records an order with its electronic till, the till must record it individually and protect it with its technical security device; the operating company must issue a receipt for it and keep the records (Art. 6(1)(c) GDPR in conjunction with §§ 146, 146a and 147 AO). We also store the pickup number and the till’s receipt number with your booking on behalf of the operating company (section 2.5), because it must be possible to trace how each order came about and how it was handled (Art. 6(1)(c) GDPR in conjunction with § 145 Abs. 1 Satz 2 AO). We store the status of your order, the other receipt data and the price check because we need them for your check-in and to handle your booking, for example for queries and refunds, including the refund of a difference (Art. 6(1)(b) GDPR).

5.8 Till receipt in the app and in the order portal

Once your transaction has been completed at the till, the point-of-sale system sends us the operating company’s till receipt as a PDF file to the e-mail address that we transmitted instead of yours (section 5.7). Lightspeed sends it through its e-mail service provider in the USA, currently SendGrid (section 15.3). Cloudflare receives the e-mail for us in its worldwide network (section 15.1) and stores it in a storage facility in the European Union. Our server checks that it comes from Lightspeed, automatically reads the receipt number, the total, our order number and the details of the technical security device from the PDF file and uses them to match the till receipt to your booking. We store the PDF file with these details and a checksum with our service provider Supabase and then delete the e-mail (section 16.1). We delete till receipts for a refund made at the till immediately, without storing them or showing them to you.

After check-in, you can see the till receipt and your pickup number with your booking in the app and in the order portal. If the staff enter your order at the till (section 5.7), the point-of-sale system does not send us a till receipt; you then get it at the till. You can share or save the PDF file; we do not send you the till receipt by e-mail. It contains the details of the till receipt, including the details of the technical security device, as well as your first name, your pickup number and our order number. You can get a paper receipt at the till on request. The staff at the door can also see your till receipt after check-in in order to reconcile it with the till and to clarify queries (section 5.2).

The legal basis is Art. 6(1)(c) GDPR in conjunction with § 146a Abs. 2 AO, because the operating company must provide you with a receipt, and Art. 6(1)(b) GDPR, because we show you the till receipt in your customer account. We store the till receipt and the related details until your customer account is deleted (section 16.1); until then, you can open and save it with your booking, and your data export shows its number (section 16.2). We and the operating company are jointly responsible for providing the till receipt after your check-in (section 2.3); after that, we show it to you in your customer account under our own responsibility (section 2.5).

6.1 How payment works

You pay in advance to the operating company, which has its own account with Stripe for this purpose (Stripe Payments Europe, Limited, Dublin, Ireland). In the app, you pay by credit or debit card or, depending on your device and on activation, with Apple Pay, Google Pay, Klarna or Link; in the order portal, by credit or debit card, with Klarna and, depending on your device and browser, with Apple Pay or Google Pay (section 6.4). You enter your payment details directly in Stripe’s payment window in the app, in Stripe’s payment field on the checkout page of the order portal or with the payment service you choose; we and the operating company do not receive them. Depending on the payment method, the payment window or the payment field may also ask for your e-mail address, phone number or address; this information goes directly to Stripe or to the service you choose. On behalf of the operating company, we send Stripe the amount, the currency, the order number, the internal identifier of the order, the subtotal, the tax amount, the time slot and the number of people, and in the case of a refund the payment reference, the refund amount, the order number, the internal identifier of the order and the reason for the refund, but neither your name nor your e-mail address. Stripe sends us information about each payment and refund, such as the payment status, the payment reference, the amounts and the payment method, where applicable also features of your payment method such as the card brand and the last four digits of the card number, and information you entered in the payment window or payment field. Of this, we only store the status, the payment reference, the amounts and the payment method without the card number, for example “Visa”, “Apple Pay” or “Klarna”; the booking confirmation also shows you the payment method.

6.2 Data that Stripe collects on your device in the app

Stripe’s payment module is part of the app and currently starts when the app starts. It reads information about your device, such as the device model, operating system, language setting and screen size, as well as an identifier that your device assigns separately for each app provider (on iPhones, the “identifier for vendor”; on Android, the Android ID). In addition, it stores its own identifiers on your device, records how you use the payment window and sends this data to Stripe, including the device identifier, which it also sends together with usage data for analytics. Stripe uses the data under its own responsibility to detect fraud, to secure the payment window and to improve its products through its own analytics, but, according to Stripe, not for advertising. Stripe decides how long it stores its identifiers on your device; you can find the details in Stripe’s privacy policy (section 6.3).

The legal basis for storing and reading this information is § 25 Abs. 2 Nr. 2 TDDDG (German Telecommunications Digital Services Data Protection Act), because this is necessary so that the app’s payment function is available securely and fraud can be detected. For the app’s transmission of this data to Stripe and for our provision of payment data to Stripe for fraud prevention, we and the operating company rely on the legitimate interest in secure payments and in preventing fraud (Art. 6(1)(f) GDPR).

6.3 Legal basis and role of Stripe

The legal basis for the payment is Art. 6(1)(b) GDPR. Stripe Payments Europe, Limited processes the payment data as a processor on behalf of the operating company. As authorised payment service providers, Stripe Technology Company, Limited, Stripe Payments Europe, Limited and Stripe Technology Europe, Limited, all in Ireland, are jointly responsible in their own right for the payment. Stripe is also responsible in its own right for fraud prevention, for legal obligations such as preventing money laundering and for its own analytics; in the process, data is also sent to Stripe, LLC in the USA (section 15). You can find more information in Stripe’s privacy policy (opens in a new tab); you can also exercise your rights directly with Stripe.

6.4 Apple Pay, Google Pay, Klarna and Link

If you choose Apple Pay or Google Pay, Apple (Apple Distribution International Limited, Cork, Ireland) or Google (Google Ireland Limited, Dublin, Ireland) processes the payment with the payment method from your wallet under its own responsibility. If you choose Klarna, the payment window or the payment field takes you to Klarna (Klarna Bank AB (publ), Sveavägen 46, 111 34 Stockholm, Sweden); Klarna processes the information you provide there, such as your name, address, e-mail address and phone number, under its own responsibility and, according to Klarna, may check your identity and your ability to pay. If you use Link, you give Stripe your e-mail address or phone number yourself, and Stripe stores your payment details in your Link account under its own responsibility. We only offer Link in the app. Klarna’s privacy terms apply on Klarna’s page, including to cookies that Klarna sets there; in the order portal, you then return to the page of your order (section 12.4). From all of these services, we and the operating company only receive, via Stripe, the information listed in section 6.1. The legal basis is Art. 6(1)(b) GDPR. You can find more information in the privacy policies of Apple (opens in a new tab), Google (opens in a new tab), Klarna (opens in a new tab) and Link (opens in a new tab).

6.5 Data that Stripe collects in your browser in the order portal

In the order portal, we only load Stripe’s payment module (Stripe.js) on the checkout page, that is, only once you go to the checkout; the page on which you pay for an order that has not yet been paid also counts as the checkout page. It displays the payment field and helps prevent fraud. For this purpose, it sets the cookies __stripe_mid, with a lifetime of one year, and __stripe_sid, with a lifetime of 30 minutes, for our entire domain citychickennhas.de; both lifetimes start again as soon as Stripe.js is loaded again. According to Stripe, the cookie m, with a lifetime of up to two years, is added for the domain m.stripe.com. Stripe.js also collects characteristics of your browser and device, such as the browser, operating system, language setting and screen size, the address and title of the checkout page, and information on how you use the checkout page and the payment field, such as mouse movements and the time spent, and sends this data to Stripe. According to Stripe, a security check by the hCaptcha service, which Intuition Machines, Inc., USA, operates as a processor for Stripe, may be loaded in the process. According to Stripe, it uses this data only to detect fraud and to secure payments and not for advertising. We and the operating company are jointly responsible for embedding Stripe.js on the checkout page and for transferring this data to Stripe; Stripe is responsible for its further use (section 6.3).

The legal basis for storing and reading this information is § 25 Abs. 2 Nr. 2 TDDDG, because this is necessary so that the payment function you use by opening the checkout is available securely and fraud can be detected. For the transfer to Stripe, we and the operating company rely on the legitimate interest in secure payments and in preventing fraud (Art. 6(1)(f) GDPR).

7.1 Permission and device token

As soon as you have registered and confirmed your mobile number, the app asks you whether it may send you notifications; on iPhones and from Android 13 onwards, this happens through your device’s dialog. On devices with Android up to version 12, there is no such request; there, notifications are allowed until you turn them off in your device settings. For delivery, Google’s notification service Firebase Cloud Messaging creates an installation ID and a device token on your device; this may already happen the first time you start the app. The app sends the token to us, and we store it with your customer account. On iPhones, Apple delivers the notifications through the Apple Push Notification Service. We do not send push notifications in the order portal.

7.2 Which notifications

By push notification, we may send you messages about your bookings and about using the app, for example a notice about a booking or about a change to the app. We do not send you advertising or requests for ratings by push notification; if we want to do so in the future, we will ask you separately beforehand. Notifications may also appear in the app’s list of notifications.

7.3 Legal basis and turning them off

The installation ID and the token are stored and read because this is necessary to deliver the notifications (§ 25 Abs. 2 Nr. 2 TDDDG); we base any further processing on Art. 6(1)(b) GDPR. You can turn off the notifications at any time in your device settings. If you sign out, we delete the token on our systems; if you delete your customer account, we delete it after 30 days at the latest (section 16.1). The installation ID remains on your device until you delete the app.

8.1 Map services from Google and Apple

On Android devices, the map on the app’s “Stores” screen comes from Google Maps. On the iPhone, you choose in the notice about the map whether the app loads it from Apple (Apple Maps) or from Google Maps. The app only loads a map when you tap “I am 16 or older – load map” in the notice about the map on Android, or “Load Apple Maps” or “Load Google Maps” on the iPhone; only then does your device connect to the map service you chose. The order portal does not show a map.

If you load the map from Google, according to Google, it processes, among other things, your IP address, device identifiers and usage, performance and crash data, including for its own purposes, and may transfer data to Google LLC in the USA (section 15). We are responsible for embedding the map and for transferring this data to Google, and Google Ireland Limited, Dublin, Ireland, is responsible for its further use; you can find more information in Google’s privacy policy (opens in a new tab).

If you load the map from Apple, your iPhone retrieves the map data from Apple’s servers. Apple receives your IP address and, according to its information on Apple Maps, among other things the time of the request, the device model and software version, the input language, the map area visible on your device and details of how you use the map. According to Apple, it associates this usage data with an identifier that changes several times an hour and is not linked to your Apple Account; for performance, statistics and protecting the service, Apple also uses longer-lived identifiers, which are not linked to your Apple Account either. Apple also uses the data to provide and improve its maps and other location-based services, generally stores data with Apple Inc. in the USA and bases the transfer there on standard contractual clauses. We are responsible for embedding the map and for transferring this data to Apple, and Apple Distribution International Limited, Cork, Ireland, is responsible for its further use; you can find more information in Apple Maps & Privacy (opens in a new tab) and in Apple’s privacy policy (opens in a new tab).

8.2 Consent and withdrawal

The legal basis for loading the map is your consent (§ 25 Abs. 1 TDDDG, Art. 6(1)(a) GDPR). You give it by confirming that you are at least 16 years old and loading a map; on the iPhone, it applies to the map service you choose. If you are under 16, the law does not allow you to consent on your own; in that case, tap “Continue without map” and you will see the restaurants as a list with their addresses. The app only stores your decision on your device. You can withdraw your consent at any time with effect for the future: on Android devices by turning off the “Map display” switch in the app’s settings, on the iPhone by choosing “No map” under “Map display” there. After that, the app no longer loads a map. On the iPhone, you can also switch the map service under “Map display”; the app then no longer loads the map of the previous service.

8.3 Your location

The app does not ask for your location itself. If you have allowed the app to access your location in your device settings, the loaded map shows your position as a dot; on iPhones, this may also lead your device to ask you for permission the first time the map loads. Your position is processed by the map service whose map you have loaded (section 8.1); we do not receive or store your position. You can withdraw location access at any time in your device settings. With “Directions” on a restaurant’s page, you open its location outside the app in a map service, on the iPhone in Apple Maps or Google Maps as you choose; the privacy terms of its provider apply there. The order portal does not access your location; there, “Get directions” opens Google Maps in a new tab, and Google’s privacy terms apply.

The app does not currently use any usage analytics. If we introduce it, we will ask for your consent in the app beforehand and add to this section.

10.1 Which data

Using “Feedback”, you can send us a message with a category, a subject and up to five pictures from your photo library, for example a question, a complaint or an enquiry about press, partnerships or franchising. We process your message, the pictures and your customer account data to deal with your request; we deal with requests about a booking together with the operating company (section 2.3). If your message otherwise concerns a particular restaurant, we pass it on, where necessary, with your name and contact details to that restaurant’s operating company; the operating company then deals with your request under its own responsibility. We store messages and pictures with our service provider Supabase. Please do not upload pictures of other people without their permission.

The “Feedback” contact form is only available in the app. If you use the order portal, you can reach us by e-mail at media@citychicken-nhas.de or through the contact form on our website, which is covered by the website’s privacy policy.

10.2 Legal basis

If your request concerns your customer account or a booking, the legal basis is Art. 6(1)(b) GDPR. Otherwise, we base the processing and the passing on to the operating company on Art. 6(1)(f) GDPR; our legitimate interest is to answer your enquiry. We only process information about health problems, for example after a visit to a restaurant, to clarify your complaint and to examine possible claims (Art. 9(2)(f) GDPR), and we only pass it on to the operating company of the restaurant concerned.

11.1 Requests to our interface

Our interface runs on Cloudflare; for technical reasons, every request from the app transmits your IP address. Requests from the order portal are first received by our server at Vercel (section 11.5), which forwards them to the interface together with your IP address so that the following limits apply to each guest individually; so that nobody can fake another person’s IP address, our server marks it in a way that cannot be forged. To fend off misuse and attacks, we count requests to the interface:

• per IP address,
• per e-mail address for sign-in attempts,
• per customer account after sign-in.

These counters expire after about one hour at most. Our server at Vercel also counts how often codes are requested and checked, sign-ins are set up and videos are converted from an IP address, and how often a customer account changes its profile picture, requests cancellations or refunds, exports its data or requests its deletion. Each of these counters applies for one to ten minutes; for this purpose, our server only keeps your IP address in its working memory, and for no more than ten minutes.

11.2 Sign-in and sessions at Supabase

When you register, sign in with codes or confirm your mobile number, and each time the app renews your sign-in, the app connects to Supabase or we pass your IP address on to Supabase. Supabase processes your IP address to detect and limit abusive sign-in attempts. So that you stay signed in, Supabase also stores each session with the IP address until you sign out, the session expires or your customer account is deleted (Art. 6(1)(b) and (f) GDPR). Supabase deletes logs of these events after 7 days. In the order portal, your browser connects to Supabase directly in part (section 3.2); signing in with a code sent by text message and every renewal of your sign-in go through our server at Vercel, which passes your IP address on to Supabase in the process.

11.3 Security logs

We log security-related events such as sign-ins, agreements to the Terms and Conditions, payments, cancellations, refunds and changes to the customer account with a shortened IP address and the identifier of the app and operating system (user agent), and for sign-in attempts with an e-mail address for which there is no customer account yet also with this address; this also happens in the first step of every registration. For events in the order portal, the log also contains your shortened IP address, but no identifier of your browser. We keep entries that prove the conclusion or performance of a contract for as long as the related bookings or your customer account; we delete all other entries after one year, unless we need individual entries for longer to investigate a specific security incident.

11.4 Legal basis

The legal basis is our legitimate interest in operating the app and the order portal securely and in protection against misuse and fraud (Art. 6(1)(f) GDPR). Cloudflare also processes certain information derived from the data traffic under its own responsibility, for example to detect attacks.

11.5 Server of the order portal at Vercel

We run the order portal on servers of Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA, as our processor. Vercel receives your requests in the data centre of its worldwide network that is closest to you and decrypts them there; if you use the order portal in Germany, this is usually a data centre in the European Union. The server functions of the order portal run in Frankfurt am Main; Vercel may carry out preliminary checks when a page is requested, such as renewing your sign-in, in the data centre that receives the request. With every request, our server checks your sign-in using the cookie bp-auth-token, renews it with Supabase where necessary and forwards your requests to our interface; in doing so, it passes your IP address on to the interface and to Supabase (sections 11.1 and 11.2). It does not store the content of your requests permanently; it keeps your initials and the reference to your profile picture for the header of our website in its working memory for about one minute. It delivers pictures of the menu in a suitable size; your browser loads videos directly from Supabase or, if it cannot play the video format, as a converted file from our server. Vercel records technical log data for every request, such as the IP address, the time, the address requested and information about your browser, and deletes it after 30 days at the latest. The legal basis is Art. 6(1)(b) GDPR insofar as our server handles requests about your customer account and your bookings, and otherwise our legitimate interest in a secure and fast order portal (Art. 6(1)(f) GDPR). Section 15.1 explains the transfer to the USA.

11.6 How we protect your data

We only transmit your data in encrypted form between the app or your browser and our servers. At our company and at the operating company, only people who need your data for their tasks can access it. Our processors are contractually obliged to process your data only on our instructions and to protect it with appropriate technical and organisational measures (Art. 28 and 32 GDPR).

12.1 What the app stores

The app only stores on your device what it needs in order to work:

• your sign-in and the language you have chosen,
• your basket during an order,
• a copy of your QR ticket until the end of the business day of your time slot (4 a.m. on the following calendar day), so that you can show it even without an internet connection,
• cached pictures and videos, for example of the menu and the restaurants,
• your decision about the restaurant map (section 8),
• map data cached by the map service you chose (section 8),
• the installation ID and token for push notifications (section 7),
• the identifiers of Stripe’s payment module (section 6.2),
• your till receipt as a PDF file in the app’s cache as soon as you view it (section 5.8).

A file with your data that you export (section 16.2) remains on your device until you delete it.

12.2 Deletion in the app

When you sign out, the app deletes your sign-in, the copy of your QR ticket, cached till receipts, the stored copy of the push token and your decision about the restaurant map; it also deletes the copy of the QR ticket when you cancel your booking, request a refund or check-in is no longer possible. You can remove everything else by deleting the app.

12.3 Legal basis for the app

The legal basis for storing this information is § 25 Abs. 2 Nr. 2 TDDDG, because this is necessary for the functions you use; section 8 applies to the map. The app does not read your device’s advertising identifiers, and it does not set any cookies for advertising or analytics purposes.

12.4 What the order portal stores in your browser

The order portal only stores in your browser what is needed for the functions you use there. Other websites cannot read the entries on our domain. Your browser only sends the order portal’s cookies over encrypted connections.

In addition, your browser keeps pictures and videos of the menu for up to one year and your profile picture for no more than five minutes in its cache so that the pages load faster. If you export your data in the order portal (section 16.2), the downloaded file remains on your device until you delete it. You can find an overview of all cookies and entries on citychickennhas.de in our website’s privacy policy.

12.5 Deletion and legal basis in the order portal

When you sign out in the order portal or through the account icon on our website, we delete the cookies bp-auth-token, bp_remember and bp_present and your basket. We also delete your basket as soon as you order and when you sign in again. If you delete your customer account in the order portal, we sign you out on all devices and also delete these entries in your browser. The other entries expire as stated in section 12.4; you can delete them at any time in your browser settings.

The legal basis for storing and reading this information is § 25 Abs. 2 Nr. 2 TDDDG, because this is necessary for the functions you use: signing in, and if you tick the box to stay signed in also beyond closing your browser, showing that you are signed in in the header of our website, the basket, payment, the language setting and your setting for the videos; section 6.5 applies to Stripe. We process the data in these entries on the basis of Art. 6(1)(b) GDPR insofar as it is necessary for your customer account and your order, and otherwise on the basis of our legitimate interest in a secure and easy-to-use order portal (Art. 6(1)(f) GDPR). The order portal does not set any advertising or analytics cookies.

12.6 Connection check in older app versions

Versions of the app up to and including 1.0.0 call a test address operated by Google (clients3.google.com) on iPhones when the app starts, whenever the network changes and, while the app is open, about once a minute, or every five seconds if there is no answer; this also applies while the app only asks you to update. Google receives your IP address and the technical details of the request, such as the identifier of the app and the operating system. This check is a default setting of a software library; the app does not use its result, because it learns from your operating system whether you are offline. We can no longer switch the check off in a version that is already installed; from version 1.0.1, it no longer takes place. Please update the app for this reason. The check does not take place on Android devices. Until you update, the legal basis is our legitimate interest in continuing to provide the version of the app that you have installed (Art. 6(1)(f) GDPR).

13.1 Legal texts on our website and addresses at nhascitychicken.app

We publish this Privacy Policy, our Terms and Conditions and our accessibility information on our website at citychickennhas.de/en/datenschutz/kundenkonto, citychickennhas.de/en/agb and citychickennhas.de/en/barrierefreiheit; you can also read the Terms and Conditions and the Privacy Policy directly in the app. The website’s privacy policy applies to visits to these pages; we do not load any services for audience measurement or advertising on them. If you open an earlier address of these texts at nhascitychicken.app, we show you the same version there or permanently redirect you to our website; we provide the PDF files of our legal texts at nhascitychicken.app. Cloudflare delivers the pages, redirects and files at nhascitychicken.app for us; pictures on these pages come from our service provider Supabase. For technical reasons, your IP address, the date and time of access, the address requested and information about your browser are processed in order to deliver them and protect them against attacks. The legal basis is our legitimate interest in secure delivery (Art. 6(1)(f) GDPR). We do not use cookies or tracking for this. Sections 11.5 and 12.4 explain how the pages of the order portal are delivered and what your browser stores there. Cookies on citychickennhas.de are covered by the website’s privacy policy.

13.2 Account icon in the header of our website

If you are signed in to the order portal, the header of our website citychickennhas.de shows an account icon with your profile picture or your initials. When you open it, it takes you to your orders, your profile and signing out. For this, the website checks whether the cookie bp_present is set in your browser and only then requests your initials and your profile picture from our server; your browser sends the cookie bp-auth-token with this request, and this may extend your sign-in (section 12.4). Your initials are not part of the text of the page. We only show this information to you; we do not pass it on to the analytics and advertising services that run on the website only with your consent. If you go from the order portal to the other pages of the website, these services only learn that you came from our domain, not from which page of the order portal. The legal basis is § 25 Abs. 2 Nr. 2 TDDDG for reading the cookies and Art. 6(1)(b) GDPR for showing your details as part of your customer account. All other processing on the website is covered by the website’s privacy policy.

14.1 Who receives data

Your data is only received by those who need it for the purposes described: the staff and the administration of the operating company of the booked restaurant (section 5), the operating company of a restaurant if your request concerns that restaurant (section 10), and these service providers:

14.2 Contracts and authorities

Processors are bound by contract to the instructions of the company responsible in each case. For joint processing, we also conclude these contracts in the name of the operating company; it concludes the contracts with Stripe and Lightspeed itself. Recipients acting under their own responsibility process and transfer data in accordance with their own privacy terms. Authorities, courts and advisers, such as the operating company’s tax advisers, only receive data if we or the operating company are legally obliged to provide it or if this is necessary to assert or defend claims.

The operating company and our processors have contractually undertaken to protect your data as required by the GDPR and this Privacy Policy. Recipients acting under their own responsibility are themselves bound by the GDPR when processing your data or, where they are based in the United States, by the principles of the EU-U.S. Data Privacy Framework (section 15.1).

14.3 App stores

If you download the app from the App Store or Google Play, Apple (Apple Distribution International Limited, Ireland) and Google (Google Ireland Limited, Ireland) process the data needed for this, for example about your store account, under their own responsibility; we have no influence on this.

15.1 United States and worldwide data centres

Some service providers process personal data outside the European Union and the European Economic Area, in particular in the United States of America, in Canada and in Singapore; Cloudflare, Google and Vercel also process data in their data centres around the world. For the United States, the European Commission found in Commission Implementing Decision (EU) 2023/1795 that organisations certified under the EU-U.S. Data Privacy Framework ensure an adequate level of protection (Art. 45 GDPR). We base transfers to Cloudflare, Inc., Twilio Inc., Google LLC and Vercel Inc. on this, and the operating company bases transfers to Stripe, LLC on it, as long as these companies are listed as actively certified in the official list at dataprivacyframework.gov (opens in a new tab).

Vercel receives requests to the order portal in its worldwide network of data centres, and Vercel Inc. can access data from the USA for operation and support; in addition to its certification under the EU-U.S. Data Privacy Framework, the standard contractual clauses in our data processing agreement with Vercel apply (Art. 45 and Art. 46(2)(c) GDPR).

Cloudflare operates a worldwide network of data centres. Requests from your app to our interface and requests for addresses at nhascitychicken.app are handled by the data centre that receives the request; if you are in Germany, this is usually a data centre in the European Union. Cloudflare stores the counters for protection against misuse centrally and also keeps them in other data centres for a short time. We have not restricted processing at Cloudflare to the European Union, including for sending and receiving e-mails; your data may therefore also be processed outside the European Union, including in countries without an adequacy decision. This is based on the certification of Cloudflare, Inc. under the EU-U.S. Data Privacy Framework and on the standard contractual clauses in our data processing agreement with Cloudflare (Art. 45 and Art. 46(2)(c) GDPR).

15.2 Singapore and standard contractual clauses

Our database, the customer accounts and the stored files are hosted by Supabase in an Amazon Web Services data centre in Ireland (EU); the function that creates our e-mails with codes also runs in Ireland. Supabase Pte. Ltd. is based in Singapore, for which there is no adequacy decision, and can access the data for operation and maintenance. The European Commission’s standard contractual clauses (Commission Implementing Decision (EU) 2021/914) in our data processing agreement with Supabase apply to this (Art. 46(2)(c) GDPR). You can obtain a copy of the standard contractual clauses on request at media@citychicken-nhas.de.

15.3 The restaurant’s point-of-sale system: Canada and other countries

The operating company’s point-of-sale system is provided by Lightspeed Netherlands B.V. in Amsterdam. Its parent company, Lightspeed Commerce Inc. in Montréal (Canada), processes the data as a further processor. For Canada, the European Commission has found that organisations subject to Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA) ensure an adequate level of protection (Decision 2002/2/EC, which remains in force under Art. 45(9) GDPR). Where this decision does not apply, the European Commission’s standard contractual clauses (Commission Implementing Decision (EU) 2021/914) in the operating company’s data processing agreement with Lightspeed apply (Art. 46(2)(c) GDPR). Lightspeed runs the point-of-sale system in data centres of Amazon Web Services and Google, sends the till receipts through the e-mail service provider SendGrid in the USA and may use other group companies and service providers outside the European Union, including in the USA and in countries without an adequacy decision; processing is not contractually limited to the European Union. Lightspeed must safeguard such onward transfers with standard contractual clauses or, for recipients in the USA that are certified under the EU-U.S. Data Privacy Framework, rely on that framework (section 15.1). You can obtain a copy of the standard contractual clauses in the operating company’s contract with Lightspeed on request at media@citychicken-nhas.de.

16.1 Retention periods

We delete your data after these periods:

• Customer account: when you delete it, in the app under Profile → Settings → “Delete Account”, in the order portal under “Profile”, or by sending an e-mail to media@citychicken-nhas.de. Once you have asked for it to be deleted, your customer account is deactivated immediately, and we sign you out on all devices. If you sign in again with a code in the app or in the order portal within 30 days, it is restored; simply opening a page does not restore it. After 30 days, we delete your name, e-mail address, mobile number, country, profile details including pictures, push tokens, your list of notifications, ratings on bookings, your till receipts with the related details, your sign-in data at Supabase and your messages and pictures from the contact form. What was passed to the restaurant’s point-of-sale system at check-in remains stored there as described in section 5.7, including your first name. What remains is a record with your customer number, without your name or contact details, which keeps your bookings together; we delete it together with the bookings.
• Bookings and payments (section 5.1): ten years from the end of the calendar year in which you booked, and longer only as long as they are relevant to a tax assessment that is still open. The operating company must keep books and records for this long, and accounting vouchers, including invoices, for eight years (Art. 6(1)(c) GDPR in conjunction with § 147 AO (German Fiscal Code), § 257 HGB (German Commercial Code) and § 14b UStG (German Value Added Tax Act)). If you delete your customer account, this data remains stored without your name and contact details. You can cancel an order that you do not pay for; otherwise our system cancels it once the period for paying has expired. It is kept like a booking.
• The restaurant’s point-of-sale system (section 5.7): ten years from the end of the calendar year in which your order was recorded in the till, and longer only as long as the records are relevant to a tax assessment that is still open; after that, the operating company has them deleted (Art. 6(1)(c) GDPR in conjunction with § 147 AO and § 257 HGB).
• E-mails with till receipts (section 5.8): as soon as we have matched the till receipt to your booking; if it cannot be matched to a booking, seven days after it arrived; till receipts for a refund made at the till immediately. In any case, the storage facility at Cloudflare deletes every e-mail after 30 days at the latest.
• Holds: seven days after they end.
• Abandoned registration: If you abandon registration in the app or in the order portal before you have saved your personal details, we delete your sign-in data at Supabase seven days after you started registering. If you have already saved them, your customer account already exists, and the period for the customer account applies.
• Records relating to the Terms and Conditions and the Privacy Policy: we store the details listed in section 3.1 about your agreement, our notice or your acknowledgement as long as your customer account exists, and after that, without your name and contact details, until the end of the third calendar year after your customer account is deleted. The version of the Terms and Conditions that applies to a booking is stored with the booking (section 5.1).
• Push notifications: delivery logs with your device token after 90 days, read notifications in your list of notifications one year after you read them, and otherwise together with your customer account.
• Contact form: together with your customer account (see above); if you wish, we delete individual messages and pictures earlier.
• Security logs: as stated in section 11.3; records of access in our management system: as stated in section 5.2; counters for protection against misuse: after about one hour at most, and at our server at Vercel after ten minutes at most (section 11.1); sign-in logs at Supabase: as stated in section 11.2; logs at Vercel: after 30 days at the latest (section 11.5).
• Data on your device and in your browser: as described in section 12.

16.2 Data export and access

As long as your customer account exists, you can export the data that we store about you in your customer account yourself: in the app under Profile → Settings → “Export My Data” as a file that you can download or display, and in the order portal under “Profile” as a file in JSON or CSV format. The file contains your customer account data and your bookings, including the identifier of your ticket, the payment reference and, after check-in, your pickup number, the copy of the receipt data and the number of your till receipt, but no security values such as check values of codes; you can save the till receipt itself as a PDF file with your booking (section 5.8). Once you have asked for your customer account to be deleted, the export is no longer possible. If you ask us at media@citychicken-nhas.de, we will also provide you with the same file. If you ask us at the same address, you will receive full information about all the data that we and the operating company process about you, including logs, data held by our service providers and data in the restaurant’s point-of-sale system, within one month.

17.1 Your rights at a glance

You have the right to access your data, to have it corrected or erased, to have its processing restricted and to data portability (Art. 15 to 18 and 20 GDPR). You can withdraw consent at any time with effect for the future, for the restaurant map with the switch in the app (section 8.2). At present, you cannot change your e-mail address or your mobile number yourself, either in the app or in the order portal; to do so, write to us at media@citychicken-nhas.de or use the contact form on our website.

Right to object (Art. 21 GDPR): Where we process data on the basis of our legitimate interest (Art. 6(1)(f) GDPR), you have the right to object, on grounds relating to your particular situation, at any time to this processing. We will then no longer process the data. An exception applies if we can demonstrate compelling legitimate grounds for the processing which override your interests, rights and freedoms. An exception also applies if the processing is for the establishment, exercise or defence of legal claims.

17.2 How to exercise your rights

You can delete your customer account yourself in the app and in the order portal and export your data there, in the order portal even if you have not yet agreed to new Terms and Conditions (section 16). For all other requests, and also for deletion and export if you prefer to write to us, contact media@citychicken-nhas.de or our data protection officer (section 2.6). We are your central point of contact, including for booking data for which we are jointly responsible with the operating company.

17.3 Complaint to a supervisory authority

You can lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the Member State of your place of residence, your place of work or the place of the alleged infringement. The authority responsible for Nhas Food 1993 GmbH and MOG Gastro GmbH is the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit), Alt-Moabit 59–61, 10555 Berlin, e-mail mailbox@datenschutz-berlin.de, www.datenschutz-berlin.de (opens in a new tab).

17.4 Automated steps and human review

We do not make any decisions based solely on automated processing which produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR). The only steps that run automatically are those that apply the agreed booking rules without assessing you personally, for example these: the app and the order portal check the number of people, the booking period, the minimum order value, maximum quantities and the maximum order value and only let you order once your order complies with these rules; they refuse a booking if the time slot is fully booked, you have reached the number of time slots that the restaurant allows per business day, or prices have changed. An expired hold is released and an unpaid order is cancelled. Once the cancellation deadline has passed, you can no longer cancel in the app or in the order portal, and our system calculates the refund amount according to the booking rules. A booking without check-in expires at the end of the check-in window, and a booking that the restaurant has refunded in full is cancelled. Where changed Terms and Conditions require your agreement before you can book again, you cannot reserve or book any new time slots until you have agreed. Depending on its version, the app also locks its other functions until then; in the order portal you can still view and cancel your existing bookings, request the refund for them, delete your customer account and export your data. You can also ask us by e-mail at any time to delete your customer account or export your data (section 17.2). If you think such a step is wrong, write to us at media@citychicken-nhas.de. A person at the operating company or one of our staff will then review your case, and you can explain your point of view. Stripe carries out fraud checks on payments under its own responsibility (section 6.3).

18.1 Minimum age and parental consent

You may use the app and the order portal from the age of 13. If you are not yet 18, you need the consent of your parents or other persons with parental custody for your customer account and your bookings, as described in the Terms and Conditions. Until they have decided, we process your data because you have asked us to let you use the platform (Art. 6(1)(b) GDPR). If they refuse, we delete your customer account as soon as they or you tell us; the operating company only keeps booking data for as long as the law requires it to (section 16).

18.2 Consent under data protection law

We only need consent under data protection law for the restaurant map in the app (section 8). If you are under 16, you cannot give it on your own; in that case, please decline the request. You can allow push notifications yourself, even at the age of 13, because they do not require consent (section 7). We do not ask for consent in the order portal. On the other pages of our website, a cookie banner asks whether you agree to analytics and marketing services; if you are under 16, please decline.

18.3 No advertising profiles, requests from parents

We do not create advertising profiles. You can exercise your rights yourself. Your parents can also contact us, for example to request information or to have your customer account deleted; to make sure that no unauthorised person receives your data, we then ask them for proof of their parental custody.

19.1 Updates

We update this Privacy Policy when the app, the order portal or the law changes. We tell you about significant changes with a separate notice the next time you use the app or the order portal; you do not need to agree to the Privacy Policy. You can always find the current version in the app and on our website at citychickennhas.de/en/datenschutz/kundenkonto, where it is also available as a PDF. You can request earlier versions by e-mail to media@citychicken-nhas.de.