Yes Chef AI · Legal
Cookie Policy
What cookies and similar technologies Yes Chef AI uses, based on a current inspection of the public site and the logged-in application.
1. What this policy covers
This policy explains cookies and similar technologies (including localStorage and sessionStorage) used on the public Yes Chef AI website and in the logged-in Yes Chef AI application. It should be read with the Privacy Policy.
Under the Privacy and Electronic Communications Regulations, we must tell you about cookies and, except where an exemption applies, obtain consent before storing or accessing information on your device. An exemption applies where the technology is strictly necessary to provide a service you have requested, or is solely for carrying a communication over an electronic communications network.
2. Public website (yeschefai.co.uk)
On 23 August 2026 we loaded the public home, plans, contact, terms, privacy and cookies pages in a browser. The browser reported:
- no cookies set;
- no localStorage keys;
- no sessionStorage keys; and
- only first-party scripts needed to operate the header, product story film and image lightbox.
Email links on the public site open the visitor's own email application. They do not set a Yes Chef AI cookie. The public site does not currently use Google Analytics, advertising pixels or similar non-essential trackers.
Because the public site does not set non-essential cookies, PECR does not currently require a consent banner for this website. If we add non-essential analytics or advertising technologies, we will update this policy and provide a consent mechanism before they are used.
3. Logged-in application
The application hosted at kitchen-pro-kappa.vercel.app (and any successor production host) uses strictly necessary cookies and similar technologies to sign users in, keep a session, apply access controls and remember settings the user has requested. Those technologies are needed to provide the online service the user has asked for. They are not used for advertising, and they are not offered as an opt-out while the user remains signed in.
Cookies used by the application
| Name | Purpose | Party | Duration | Classification |
|---|---|---|---|---|
kp_tenant_id | Identifies the signed-in organisation so the application can load the correct tenant | First party | 7 days | Strictly necessary |
kp_user_id | Identifies the signed-in user for admission to the application | First party | 7 days | Strictly necessary |
kp_role | Stores the user's role so the application can apply access rules | First party | 7 days | Strictly necessary |
kp_site_id | Stores the selected site/venue context | First party | 7 days | Strictly necessary |
kp_theme | Remembers a light or dark theme the user has chosen | First party | 1 year | Strictly necessary (user-requested interface setting) |
| Supabase authentication cookies | Maintain the authentication session with our authentication provider | First party (set for the application host) | Session or provider-defined | Strictly necessary |
The kp_* admission cookies are HttpOnly, use SameSite=Lax, and are
marked Secure in production. Exact Supabase cookie names depend on the authentication
project configuration.
Local and session storage used by the application
| Technology | Purpose | Party | Duration | Classification |
|---|---|---|---|---|
sessionStorage key yeschef-legal-acceptance | Temporarily holds Terms and Privacy acceptance details between signup and onboarding | First party | Until onboarding completes or the tab session ends | Strictly necessary |
| localStorage locale keys | Remembers a language/locale the user has selected | First party | Until cleared by the user or the application | Strictly necessary (user-requested interface setting) |
| Due-diligence PWA localStorage | Stores tenant, site, device identifier and related offline-session data so the requested offline due-diligence tools can work | First party | Until cleared by the user or the application | Strictly necessary for the requested offline feature |
4. Browser controls
Most browsers allow you to block or delete cookies and site data. Blocking strictly necessary cookies or storage will prevent sign-in and other requested application features from working correctly. Blocking cookies on the public website should not stop you reading these pages, because the public website does not currently depend on cookies.
5. Changes
If we change the technologies described here, we will update this policy. If we introduce non-essential analytics or advertising cookies, we will request consent where PECR requires it before those technologies are used.
6. Contact
Questions about cookies can be sent to hello@yeschefai.co.uk.
Company details
Yes Chef AI Ltd
Registered in England and Wales
Company no. 17117657
Registered office: 71–75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ
hello@yeschefai.co.uk