Privacy policy

Controller

The controller for data processing on letuzz.com is:

Simon Petz
Vienna, Austria
[email protected]

There is no data protection officer; letuzz is not required to have one.

The essentials

• You don't need an account. We never ask for your name or email address.
• Google Analytics loads only with your consent. There are no ads or social media plugins.
• Fonts and images come from letuzz itself, not from Google or other services.
• We store your cookie choice for 180 days. With your consent, Google sets analytics cookies. When you contribute, we also set a cookie with a random ID. The lunch cookie lasts until the end of the week at most; Discover uses a separate ID lasting until the end of the calendar year following the selected season year at most. Favourite venues use another separate ID that expires 12 months after it was last used.
• We don't sell data. Contabo (server and database) and Cloudflare (protection and delivery) process data needed to operate letuzz. Google receives analytics data only with your consent.

Visiting the site and hosting

letuzz runs on a server we rent from Contabo GmbH, Welfenstraße 22, 81541 München, Deutschland. It is located in a data centre in the European Union. Contabo processes the data on our behalf (Art. 28 GDPR). With every request the server processes technically necessary data: IP address, time, requested address (including the search term if you search), referrer, browser and operating system, and the response status. No page can be delivered without it.

In front of our server sits a service from Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. It receives your request, forwards it to our server, delivers files such as fonts and images from its worldwide network and fends off attacks and automated bulk requests. Cloudflare processes the same technically necessary data, above all your IP address. As Cloudflare is a US company, data may be transferred to the USA. Cloudflare is certified under the EU-U.S. Data Privacy Framework, which is covered by an adequacy decision of the European Commission (Art. 45 GDPR), with standard contractual clauses as a fallback (Art. 46 GDPR). Cloudflare processes the data on our behalf under its data processing addendum (Art. 28 GDPR). More: Cloudflare privacy policy.

Our server keeps access logs, including IP addresses. They are rotated by size and older entries are overwritten; at today's traffic that is a few days. letuzz adds its own events to the log, such as "lunch page viewed, language English, day Monday" or a search term, and for letuzzTap that a round was opened, revealed or shared, with its number and the score. These entries contain no IP address. More about Contabo is in the Contabo privacy policy.

The legal basis is our legitimate interest in delivering the site securely and without errors (Art. 6(1)(f) GDPR).

Offer data and your contributions are stored in a database on the same server at Contabo, that is in the European Union. We keep a daily backup of the database on the server for 14 days. Until 24 November 2026 an older copy of the database also remains at Neon and of the former site at Vercel; we then delete both.

Cookies and storage on your device

Without analytics consent there are no analytics cookies. We store your choice in letuzz_analytics for 180 days so that we can respect it. It contains only acceptance or refusal, with no user ID. We don't remember your language either: it is part of the address (/de/ or /en/). If you open letuzz.com without a language, we follow your browser's language setting.

letuzzTap, the daily question behind the dot in the logo, stores nothing on your device either: your answers live only in the memory of the open page and are gone once you reload it.

When you contribute on lunch, restaurant or menu pages, we set this necessary cookie:

• Name: letuzz_sid, set by letuzz.com itself.
• Content: a random ID (UUID). It contains nothing about you or your device.
• When: only when you confirm an offer, choose a dish for today or as a favourite, suggest a venue or report something wrong with a venue or a menu.
• Purpose: letuzz links your contributions of this week to your browser. That way your vote counts once, you see your own answer and you can change or withdraw it. A favourite dish counts once a week: if you choose it again in a later week, it counts once more.
• Duration: until 23:59 on Friday of the week letuzz is showing (at the weekend that is already the next week), so seven days at most. It is never extended.

Scripts on the page cannot read the cookie, and it is only sent over encrypted connections.

This cookie needs no consent. Under § 165(3) of the Austrian Telecommunications Act 2021, storing information on your device without consent is allowed where it is strictly necessary for us to provide a service you have explicitly requested. You request that service when you tap an answer, a dish, "Suggest a restaurant" or "Report" yourself. Without the ID we could not count your vote only once, and you could neither change nor withdraw it.

