Privacy
What Chef Connect keeps, who sees it, and for how long
This page says what Chef Connect keeps about you, who sees it, where it lives and how long it stays. It was written by reading the code and the database that run the site, not by filling in a template, so it describes what the site does today. Where a sentence is a promise rather than a description, it is short, and a lawyer will review it before this page is final.
At a glance
- No analytics, no advertising, no tracking pixels.
- We do not sell your personal information, and we do not use it for targeted advertising.
- Card details go to Stripe, in Stripe's own form, and never reach our servers.
- Your allergies and diets for a dinner are seen by that dinner's host and chef, once you have a seat.
- A host's street address is kept apart; a guest sees it only with a paid, confirmed seat, once the host has released it for that dinner.
- Ask for a copy of what we hold, a correction, or deletion: daolnwod.tcennocfehc@kcaz. A person does it by hand.
Who we are
Chef Connect (a working name) is run by Vornehm LLC, 2122 snekciD ,evA ettolrahC CN 80282. It is a website, chefconnect.download, where chefs cook private dinners in hosts' homes for guests who take a seat. Joining is by invitation, and only for people 18 or older.
What we keep, and why
You sign in with your Google account, and joining with an invitation code makes your account. From then on the site keeps what you give it to run your account and your dinners. It keeps no history of the pages you look at.
- Your account. Your first and last name, as you type them when you join; the time you confirmed you are 18 or older; the invitation that admitted you; your membership level and its history; a phone number for the day of a dinner, if you give one; and a profile picture, if you add one.
- Your email address. Sign-in goes through Supabase's sign-in service, which keeps your email address with your sign-in. Our own account table holds no email address: the site reads it from the sign-in service when it needs it, for example to recognise the founder's account. The site asks Google for no permissions beyond its standard sign-in.
- Your profiles. You add a profile for each role you take: chef, host, guest or vendor. Each keeps what you write in it. A chef's: cuisines, highlights, signature dishes, years cooking, training, diets cooked, seat and price ranges, travel distance, an equipment list, certificates (the number, the expiry date and an optional picture of the card) and links to X, Instagram or TikTok. A host's: hosting style, why they host, household notes, usual house rules and seating preferences. A guest's: a short introduction for the table, drinks answers, accessibility needs, interests, the name of a usual plus-one, a usual photo answer and a ZIP code. A vendor's: business name, category, what they offer, service area, a link, a price range and a permit as they state it.
- Your ZIP code is used only to show how far away a dinner is, measured from the centre of the ZIP area, never from an address.
- Your allergies and dietary restrictions. A guest profile can hold them. When you enter a dinner you confirm or update them, and a copy is kept with that entry, so the dinner is cooked for what you said for that dinner.
- A host's home. A host's venue record holds the seats, the kitchen (hob, burners, ovens, ventilation, electrical limits), household food rules, alcohol, pets, smoking, children in the home, step-free access, public transport and an equipment list. The street address is kept apart, in one table of its own, with a map pin the site finds from it.
- Your dinners. For each dinner you enter: when you entered, which version of the house rules you accepted, your allergies and diets for that dinner, your photo answer for that dinner, and your plus-one if you bring one. When seats are given: the order they were given in and the rule that placed you, your seat, its six-character check-in code and when you checked in.
- Your plus-one. You give their name and an email address or a phone number. Your plus-one answers on a page of their own, with no account: they confirm they are 18 or older, accept the waiver, and give their allergies, diets and photo choice. We keep when they answered, which waiver version they accepted, whether they answered by the link or at the door, and a short description of the browser they used.
- Payments. Card details go to Stripe, in Stripe's own form, and never reach our servers. We keep Stripe's references to your customer record and your saved card, and a record of each hold, charge and refund: the amount, the outcome and Stripe's reference. Chefs and hosts who are paid set up payouts with Stripe; we keep the reference to that Stripe account.
- Messages and reports. What you write in a dinner's conversation, how far you have read it, and any report you make: of a message, or of a person or a dinner from the Help page.
- Goods sold through the site. If a chef or host sells goods: each product's name, text, price and picture. If you buy: the order, and the name and address you give when it ships.
- A chef's own tools. A chef's recipes and menus.
- Your answers to our texts. Each time you accept or decline one of our texts (a waiver, a home's house rules, saving a card, a host's release of the address), we keep which version, whether you said yes, and when.
- Notices. The notices the site shows you: what kind, which dinner, and when you read it. A notice never holds an address or the words of a message.
- A log of actions. Which account did what, to what, and when. It is added to and never edited.
What we do not do
- No analytics, no advertising, no tracking pixels. The site's code has none. The only scripts it loads from anyone else are Stripe's, on the pages where you enter a card or set up payouts, and Cloudflare's bot check, on the joining pages. The typefaces are served from the site itself.
- No selling. We do not sell your personal information, and we do not use it for targeted advertising.
- No IP address in our database. When you join, the site passes your IP address to Cloudflare's bot check so it can tell a person from a program; our database keeps no IP address.
- No email today. The site is built to send some notices and messages by email, through Resend, but that is switched off, so no email leaves the site now. It sends no text messages: if your plus-one's contact is a phone number, your booking page offers to open a text on your own phone.
- No search engines. Every page asks search engines not to list it.
Who sees what, and when
| What | Who sees it | When |
|---|---|---|
| Your allergies and diets for a dinner, and your plus-one's | That dinner's host and chef | Once you have a seat |
| Your table introduction, drinks answers, accessibility needs and interests | That dinner's host and chef | Once you have a seat |
| Your phone number, as a guest | That dinner's host and chef | Only for a paid seat, once the dinner is booked to go ahead |
| Your phone number, as a vendor on a dinner | That dinner's host and chef | Once the dinner is booked to go ahead |
| Your plus-one's email or phone | Never a host or a chef | |
| A host's street address and map pin | The host; a chef the host has accepted; guests with a paid, confirmed seat; the people who run Chef Connect | Guests: at the host's reveal time, once the host has released it for that dinner |
| Where a dinner is, before that | Anyone who can see the dinner | The neighbourhood's name and a circle on the map whose centre is drawn 1 to 5 miles from the home |
| Children in a host's home, and the public transport detail | The host, and a chef the host has accepted; for the transport detail, also guests with a paid, confirmed seat, after the reveal | |
| A chef's profile | Signed-in members; visitors who are not signed in only if the founder opens chef pages to them | |
| A certificate's card picture | The chef, and the people who run Chef Connect | Never on a public page |
| A chef's recipes and menus | That chef alone | |
| Messages | The people in that dinner's conversation | The founder reads a conversation only when a member reports it |
| The name and address for an order that ships | The seller of that order |
The people who run Chef Connect see account records to admit people and run the service.
Where it lives
- Vercel runs the site.
- Supabase holds the database and the sign-in service, in a United States region, and starts the site's timed job every five minutes.
- Google handles sign-in. Our own mailbox, at chefconnect.download, is Google Workspace.
- Stripe holds cards and runs payments and payouts.
- Cloudflare stores the pictures and the map's files, and runs the bot check on the joining pages.
- The US Census Bureau's address lookup receives a host's address from our server each time the host saves it, to place the home on the map.
- Resend will carry the site's email once it is switched on.
These companies run the machines and keep their own records under their own policies. This page speaks for the site, not for them.
How long we keep it
- While your account is open. The site has no way yet to close an account by itself, so what is listed above stays while your account exists. Write to us to ask for a copy of what we hold, a correction, or your account and what it holds to be deleted; a person does it by hand.
- Your plus-one's allergies, diets, contact and photo choice are cleared automatically 120 days after the dinner ends. Their name and the record that they accepted the waiver stay.
- Pictures. When you replace or remove a picture (your own, a dinner's, a certificate card or a product), the old file is deleted from storage.
- Certificates, recipes and menus. Removing a certificate deletes it and its card picture. A chef who deletes a recipe or a menu deletes it.
- Your profile. A field you clear is gone from your profile. The allergies and diets you confirmed for a dinner you entered stay with that entry.
- Conversations. A conversation that a member blocks is closed: nobody can post in it, and its words stay readable to its members.
What Stripe, Supabase, Google and Cloudflare keep in their own systems follows their own rules.
Your choices
- Change or clear what your profiles say, and change your name, at any time. You confirm your allergies and diets each time you enter a dinner.
- Add, replace or remove your picture.
- Choose, each time you enter a dinner, whether you are happy to appear in photos taken at it.
- Remove a saved card on the Cards page; it is removed at Stripe too.
- Block a conversation, report a message, or report a person or a dinner from the Help page.
- Ask for a copy of what we hold, a correction, or deletion, at the address below.
- Depending on where you live, the law may give you more rights over your data. Write to us and we will help.
Children
Chef Connect is for people 18 and older. Joining asks you to confirm it, and a plus-one confirms it too. We do not knowingly keep data about anyone younger; tell us if you think we do, and we will remove it.
Security
Card details stay with Stripe. A host's street address is kept apart and shown only as the table above says. Sign-in cookies cannot be read by scripts on the page, and the site tells browsers to reach it only over HTTPS. No system is perfectly secure: if your account seems at risk, tell us at once.
When this page changes
The date at the top moves when the words change. If the site starts keeping something this page does not mention, this page changes with it.
Reach us
Vornehm LLC, 2122 snekciD ,evA ettolrahC CN 80282.
Email daolnwod.tcennocfehc@kcaz, or use the Help page. A person reads it, and a person answers.