Covered Kitchen

Privacy notice

Last updated: [Date this version takes effect]

The short version

  • Covered Kitchen holds the records a kitchen keeps to run safely: staff accounts, checks, temperatures, training, and the guest allergy details the kitchen needs for service.
  • For most of it, the kitchen decides what goes in, and we look after it on the kitchen’s behalf.
  • We don’t sell personal information, and we don’t use advertising or tracking cookies.
  • Covered Kitchen runs in London and its database is in Ireland. The AI features send only what they need to Anthropic to get an answer.
  • You can ask to see, correct or delete your information. The details are below.

Who we are

Covered Kitchen is a HAMR Tech product. In this notice, “we” and “us” mean [Company legal name], company number [Company number], whose registered address is [Registered address].

We are registered with the Information Commissioner’s Office (ICO) under number [ICO registration number].

For anything about your personal information, email hello@covered.technology.

Who this notice is for

Everyone whose information is in Covered Kitchen:

  • the business that opens an account, and the people who manage it;
  • staff who use Covered Kitchen, or whose training and records are kept in it;
  • guests of a kitchen, whose booking details reach the kitchen for service;
  • anyone who visits the sign-in page.

Who is responsible for your information

Most of the information in Covered Kitchen is put there by a kitchen, for its own reasons: its staff, its checks, its guests. For that information the kitchen is in charge (in law, the “controller”). We look after it on the kitchen’s behalf and only on its instructions (the “processor”).

We are in charge ourselves of what we need to run our own business with each kitchen: who its account contacts are, billing, and keeping Covered Kitchen secure.

So if you work at a kitchen, or ate at one, the kitchen is usually the best place to start with a question about your information. You can still contact us, and we will help the kitchen answer.

What information we hold

  • Staff accounts: name, work email, role and permissions, two-step sign-in settings, and when you last signed in. Passwords, admin PINs, and invite and reset links are stored scrambled (hashed), so nobody can read them, including us.
  • Records of work: checklists, temperature readings, cleaning, COSHH reviews, probe checks, stock counts and fault reports, each with who did it and when. Some include a signature, a photo or a note.
  • Training and policies: training records (name, email, course, dates, trainer and a certificate link), the policy updates sent to staff, and each person’s confirmation in their own words, with the date. These keep the person’s name even if their account is later removed, because an inspector can ask about someone who has left.
  • Rota: shifts, and requests such as holidays, with any note and the manager’s decision.
  • Newsboard posts and staff documents, such as a staff handbook, with who posted or uploaded them.
  • Supplier invoices and safety data sheets that are scanned or uploaded. These are business documents, but can include the name of a contact at the supplier.
  • Guests of kitchens that use Covered Bookings: Covered Kitchen reads the details the kitchen needs for service straight from Covered Bookings, such as the time, party size, pre-orders, allergies and dietary needs, and shows them to the kitchen team. It doesn’t keep its own copy, apart from any note a chef adds to a booking.
  • Guests of kitchens that type bookings in by hand, or send them from another booking system: the guest’s name, the time, party size, allergies, dietary notes, special requests, pre-order items and any chef’s note.
  • The activity log: what was changed, by whom and when, and for most changes the internet (IP) address it came from.
  • Failed sign-ins: we count them for each email address and internet address for 15 minutes, to stop password guessing. The counts are kept in memory for those 15 minutes, not saved.
  • Hosting records: like any website, our hosting keeps short-lived technical logs of requests, such as the internet address, the page asked for and the browser used.
  • Ask Covered: the questions you type are sent to our AI provider to answer (see below). We don’t store them: we record who asked, when, and what it cost. Your recent searches stay on your own device, as the Cookie policy explains.

Allergies and dietary needs are health information, which the law protects more strongly. Kitchens hold it to keep guests safe, and Covered Kitchen shows it to the kitchen team for that reason only. [Solicitor to confirm the lawful condition for kitchens holding guests’ allergy details].

How we use it, and why we are allowed to

  • To provide Covered Kitchen to the kitchen, as our contract with the kitchen requires.
  • To keep Covered Kitchen and its records secure, and to stop misuse. This is in our legitimate interests, and the kitchen’s.
  • To run our business with the kitchen: its account, billing, answering questions and fixing problems. This is in our legitimate interests.
  • To meet our legal duties, such as keeping tax records.

