Privacy notice

Last updated 16 November 2026

The short version: we collect what it takes to run your event, guests' dietary needs are shown only to their host, we never sell data, and the one third-party script on this site loads only if you say yes.

1. Who we are

DishDibs (dishdibs.app) is run by a sole proprietor, who is the controller of your personal data:

  • Name: [TODO: owner's full legal name and trading name]
  • Address: [TODO: registered business address]
  • Registration number: [TODO: sole-proprietorship registration number]
  • Tax or VAT number: [TODO: tax / VAT number]
  • Email: [TODO: privacy contact address, e.g. privacy@dishdibs.app, and confirm it exists]

We have not appointed a data protection officer. [TODO: confirm none is required: dietary and allergy data is health data, so check GDPR Art. 37(1)(c)]

2. What we collect

Hosts (people who plan an event) give us:

  • an email address, to sign in with a link;
  • a name, if they add one;
  • event details: title, type, date and time, place, notes, budget, the dishes and things needed, and expenses;
  • billing details, handled by Stripe. We never see or store card numbers. We keep the Stripe customer and subscription IDs, your plan, its status and renewal date.

Guests (people who open an invite link) give us, without an account:

  • a name, and an email address only if they choose to;
  • their answer (coming, maybe, can't go) and how many people they bring;
  • dietary needs and allergies, and any note they add;
  • what they are bringing, an optional note and what it cost.

Dietary and allergy information is sensitive. Allergies are health information, and some diets (such as halal or kosher) can reveal religious beliefs. We treat all of it as special category data:

  • it is optional; leave it blank if you prefer;
  • it is used only to run that one event;
  • it is visible to the host of that event and to nobody else. Other guests do not see it. [TODO: confirm with the guest flow (WO-06) exactly what other guests can see]
  • it is never used for marketing, advertising or profiling, and never sold;
  • it is deleted when the event is deleted.

Everyone: when you visit, Cloudflare (our host) handles your IP address and browser details to deliver the page and protect it from abuse. We use your IP address briefly to limit how fast forms can be sent; we do not store it in our database. [TODO: state how long rate-limit counters keyed on IP are kept]

3. Why we use it, and on what legal basis

  • Running DishDibs for hosts
    Data
    Account, events, items, expenses
    Basis
    Our contract with you (GDPR Art. 6(1)(b))
  • Running an event for its guests
    Data
    Name, answer, what you bring, costs
    Basis
    Legitimate interest of the host and of us in organising the event you were invited to (Art. 6(1)(f))
  • Dietary needs and allergies
    Data
    Dietary tags and notes
    Basis
    Your explicit consent, given by choosing to enter them (Art. 9(2)(a)). You can remove them at any time. [TODO: confirm the guest form asks for this clearly]
  • Payments and accounting
    Data
    Plan, billing records, invoices
    Basis
    Contract, and our legal duty to keep accounts (Art. 6(1)(b) and (c))
  • Security and abuse prevention
    Data
    IP address (briefly), request details
    Basis
    Legitimate interest in keeping DishDibs safe (Art. 6(1)(f))
  • Hackathon traffic verification
    Data
    See section 5
    Basis
    Your consent (Art. 6(1)(a)), only if you click Accept
  • Recording your cookie choice
    Data
    Anonymous ID, choice, policy version, time
    Basis
    Our legal duty to show consent was given (Art. 6(1)(c), Art. 7(1))

4. Cookies

We set only the cookies DishDibs needs to work. They are first-party (set by dishdibs.app), strictly necessary, and need no consent. We set no analytics or advertising cookies.

  • dd_consent
    Purpose
    Remembers whether you accepted or rejected the hackathon script
    Holds
    Your choice, the policy version and a random ID that is not linked to you
    Lasts
    180 days, then we ask again
  • Host session [TODO: cookie name, set by the sign-in work order (WO-03)]
    Purpose
    Keeps a host signed in
    Holds
    A random session token
    Lasts
    Until you sign out, or [TODO: session lifetime]
  • Guest edit token [TODO: cookie name, set by the guest work order (WO-06)]
    Purpose
    Lets a guest change their answers later on the same device
    Holds
    A random token for that one invite
    Lasts
    [TODO: lifetime, e.g. until 30 days after the event]

When you pay, Stripe's checkout pages (on stripe.com) set their own cookies, covered by Stripe's privacy policy.

5. The hackathon verification script

DishDibs is an entry in the Ship or Die $100K Hackathon, which ranks entries by profit. The organisers ask every entry to run a small script, verify.js, from Ship or Die (www.ship-or-die.com). It lets them check that the traffic and revenue an entry reports are real.

  • verify.js by Ship or Die
    Provider
    Ship or Die, organiser of the Ship or Die $100K Hackathon. [TODO: provider's legal name, address and privacy notice link]
    Purpose
    Verifying hackathon traffic and revenue
    Sends
    The page path you visit, the website you came from (its domain only), the utm_source and utm_medium in the link, and whether you arrived from a paid ad click
    Also receives
    Like any web request: your IP address and browser details
    Cookies
    None. It stores nothing on your device
    Loads
    Only after you click Accept

It does not load if you click Reject, if you ignore the banner, or if your browser sends Global Privacy Control or Do Not Track (unless you then choose Accept yourself). Nothing is sent to Ship or Die before you accept.

To withdraw your consent, use here or “Cookie settings” at the bottom of any page, then Reject. The page reloads without the script. Withdrawing does not affect what was sent before.

[TODO: where Ship or Die stores this data and for how long]

6. Who else handles your data

These companies process data for us, under contract and only on our instructions:

  • Cloudflare
    Does
    Hosting, database, network and security
    Where
    Worldwide, including the US
  • Stripe
    Does
    Payments, subscriptions, invoices
    Where
    EU and US. Stripe is also a separate controller for some payment data, under its own privacy policy
  • Email provider [TODO: name the provider once chosen]
    Does
    Sends sign-in links and event emails
    Where
    [TODO: location]

Ship or Die receives data only with your consent (section 5) and is not our processor. Hosts see their guests' answers; that is the point of the service.

Where data leaves the EU, we rely on the EU–US Data Privacy Framework or the European Commission's standard contractual clauses. [TODO: check each provider's transfer mechanism and data processing agreement]

[TODO: if AI menu suggestions ship, add the AI provider here before launch and say that guest text is sent to it]

7. How long we keep it

  • Events, guests' answers and dietary information: until the host deletes the event or their account, then deleted together. [TODO: decide an automatic deletion period, e.g. 90 days after the event]
  • Host accounts: until you delete your account.
  • Billing records: as long as accounting law requires. [TODO: period under the owner's national law, e.g. 8 years]
  • Cookie choices (consent log): as long as we need to show consent was given. [TODO: period, e.g. 3 years after the choice]
  • Server and security logs: kept by Cloudflare for a short time under its own policy.

8. Your rights

You can ask us to:

  • show you the data we hold about you, and give you a copy;
  • correct it;
  • delete it;
  • restrict how we use it, or object to how we use it;
  • send it to you or another service in a common format.

You can withdraw consent at any time: for dietary information by removing it, for the hackathon script with .

Deletion: hosts can delete an event, which deletes its guests' answers and dietary information, or their whole account. [TODO: confirm account deletion exists in the app before launch] Guests can change or clear their answers from their invite link, ask the host, or email us.

Email us at the address in section 1. We answer within one month. You can also complain to a data protection authority, for example the one where you live. [TODO: name the owner's lead supervisory authority]

9. Children

Hosts must be adults. Guests under 16 should fill in an invite with a parent or guardian. [TODO: confirm the age threshold for the owner's country]

10. Changes to this notice

If we change what the hackathon script does or add another one, we ask for your consent again. This notice is version 2026-11-16.