Privacy Policy

If you're a chef using ChefSpot

• · Your account email and password. Passwords are handled by our authentication provider (Supabase) — we never see or store your password in plain text.
• · The profile details you add: display name, bio, headshot, location, timezone, cuisines, and social links.
• · Menus and photos you upload.
• · The payment contact details you choose to display to your own clients — for example a PayPal email, Wise handle, or bank transfer instructions. This is information you're choosing to publish so clients can pay you directly; ChefSpot never processes or touches that money.
• · Your subscription plan and status, and a customer ID from our payment processor, Polar — see “Who we share it with” below.
• · Your custom domain, if you connect one on the Pro plan.

If you're a client contacting or booking a chef

Clients don't need a ChefSpot account. When you submit an inquiry or booking request, we collect your name, email, phone (if you provide it), event date and time, guest count, budget, and any message you write — and pass it directly to the chef you contacted. Afterward, you access your booking through a private link sent to your email, not a login.

Collected automatically

• · When someone visits a public chef profile, we record a country code (derived from network location, not your IP address) and the domain that referred the visit — used only to power that chef's own analytics dashboard.
• · To prevent abuse of public inquiry and booking forms, we rate-limit by IP address. That IP is cryptographically hashed with a secret salt before storage — we don't keep a plain log of who submitted from where.

How we use it

• · To operate your profile, menus, bookings, and inquiries as you've set them up
• · To send transactional emails — booking updates, inquiry alerts, password resets, subscription receipts
• · To process Pro subscription payments
• · To prevent spam and abuse on public forms
• · To respond when you contact support

We don't sell your data, and we don't use tracking pixels or ad networks.

Who we share it with

• · Supabase — our database, authentication, and file storage provider
• · Polar — processes ChefSpot subscription payments as our merchant of record. Polar handles your card details directly; we never see or store your card number.
• · Resend — delivers our transactional emails
• · Upstash — rate-limiting infrastructure; only ever receives the hashed, salted version of an IP, never the IP itself
• · Vercel — hosts the application and, for Pro custom domains, routes your traffic

None of these providers may use your data for their own purposes beyond providing their service to us.

If you're a chef receiving client data

Inquiry and booking details your clients submit are shared with you so you can run your business. You're responsible for handling that information appropriately once it reaches you — for example, not sharing a client's contact details elsewhere without their consent.

Cookies

We use only strictly necessary cookies to keep you signed in, set by our authentication provider. We don't use advertising or cross-site tracking cookies.

Your rights

• · You can edit or remove most of your profile, menu, and photo information directly from your dashboard at any time.
• · To request a copy of your data or full account deletion, email hello@chefspot.pro — we'll respond within 30 days.
• · Depending on where you live, you may have additional rights under laws like the GDPR or CCPA — including access, correction, portability, deletion, and opting out of the sale of personal data (we don't sell data to begin with). Contact us to exercise any of these.

Changes to this policy

If we make a meaningful change to this policy, we'll notify you by email before it takes effect.

Contact

Questions about this policy? Email hello@chefspot.pro. A human will reply.