Spaces

Customer privacy checklist for food makers and their chats

This checklist helps a food maker look after the personal details customers share in chat, such as delivery addresses, allergy notes and trade account details. It is for owners and teams who let an AI agent help with messages.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Food customers share more than they realise. A home buyer gives an address and a phone number for a cake collection. A parent mentions their child has a serious allergy. A trade buyer sends account numbers and delivery contacts. All of this sits in your chats, and it deserves care.

Go through the list with whoever manages your accounts and chats. You do not need a legal team to look after people well. Most of it is common sense, applied consistently: collect only what you need, keep it only as long as you need it, and let the right people see it.

Tick each one as you go. 0 of 10 done.

[ ] Ask only for the details you need to fulfil the order.
[ ] Treat any allergy or health note as sensitive and pass it only to the person who needs it.
[ ] Never ask customers to send card numbers in a chat.
[ ] Keep trade account numbers and credit terms out of general replies.
[ ] Decide who on your team can read customer chats.
[ ] Check that delivery addresses are shared only with drivers and couriers.
[ ] Write down how long you keep order chats and who deletes them.
[ ] Tell customers plainly what you will do with their details.
[ ] Use customer details only to answer the chat, never for a promotion they did not ask for.
[ ] Plan what to do if a customer asks you to delete their details.

A few examples from a food business

A home baker takes a custom cake order and notes that the birthday child has an egg allergy. That note should go to whoever bakes the cake, not into a general chat that five people can read. A cheese maker receives a purchase order with a buyer contact name and phone number. That belongs in the order record, not in a message sent to another customer.

If your agent works inside your chats, treat it like a new team member. It sees what customers send, so give it only the access it needs, and keep a person responsible for what it can read.

Easy habits that help

None of these needs special software.

  • Use work accounts for chats, not personal phones that leave with staff.
  • Remove access when someone leaves the team.
  • Never forward a screenshot of a customer chat to a group.
  • Review who has access every few months.

FAQ

Do small food makers need to worry about privacy?

Yes. Customers trust you with addresses, phone numbers and sometimes health details. Looking after them is part of good service, and the rules in your area may apply even to a very small business.

Is an allergy note a special kind of detail?

It is a health detail, so treat it with extra care. Share it only with the person who needs it to prepare the order safely, and do not copy it into places many people can read.

Should the agent store customer details itself?

It should use details to answer the chat in front of it, and anything that must be kept belongs in your normal order records. Check with whoever sets it up how long chats are kept and who can see them.

More free tools for food makers and producers

Read the guide: An AI agent for food manufacturing messages.