Privacy

wasbringich.de is built to need as little data as possible. There are no accounts, no tracking and no cookies.

Who is responsible

Guido Grogger, email kontakt@wasbringich.de (see the imprint for the full address).

What we store

• Event data: title, date, optional time, place and an optional description — entered by the organiser.
• Entries: a first name, the dish, optional allergen labels and an optional recipe link — entered by each guest.
• Suggestion log: which recipe suggestions were shown for an event and whether one of them was adopted. This record contains no IP address, no user agent and no link to a person.
• Channel code: if the event was created through a link containing ?via=…, we store that short code (for example “vegan-berlin”) with the event. It tells us which channel brings people here — nothing else. No cookie, no recognition across visits, no link to a person, and it is deleted together with the event.
• Feedback: whatever you write or say in the feedback form, the page you sent it from, and your email address if you choose to give one. Details under “Feedback” below.
• Anonymous counters: how often a page was opened, a recipe was shown, a link was clicked. Aggregated per hour, with no personal reference — details under “Counting without tracking” below.

Please only enter a first name, and nothing about other people that they would not want on a shared page.

Why

To run the potluck list you asked for (Art. 6 (1) (b) and (f) GDPR — performing the service you requested and our legitimate interest in operating it).

How long

Every event is deleted automatically 30 days after its date — including all entries and log records. A daily job does this; there is no archive and no backup copy that outlives it. Two things do not belong to an event: feedback has its own period of 180 days (see below), and the anonymous counters are kept indefinitely — they contain nothing that leads to a person, and therefore nothing that would have to be deleted (see “Counting without tracking”).

Feedback

The “Feedback” link in the footer lets you write to us from any page — typed or spoken. What we then store:

• your text and, if you recorded one, your voice message;
• the page you opened the form from: its path, the page pattern, and the event and entry id if the page belonged to a potluck. That is the whole point — without it, “the button was hard to find” cannot be placed. The rest of the address bar is not stored: neither the secret links (edit tokens) nor the draft values from the sign-up form;
• the time, the language and the app version;
• your email address, if you give one.

Legal basis. Text and page context: our legitimate interest in improving the service (Art. 6 (1) (f) GDPR). Voice message and email address are explicitly optional — sending them is your consent to processing them (Art. 6 (1) (a) GDPR). The form works just as well without either.

Voice message. Recording only starts once you press the record button and your browser has additionally asked you for microphone permission. You can listen to the recording and discard it before sending. It stays on our server in the EU, is listened to by us rather than transcribed automatically, goes to no speech service, and is never used to recognise you by your voice.

Email address. Used for exactly one thing: replying to this piece of feedback. No advertising, no newsletter, never passed on, no recognition across visits.

Contact by email. Email sent to any address @wasbringich.de (for example kontakt@wasbringich.de) is handled in the same feedback workflow and stored in full for that purpose — including its technical headers (sender, recipient, time, message id), so that later on it remains verifiable who wrote what and when, and what we replied. Replies go to your sender address and are archived the same way. Legal basis: handling your request (Art. 6 (1) (b) and (f) GDPR). The same 180-day period applies — the email, the conversation and the archive are deleted automatically.

Withdrawal and deletion. You can withdraw your consent at any time with effect for the future and ask us to delete your feedback — an informal email to kontakt@wasbringich.de is enough. Processing that happened before the withdrawal stays lawful.

What comes of it. Changes that grow out of feedback are listed under Changes. That page says what changed and since when — nothing about the person: no text from the form, no address, no date of arrival, and not how many people reported the same thing.

Period. Feedback is deleted automatically 180 days after it arrives, together with the voice message and the email address.

Cookies and tracking

None. No cookies at all, no analytics service, no external fonts, no CDN. The protection against cross-site form submissions uses a signed token inside the form itself, not a cookie. Nothing about you is passed to a third party, and nothing recognises you across visits — not between two pages, not between two days, not between two devices.

Counting without tracking

We do count. We want to know which pages are used, which recipes people actually cook, and how often someone went from here to one of the linked recipe blogs — that last number is the only thing those blogs get from us, and we would like to be able to tell them.

What that looks like. Every hour there is a row saying, for example: “between 20:00 and 21:00, the suggestions page was opened 14 times in German”, or “recipe X was clicked 3 times, target eat-this.org”. When an event expires we additionally note its size as a range (“6–9 entries”) before it is deleted. That is all: a time slot, a few labels from fixed lists, a number.

What is deliberately not in there. No IP address, no user agent, no cookie, no device or session identifier, no event id, no entry id, no first name, no dish, no free text, no exact address you clicked — only the domain. There is no identifier of any kind, so two counted events cannot be joined into anyone's path through the site. Nothing in that table refers to a person, not even indirectly.

Which is why it is kept. Anonymous data is not personal data (recital 26 GDPR): there is nobody it could be deleted for. So these counters are not covered by the 30-day period and are kept indefinitely — they are what makes a comparison over months possible in the first place. Everything that does relate to a person still disappears on schedule, and that is precisely why the counters had to be built this way.

Recipe links go through us. A link to a recipe first goes to an address on this site, which counts the click and forwards you immediately. Nothing is stored about you in the process, and the page you land on is exactly the one shown on the link. We still send no referrer.

Programs are not counted. The user agent is read to tell a browser from a crawler — the WhatsApp link preview fetches every shared page — and is then discarded. It is stored nowhere.

Server logs

The web server logs technical request data (including IP address) for a short time to keep the service secure and working. These logs are not merged with event data.

External links

Recipe links point to third-party sites (for example eat-this.org, veganheaven.de, biancazapatka.com, zuckerjagdwurst.com). If you follow such a link, the site you land on receives your request; its own privacy policy applies. In the English interface the "Google Translate" link sends the recipe address to Google Translate — only if you click it. We send no referrer with these links.

Your rights

You may ask for access, correction, deletion, restriction, objection and data portability, and complain to a supervisory authority. In practice: everyone can delete their own entry with their personal edit link, and the organiser can delete the whole event at any time with the edit link. If you have lost the link, write to kontakt@wasbringich.de.

Hosting

The app runs on a server in the EU. Data is not passed to third parties.