We also store the ID in our database, with every contribution you make with it. We don't know who you are, but we can recognise your browser while the cookie is valid. We therefore treat the ID as personal data. The legal basis for processing it is Art. 6(1)(f) GDPR. Our legitimate interest is that every vote counts only once and that you can change or withdraw your own contributions. As the cookie expires with the week, contributions from different weeks get different IDs and cannot be linked to each other.

You can delete the cookie in your browser settings at any time. letuzz can then no longer link your contributions to this browser: they still count, but you can no longer change them.

Your favourites and reports in Discover

In Discover you can anonymously choose one favourite offer per category and season, change your choice or withdraw it. You can also report an incorrect price, availability or detail. Reading Discover does not create a contribution cookie.

Only when you take one of these actions, letuzz sets a separate necessary cookie named letuzz_discover_<season year>, containing a random UUID. It expires at the start of 1 January of the second following year in the category city's time zone (for the 2026 season, 1 January 2028). This keeps your choice available through a winter season that continues after New Year. Voting again does not extend it. Scripts cannot read it; in production it is sent only over encrypted connections. It contains no name, email, device fingerprint or account information. It is separate from the weekly lunch identifier, and different season years get different IDs.

We store your chosen offer, category, season, this identifier and the time of your last choice. Only favourite totals appear publicly. Reports store the offer, reason, date and your optional note with the same identifier; they are visible only in the protected backoffice. Please do not include personal details in notes. We delete favourites within 12 months of the last choice and reports within 12 months of their report date, including the identifier. You can delete the cookie at any time; afterwards you can no longer change the contributions linked to it.

The cookie is necessary to provide your explicitly requested choice or report service (§ 165(3) TKG 2021). The legal basis for processing is our legitimate interest in counting each voluntary favourite once, allowing changes and withdrawals, and correcting offer information (Art. 6(1)(f) GDPR). The same hosting, security and data rights described here apply.

Your favourite venues

On the restaurant and menu pages you can keep up to 3 venues as favourites, without an account. The same venue counts once on both kinds of page; branches of a chain are separate venues. Reading the pages, or asking for your favourites before you have chosen one, does not create a cookie.

Only when you choose your first favourite, letuzz sets a separate necessary cookie named letuzz_fav, containing a random UUID. Your browser sends it only to letuzz's favourites interface (/api/venues/favourites), not with the pages you read. Scripts cannot read it; in production it is sent only over encrypted connections. It contains no name, email, device fingerprint or account information and is separate from the weekly lunch identifier and from Discover. It expires 12 calendar months after you last used your favourites, that is after you last added or removed one or opened your list of favourites; each such use starts this period again. There is no weekly reset.

We store which venues you keep, when you chose them, when you last used your favourites, and a one-way hash of the identifier from the cookie, not the identifier itself. Only how many browsers keep a venue appears publicly; no one can see who chose what. If a venue is no longer shown publicly, it no longer counts and frees its place in your favourites. We delete your favourites, including the hashed identifier, 12 calendar months after your last use; removing a favourite deletes it at once. You can delete the cookie at any time; afterwards your favourites can no longer be linked to you and are deleted at the end of the same period.

The cookie is necessary to provide the favourites you explicitly asked for (§ 165(3) TKG 2021). The legal basis for processing is our legitimate interest in keeping your choice, counting each voluntary favourite once and showing how popular venues are (Art. 6(1)(f) GDPR). The same hosting, security and data rights described here apply.

Google Analytics — only with your consent

With your consent we use Google Analytics 4 from Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, to understand page views, visits, traffic sources and device types and improve letuzz. Google processes visited pages, times, browser and device information, a coarse location derived from the IP address, and random cookie identifiers. The connection also discloses your IP address to Google; Google states that GA4 does not log or store individual IP addresses.

We load the Google tag only after you choose “Allow analytics”. Before consent, after refusal and after withdrawal we send no analytics requests to Google. We do not enable advertising personalization or Google signals, send user IDs, contribution IDs, search text, URL query parameters or form contents. Automatic enhanced measurement is disabled; page views are sent by letuzz.

We also count clicks on original sources and restaurant websites, use of search and filters, and successfully saved dish choices, offer confirmations, menu favourites and restaurant suggestions. Only the type of action is sent with the visited page. Search terms, selected filter values, dish names, suggestion contents, notes, contribution identifiers and outbound destination URLs are not sent. Removing a dish choice or favourite is counted separately.

