gastrozukunft.de Online-Bestellsystem
Login

Privacy policy

This privacy policy informs you about the type, scope and purpose of processing personal data when visiting gastrozukunft.de and using our B2B offers for restaurants.

Controller

YASEEN Design and print service
Arndtstr. 9
99880 Waltershausen
Germany

Email info@yaseendesignservice.de WhatsApp +49 1590 1887622

Data processed and purposes

We process personal data solely to provide and improve our platform:

  • Technical server logs (IP address, date/time, requested page, user agent) to ensure secure operation. To protect our forms (registration, contact, newsletter, chat, customer portal including sign-in and password reset, ordering and payment on gastrozukunft.de) against automated requests, your browser quietly solves a small arithmetic task when you first type in a form; the task is set and checked by our own server. For the sign-in of our team this happens only after repeated failed attempts. No cookies are set, nothing is stored in your browser and no third party is involved. Only the solution, whether your browser reports itself as remote-controlled, and the number of your inputs in the form are transmitted; your IP address is used only as a non-reversible check value, for at most one hour, in counters that determine whether a task is set and how large it is. Running the task in your browser is strictly necessary for the submission you requested (Section 25(2) No. 2 TDDDG); the legal basis is Art. 6(1)(f) GDPR, our legitimate interest being protection against abuse.
  • Contact data you transmit to us voluntarily (e.g. via the contact form, e-mail or WhatsApp), in order to handle your enquiry and prepare an offer.
  • B2B contract, billing and project data when working with restaurants (e.g. contact person, billing and delivery address, order and payment details).
  • Optional media (e.g. uploaded logos/menus) for contract fulfillment and design of your materials.
  • Audience data for our own pages (page requested, time, device category, coarse region of origin) in order to shape the offering to demand — without cookies and without storing the IP address.
  • With every enquiry sent through the sign-up form we store the IP address and the browser identifier at the time of submission, as evidence of the submission and to detect abuse and duplicate sign-ups; they are deleted together with the enquiry. If we find that an enquiry is abusive – for example because it comes from a competitor – we keep, after deleting the enquiry, only a non-reversible check value derived from its IP address, e-mail address and phone number (or from the contact details the business publishes), to prevent our public pages from being accessed from that IP address (30 days) or a new registration with that e-mail address or phone number (12 months); the legal basis is Art. 6(1)(f) GDPR, our legitimate interest being the protection of our offer and our trade secrets.
  • Reminders by email: If you ticked the voluntary box “Yes, remind me by email …” in the sign-up form, we remind you by email of the steps of your setup that are still open – at most four times (about 1, 3, 7 and 14 days after your enquiry), only Monday to Saturday between 09:00 and 18:00 (time zone Europe/Berlin), and no longer once your setup is complete. The legal basis is your consent (Art. 6(1)(a) GDPR). As proof we store with your enquiry the time, the version of the box text and the page on which you ticked it; the proof is deleted together with your enquiry. Without this tick we send no reminders by email; your sign-up does not depend on it. You can withdraw your consent at any time with effect for the future: with the unsubscribe link in every reminder, with the unsubscribe function of your email program, by removing the tick on the “Your business” page of your setup, or with an informal message to info@gastrozukunft.de. If you chose WhatsApp as your contact channel, the section “WhatsApp Business Platform” applies to reminders there.

Legal bases

Processing is based on Art. 6(1)(b) GDPR (contract/pre-contractual measures) and Art. 6(1)(f) GDPR (legitimate interest in secure and efficient platform operation). Where there is a legal obligation (e.g. tax retention), we rely on Art. 6(1)(c) GDPR.

Recipients and processors

We use suitable hosting providers and technical service providers under data processing agreements. Transfers to third countries take place only where appropriate safeguards exist (e.g. EU standard contractual clauses) and where necessary to provide the service.

For payment processing we use Stripe (Stripe Payments Europe Ltd., Ireland). Required contact data (name, email) as well as payment and transaction data are processed. Payments are handled via Stripe Checkout; payment data (card details) are entered directly at Stripe and are not stored on our servers.

If you choose PayPal as the payment method during checkout, we use PayPal (Europe) S.à r.l. et Cie, S.C.A., 22-24 Boulevard Royal, L-2449 Luxembourg. The data required to process the payment is transmitted (order and amount data, contact e-mail, and the order and payment identifiers issued by PayPal); you enter your PayPal credentials with PayPal only, never with us. The legal basis is Art. 6(1)(b) GDPR. For invoicing and for matching refunds we process the payment and refund confirmations PayPal returns to us.

If a restaurant additionally sets up its own PayPal merchant account through our platform, the restaurant master data as well as the PayPal merchant id and account status are exchanged between PayPal and us. This only happens after the restaurant has given explicit consent (Art. 6(1)(a) GDPR), which we document with timestamp, text version, language and context, and which can be withdrawn at any time with effect for the future. PayPal, Inc. (USA) is involved as well; that transfer to a third country is safeguarded by the EU Standard Contractual Clauses (Art. 46 GDPR). The full consent text: /paypal_share_data_consent.php

If you order print products from us through the restaurant panel (e.g. QR cards), we pass the print file and the delivery address to the print shop we commission, which produces the products and ships them to the address given. The legal basis is Art. 6(1)(b) GDPR. Orders that are not paid are deleted together with the print file after 30 days; for paid orders the statutory retention periods for invoices and contract documents apply.

For legal details about delegated Stripe Connect data submission on behalf of the restaurant: /stripe_delegation.php

Services used and processors

We use carefully selected service providers as processors within the meaning of Art. 28 GDPR; data processing agreements are in place with them. In particular, we use:

  • IONOS SE, Montabaur (Germany) – hosting and server provision; processing within the EU. Purpose: technical operation of the website and platform. Legal basis: Art. 6(1)(b) and (f) GDPR.
  • Google Ireland Limited, Dublin (Ireland) – Google Workspace as storage for the nightly backup copies of our servers (since 18.10.2026), on the basis of Google's Cloud Data Processing Addendum; Google's sub-processors may be located outside the EU (Google LLC, USA: adequacy decision under Art. 45 GDPR – EU-US Data Privacy Framework –, supplemented by EU standard contractual clauses under Art. 46 GDPR). Retention: up to eight weeks; data we delete in ongoing operation may still be contained in a backup until then and is not removed from backups individually. Purpose: restoration after data loss. Legal basis: Art. 6(1)(b) and (f) GDPR.
  • Stripe Payments Europe Ltd., Ireland (where applicable Stripe, Inc., USA) – payment processing. Purpose: processing of payments; card data is entered directly with Stripe and not stored by us. Legal basis: Art. 6(1)(b) GDPR.
  • PayPal (Europe) S.à r.l. et Cie, S.C.A., Luxembourg – payment processing via PayPal. Purpose: processing of payments when you choose PayPal as the payment method. Legal basis: Art. 6(1)(b) GDPR.
  • OpenAI Ireland Ltd., Ireland (where applicable OpenAI, L.L.C., USA) – AI-supported functions: advisory, setup and panel chat, transcription of voice messages from those chats, reading uploaded menus (photo, PDF, document), derivation of allergen and additive information from dish names and ingredients, generation of logo drafts, and translation of menu texts. Purpose: providing these functions; content is not used to train the models. Legal basis: Art. 6(1)(b) and (a) GDPR. Details in the section "AI-supported functions".
  • WhatsApp Ireland Limited, Dublin (Ireland) – sending and receiving messages via the WhatsApp Business Platform, provided you have chosen WhatsApp as your contact channel or switched on the WhatsApp notices about your restaurant. Purpose: information about your enquiry and about setup, notices about your restaurant and receiving your replies. Legal basis: Art. 6(1)(a), (b) and (f) GDPR. Details in the section “WhatsApp Business Platform”.
  • seven communications GmbH & Co. KG, Kiel (Germany) – sending the confirmation codes to the telephone numbers you enter in the registration form: by SMS and – for landline numbers that cannot receive an SMS – by an automated call in which the code is read out. That call comes from a number belonging to the service provider and not from a number of ours. Only your telephone number and the text containing the code are transmitted. Purpose: checking that the number is reachable and belongs to you. Legal basis: Art. 6(1)(b) GDPR.

Where a transfer to the USA takes place, it is safeguarded by appropriate guarantees: EU standard contractual clauses (Art. 46 GDPR) or certification of the recipient under the EU-US Data Privacy Framework (adequacy decision pursuant to Art. 45 GDPR). You can obtain a copy of the EU standard contractual clauses used in each case on request by email to info@gastrozukunft.de.

Support appointments / Google Meet

While setting up your restaurant presence you can optionally book a personal support appointment (a video consultation via Google Meet). Using this offer is optional and not strictly required to fulfil the contract.

When you book a support appointment we process:

  • name and e-mail address (to confirm, remind about and manage the appointment),
  • phone number (optional, used only as a fallback channel via WhatsApp if the video connection fails),
  • your language and the voluntary details you enter about your request (the “How can we help?” note field),
  • appointment data (date, time, status, number of reschedules) as well as the version and timestamp of the consent you gave,
  • technical metadata needed to deliver the confirmation, reminder and cancellation e-mails including the calendar invite (.ics),
  • the content of the call itself is neither recorded nor stored.

The sole purpose of the processing is to arrange and hold the personal consultation/setup call you requested.

The legal basis is Art. 6(1)(b) GDPR (carrying out pre-contractual or contractual measures at your request). For the voluntary request note and for holding the video call we additionally rely on your consent under Art. 6(1)(a) GDPR, which you give explicitly when booking and can withdraw at any time with effect for the future (by cancelling the appointment).

The video call takes place via Google Meet (provider: Google Ireland Limited, Ireland; technical infrastructure may involve Google LLC, USA). Google processes connection and usage data in this context. Any transfer to the USA is safeguarded by appropriate guarantees (EU Standard Contractual Clauses or the EU-US Data Privacy Framework). A fixed meeting room is used; screen sharing only happens if you actively start it yourself. Please also note Google’s own privacy information.

