Cookie Policy
This policy explains the cookies and browser-storage technologies used on the Vital Kitchen Lab website, why they are used and how you can manage your preferences.
1. Purpose and scope
This Cookie Policy describes how Vital Kitchen Lab uses cookies, local storage and similar technologies on freshtableacademy.sg. It applies to pages delivered by Vital Kitchen Lab and to the preference controls included in this website. A third-party website reached through a link may use its own technologies under its own policy.
We use the term “cookie” broadly in this document where convenient, but distinguish between a traditional cookie and browser local storage where the distinction matters. The initial website build supplied with this project uses browser local storage to remember the visitor’s cookie-banner choice. It does not, by itself, activate advertising trackers or an analytics library. If the deployed website later adds optional analytics, embedded video, chat, advertising or another third-party service, the live policy and consent implementation should be updated before that technology is enabled.
2. What cookies and similar technologies are
A cookie is a small text file that a website or related service places on a browser or device. It may contain an identifier, preference or limited technical information. Some cookies last only for a browser session and are removed when the browser closes. Others remain until a defined expiry, deletion by the user or replacement by the service.
Local storage is a browser feature that allows a website to save a small key and value on the device. Unlike a traditional cookie, local-storage data is not automatically included with every network request. The Vital Kitchen Lab preference Interface records a value named fta_cookie to remember whether the visitor selected “Accept All”, “Functional” or a customised partial choice. This avoids displaying the banner repeatedly on the same browser unless storage is cleared.
Related technologies can include pixels, software-development kits, device storage, embedded content, server logs and link parameters. Whether information from a technology is personal data depends on what it contains and whether it can identify an individual alone or together with other available information.
3. Categories used by this website
3.1 Strictly necessary technologies
Strictly necessary technologies support a service requested by the user, basic security or operation that cannot reasonably function without them. Examples may include routing a request, remembering a consent decision, protecting a form from misuse, preserving a short-lived session or balancing traffic. The current Vital Kitchen Lab build uses local storage to remember the cookie choice and uses ordinary server processing to receive forms.
Where a technology is genuinely essential, the website may use it without treating the user’s choice as permission for unrelated optional tracking. Essential technologies should be limited to the relevant function and not repurposed for advertising.
3.2 Functional technologies
Functional technologies remember convenience choices, such as display preferences, accessibility settings or a voluntary Interface state. The “Functional” button in the cookie banner records a preference indicating that the visitor wishes to use only necessary and functional storage. The current build does not require a separate functional vendor, but the category is included so the preference model can remain understandable if appropriate features are added.
3.3 Analytics technologies
Analytics may help an organisation understand aggregated page usage, navigation, broad device categories and technical performance. The supplied project does not load an external analytics library. The customised “Partial” preference modal includes an analytics checkbox as an Interface-ready control, but checking it does not create analytics processing unless the site operator separately installs and configures a suitable analytics service.
Before enabling analytics, the operator should assess the provider, information collected, retention, transfer locations, masking options and applicable consent requirements. The cookie inventory below must then be updated with the actual name, provider, purpose and lifespan. Optional analytics should not load before the relevant preference where consent is the selected basis.
3.4 Marketing and advertising technologies
The supplied website does not include behavioural advertising pixels, retargeting scripts or cross-site advertising cookies. Vital Kitchen Lab does not need marketing cookies to receive an ordinary course enquiry or newsletter request. If advertising technology is introduced in the future, it should be categorised separately, described transparently and controlled through an appropriate choice before activation where required.
4. Current technology inventory
| Name | Type | Purpose | Typical duration | Category |
|---|---|---|---|---|
| fta_cookie | Browser local storage | Remembers whether the visitor selected all, functional or partial cookie preferences so the banner need not reappear on every page. | Until the visitor clears site storage or the website changes/removes the value. | Strictly necessary preference record |
| Standard server request logs | Server log, not a browser cookie | Supports security, error investigation, availability and operational diagnostics. Content and retention depend on the hosting configuration. | Limited operational period set by the host or site operator. | Security and operations |
This inventory reflects the generated project at the effective date. Hosting control panels, content-delivery networks or security services may add operational cookies depending on deployment. The site operator should inspect the production website and revise this table whenever infrastructure or third-party scripts change.
5. How the preference banner works
The fixed cookie banner presents three choices. “Accept All” stores a value indicating broad acceptance for categories described and actually implemented. “Functional” stores a value limiting the choice to necessary and functional features. “Partial” opens a preference modal where optional analytics can be selected or left off. The choice is stored locally in the browser.
A stored preference is not a licence to deploy technologies that were not disclosed. If Vital Kitchen Lab introduces a materially different purpose or category, it should refresh the notice and, where appropriate, ask for a new choice. The website should also provide a reasonably accessible way to reopen preferences. In this build, the footer contains a “Cookie preferences” button that opens the modal.
If browser storage is blocked, private browsing is used or site data is deleted, the website may not remember the choice and may display the banner again. Choices apply to the specific browser and device rather than automatically following a person across all devices.
6. Managing cookies through your browser
Most browsers allow users to view, block or delete cookies and site data. Controls are generally found under privacy, security, cookies or site settings. You may be able to block all storage, block third-party storage, clear data for a particular domain or automatically remove data when the browser closes.
Blocking every technology can affect website functions. For this website, clearing local storage removes the remembered cookie preference, so the banner may return. A browser setting may also affect form protection, accessibility preferences or embedded services if those are introduced later. Vital Kitchen Lab cannot control the menus or terminology used by each browser vendor, which may change over time.
Device-level privacy controls, content blockers and network tools can provide additional options. Their behaviour is determined by the relevant provider. Users should choose controls that match their needs and understand that blocking a script may also block content delivered by that script.
7. Third-party content and services
The website loads Tailwind CSS from a content-delivery source and Google Fonts to provide the specified design and typography. When a browser requests a third-party asset, the provider may receive standard network information such as the Internet Protocol address, browser headers and request time. Vital Kitchen Lab does not control the provider’s independent logging practices. A privacy-focused production deployment may instead self-host compiled styles and licensed webfont files, subject to applicable licence terms.
If future pages embed video, maps, social posts, scheduling tools or course-platform widgets, those services may set or read their own cookies. The live site should avoid loading non-essential embeds before the relevant preference where consent is needed. A simple link that opens another website is different from an embedded service that loads inside the page.
8. Personal data and purposes
Cookie and technical data may be personal data where it identifies or can reasonably be linked to an individual. We use such information only for notified and appropriate purposes, such as remembering preferences, protecting forms, maintaining the website, investigating errors, understanding optional aggregated usage and complying with legal obligations. We do not sell cookie-derived personal data to advertisers.
Information collected through an optional service may be processed by a provider acting for us or independently under its own terms. Supplier selection should consider security, retention, access, onward disclosure and overseas transfers. Further information about our general data practices appears in the Privacy Policy.
9. Retention
The local-storage preference remains until it is removed by the user, cleared by the browser, replaced by a later choice or removed by a website update. This persistence is intended to respect the visitor’s choice across sessions. Server logs should be retained for a limited period appropriate to security and operational needs, then deleted or anonymised unless a specific incident, legal obligation or dispute requires longer preservation.
If analytics is added, the operator should select the shortest useful retention period, avoid unnecessary user-level data and document the period in this policy. Indefinite retention should not be used merely because storage is available.
10. Changes to cookie use
Technology changes frequently. We may update this policy when we add or remove a tool, change a purpose, alter the preference Interface or respond to legal and operational developments. The effective date identifies the current published version. A material new optional category should not be silently treated as covered by an earlier choice that did not describe it.
Because the generated website is deployment-ready but the production host may add services, the site administrator should conduct a cookie and network scan after deployment and after every material integration. The scan should be checked against this policy and the banner behaviour.
11. Contact and preference questions
Questions about cookies, browser storage or related personal data may be sent to [email protected], addressed to the Data Protection contact, or posted to Vital Kitchen Lab, 51 Bras Basah Road #09-04 Singapore 189554 You may also call +65 6338 4275 during business hours. Please describe the device, browser and page involved without sending passwords or unnecessary confidential information.
To change the preference stored by this website, use the “Cookie preferences” control in the footer, save a new selection or clear site data through your browser. A change affects future optional activity on that browser; it does not reverse processing that lawfully occurred before the change.
12. Responsible implementation note
This policy is written for the Vital Kitchen Lab project described above. It is not a generic assurance that every future script is compliant. The organisation deploying the website remains responsible for ensuring that the production implementation, vendor contracts, consent signals and actual data flows match the published description and applicable requirements.