Personal Chef FinderCookie Policy
Last updated: August 16, 2026
This page explains how Personal Chef Finder, operated by PersonalChefApps, LLC, uses cookies and similar technologies. Personal Chef Finder uses necessary cookies only. We do not use PostHog, Google Ads, Meta Pixel, or other optional analytics or advertising cookies on this site.
Chef membership lives on Cookday Recipe Manager (Cookday). Cookday has its own cookie settings, described in Cookday’s Cookie Policy.
Categories
Necessary
Required for chef sign-in, security, and core features such as the map. These cannot be turned off if you use those features.
Analytics and marketing
We do not set analytics or marketing cookies on Personal Chef Finder. There is no cookie banner on this site because there is nothing optional to accept or decline here.
Cookies and storage we use
The table below describes the main technologies. Exact cookie names may change when we update the service.
| Name / key | Type | Provider | Purpose | Category |
|---|---|---|---|---|
| Auth session | Cookie | Neon Auth | Keep chefs signed in (shared with Cookday) | Necessary |
| Cloudflare Turnstile | Challenge / similar | Cloudflare | Bot checks on contact and request forms | Necessary |
| Mapbox | Cookie / local storage | Mapbox | Map tiles and geocoding for the directory map | Necessary |
First-party directory metrics
Separately from browser cookies, this site records listing events (such as profile views and contact clicks) on our own servers so chefs can see dashboard metrics. That is first-party operational data. It is not sent to PostHog, Google, or Meta.
Changes
If we later add optional analytics or advertising cookies, we will update this policy and ask for consent before those tools run. See also our Privacy Policy.