Your personal appointment data (name, e-mail, phone, note, internal note) is deleted automatically at the latest 30 days after the appointment closes or after onboarding is completed; only anonymised statistical and log data without any personal reference remains.

You can reschedule or cancel a booked appointment yourself at any time via the link in the confirmation e-mail. The data-subject rights listed under “Your rights” (Art. 15–21 GDPR) also apply.

Consent text version: v1 (as of this privacy policy).

AI support chat (chat assistant)

During the setup of your restaurant presence, and afterwards in the restaurant panel, an AI-supported chat assistant is optionally available to you that answers your questions and can pass you on to a human if needed. This section applies to both: the chat during setup and the chat in the restaurant panel, which remains permanently available after setup is complete. For the advisory chat on our public campaign pages, the separate section "Advisory chat on our campaign pages" applies. Use is voluntary and not strictly necessary for the performance of the contract.

When you use the chat assistant we process:

  • the chat messages (text) you enter, to answer your onboarding questions,
  • images you optionally upload or paste, a capture of the setup page that you trigger yourself (screenshot), and voice messages you record – for voice messages, additionally the transcript produced from them, which we store with the conversation,
  • your language and technical metadata (timestamps, the link to your onboarding session and conversation) as well as the version and time of the consent you gave,
  • if your request is handed to our team: the messages exchanged in the conversation, for handling by a human,
  • please do not enter passwords, payment or card data into the chat – such data is not needed for support.

The processing serves solely to answer your questions during onboarding and – at your request – to hand you over to a human contact.

The legal basis is Art. 6(1)(b) GDPR (performance of pre-contractual or contractual measures at your request). For the content and attachments you voluntarily submit we additionally rely on your consent under Art. 6(1)(a) GDPR, which you give in the chat and can withdraw at any time with effect for the future (stop using it).

To generate the answers and to process your attachments we use the AI service OpenAI as a processor (OpenAI Ireland Ltd., Ireland, or OpenAI, L.L.C., USA). Your messages and attachments are transmitted to OpenAI for this purpose and processed there; voice messages are transmitted to OpenAI additionally in order to transcribe them into text. An automated moderation check is also carried out to prevent misuse. Any transfer to the USA is safeguarded by appropriate safeguards (EU standard contractual clauses). The content is processed exclusively to answer your enquiry and is not used to train OpenAI's models.

The content of the conversation (message texts, transcripts) and uploaded attachments are deleted automatically: for the chat during setup at the latest 30 days after the conversation ends or after setup is completed, for the chat in the restaurant panel at the latest 60 days after the last activity in the conversation. Attachments are stored outside the public web area, are never served publicly and their files are permanently removed in the process. Only anonymised statistical and log data without any personal reference remains.

From completed conversations of the advisory, setup and panel chat, an anonymised, generalised question-and-answer pair may be derived and stored in an internal knowledge base, in order to answer similar questions more quickly in future. The derivation is automated: names, e-mail addresses, telephone numbers as well as order and session identifiers are removed automatically in the process, and the anonymised entry is reviewed by our team before it is released. These entries contain no personal data. The legal basis is our legitimate interest in efficient and consistent support quality (Art. 6(1)(f) GDPR). No additional processor is used and the content is not used to train AI models. Such anonymised entries are retained even after the original conversation has been deleted in a data-protection-compliant manner.

You can stop using the chat assistant at any time and thereby withdraw your consent for the future. The data subject rights listed under “Your rights” (Art. 15–21 GDPR) also apply.

Consent text version: v1 (as of this privacy policy).

Advisory chat on our campaign pages

On our public campaign and offer pages we provide an AI-supported advisory chat that answers your questions about our offer (features, prices, setup) straight away and, if you wish, passes you on to a human. Using it is voluntary. As long as you only see the chat and do not use it, we process no data about you for it and set no cookie.

When you send something in the advisory chat, we process:

  • the messages you enter as well as images and voice messages you attach,
  • for voice messages, additionally the transcript produced from them, which we store with the conversation,
  • your language and technical metadata (times, the assignment to your conversation, a value derived from your IP address that cannot be reversed, for abuse prevention),
  • if you ask to be contacted by a human: the contact details you provide for that purpose (name, e-mail address, optionally telephone number) and your note about your request.

The purpose is exclusively to answer your questions about our offer and – at your request – to pass you on to a human contact. Please do not enter passwords, payment or card details into the chat; they are not needed for the advice.

The legal basis is Art. 6(1)(b) GDPR (taking steps at your request prior to entering into a contract). For attachments you transmit voluntarily – images and voice messages – we additionally rely on your consent under Art. 6(1)(a) GDPR, which you can withdraw at any time with effect for the future by ending your use of the chat.

To generate the answers we use the AI service OpenAI as a processor (OpenAI Ireland Ltd., Ireland, or OpenAI, L.L.C., USA). Your messages and your attachments are transmitted to OpenAI for this purpose; voice messages are transmitted additionally in order to transcribe them. An automated moderation check is also carried out to prevent misuse. Any transfer to the USA is safeguarded by appropriate safeguards (EU standard contractual clauses). The content is processed exclusively to answer your enquiry and is not used to train OpenAI's models.

For this chat we set two cookies, and only once you send something in the chat – not when you merely open the page: "gz_lsc_vk" (90 days) assigns your conversation to you so that you can continue it on a later visit; "gz_lsc_contact" (30 days) is created only if you have provided contact details for a reply and pre-fills those fields next time. The legal basis for both is § 25(2) no. 2 TDDDG, as they are necessary for the service you have expressly requested. You can delete them yourself at any time in your browser settings.

Messages, attachments, transcripts and the contact details you provided are deleted or anonymised automatically at the latest 60 days after the last activity in the conversation; the files of attachments are permanently removed in the process. Only anonymised statistical and log data without any personal reference remains.

You can stop using the advisory chat at any time. In addition, the data subject rights listed under "Your rights" apply (Art. 15–21 GDPR).

AI-supported functions

AI-supported functions are available in the restaurant area and during registration for the free trial. This section describes which content is transmitted to our AI service provider in the process. It is addressed above all to restaurant owners and their staff, who upload such content.

Reading a menu: if you upload a menu as a photo, PDF or text document in order to have it captured automatically, we transmit the file to OpenAI. For photos we transmit the complete image of the page and, in addition, up to four enlarged sections of it in high resolution; small images are scaled up by a factor of up to three in the process. This means: everything visible in the photo – including people or surroundings in the background – is transmitted along with it, possibly larger than in the original. If the image cannot be prepared on our server (for instance with certain file formats), we transmit the original file unchanged, including the additional information stored in it such as the time of capture and location data. PDF files are transmitted in full with all pages and document properties (up to 30 MB); with text documents the embedded images are transmitted as well. Please therefore upload only menus, and no pictures in which people are recognisable who have nothing to do with them.

If the uploaded menu contains contact details of the business (e.g. address, telephone number, e-mail address or website), these are read out of the document and stored for your restaurant profile.

Allergens and additives: from the name, category and ingredient list of a dish we derive allergen and additive information. For that we transmit exclusively these four items per dish to OpenAI – no image and no personal data. This derivation starts automatically, without you triggering it individually: a few seconds after a dish is saved, and after a menu has been imported. Machine-generated information is marked as such in the restaurant area and has to be confirmed.

Logo drafts: if you have logo suggestions generated, we transmit the business name, the location and your description to OpenAI. If you have uploaded your own image as a reference, we transmit that image as the original file as well (up to 12 MB). After a logo reference has been uploaded we automatically produce a first draft from it, without you triggering this separately; for images that are already cut out this does not happen.

Translations: on request we translate the texts of your menu (dish names, descriptions, categories) into the further languages of your presence using an AI service – via Anthropic (Claude) or OpenAI; we decide which service is used for your restaurant, and if there is a disruption OpenAI takes over automatically. Only these menu texts are transmitted – no personal data of your guests or staff.

Voice messages: voice messages recorded in our chats are transmitted to OpenAI in order to transcribe them into text; we store the transcript with the conversation. There is no longer any voice control of the platform.

The recipient of this content is OpenAI (OpenAI Ireland Ltd., Ireland, or OpenAI, L.L.C., USA) as a processor; menu translations may instead go to Anthropic (Anthropic Ireland, Limited, Ireland, or Anthropic, PBC, USA) as a processor. Any transfer to the USA is safeguarded in each case by EU standard contractual clauses (Art. 46 GDPR). The content is not used to train the models. No image, audio or text content is transmitted to Google for these functions. Where we use Google services for other purposes – for example maps, push notifications, video appointments, measuring sign-ups from Google ads or, if you connect it, your Google Business Profile – this is described in the relevant section of this policy.

The legal basis is Art. 6(1)(b) GDPR (providing the service you have commissioned). In so far as you voluntarily upload your own images or documents, we additionally rely on your consent under Art. 6(1)(a) GDPR, which you can withdraw at any time with effect for the future by no longer using the function.

Uploaded menu files and intermediate results of the analysis are deleted automatically at the latest 30 days after upload; files without an associated process are removed immediately. The result – your menu, your logo – remains part of your presence for as long as you use it.

Cookies, local storage and optional services

