Privacy Policy

When you create an account: your name, email address, phone number and a password we store only as a hash — we never hold your actual password and cannot recover it. If you sign in with Google or Apple we receive your name and email from them instead.

When you request a chef: the address the event is at, the date and time, how many guests, the occasion, any cuisines you prefer, and — importantly — any dietary requirements and free-text notes you write. Your address is geocoded to coordinates so we can find chefs who actually cover it.

When you pay: we store the amount, the fee breakdown, and the card brand and last four digits so you can recognise the card later. We never see or store your full card number. That goes directly to Stripe, our payment processor.

When you message a chef: the contents of those messages, so both of you keep a record of what was agreed.

Only the chefs your request is actually sent to, and contact details are withheld until a booking is paid for. Before that point, chefs quoting on your event see what they need to quote — the area, the date, the headcount, your dietary needs — not your street address or your phone number. This is deliberate: a request that has not become a booking should not hand your home address to several strangers.

We use a small number of processors, each for one job, and none of them are sold your data:

• Stripe — payments, refunds and chef payouts. Stripe holds card details; we do not.
• Resend — transactional email (booking confirmations, receipts, password resets).
• Twilio — text messages about a booking, where enabled.
• Cloudflare R2 — storage for photos you or a chef upload.
• Google Maps — turning an address into coordinates and a timezone.
• PostHog — product analytics. We deliberately send only account identifiers and facts about events (for example “a booking was requested”). No name, email, phone number or address is ever sent to our analytics. Session recording is switched off in code, not merely unticked in a dashboard.

We do not sell your personal information. We do not resell your booking request as a lead to anyone who did not receive it through the platform. We do not run advertising trackers on this site.

Account and booking records are kept while your account is open, and after closure for as long as we need them for tax, accounting and dispute records — a card payment can be disputed with the cardholder’s bank for around 120 days, and financial records are generally kept for seven years. Messages tied to a booking are kept with that booking.

You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete your account and personal data. Some records we must keep even then — a completed payment cannot simply be erased from the accounts — but we will tell you specifically what is retained and why, rather than refusing in general terms. Email us at the address below and we will respond within 30 days.

We use cookies to keep you signed in and to keep your session secure. Our analytics sets a cookie to recognise a returning visitor. We do not use advertising or cross-site tracking cookies.

ChefLynk is not intended for anyone under 18, and we do not knowingly collect information from children.

Questions, requests or complaints about privacy: support@cheflynk.com.