Legal basis: your consent under Art. 6(1)(a) GDPR and § 165(3) TKG 2021. You can refuse without losing any functionality and withdraw at any time using “Cookie settings” in the footer. Withdrawal applies to future collection and does not affect the lawfulness of processing before withdrawal.

The cookies _ga and _ga_… identify your browser and visits. We limit their lifetime to 60 days without extending it on each visit. Our necessary letuzz_analytics cookie records only your choice for 180 days (no user ID), so we can respect it (§ 165(3) TKG 2021; Art. 6(1)(c) GDPR).

Event and user data retention in Analytics is set to two months, without resetting on new activity. Aggregated standard reports may be retained longer. Google processes data on our behalf under its data processing terms (Art. 28 GDPR). Processing may take place in the USA. Google uses the EU-U.S. Data Privacy Framework for covered transfers (Art. 45 GDPR) and standard contractual clauses where applicable (Art. 46 GDPR). See Google’s international transfer information and Google’s privacy policy.

When you contribute

You can contribute on the lunch page, on the restaurants' pages and on the menus without signing in. We store:

• "Is this lunch offer still current?" Your answer, the time and, if you write one, your note on what changed. Only the number of confirmations and the time of the latest one are shown publicly, never your note.
• "I'm having this today" Which dish you chose for today. Only the number of people who chose a dish is shown publicly.
• "Favourite" Which dishes of a menu you chose as a favourite (three per menu at most), and the day. Only the number of people who chose a dish is shown publicly.
• "Suggest a restaurant" The name of the restaurant and, if given, the district.
• "Something wrong?" The restaurant or menu you are reporting on and what is wrong with it (such as "closed today" or "price is wrong"). If you report a price or a dish, we also store the dish you picked from the list. We add the day and, if you write one, your note. None of it is shown publicly.

Each contribution is linked only to the random ID in the letuzz_sid cookie, not to your name or email address. Please don't put details about yourself or other people in a note.

We use contributions to show current lunch offers and menus, find errors in offers, menus and venue details, add new venues and show which dishes are popular. The legal basis is our legitimate interest in correct and complete lunch offers and menus and in showing the popularity of dishes based on voluntarily submitted favourite votes (Art. 6(1)(f) GDPR). We delete contributions, including the ID, no later than 12 months after the day they refer to, and suggestions no later than 12 months after we receive them.

Protection against abuse

So that nobody can skew the counts with automated requests, the server counts how often contributions come from one IP address. This count lives only in memory, is stored neither in the database nor in the log, and is discarded after ten minutes. The legal basis is our legitimate interest in reliable information (Art. 6(1)(f) GDPR).

Links and sharing

Every offer links to the restaurant's source. Your browser connects to that site only when you click the link. From then on, that operator's privacy policy applies.

You can share a letuzzTap result. "Facebook" is an ordinary link to Facebook's share dialog: your browser connects to Facebook only when you tap it, and from then on Meta's privacy policy applies. Instagram and other apps are reached through your device's share menu; letuzz only hands over the result image and the link. The link contains only the number of the round and your score. No Facebook or Instagram script runs on letuzz.

Your rights

You have the right of access, rectification, erasure and restriction of processing, and the right to data portability (Art. 15 to 20 GDPR). To use them, write to [email protected].

As we don't know who you are, we can only link contributions to you if you send us the ID from the letuzz_sid cookie, the letuzz_discover_… cookie for your Discover season or the letuzz_fav cookie for favourite venues while it is still valid (Art. 11 GDPR). Once the cookie has expired or been deleted, letuzz itself can no longer link your contributions to anyone.

You can also lodge a complaint with the Austrian Data Protection Authority: Barichgasse 40-42, 1030 Vienna, www.dsb.gv.at.

Your right to object

You may object at any time, on grounds relating to your particular situation, to processing based on our legitimate interest (Art. 21 GDPR). This covers processing based on that legal ground. We will then stop processing the data unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. To object, write to [email protected]. You can separately withdraw analytics consent at any time through “Cookie settings”.

No automated decisions

letuzz makes no automated decisions about people and builds no advertising profiles. You are not obliged to provide any data. Without the cookie needed for a contribution you can read letuzz but not contribute.