Without your consent we use only technically necessary cookies and local storage (e.g. LocalStorage) for the operation of the website and our platform, as well as those that record a choice you have made. By purpose these are: a session cookie for the duration of your visit; your language choice (a cookie lasting 12 months plus a copy on your device that stays there until you delete it); several short-lived cookies around the registration process which expire by themselves after one hour at the most; your consent to loading the Google reviews; and drafts of the registration form, which stay on your device for a maximum of seven days. Optional services are only used if you actively select them or if they are deliberately activated within a restaurant account. If you consent to the “Marketing and ad measurement” category, cookies and storage entries of Meta, Google Ads and OpenAI are added; those of Google Ads and OpenAI and the Meta cookies _fbp and _fbc are described below, and the Meta pixel may also create the storage entries lastExternalReferrer and lastExternalReferrerTime. We maintain a complete register of all cookies and local storage with purpose and lifetime internally and present it to the supervisory authority on request.

  • gz_consent: stores your choice about optional services (cookie, 12 months) so that it applies on every visit and the notice is not shown again. The value contains only the version of the notice, the time of your choice and the categories you agreed to – no personal data. You can change your choice at any time via "Cookie settings" in the footer. As a record of your choice – including a refusal – we additionally store on the server the time, the version of the text, the page visited, the language, the IP address and the browser identifier (Art. 6(1)(c) in conjunction with Art. 7(1), or Art. 6(1)(f) GDPR). After 90 days we delete the IP address from this record and reduce the browser identifier to the browser and system family (e.g. "Chrome/Windows"); we delete the remaining record three years after the respective choice.
  • WhatsApp: links/buttons open WhatsApp only when clicked (domain wa.me); message/phone number data is then transferred to WhatsApp.
  • Maps/navigation: embedded maps or route links are loaded/opened only after active selection.
  • Optional videos: on offer pages, videos are embedded only after clicking “Load video”. If a local MP4/WebM link is stored, the video is loaded directly from this website. Otherwise embedding is done via YouTube/Google (default: youtube-nocookie.com, optional: youtube.com or opening via youtu.be).
  • Optional AI functions: restaurant staff in the admin area and prospective customers during registration for the free trial period can use AI functions (e.g. reading a menu, derivation of allergen and additive information, logo drafts, translations, transcription of voice messages in the chats). In the process, content (image, audio, text, documents) is transmitted to OpenAI. Some of these functions start automatically, without you triggering them individually – in particular the derivation of allergen and additive information shortly after a dish is saved and after a menu has been imported. Which content is transmitted in detail is described in the section "AI-supported functions".
  • Optional external postal code check (only if enabled): to assist address entry, postal code/city checks can be made via api.zippopotam.us. This feature is disabled by default.
  • Landing reviews: Google reviews are loaded only after active consent; review texts are not permanently stored locally. Every review is transparently labeled with the related branch/address.
  • Platform reviews: reviews submitted directly on this platform are moderated before publication (status: pending, approved or rejected).
  • Meta pixel (only with your consent): on our campaign pages we use the Meta pixel from Facebook/Instagram to measure which of our ads led to a sign-up being started or completed. Initially the page delivers only a consent-controlled loader that we provide ourselves from our own domain. Without your consent to the “Marketing and ad measurement” category, no Meta script is loaded, no connection to Meta is established, no Meta event (e.g. PageView) is transmitted and no counting pixel is delivered. Only after your consent is the Meta pixel activated and data transferred to Meta Platforms Ireland Limited. The legal basis is your consent (Art. 6(1)(a) GDPR; § 25(1) TDDDG where information is stored on or read from your device). Consent is voluntary and can be withdrawn at any time with effect for the future via “Cookie settings” in the footer. Details are set out in the section “Meta pixel: recipient, third-country transfer and joint controllership”.
  • _fbp and _fbc (Meta, only with your consent): if the Meta pixel is activated after your consent, Meta may set the cookie _fbp in your browser and – if you reached us from a Facebook/Instagram ad carrying a click identifier (fbclid) – the cookie _fbc. They serve to attribute your visit and a later event to the same ad measurement. These cookies are not set before your consent; _fbc does not arise on every visit. The storage period is determined by Meta; Meta’s current information is decisive. If you withdraw your consent, the website prevents any further Meta measurement; Meta cookies that have already been set are not deleted automatically by us and remain until they expire or until you delete them manually in your browser.
  • Drafts and intermediate states (only on your device): on the page "Your business" (/3-monate-kostenlos/anmelden/) your browser temporarily stores the details you have entered in LocalStorage, so that they are not lost if the page is accidentally closed or reloaded; they are deleted as soon as you submit the form, and after seven days at the latest. After submission your browser remembers the number of your enquiry in the same way, so that it is not lost when the page is reloaded. On the further stations of the setup process your browser stores small intermediate states (e.g. where you last were) only for the duration of the browser tab; they disappear when the tab is closed. All of this data remains exclusively on your device, is not transmitted to us and is not read by us; you can remove it yourself at any time via your browser settings. The legal basis is § 25(2) no. 2 TDDDG, as the storage is necessary for the registration and setup process you have expressly requested.
  • gz_lsc_vk (advisory chat): assigns your conversation in the advisory chat on our campaign pages to you (cookie, 90 days) so that you can keep reading and writing there. It is only created once you send something in the chat – not when you merely open the page. The legal basis is § 25(2) no. 2 TDDDG. Details in the section "Advisory chat on our campaign pages".
  • gz_lsc_contact (advisory chat): stores the name and e-mail address you provided for a personal reply (cookie, 30 days) so that you do not have to fill in those fields again. It is created only if you have provided such contact details. The legal basis is § 25(2) no. 2 TDDDG.
  • Google Ads conversion measurement (only with your consent): on our campaign page and on the sign-up page, we use Google Ads to measure whether a started sign-up goes back to one of our Google ads. Initially the page delivers only a consent-controlled loader that we provide ourselves from our own domain. Without your consent to the “Marketing and ad measurement” category, no Google script is loaded, no connection to Google is established for this measurement, no Google cookie is set and no event is transmitted. Only after your consent is the Google tag loaded – on the campaign page only if the address contains a click identifier of a Google ad or the Tag Assistant test parameter, on the sign-up page on every visit – and data transferred to Google Ireland Limited. The legal basis is your consent (Art. 6(1)(a) GDPR; § 25(1) TDDDG where information is stored on or read from your device). Consent is voluntary and can be withdrawn at any time with effect for the future via “Cookie settings” in the footer. Details are set out in the section “Google Ads: conversion measurement, recipient, third-country transfer and responsibility”.
  • _gcl_au, _gcl_aw, _gcl_gb, _gcl_dc, _gcl_gs and _gcl_ag (Google, only with your consent): if the Google tag is loaded after your consent, Google may set these cookies in your browser, and only for our domain gastrozukunft.de itself, not for its subdomains. _gcl_au contains a random identifier of your browser and is created when the Google tag loads, even without an ad click; the other cookies store information about a click on a Google ad – for example the click identifier gclid in the cookie _gcl_aw – and serve to attribute a later registration to that ad click. Which of these other cookies arise in an individual case depends on whether, and through which type of Google ad, you reached us. They are not set before your consent. The storage period is determined by Google; according to Google (business.safety.google/adscookies) it is 90 days. In addition, after your consent the Google tag calls a Google address (www.googleadservices.com) through which Google can set a cookie on its own domain that is used only together with our website; we cannot delete this cookie. The legal basis is your consent (Art. 6(1)(a) GDPR; § 25(1) TDDDG). If you withdraw your consent or refuse the category, the website automatically deletes these cookies from your browser, together with the cookies _gcl_ha and _gcl_gf, which also begin with “_gcl_”.
  • _gcl_ls and gz_gads_fired_v1 (local storage, only with your consent): under _gcl_ls the Google tag may, after your consent, store information about the ad click in the local storage (LocalStorage) of your browser; the storage period is determined by Google. gz_gads_fired_v1 is created by our loader as soon as the Google tag has sent the report of a started sign-up: the entry contains only the pseudonymous transaction identifiers of the reported sign-ups (at most 20) and prevents the Google tag from being loaded again for the same identifier when the sign-up page is reloaded on the same day. It has no fixed expiry date, stays on your device and is not transmitted to us. The legal basis is your consent (Art. 6(1)(a) GDPR; § 25(1) TDDDG). The website deletes both entries automatically if you withdraw your consent or refuse the category; you can also remove them yourself at any time in your browser settings.
  • OpenAI pixel with __obref and __oppref (OpenAI, only with your consent): On our campaign page and on the sign-up page we use the OpenAI pixel to measure whether a started or confirmed sign-up follows one of our ads in ChatGPT. At first only a loading function provided by ourselves is delivered; only after your consent does it load the OpenAI script in an invisible frame without form fields (see the section “OpenAI pixel and server-side transfer”). The pixel then sets, for our domain gastrozukunft.de including its subdomains, the cookie __obref (a random identifier of your browser, 12 months) and – only if you reached us through an ad in ChatGPT with a click identifier (oppref) – the cookie __oppref (this click identifier, 30 days); to determine the domain it briefly sets the cookie __oaiq_domain_probe (at most 60 seconds). After a withdrawal it may create the cookie __oaiq_consent and the local storage entry oaiq_consent with the value “no consent” (30 days); in session storage it may create entries with the prefix oaiq_cs:, which end when the tab is closed. When the sign-up is submitted, our server reads the value of the cookie __obref with your consent and stores it with your enquiry for the server-side transfer (see there). The legal basis is your consent (Art. 6(1)(a) GDPR; Section 25(1) TDDDG). The website deletes __obref, __oppref, __oaiq_consent, __oaiq_domain_probe and oaiq_consent automatically when you withdraw your consent or refuse the category; you can also remove them yourself at any time in your browser settings.

Without your consent no ad measurement by Meta, Google or OpenAI, no advertising or profile building and no cross-site tracking takes place. If you consent to the “Marketing and ad measurement” category, we measure the success of our own ads with the Meta pixel, with Google Ads conversion measurement and with the OpenAI pixel (see the sections on the Meta pixel, on Google Ads and on the OpenAI pixel); personalised advertising and remarketing are switched off in our Google Ads integration. For the anonymous audience measurement of our own pages, see the section “Audience measurement (without cookies)”.

Meta pixel: recipient, third-country transfer and joint controllership

On our campaign pages (e.g. gastrozukunft.de/3-monate-kostenlos/ and the sign-up page linked there) we use the Meta pixel to measure the success of our own advertising. It is used exclusively after your express consent to the “Marketing and ad measurement” category.

