Back

Privacy policy

The short version: we collect what we need to seat you, feed you and find you a bed; we share it with the people running the weekend; and we delete all of it afterwards. No tracking, no analytics, no cookies. The long version follows.

Who is responsible

Korbinian Weidinger, Kellerstraße 33, 81667 München, for both of us. Any question about your data, and any of the requests further down, goes to korbi.weidinger2@gmail.com. One email is enough — there is no form to fill in.

When you simply visit

Our host, Vercel, writes a log entry for every request: your IP address, the time, which page you asked for, your browser and operating system, and the page you came from. That is how the site reaches you and how we would notice an attack. We don't read those logs for entertainment, we don't join them to your reply, and they aren't used to recognise you later.

Nothing else happens while you read. No analytics, no tracking pixel, no advertising, no social buttons, no map or video embedded from somebody else's server. Even the fonts come from our own domain instead of from Google. Legal basis: Art. 6(1)(f) GDPR — our interest in a site that works and stays standing.

Cookies, and why there's no banner

We set no cookies. None at all.

When you type in your invitation code, your browser keeps it in local storage so you don't have to type it again on every page. It stays on your device, and “Sign out” deletes it. Keeping it there is strictly necessary to show you the invitation you asked for — precisely the case that § 25(2) no. 2 TDDDG exempts from consent. So there's no banner: not as a shortcut, but because there's nothing to ask you about.

When you send your reply

All of this you typed in yourself, on the RSVP page:

  • Names — First and last name of everyone on your invitation, so we know who's coming and whose name goes on which place card.
  • Age group — Adult, teen, child or baby. It decides the room plan, the menu, and who pays for a bed.
  • Which events — Whether you're joining the Friday welcome dinner and the Sunday farewell brunch, so the kitchen cooks the right number of plates.
  • Languages you speak — For the seating plan, so nobody spends an evening unable to talk to their neighbours.
  • Diet — Omnivore, vegetarian, vegan, pescatarian or something else — for the caterer.
  • Allergies and intolerances — Optional, and handled separately. See the next section.
  • Your postal address — So we can send you the printed invitation and anything else that needs a stamp.
  • Your invitation code — It identifies your household and it's how you reach the guest area. We made it up; you didn't give it to us.
  • When you replied — The time of your first reply, so we know who still needs a nudge.

We also note by hand whether the payment for your room has arrived — and that is the entire list, with no hidden fields. The legal basis is Art. 6(1)(f) GDPR: we invited you, and we have an obvious interest in organising our own wedding properly. None of it is used for anything else, ever.

Allergies, diet and your health

Allergies and intolerances say something about your health, and the GDPR guards that more closely than the rest (Art. 9). So the field is optional, and nothing about your reply depends on it.

If you do fill it in, you give us your explicit consent (Art. 9(2)(a) GDPR) to pass it to the venue and the kitchen, for the single purpose of not making you ill. Nothing else. You can take that back whenever you like: clear the field and send your reply again, or write to korbi.weidinger2@gmail.com. Do it early if it matters — once the kitchen is holding a printed list, we can't unprint it.

If your diet is a choice rather than a medical matter, just pick it under “Diet” and leave the allergy field empty. The kitchen gets what it needs either way.

Who else sees it

Only the people actually running the weekend:

  • Our wedding planner — Vanessa of Marry Me in Umbria, in Italy. She holds the guest list, the room plan and the catering notes, because she's the one who turns them into a wedding.
  • The venue — Borgo Colognola, in Italy: names and the room plan, so there's a bed with your name on it.
  • The caterer — Headcount, diets and allergies — usually as a kitchen list, without the rest of your details attached.
  • Our hosts — Supabase stores the database, Vercel serves the site. They hold the data on our instructions and make no use of it themselves.

Nobody else. We sell nothing, we publish no guest list on this site, and the guest area opens only with an invitation code. What we have with our planner is a spoken agreement rather than a signed contract: the data goes no further than the people who need it for the weekend. With Vercel and Supabase we rely on their standard data processing terms.

Where it's stored

The database sits in the European Union (Supabase, EU region). Our planner, the venue and the caterer are in Italy, so inside the EU as well.

Vercel, who serve the site, are a US company. The site itself is delivered from their European locations, but for operations and server logs access from the United States can't be ruled out. That case is covered by the EU standard contractual clauses in Vercel's data processing terms.

How long we keep it

Until the wedding has happened and the last bill is settled — then it goes. Concretely: everything described above is deleted from the database by December 31, 2027.

Want yours gone sooner? Write to korbi.weidinger2@gmail.com and we'll delete your household's entry. Fair warning: do it before the wedding and we'll have to come back and ask you the same questions by hand.

Your rights

The GDPR gives you every one of these, and you never need a reason to use them:

  • Ask what we hold about you and get a copy (Art. 15).
  • Have it corrected if we've got something wrong (Art. 16).
  • Have it deleted (Art. 17), or restricted to mere storage (Art. 18).
  • Receive it in a portable file (Art. 20).
  • Object to the processing we base on legitimate interest (Art. 21).
  • Withdraw your consent for the allergy data at any time (Art. 7(3)). What happened before stays lawful, but it stops there.

An email to korbi.weidinger2@gmail.com is all it takes, and we'll answer well within a month. If you'd rather complain to someone official, the authority responsible for us is the Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Ansbach.

Links that leave this site

We link to the Borgo, to our planner, and to Google Maps. Those are plain links: nothing loads from them until you click, and once you have, that site decides what it collects. Their privacy policy applies there, not ours.

Changes

If this site ever grows a feature that needs more than the above, we'll rewrite this page and change the date at the top. We won't quietly start collecting something new.

Last updated November 2026.