Privacy

Draft — awaiting owner approval

Short version: we keep what an event needs, show each person only what they should see, delete it on a schedule, and do not run ads or trackers.

What we store

Event details: title, date, time, place, notes, look, courses and an optional password (stored hashed).
Your email, as host, so we can send your private host link. Stripe sends your payment receipt to the same address.
Guest sign-ups: the name, number of people, and any dietary needs or notes a guest enters.
Dish information: names, notes, labels and any photos guests upload.
A hashed form of IP addresses and emails (not the raw values), used only to limit abuse such as repeated event creation or password guessing.

Anyone with the guest link (and password, if set) sees the event, who is coming, dishes and photos.
Dietary needs are shown to guests only as counts. The names are visible to the host only.
Your email and host link are visible to you only. Payment details are handled by Stripe; we never see your card number.

Unpaid drafts: deleted after 7 days.
Paid events, including sign-ups and photos: deleted 30 days after the event date.
Abuse-limiting records: deleted automatically within about two days.

Supabase: database and photo storage.
Vercel: hosting.
Stripe: payments.
Google Fonts: pages load their typefaces from Google, so your browser contacts Google's servers (which see your IP address) when you open one.
An email provider, to be chosen, for sending host links.

None. We do not show ads, sell data, or use analytics or tracking cookies. We set only the cookies needed to make the site work:

A guest cookie that lets you edit your own sign-ups from this browser.
One cookie per password-protected event you unlocked, so you don't have to type the password again.
One cookie per event you host, so this browser can show you every photo on it, including ones hidden after a report.
An owner cookie, only for the site operator, for reviewing reported photos.

Questions? See the FAQ.