The recipient of the data is Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland. No data is transmitted to Meta until you have consented to the "Marketing and advertising measurement" category. Transmission then happens on two paths: through the Meta pixel in your browser and, in addition, from our server through the Conversions API. The server-side transmission does not require an active pixel; it therefore also takes place if the pixel is blocked in your browser or fails to load. Without your consent no transmission takes place on either path.

After your consent, the following data in particular may be processed:

  • the page of our website you have called up,
  • the date and time of the request,
  • information about your browser and device (e.g. browser type, operating system, language setting, screen resolution),
  • your IP address, insofar as it is technically transmitted to Meta,
  • referrer information (the page previously visited or the origin of the request),
  • Meta-related identifiers such as the cookie _fbp and, where applicable, _fbc,
  • the event triggered in each case (see below).

Not every one of these values occurs on every visit. Which data is transmitted in an individual case depends on your browser, your device and your behaviour on the page.

We use the following events: “PageView” can be transmitted after consent when you open the campaign page or the sign-up page. “Lead” is transmitted as soon as you open the sign-up page (gastrozukunft.de/3-monate-kostenlos/anmelden/) and valid marketing consent is in place – given earlier or only on this page. It marks the start of a sign-up, not its completion: it is transmitted even if you do not fill in or do not submit the form, and it contains no details from the form. The event carries a pseudonymous event identifier that we compute with a secret key from your IP address, your browser identifier, our domain and the calendar day; the same browser receives the same identifier on the same day, so reloading the page does not count twice. “Lead” is not transmitted for our automated test calls. “CompleteRegistration” is not triggered by the pixel in your browser but exclusively by our server once your sign-up is confirmed (see the following paragraph).

As soon as you have confirmed both your e-mail address and your phone number and your enquiry has thereby come into existence, we transmit the event “CompleteRegistration” from our server to Meta (Conversions API) – only as long as your consent to “Marketing and ad measurement” is in place at that moment. We transmit your e-mail address, your phone number, your first and last name, your postcode and the country of the campaign (Germany) – these six details exclusively as SHA-256 hash values and never in plain text. In addition: the ad click identifier formed from the “fbclid” parameter, the address of the campaign page you visited, the time of the event and an event identifier that we create when your enquiry is stored; it ensures that a repeated transmission of the same event is not counted twice by Meta. The purpose is to attribute the confirmed sign-up to your ad. We do not transmit your IP address or your browser identifier via this route. The events “PageView” and “Lead” are triggered exclusively by the Meta pixel in your browser, not by our server; “CompleteRegistration” is transmitted exclusively by our server, not by the pixel. If you withdraw your consent via “Cookie settings”, measurement in the browser stops immediately. If a page you opened via your personal link is open at that moment, that page reports the withdrawal to our server immediately and we record it in your enquiry record; otherwise we record it the next time you open a page via your personal link. Before every server-side transmission and before every retry, our server re-checks the enquiry record; from the moment the withdrawal is recorded, the event is neither sent nor resent. Events already transmitted cannot be recalled. From 15.09.2026 to 17.09.2026 the server-side transmission was suspended; from 17.09.2026 until this version took effect on 19.09.2026 our server transmitted the event “Lead”. For enquiries you submitted before this version took effect, our server does not transmit any event to Meta, not even retrospectively.

In addition, Meta's Meta-enabled Conversions API (supported by Meta) is connected for our Meta data source. It provides a server-side complement to browser-side measurement. In the configuration currently reviewed, automatic addition of page and product information is enabled, while automatic advanced matching and automatic events are disabled. These settings describe enabled functions and do not prove that particular data was actually transmitted during a particular visit. Where the connection transmits data to Meta for an event, the data concerned may, depending on the page and the event, include event and page context and, where available for that event, product information. The present review provides no basis for stating that this function automatically transmits contact data through Advanced Matching or automatically generated events.

Meta may also process the data outside the European Union, in particular in the USA; a transfer to the USA or to further third countries can therefore not be ruled out. According to Meta, such a transfer is based, depending on the constellation, on an adequacy decision under the EU-US Data Privacy Framework (Art. 45 GDPR) and/or on EU Standard Contractual Clauses (Art. 46 GDPR). Which mechanism applies in an individual case follows from Meta’s current information and contractual terms; we cannot warrant that every processing by Meta rests on a single one of these mechanisms alone. Despite these safeguards, access by authorities in third countries cannot be entirely excluded.