We don’t sell personal information, and we don’t use it for advertising.

We don’t make decisions about people by computer alone. Where Covered Kitchen uses AI, a person checks the result: a chef confirms the allergens of any ingredient created from a scanned invoice, and allergen answers are worked out from the kitchen’s own records, never by the AI.

The AI features

Some features send information to Anthropic, the company that makes the Claude AI models, to get an answer:

  • Ask Covered: the question, and the parts of the kitchen’s records the person asking is allowed to see, such as recipes, allergens, COSHH products and training records (which include staff names). About bookings it sends only numbers, and for a dish asked about, when it has been pre-ordered: the day, time, party size and how many were ordered. Never a guest’s name, allergies or notes.
  • Invoice and safety data sheet scanning: the file or photo being scanned.
  • Drafting a policy update: the staff documents a manager chooses, such as the staff handbook. A manager checks every draft before anyone sees it.

Anthropic acts as our processor. [Confirm from Anthropic’s current commercial terms: that it does not train its models on this information, how long it keeps it, and where it processes it].

Who we share it with

We use a small number of companies to run Covered Kitchen. They only use the information to provide their service to us:

  • Vercel, which hosts Covered Kitchen, in London;
  • Supabase, which runs our database and file storage, in Ireland;
  • Resend, our email service, which sends the account emails (staff invites, password resets and the welcome message after sign-up) on our behalf;
  • Anthropic, for the AI features above;
  • Sentry, which tells us when something goes wrong in the app: error reports and speed measurements. Names, contact details and guest information are removed before a report is sent; it keeps reference codes for the account and the business involved, the page and the type of browser, so we can trace the fault.

[Name the payment provider here once card payments are switched on].

Our other products, such as Covered Bookings, are separate, and each has its own privacy notice.

We may also share information when the law requires it, for example with the police or a regulator, or to protect someone from harm.

Where it is kept

The database and uploaded files are in Ireland, in the European Union, which UK law recognises as protecting personal information properly. Covered Kitchen itself runs on servers in London.

[Confirm where Vercel, Anthropic, Resend and Sentry may process information outside the UK, and the safeguard for each (for example the UK International Data Transfer Addendum)].

How long we keep it

  • While a kitchen’s account is open, its records are kept for as long as the kitchen keeps them. Compliance records are often needed long after the day they were made, because an inspector can ask about the past.
  • If a subscription goes unpaid, the account closes after 4 months. We then keep its records for 12 months, so everything can come back if the kitchen pays. After that we delete them for good, with a final warning first. The Terms of use set out the full timeline.
  • What is kept in your own browser lasts as the Cookie policy says.
  • [How long database backups and hosting logs are kept].

Keeping it safe

  • Every connection to Covered Kitchen is encrypted.
  • Passwords are stored scrambled (hashed), and every account can turn on two-step sign-in.
  • Nobody stays signed in for more than 8 hours without using Covered Kitchen.
  • On a shared kitchen tablet, admin changes can be locked behind a PIN.
  • Each kitchen’s records are kept apart from every other kitchen’s, and each person only sees what their role allows.

Your rights

Under UK data protection law (the UK GDPR and the Data Protection Act 2018) you can ask:

  • for a copy of your information;
  • for wrong information to be corrected;
  • for your information to be deleted, or its use limited;
  • us to stop using it, where we rely on our legitimate interests;
  • for information you gave us to be handed to you, or to another organisation, in a common format.

Email hello@covered.technology. It is free, and we will reply within one month. If a kitchen holds your information, we will pass your request to the kitchen and help it answer.

Some records can’t be deleted on request while a kitchen still needs them, for example food safety records an inspector may ask to see. If that applies, we will tell you why.

Complaints

If you are unhappy with how we have handled your information, please tell us first so we can put it right. You can also complain to the Information Commissioner’s Office at ico.org.uk or on 0303 123 1113.

Changes to this notice

When we change this notice we update the date at the top. If a change affects you significantly, we will tell each kitchen’s account contacts before it takes effect.