For the collection of the data on our website and its transmission to Meta through the Meta pixel and the Conversions API, we and Meta Platforms Ireland Limited are joint controllers within the meaning of Art. 26 GDPR. This joint controllership is limited to that collection and transmission. For the subsequent independent processing of the data by Meta, Meta is solely responsible; we have no influence on it. The basis is Meta's Controller Addendum (https://www.facebook.com/legal/controller_addendum), which is incorporated through the Meta Business Tools Terms. The essence of this arrangement: we obtain your consent and inform you about the joint processing with this section; Meta is responsible for granting you the rights under Art. 15 to 20 GDPR (access, rectification, erasure, restriction, data portability) for the data stored at Meta after the transmission. Under Art. 26(3) GDPR you can exercise your rights against us and against Meta. How Meta processes the data afterwards is described in Meta's Privacy Policy (https://www.facebook.com/privacy/policy).

Your consent is voluntary; you suffer no disadvantage in using our website without it. You can withdraw it at any time with effect for the future via “Cookie settings” in the footer. After a withdrawal the website prevents any further Meta measurement. Meta cookies already set in your browser (e.g. _fbp, _fbc) are not deleted automatically by us; you can remove them yourself at any time in your browser settings. The lawfulness of the processing carried out until the withdrawal remains unaffected.

OpenAI pixel and server-side transfer: conversion measurement for ads in ChatGPT, recipient, third-country transfer and responsibility

On our campaign page gastrozukunft.de/3-monate-kostenlos/ (including its language versions) and on the sign-up page linked there (gastrozukunft.de/3-monate-kostenlos/anmelden/) we use the OpenAI pixel. It lets us see whether a started or confirmed sign-up follows a click on one of our ads in ChatGPT. Where OpenAI offers this for our ad account, OpenAI also attributes a sign-up to one of our ads that was only shown to you in ChatGPT within one day before the sign-up, without you clicking on it (view-through attribution); OpenAI reports such sign-ups to us separately. It is used only after your express consent to the “Marketing and ad measurement” category; the legal basis is this consent (Art. 6(1)(a) GDPR; Section 25(1) TDDDG for storing and reading information on your device). Before your consent and after a refusal, your browser loads no script from OpenAI for this, no connection to OpenAI is made for this measurement and no OpenAI cookie is set; nor do we then transfer anything to OpenAI from our server (when a later withdrawal ends the server path is described in the paragraph “Server-side transfer”). After your consent, the pixel is loaded on the campaign page only if the address you opened contains the click identifier of an ad in ChatGPT (parameter “oppref”); on the sign-up page it is loaded on every visit; on the setup pages (gastrozukunft.de/3-monate-kostenlos/reise/) it is not loaded.

The recipient of the data is OpenAI Ireland Ltd., Ireland – our contracting partner for advertising in ChatGPT under OpenAI's Advertising Terms. The data is transferred in two ways: by the pixel in your browser and – once your sign-up is confirmed – additionally from our server through OpenAI's Conversions API (see the paragraph “Server-side transfer” below). The server-side transfer does not require an active pixel; it therefore also takes place when the pixel is blocked in your browser or does not load. Without your consent no transfer takes place on either path; from when a withdrawal ends the server path is described in the paragraph “Server-side transfer”. The script is loaded from bzrcdn.openai.com and sends its reports to bzr.openai.com. OpenAI has switched on automatic advanced matching for the pixel, with which the pixel captures details entered in form fields of the document it runs in – such as an e-mail address, phone number or name – as a hash value and transfers them to OpenAI. So that none of your entries is captured, we do not start the pixel in our page but in a separate, invisible frame of our domain (gastrozukunft.de/assets/js/marketing/gz-openai-frame.html) that contains no form and no input field; the pixel therefore does not capture what you enter in the sign-up form or in other forms on our pages.

After your consent, the following data in particular may be processed: the address of this frame (where applicable with the click identifier of your ad) and – as its origin – the address of the page you are on; date and time; information about your browser and device (e.g. browser type, operating system, language setting); your IP address, insofar as it is technically transmitted to OpenAI; the random identifier of your browser from the cookie __obref; the click identifier of your ad from the cookie __oppref, where present; and the event “lead_created” with a pseudonymous event identifier (see below). The pixel neither captures nor transfers your name, e-mail address, phone number or any other details from the sign-up form; what our server transfers after your confirmed sign-up is described in the paragraph “Server-side transfer” below. Not every one of these values arises on every visit; OpenAI determines which technical details the pixel transmits in each case.

As conversion events we transfer two events to OpenAI: “lead_created” from your browser and “registration_completed” from our server (see the paragraph “Server-side transfer” below). “lead_created” is transferred as soon as you open the sign-up page – that is, at the start of the sign-up – and consent to “Marketing and ad measurement” is in place in your browser, given earlier or only on that page. It marks the start of a sign-up, not its completion: it is transferred even if you do not fill in or do not submit the form, and it contains no details from the form. The event carries a pseudonymous event identifier that we calculate with a secret key from your IP address, your browser identification, our domain and the calendar day; the same browser receives the same identifier on the same day, so that reloading the page does not count twice. The event is not transferred for our automated test calls. On the campaign page we send no conversion event to OpenAI; there the pixel stores the click identifier of your ad for the sign-up page. In addition, when it loads on either page the pixel itself reports technical events to OpenAI, such as its start (“openai::sdk_init”) and diagnostic messages, each with the address of the frame and of the page, the random identifier of your browser and, where applicable, the click identifier of your ad.

Server-side transfer (Conversions API): Once you have confirmed both your e-mail address and your phone number and your enquiry has thereby come into being, we transfer the event “registration_completed” from our server to OpenAI (Conversions API) – only as long as your consent to “Marketing and ad measurement” is in place at that moment and you submitted your sign-up under a version of this privacy notice that describes this transfer. Transferred are your e-mail address, your phone number and your first and last name – these details only as a SHA-256 hash value and not in plain text –, your postcode and the country of the campaign (Germany), the click identifier of your ad in ChatGPT (parameter “oppref”) and the random identifier of your browser from the cookie __obref, insofar as we stored both at your sign-up with your consent, the address of the campaign or sign-up page through which you came to us, the time of the confirmed sign-up and an event identifier that we calculate with a secret key from the random identifier of your enquiry; it ensures that a repeated transfer of the same event does not count twice at OpenAI. The purpose is to attribute the confirmed sign-up to our ad that you clicked on or that was shown to you (see above); for this, OpenAI may match the transferred details with the data OpenAI holds about your use of ChatGPT. We give every event the “opt_out” flag provided by OpenAI, which excludes it from future personalisation at user level. We do not transfer your IP address or your browser identification (user agent) on this path. The event is not transferred for our automated test calls. We store the click identifier and the browser identifier at your sign-up only with your consent to “Marketing and ad measurement”; if you say no or withdraw, we delete both from your enquiry record. Otherwise we delete both as soon as the event has been transferred or it is certain that it will not be transferred, but no later than seven days after you submitted your sign-up. If you withdraw your consent via “Cookie settings” while a page you opened through your personal link is open, that page reports the withdrawal to our server immediately and we apply it to your enquiry record; otherwise we apply it as soon as you next open a page through your personal link. Before every server-side transfer and before every retry our server checks the enquiry record again; from the moment the withdrawal is applied the event is neither sent nor re-sent. We cannot recall events already transferred. For enquiries you submitted before this version took effect, we transfer no event to OpenAI from our server.

We transfer the data to OpenAI Ireland Ltd., based in Ireland; we do not transfer it to a third country. As an independent controller (see below), OpenAI may also process the data outside the European Economic Area, in particular in the USA, and is itself responsible for such a transfer and its safeguards; OpenAI's privacy policy gives the details. Access by authorities in third countries cannot be completely ruled out there.

We decide whether and when the OpenAI pixel is integrated and triggered on our website and whether and when our server transfers events to OpenAI, and we are responsible for this integration, for the server-side transfer and for the consent they require. OpenAI Ireland Ltd. is the independent controller for the processing of the data it receives, under OpenAI's Advertising Terms and Ad Tools Data Processing Addendum (https://openai.com/policies/advertising-terms, https://openai.com/policies/ad-tools-dpa). How long OpenAI stores the data and what OpenAI uses it for is described in OpenAI's privacy information (https://openai.com/policies/).

Your consent is voluntary; without it you suffer no disadvantage in using our website, and you can still register. You can withdraw it at any time with effect for the future via “Cookie settings” in the page footer. After a withdrawal, the website tells a pixel already loaded on the open page that consent is no longer in place and gives it no further commands; an event not yet sent at that moment may then be transferred by the pixel without the identifiers from __obref and __oppref. The website deletes the cookies __obref, __oppref and __oaiq_domain_probe in your browser on withdrawal and afterwards on every visit to a page of our main domain gastrozukunft.de with “Cookie settings”, as long as your refusal is stored there; it deletes the cookie __oaiq_consent and the local storage entry oaiq_consent, which the pixel may create on withdrawal, at the latest on the next page visit. The same happens if you refuse the category. For the server-side transfer the paragraph “Server-side transfer” applies: from the moment your withdrawal is applied to your enquiry record our server no longer transfers the event “registration_completed”, and we delete the click identifier and browser identifier stored at your sign-up. We cannot recall reports already transferred to OpenAI. The lawfulness of the processing carried out until the withdrawal remains unaffected.

WhatsApp Business Platform: messages about your enquiry and your restaurant

If you give us your mobile number and expressly choose WhatsApp as your preferred contact channel, we send you information about your enquiry and about setting up your account via the WhatsApp Business Platform (Cloud API). Without that express choice we send no WhatsApp messages at all; email is always the default. If you choose WhatsApp there, you also consent – as the text at that point says – to the WhatsApp notices about your restaurant (section “WhatsApp notices about your restaurant”).

You make this choice yourself during setup, and it is voluntary. If you do not choose WhatsApp, you receive the information about your enquiry by email – with no disadvantage of any kind; reminders by email, however, only if you agreed to them in the sign-up form (section “Data processed and purposes”).

The following data is processed:

  • your mobile phone number,
  • your name or the form of address you gave us,
  • the content of the messages we send you and of your replies to us,
  • delivery information (sent, delivered, read, failed) together with the time,
  • the language you selected, so that you receive the message in your own language.

The legal basis is your consent under Art. 6(1)(a) GDPR, which you give by choosing WhatsApp as your contact channel, together with Art. 6(1)(b) GDPR for pre-contractual steps taken at your request.

For sending and receiving we use the WhatsApp Business Platform provided by WhatsApp Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland (Meta group of companies) as a processor within the meaning of Art. 28 GDPR, on the basis of the WhatsApp Business Data Processing Terms.

To be straightforward about it: we do not operate a WhatsApp client of our own. Messages travel through the Cloud API hosted by Meta. Unlike a conversation between two private devices, the message content is present at Meta on this path and is processed there. Please therefore do not send us any special categories of personal data within the meaning of Art. 9 GDPR via WhatsApp.

Processing outside the European Union, in particular in the United States, cannot be ruled out. According to Meta, such transfers rely on an adequacy decision under the EU-US Data Privacy Framework (Art. 45 GDPR) and/or on EU standard contractual clauses (Art. 46 GDPR). Despite these safeguards, access by authorities in third countries cannot be entirely excluded.

You can stop receiving messages on WhatsApp at any time by replying “STOP” to us in WhatsApp. We recognise that word and a fixed list of equivalents in German, English, Arabic, Turkish and Kurdish – among them “STOPP”, “قف”, “DUR” and “RAWESTE”; every word is valid in every language, regardless of the language your enquiry is held in. The withdrawal takes effect immediately and for every enquiry held under that phone number: you will receive no further WhatsApp messages from us. If you agreed to reminders by email, we then continue the reminders for your enquiry by email; your delivery is switched to email for that purpose. If you do not want those either, the unsubscribe link contained in every one of our reminder emails is enough – it ends the reminder sequence entirely. You receive exactly one confirmation on WhatsApp and no further WhatsApp message after that. An informal message to info@gastrozukunft.de is equally sufficient.

Replies you send us about your enquiry on this number are not read by a person. If you write anything there other than a stop instruction, you receive one automatic reply per day pointing you to our customer-service chat; it contains none of your data. This does not apply to messages restaurant owners send from the number they have confirmed for the WhatsApp notices about their restaurant – see the paragraph on WhatsApp notices about your restaurant below.

We send reminders about your enquiry only from Monday to Saturday between 09:00 and 18:00 (Europe/Berlin time zone) and at most three times per phone number per day.

We never send access credentials, confirmation codes or invoices via WhatsApp; those always go by email only.

We delete message content and delivery information as soon as it is no longer required for the stated purpose, and at the latest when the associated enquiry is deleted. Statutory retention obligations remain unaffected.

WhatsApp notices about your restaurant

If you run a restaurant on our platform, you receive important notices about your restaurant by email. If you wish, we also send them to you on WhatsApp. To do so, you agree explicitly when signing up – when you choose WhatsApp as the way for our messages, or next to the data processing agreement – or on a page of its own. The number for it is your confirmed WhatsApp number or one you give for these notices; it is shown nowhere. If you already confirmed exactly this number with a code when signing up, the channel is active at once; otherwise you confirm it by sending us “JA” with the code shown to you on WhatsApp from this number. On a page of its own, this is the mobile number stored in your registration or in your restaurant details. If, when WhatsApp is first switched on, the code comes from a number we cannot match to your restaurant, we send the notices not to that number but to the WhatsApp number stored in your restaurant details or in your registration – provided there is one and it has not objected to our messages; we also tell you so by email. Your consent is voluntary – without it you receive every notice by email as before. The messages come in the language in which you agreed, where Meta has approved the templates in that language, otherwise in German (if you chose Kurdish, you receive them in German).

The notices cover everything that concerns your restaurant on our platform, today for example: the upcoming and the actual end of the trial period or term, an extension, the announcement of a deletion of your restaurant and its stopping. Each of these messages has a button to a page that shows the current status of your restaurant and, where possible, the way to extend it; for an announced deletion it leads to a page where you can stop the deletion, request a copy of your data or have your email address corrected. These messages contain no access details, codes or invoice data. We always send the formal notice of a deletion by email; the WhatsApp message does not replace it. We do not send advertising on WhatsApp.

Your consent also covers notices about what Google asks for to verify your Google Business Profile and – once Google has verified it – a link with which you can have the ordering link added at Google. You then receive these notices on WhatsApp instead of by email; where WhatsApp is not possible in a given case, by email (see the section on the Google Business Profile). All other emails stay.

The following is processed:

  • your mobile number: in the WhatsApp channel we store only a cryptographic check value of it, its last four digits and the country. Messages go to the number from your registration or restaurant details that matches this check value. We store the number you give for these notices with your restaurant (it is shown nowhere) and delete it together with the restaurant,
  • your consent: the version and the check value of its wording, the time and the way in which you gave it, and as evidence a salted check value of your IP address and the identifier of your browser (user agent); likewise a withdrawal with its time and way – in each case the latest consent and the latest withdrawal,
  • the confirmation code – only as a check value – with the times it was issued and redeemed, and the check value, last four digits and message ID of the number from which you sent it,
  • for every message we send you: its kind, template and language, the times, the delivery status (sent, delivered, read, failed) with an error code, the message ID at WhatsApp and the check value and last four digits of the recipient number – not the text itself, which follows from the template,
  • your replies to us: text, time of arrival and message ID; we do not download the content of voice messages, pictures or files,
  • the raw data Meta transmits about every incoming message – including your full number, where applicable your WhatsApp profile name and the content (for media their ID and caption, for locations the coordinates),
  • the language in which you receive the messages.

We store your replies from the confirmed number; our team sees them in our administration and receives by email only a notice without the text. If your request needs an answer, we answer you by email. For your message you receive at most one automatic acknowledgement per day – and, if your message stops an announced deletion, a confirmation of that. If you write to us while a deletion of your restaurant is pending – even with just a stop word – or confirm “Keep restaurant” on the page, we stop the deletion, as long as it can still be stopped, until we release it; without a decision we extend the retention by 90 days at a time.

We send reminders about the term and a deletion from Monday to Saturday between 09:00 and 18:00 (Europe/Berlin time zone), as a rule at most one per day – a notice about an announced deletion may follow on the same day; confirmations – for example of an extension or of a stopped deletion – at any hour, usually within one hour.

The legal basis for the notices on WhatsApp and the data stored for them is your consent under Art. 6(1)(a) GDPR. We base the handling of your replies and the stopping of a deletion on Art. 6(1)(b) GDPR, because they concern your contract with us; if you act for a business that is a legal person, on Art. 6(1)(f) GDPR – our legitimate interest is looking after the contract with your business. We keep the evidence of your consent and of a withdrawal under Art. 6(1)(c) in conjunction with Art. 7(1) GDPR, alternatively under Art. 6(1)(f) GDPR (evidence and respect of the withdrawal). We keep the evidence of recognised terminations and consents under Art. 6(1)(c) GDPR in conjunction with Section 257 HGB or Section 147 AO, alternatively – and for recognised objections and requests for erasure or access – under Art. 6(1)(f) GDPR (evidence of declarations concerning the contract and of how they were handled). Even after a withdrawal we use the check value and the last digits of your number to assign your messages to this number to your restaurant (Art. 6(1)(b) or (f) GDPR). Where we rely on Art. 6(1)(f) GDPR, you may object at any time on grounds relating to your particular situation (Art. 21 GDPR).

You can withdraw your consent at any time: by replying “STOPP” (or one of the equivalent words listed above) on WhatsApp or by email to info@gastrozukunft.de, and also on the status page linked in our messages as long as its link is valid. A “STOPP” ends the WhatsApp notices for all restaurants for which you confirmed this number. After that we send you no more WhatsApp messages – except exactly one confirmation if you withdrew on WhatsApp; we keep sending you every notice by email. If you withdraw with “STOPP” and an enquiry is still running under the same number, we switch its reminders to email. The lawfulness of the processing up to the withdrawal remains unaffected.

We delete the details of every message sent and the confirmation code 90 days after their latest time. We delete the text of your replies 90 days after arrival; what remains is only that and when a reply arrived (with the check value and the last four digits of the number), for as long as your restaurant exists. Replies that our system recognises from keywords as a possible legal declaration – for example a termination, a consent, an objection or a request for erasure or access – we additionally keep as evidence (text, time of arrival, message identifier, the last four digits of the number, the kind recognised and the link to your restaurant): a termination or consent until the end of the sixth calendar year after arrival (Section 257 of the German Commercial Code, HGB, or Section 147 of the German Fiscal Code, AO), an objection or a request for erasure or access until the end of the third calendar year after arrival (Sections 195 and 199 of the German Civil Code, BGB) – also after your restaurant has been deleted. We keep the details of your consent and of a withdrawal for as long as your restaurant exists, so that a withdrawal can be respected. When your restaurant is deleted, we delete the details of the WhatsApp channel; the deletion record notes, without the number, whether and when a consent existed. We delete the raw data Meta transmits about incoming messages after 30 days and the entry about it after 90 days – independently of the deletion of your restaurant.

For sending and receiving, the information above on WhatsApp Ireland Limited as processor, on Meta's Cloud API and on transfers to third countries applies accordingly.

Connecting your Google Business Profile

While setting up your restaurant, you can connect your Google Business Profile to our platform so that we can find your restaurant's profile on Google – or create one if there is none yet – and add the order link to your menu to it. This section is aimed at restaurant owners. The connection is voluntary; you can complete the setup without it.

To connect, you sign in directly with Google using your own Google account; you enter your Google password only at Google. Google asks you for permission to manage the Business Profiles of that account. Your roles on Google do not change as a result.

If you establish the connection, we process:

  • the authorisation granted by Google in the form of a refresh token, which we store encrypted,
  • the names and identifiers of the Google business accounts your Google account has access to, and the names and identifiers of the Business Profiles of the connected account,
  • the profile selected in your connection and the times at which the connection was established and checked,
  • to search for your profile, the name and address of your business from your registration – never the owner's name, phone numbers or e-mail addresses; Google can associate this search with your Google account,
  • the information Google returns about profiles found (name, address, website, link to Google Maps, verification status). We only display these results to you and do not store them. The verification status of your selected profile is the exception; see the paragraph on the verification status below. After a click on “Yes, start” we also use them to select your profile or to decide whether we create one; only the profile selected or created in this way is stored – see the paragraph on the “Yes, start” button below.

Until you expressly ask us to, we use the connection for reading only: for the search, to display the selected profile and its verification status and – automatically, about twice a day – to check the verification status of your selected profile, so that we can tell you what Google asks for to verify it (see the paragraph on the verification status below).

When you click, we add an order link to your Business Profile that leads to your restaurant's menu with us. Without that click this does not happen; the setup can be completed without it. Google reviews the change before it appears – we cannot promise that or when it becomes visible. Immediately before each entry we read your profile, its verification status, the order links already there and the link types available in your country once more; only then is anything written. This click can also be the click on “Yes, start” if the note that we add the order link ourselves was shown there: we then add it later without a further click (see the paragraph on the automatic entry below). If you set up your restaurant through our setup, we add the link – even when you click – only once you have completed the “Receive orders” step there or our ordering app is signed in on at least one device, so that no order arrives unnoticed; for this we only check whether that is the case.

Only the following is written: the internet address of your menu as the order link and – only if you additionally tick it – the internet address of your restaurant's website as the profile's website, as well as whether your order link should be the preferred one. We neither delete nor change an order link that another provider has entered there. If Google has no profile for your restaurant yet, we create one – only when you click – using solely the name and address from your registration, the internet address of your restaurant's website with us as the website and the category “Restaurant”; Google reviews it before it appears, and you can delete it yourself at Google at any time. We do not change any other detail of your profile and do not set up any notifications at Google.

These entries are part of your public Business Profile and are therefore visible to everyone who views it on Google. You can remove or change them yourself in your Business Profile on Google at any time; if you disconnect on our side, a link that has already been entered remains on Google until you remove it there. No additional personal data arises – the addresses entered are addresses of your restaurant. You can also have us remove our order link, and you can cancel an automatic entry that has not happened yet: once Google has verified your profile, the page opened by the link in our messages about the verification status – as long as that link is valid – shows the button “Remove the ordering link at Google” if we have added the order link or it is not certain whether it arrived, or the button “Do not add the ordering link” as long as we would still add it automatically. When you click, we first end any instruction for the automatic entry; as long as the connection exists, we then no longer add the link to this profile automatically. Then we read the links of your profile at Google afresh and delete only the entries whose address is exactly our order link; we do not change links of other providers or the other details of your profile. If we cannot delete such an entry – for example because Google does not allow it to be changed – we tell you so on the page, so that you can remove it yourself at Google. We cannot promise whether or when the change becomes visible on Google. We note your click and its result in the record of Google's verification of your profile (see the paragraph on the verification status). The legal basis is Art. 6(1)(b) GDPR, as the removal too is part of the Google presence you are having us set up; if you act for a business that is a legal entity, Art. 6(1)(f) GDPR applies to your data as the acting person, as in the paragraph on the legal basis below.

On the verification status of your profile: about twice a day we automatically ask Google whether your selected profile still needs to be verified, whether a verification is in progress, has been completed or has been refused, whether Google asks for further steps – for example after a suspension – and which kind of verification Google offers (a code, instant verification, a postcard or another way). For this we store the identifiers of the profile and of the respective verification at Google, the status found, the kind of verification offered, the times of the last check and of each change, whether a check failed, and for each change a record of whether and how we informed you and whether you then had the order link added or removed through our page. Google also returns the phone number, e-mail address or postal address it would use for a verification; we discard this information immediately and store neither it nor any code. When the status changes, you receive at most one message about it and, for your profile, at most one reminder in total – on WhatsApp if you have activated WhatsApp notices for your restaurant and they cover your Google profile, otherwise by e-mail. We send these notices ourselves; we do not set up any notifications at Google for this. We never start the verification at Google ourselves: we do not request a postcard and do not enter a code. We keep the status until you disconnect or your restaurant account is deleted, and the records of the changes for 12 months. The legal basis is Art. 6(1)(b) GDPR, as this check and the notices are part of the Google presence you are having us set up. If you act for a business that is a legal entity, we base the processing of your data as the acting person on Art. 6(1)(f) GDPR; our legitimate interest is accompanying the setup your business has requested.

On the “Yes, start” button in the setup: with this click you instruct us to carry out the following steps; for creating a profile it is the click referred to above, and for the order link the paragraph on the automatic entry below applies. After you have connected your Google account as described above – or straight away if it is already connected – we search for your restaurant without a further click, using the name and address from your registration, and compare the profiles found with these details. If we find exactly one profile that is managed through your connected Google account, whose name and postcode match your registration and whose street does not differ, and no other profile that matches fully or partly, we read it once more and then select it without asking you, provided it still matches. If we find several matching profiles or one that matches only partly – for example with the same word in the name or with the same address – we ask you which of them is your restaurant; if a fully matching profile does not belong to your Google account, we explain how to request access to it at Google and do not create another profile. If we find no profile that matches fully or partly, we create the profile described above; immediately before, we search once more and first have Google only check the details without creating anything – if a matching profile turns up after all or Google rejects the details, we do not create one. If you answer our question that none of the profiles shown is your restaurant, we create the profile in the same way, but only if none of them matches fully. If we have already created a profile for your restaurant in this setup and it is accessible through your connected Google account, we select that profile again instead of creating another one. We note with the connection details which profile was selected or created in this way, and when.

On the automatic entry of the order link: if, when you clicked “Yes, start”, the note that we add the order link ourselves was demonstrably shown (for the record, see below), we add the link without a further click to the profile selected or created in the setup as soon as two conditions are met: Google has verified the profile – we find this out through the check of the verification status described above – and the condition regarding the ordering app named above in the paragraph on adding the link is met. Until then we check this again each time we check the status. Only the order link described above is added; we do not change your profile's website or whether your link is the preferred one. Immediately before, we read the profile once more as described above and check whether it still matches the name and address from your registration; if it does not match or the link cannot be added for another lasting reason, we write nothing, and the link is added only when you click. Google reviews this change too; we cannot promise that or when it appears. In this case we send you the message that Google has verified your profile only once the link has been added or it is certain that it cannot be added without your click. If you never clicked “Yes, start” or the note was not shown there, we add the link only when you click. You can prevent the automatic entry by disconnecting on our side before it happens: once our next check notices the disconnection, your instruction ends. Once Google has verified your profile, you can also end it through our page (see above on having us remove the order link). If you restore the connection to the same profile before that, or if you only remove the access in the settings of your Google account, your instruction remains in force, and we add the link as soon as we have access again. You can remove a link that has been added yourself at Google at any time or, as described above, have us remove it. As a record of your instruction we store with this profile the time of the click, the version of this policy valid at that time, a check value of the texts at the button, the language and one check value each that we derive from your IP address and from your browser's identifier – not the address or the identifier itself. We keep this information with the other connection details – at the longest until your restaurant account is deleted; if the connection is renewed or disconnected, it may be removed earlier; we also copy the time and the version into the stored status of your profile (see the paragraph on the verification status). If you have us remove the link or cancel the automatic entry, this information may be removed from the connection details at that point; if we have already copied the time and the version into the stored status of your profile, we note there, instead of the version, that your instruction has ended. We note whether and with what result we added the link in this way in the record of Google's verification of your profile. The legal basis for the entry is Art. 6(1)(b) GDPR, as it is part of the Google presence you instruct us to set up with this click; for the record it is Art. 6(1)(f) GDPR, our legitimate interest being to be able to prove your instruction. If you act for a business that is a legal entity, Art. 6(1)(f) GDPR also applies to your data as the acting person for the entry, as in the paragraph on the legal basis below.

We receive the account and profile information from Google via your Google account.

The legal basis is Art. 6(1)(b) GDPR, as you initiate this connection yourself as part of the setup. If you act for a business that is a legal entity, we base the processing of your data as the acting person on Art. 6(1)(f) GDPR; our legitimate interest is carrying out the setup your business has requested.

The recipient is Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. Google processes the data in your Google account and in your Business Profile under its own responsibility; Google's privacy notices also apply. Google LLC is certified under the EU-US Data Privacy Framework; the transfer to the USA is based on the European Commission's adequacy decision (Art. 45 GDPR).

We delete the stored authorisation as soon as the connection is disconnected – in the admin area or upon your message to the contact address given above. The remaining connection details (account and profile names, selected profile, times) remain stored with your restaurant's database until your restaurant account is deleted. If you connect a different Google account instead, the earlier connection is marked as ended; its encrypted stored details likewise remain until your restaurant account is deleted. We do not store search results and profile information that we only display to you.

Independently of this, you can remove the access at any time in the settings of your Google account; the authorisation stored with us then has no effect. The data subject rights set out in this policy apply (Art. 15 to 21 GDPR).

Audience measurement (without cookies)

To understand how our website is used, we run a simple audience measurement of our own. It runs entirely on our server in Germany, without cookies and without any third-party service.

For each page view we process:

  • the page requested and the time of the request,
  • the referring site — only its domain, not the full address — and campaign parameters if present,
  • the device category (phone, tablet, computer) and the broad browser and operating-system family,
  • the approximate origin at country and region level; we only report a city when it cannot be traced back to individuals,
  • the language preferred by your browser,
  • a technical value that lets us count several page views within the same day as a single visit.

Your IP address is processed in memory only and immediately converted into an irreversible value. It is never stored — neither in a file nor in a database. The key used for that conversion changes daily and is then deleted, so recognising a visitor beyond a single day is technically impossible.

No cookies are set, and no information is stored on or read from your device. This applies to every measurement described in this section, including the interaction signals mentioned below. Consent under § 25 TDDDG is therefore not required.

The same cookieless measurement also runs on our campaign pages (gastrozukunft.de/3-monate-kostenlos/ and the data form linked from it). In addition to the items listed above, we process the campaign attributes contained in the address you opened: campaign, creative, search term, source and medium, as well as the language the advertisement was delivered in. If the address contains an advertising click identifier, we store only the fact that such an identifier was present — never the value itself.

On the campaign pages we additionally measure how the page is used: how long it stayed open, how far it was scrolled, which sections were reached, which buttons were pressed, and which form field was last edited when the form was not submitted. Your browser sends these signals without any identifier; it stores nothing on your device for this purpose and reads nothing from it. Of the form fields, only the field NAME is transmitted — never the value you typed. The legal basis here is likewise Art. 6 (1) (f) GDPR, and “Do Not Track” and “Global Privacy Control” are honoured exactly as for the rest of the reach measurement.

On our home page (gastrozukunft.de) and on our campaign pages we also measure how far our explanatory video was watched: that it was started, and whether a quarter, half, three quarters or the end was reached. Only one of these five stages is transmitted — no point in time, no number of seconds and no playback position. The video is only loaded once you click it. Here too your browser stores nothing on your device and reads nothing from it; the legal basis is Art. 6(1)(f) GDPR, and “Do Not Track” and “Global Privacy Control” are respected exactly as they are for the rest of our reach measurement.

Separately from this, we count our own business events: that an enquiry arrived, that an e-mail was sent, that an account was created, and how many submissions were duplicates or were refused. These counts contain no information about your device, your browser or your location. They belong to the handling of your enquiry rather than to the reach measurement — objecting to the reach measurement therefore does not stop them. Your rights regarding the enquiry itself are unaffected and are described in the section on your rights.

For every enquiry sent through the sign-up form we keep a record of the set-up steps: which step was shown, completed, refused or put on hold, at what time, with a reason key and a field key from a fixed list. Entered values, IP address and browser identifier are not stored in it. The record is linked to your enquiry and visible to our team so that we can support you during the set-up (Art. 6 (1) (b) GDPR). In aggregated form, without reference to the individual enquiry, we use it to find the points where set-ups are abandoned (Art. 6 (1) (f) GDPR); you may object to that evaluation at any time (Art. 21 (1) GDPR) without any effect on your enquiry. Entries about steps that were shown are not recorded when your browser sends “Do Not Track” or “Global Privacy Control”.

We delete the entries of this record 90 days after the last recorded step, and at the latest together with your enquiry. Aggregated figures without reference to the individual enquiry are formed from it only at the time of evaluation and are not stored separately.

From the IP address stored with your enquiry we derive, during evaluation, only the country, and from the browser identifier only the device category; neither is stored separately. The country flows exclusively into aggregated figures, which are shown only from five enquiries upwards; the device category is also visible to our staff for the individual enquiry, so that display problems can be reproduced. The country is resolved from a local database on our server, without querying any third party.

The legal basis is Art. 6 (1) (f) GDPR. Our legitimate interest lies in shaping our offering to actual demand, planning server capacity, and detecting technical faults and abusive access.

Individual records are deleted automatically after 14 days at the latest. Only aggregated figures without any personal reference remain; we keep those for up to 400 days so that year-on-year comparisons are possible.

No data is passed on to third parties. Analytics services such as Google Analytics or Matomo are not used, and there is no transfer to third countries. The origin region is resolved from a local database on our own server, without querying any external provider.

IP geolocation: “IP Geolocation by DB-IP” (https://db-ip.com), licence CC BY 4.0.

You may object to the audience measurement at any time (Art. 21 (1) GDPR). We automatically honour the browser settings "Do Not Track" and "Global Privacy Control": if either is active, no measurement takes place for you. Independently of that, an informal message to the contact address above is sufficient.

For our customers' restaurant websites (addresses of the form restaurant.gastrozukunft.de) we perform the same measurement on behalf of the respective restaurant. There, the restaurant is the controller; we act as processor on its instructions.

Granular usage measurement in the restaurant admin panel

This section describes only the granular measurement of predefined panel areas and functions; operational session and login data are separate. When restaurant owners or staff use the admin panel, GastroZukunft records, to a limited extent, which predefined areas are opened and which predefined functions are invoked. The controller is YASEEN Design und Druckservice (GastroZukunft), not the restaurant. The purposes are product improvement, support, security and capacity planning.

For each event we store only:

  • the restaurant assignment, the UTC time and an identifier from the closed list of panel areas or functions. A function event only shows that an authenticated, predefined invocation was triggered; it does not prove that a business change succeeded,
  • a day-scoped, non-reversible pseudonymous visitor value whose key changes every day,
  • the device category and the interface language used. Operating-system family, browser family and a bot flag are not stored for these panel events.

The IP address and full user agent are processed briefly in memory only to derive the daily value and device category and to reject automated bots. Neither raw value is stored in spool files or in the database. For abuse prevention, a temporary technical counter file is also created: its filename is a truncated SHA-256 value derived from the restaurant assignment, session, IP address and UTC hour; its content is only a counter and contains no raw IP address.

We do not store an admin user ID, name, email address or role, form entries, work content, specific menu, order, price, payment or object identifiers, full URLs, referrer, campaign or location data. There is no breakdown by individual staff members and no automated decision about a person.

For this measurement we do not set or read cookies and do not use LocalStorage or SessionStorage. The client-side queue exists temporarily in memory only.

The legal basis for this granular usage measurement is Art. 6 (1) (f) GDPR. Our legitimate interests are needs-based product improvement, support, security and capacity planning.

Unprocessed spool files and technical files of the request limit are deleted after 24 hours at the latest. Raw events are kept for a maximum of 14 days, aggregated counters for a maximum of 400 days. The separately held login and session data of the admin panel are kept for a maximum of 90 days.

The data is processed on servers provided by IONOS SE in Germany or the EEA; IONOS acts as hosting processor. No external analytics service is used and these analytics data are not transferred to any further third party or third country. The restaurant is not provided with a breakdown by individual staff members.

You may object to this usage measurement at any time by an informal message to the contact address above (Art. 21 (1) GDPR), without restricting panel functions. Because events contain no admin user ID, a confirmed objection is implemented technically for the entire restaurant before any spool file is written. We also honour “Do Not Track” and “Global Privacy Control” automatically.

Your rights of access, rectification, erasure, restriction, data portability and objection under Articles 15 to 21 GDPR remain unaffected. Please use the contact address above.

Newsletter with product news

On our website you can voluntarily sign up for a free newsletter. In it we report on new platform features, on changes and maintenance work, and on practical tips for running a food-service business. We send only to people who actively signed up and confirmed their sign-up.

We use the double opt-in procedure: after you sign up we send you an e-mail containing a confirmation link. Only once you complete that confirmation do we add you to the distribution list. The confirmation e-mail itself contains no advertising.

The following is processed: your e-mail address, your preferred language, optionally your name, and — as evidence of your consent — the time of sign-up and of confirmation, the IP address used, your browser identifier and the page the sign-up was made from.

The purpose of the processing is to send the newsletter and to demonstrate your consent. The legal basis is Art. 6(1)(a) GDPR in conjunction with Section 7(2) no. 3 UWG; recording the evidence data relies on Art. 7(1) GDPR.

We use no tracking pixels and no tracking links in our newsletters. Your opening and clicking behaviour is neither measured nor stored. No consent under Section 25 TDDDG is therefore required for this.

You may withdraw your consent at any time with effect for the future. Every newsletter e-mail contains an unsubscribe link that works with one click, without logging in and without giving a reason; in addition our e-mails support your mail program's one-click unsubscribe. Alternatively an informal message to info@gastrozukunft.de is enough. The lawfulness of processing carried out before the withdrawal remains unaffected.

Sign-ups that are not confirmed within 30 days are deleted in full. After an unsubscribe we keep your address solely as an irreversible check value, so that we can make sure you receive no further newsletters (suppression list). The plaintext details and the evidence data are deleted once the three-year evidence period has elapsed.

Sending is done via our own server in Germany; no external newsletter provider is used. Your data is not passed to third parties for advertising purposes and is not sold.

Signing up is voluntary and is not a condition for entering into a contract or for using the platform.

Reference customers

On our website we name restaurants that use our platform as references: with the name of the business, its logo and a link to its public presence. We also state the number of participating businesses. This is information about a business; it is personal data only in so far as the business name also contains the name of a person.

The legal basis is our legitimate interest in presenting existing business relationships (Art. 6(1)(f) GDPR). For businesses that have expressly permitted us to name them, we additionally rely on that permission.

You can object to your business being named at any time and without any formality – a message to info@gastrozukunft.de is sufficient and no reason is required. We will then remove the business from the presentation and record the objection so that it takes permanent effect (Art. 21(1) GDPR).

Retention period

Server logs are generally deleted within 14 days. Contract and billing data are stored in accordance with statutory retention periods. Enquiries from the registration form that are not completed are deleted automatically as soon as 30 days have passed since your last change to the enquiry; reminders from us do not extend this period. Completed enquiries are kept until your access has been set up; if a contract is concluded, we remove the IP address and browser identifier from the enquiry at the latest 90 days after your access has been set up. The logs of the confirmation codes are deleted at the latest 90 days after they were generated. Other contact data from enquiries are deleted as soon as they are no longer needed for handling them, unless statutory obligations prevent this. For the retention period of the record of your cookie choice, see the section "Cookies, local storage and optional services".

For the order confirmation at checkout (acceptance of the terms, the right-of-withdrawal notice and the declaration of acting as a business) we store evidence containing contact e-mail, invoicing details, IP address, user agent, language and timestamp. If no payment followed, we automatically erase the personal details of that evidence at the latest 90 days after the checkout attempt; what remains is the non-personal record that the confirmation was given. If the checkout did lead to a payment, the statutory retention periods for invoices and contract documents apply.

When you submit the registration form for the three free months, we do not yet create your details as an enquiry. We first encrypt them and store only the encrypted text; we keep the key to it nowhere – it exists only in the confirmation e-mail and in the window in which you filled in the form. The enquiry comes into existence only once you have confirmed the contact details you gave – every e-mail address by a code e-mail, every telephone number by a code that we send by SMS or, for landline numbers, read out in an automated call. If you do not confirm, the encrypted entry is deleted automatically after 24 hours at the latest. During that time we cannot identify you and therefore can neither provide information about this entry nor delete it on request (Art. 11(2) GDPR) – it deletes itself in any case. Your rights regarding enquiries that already exist are unaffected.

Your rights

You have the right to access, rectification, erasure, restriction of processing, data portability and objection (Art. 15–21 GDPR). Please contact us using the contact details above.

Right to lodge a complaint

You can lodge a complaint with a data protection supervisory authority if you believe that the processing of your data violates data protection law.

The supervisory authority responsible for us is the Thuringian Commissioner for Data Protection and Freedom of Information (TLfDI), Häßlerstraße 8, 99096 Erfurt. You may also contact any other data protection supervisory authority.

Changes to this statement

We update this privacy policy when legal or technical conditions change. Please review this statement regularly.

Privacy policy for the “GastroZukunft Admin” app

Last updated: 2026-10-10

This privacy policy explains the processing of personal data when using the “GastroZukunft Admin” mobile app (restaurant login, order management and push notifications).

Scope

This statement applies to the “GastroZukunft Admin” app and related backend services that enable login, restaurant account management and notification delivery.

What data we process

  • Login data (e.g. email/username) and authentication/session tokens.
  • Restaurant and account data (e.g. restaurant name, tenant/slug, roles/permissions).
  • Operating system (iOS/Android), app version and build, installation source (App Store, Google Play, TestFlight) and language – for the “Update available” notice and for error analysis and support.
  • Firebase Cloud Messaging (FCM) token to send push notifications about new orders.
  • The app does not send automatic crash or diagnostic reports.
  • Content you create, change or upload in the app (e.g. dishes, prices, photos, files, allergens, opening hours, order status); it is stored in your restaurant’s admin panel. The AI suggestion for allergens is covered by the section “AI-supported functions”.
  • Only on your device, in protected storage (iOS Keychain or encrypted Android storage): your email address, your session token and – only if you choose “Remember password on this device” – your password. Also kept only on the device: a started draft for a new dish (until you create the dish or discard the draft) and the most recently loaded order list with your guests’ details, so that it appears immediately after a restart; both are deleted when you sign out or switch restaurant.

We do not use external marketing or analytics SDKs in the app; in particular, Firebase Analytics and Firebase Crashlytics are not included. However, our own cookieless usage measurement described in “Usage measurement in the restaurant admin panel” applies to the embedded admin panel.

Why we process data

  • Provision of app functions (login, management of restaurant data and order status).
  • Sending notifications about new orders and about messages from GastroZukunft (e.g. “Update available”) via FCM.
  • Ensuring security (e.g. abuse and error detection).
  • Stability and support (bug fixing, technical diagnosis).

Legal bases (GDPR)

Processing is based on Art. 6(1)(b) GDPR (contract/pre-contractual measures), Art. 6(1)(f) GDPR (legitimate interest in operation, security and stability) and, where required, Art. 6(1)(a) GDPR (consent).

Recipients and third parties

  • Google Firebase Cloud Messaging (FCM) for push notification delivery.
  • Google Play services (Android) as a technical requirement for push notifications.
  • Apple Push Notification service (APNs) for delivering push notifications on iPhone and iPad.

For delivery, Google and, on iPhone and iPad, also Apple receive the device token and the text of the notification, e.g. “New order” with the order number; a notification does not contain names or contact details of your guests. Google and Apple may also process these data in the USA; according to the providers, such a transfer is based on the EU-US Data Privacy Framework (adequacy decision pursuant to Art. 45 GDPR) or on EU standard contractual clauses (Art. 46 GDPR).

We use no external marketing or tracking services; Firebase Analytics and Firebase Crashlytics are not used. Our own cookieless panel usage measurement runs on servers provided by IONOS SE in Germany or the EEA; IONOS is the hosting processor. These analytics data are not transferred to any further third party or third country.

Retention period

As a rule, we store personal data only as long as your account is active and the data is required for app usage. Technical logs or error reports are retained for an appropriate period and then deleted.

Security

Data transmission is encrypted (HTTPS). Access to data is restricted to authorized persons; we implement organizational and technical measures to protect against loss, misuse or unauthorized access.

Your rights

You have the right to access, rectification, erasure, restriction of processing, data portability and objection under Art. 15–21 GDPR.

Data deletion / requests

If you request deletion of your data or information, please contact us at info@yaseendesignservice.de . We may request additional information to verify your request.

Children

The app is intended exclusively for business users (restaurants) and is not designed for children.

Changes to this privacy policy

We update this privacy policy if legal, technical or organizational changes occur. The current version is available at https://gastrozukunft.de/datenschutz.php#privacy-app .

Your choice about cookies and optional services

Technically necessary functions are always active. We only use optional services – such as measuring our ads – if you agree. You can change your choice at any time.

Privacy policy Legal notice