Privacy policy

1. Who is responsible for your information

Your Limeta account -- your login, your name, your email address, your mobile number and your children's names -- is held by Fortlyn Technologies, which runs Limeta, as its data controller. You use the same account with every caterer on Limeta, and these details are the same at each.

When you order from a caterer, that caterer decides how the information about what you do with it is used to provide meals: your orders and payments with it, the school and class it feeds your children at, the allergies you record for it, and the kitchen's lists. It is the data controller of that information, and Fortlyn processes it on the caterer's behalf as a data processor. Each caterer is a separate controller, and no caterer can see your dealings with another.

Fortlyn Technologies is also the controller of messages exchanged on Limeta, of the details of organisations registered on Limeta, and of the running of the platform.

Each login is one kind of account: a personal account (for yourself and your family), an organisation's account (for the staff of a school, company or institution), a caterer's staff account, or Fortlyn's. If you are both a parent and, say, your school's office manager, you use two logins, so the school's business and your family's stay apart.

2. What we collect

• Your account: name, email address, mobile number and password (stored only as a secure hash). These are held once: every caterer you use sees the same details, and a change you make reaches all of them.
• Your children: each child's name, and gender if given, on your account. For each caterer you add a child to: their school, class or grade, and any allergies you record for that caterer.
• Schools you connect: the schools you connected with the code the school gave you, at each caterer.
• Where you work, if you order lunch at work: the company you joined with its code, and the lunches your company pays for.
• If you are staff of an organisation: the organisation's login holds your name, your work email address, and whether you are its admin or staff, and the orders, meetings and invoices you handle for it.
• Which caterers you order from, and when you joined or left each one.
• Orders and payments: meals ordered, packages bought, event bookings and meeting orders, amounts, payment method, and payment references. Card numbers are handled by our payment provider and never stored by Limeta.
• Your usual lunches, if you switch on "order the usual every week": what you ordered on each weekday recently.
• Messages you send to or receive from a caterer on Limeta, and, if you write before having an account, your name and email address so we can confirm it is you.
• Event enquiries: your name, email, phone number, and the event's date, place, guest numbers and anything you add.
• Meeting orders: the meeting's date, time, room, number of people and any notes, and who placed the order.
• Communication choices: whether you agreed to email or text reminders, which reminders, and when. It is one choice for every caterer you use, including caterers you join later, and you can mute any caterer.
• Agreements: which version of these documents you accepted, and when. Where a consent is about a particular caterer, which caterer you gave it to.
• Credit requests: if you ask your caterer for credit, the amount, the reason you give and the caterer's decision. Write only what the caterer needs in order to decide. Credit a caterer gives you is recorded against you at that caterer, and can be spent only with that caterer.
• Technical information: sign-in records and error logs needed to keep the service secure and working.

Allergy information is health information. We collect it only because you choose to give it, with your separate consent, to warn you about dishes and to help the kitchen prepare safe meals. That consent is given to one caterer: joining another does not carry it across, and you are asked again. Sharing your child's name and allergies with their school is a separate choice, and you can withdraw it.

2a. Organisations

When a school, company or institution registers on Limeta, we collect its name, what kind of organisation it is, its registration number, phone number and address, and the name and work email address of the person registering it, who becomes its admin. Fortlyn uses these to check that the organisation is real, which includes calling the phone number, and keeps a record of that check. Its admin can add colleagues by name and work email.

When the organisation asks a caterer to work with it, that caterer sees the organisation's name, registration number, phone number and address, who asked, and what they wrote, so it can decide.

3. How it is used

• To take, prepare, deliver and charge for meals: school lunches, lunch at work, standing orders for institutions, events and meetings, and to send receipts.
• To let you find caterers on Limeta and join them, and to connect you to your school or company with its code.
• To check that an organisation registering on Limeta is real before it can work with caterers.
• To give the caterer's kitchen its daily list of meals by school, class and allergy, and its list of meetings and events.
• To place your usual lunches each week, if you switched this on, and to email you what was ordered. You pay for them as for any other order, and can switch it off at any time.
• To let you and your caterer message each other, and to email you when you have a new message (the email does not contain the message).
• To invoice companies and institutions for the meals and meetings they pay for.
• To show a school, company or institution its own numbers on its dashboard.
• To send reminders, only if you opted in, by the channels you chose and in the inbox on my.limeta.io. You can change or switch them off at any time under Account, Notifications, and mute any caterer under Account, Caterers.
• To keep accounts secure, prevent fraud, and meet tax and accounting obligations.

We do not sell personal information, and we do not use it for advertising.

4. Who can see it

• Your caterer's staff see the information needed to prepare and deliver meals and to answer your messages. What each member of staff sees depends on their role: kitchen staff, for example, see what to cook but not payments. Each caterer can see only its own customers, and only what you have done with that caterer.
• Your school, company or institution's staff see their organisation's numbers: how many meals were ordered, and what the organisation owes. Its admins also see and pay its invoices and order meetings. They see who joined with their code: for a school, your name and how many of your children are there; for a company, which employees joined. A school sees your child's name and allergies only if you chose to share them with it. A company sees how many of its employees ordered and the company's share of the cost, not who ate what.
• Fortlyn staff see totals and service health, and the details of organisations registering, in order to verify them. They see family details only when needed to fix a problem you or your caterer report, and they may read messages between you and a caterer, including details that were hidden in them (see 4a), to resolve a dispute or a report of abuse. Every time Fortlyn staff open a conversation it is recorded.
• Service providers working for us, who may use the information only to provide their service to us: Supabase (database, file storage and live message delivery, European Union), Google Cloud (hosting, South Africa), DPO Pay (card and Mobile Money payments), Resend (email delivery), Africa's Talking (text messages) and DocuSeal (electronic signing of caterer agreements, which involves caterer staff rather than families).
• Authorities, where the law requires it.

Your children's names are on your account, so every caterer you add a child to knows their name. Anything more -- their class, and above all their allergies -- is given to each caterer separately: if you ask us to copy it from one caterer to another we do that only because you asked, we record that you asked, and allergies move only with your consent to the new caterer. Nothing is copied between caterers otherwise.

### 4a. Messages

Messages between you and a caterer stay on Limeta. Until you have paid for a booking with that caterer, phone numbers, email addresses and links in messages are hidden from the other side, and the caterer's own contact details are not shown; this keeps bookings, payments and receipts in one place where they protect you. The original text of a message with hidden details is kept so that Fortlyn can look into a dispute; neither you nor the caterer can see it.

5. Where it is stored

Limeta's servers are in Johannesburg, South Africa, and its database and uploaded files are in Frankfurt, Germany. Both are outside Zambia. Where information is transferred outside Zambia, we rely on providers that apply security and data protection safeguards at least equivalent to those required in Zambia.

6. How long it is kept, when you leave, and when a caterer leaves

Account and children's details, messages and your usual lunches are kept while your account with that caterer is open.

If you leave a caterer, which you can do under Account once no paid meals are still to come and no credit is left there, your unpaid orders with it are cancelled, your usual lunches and reminders from it stop, and it keeps the record of what you ordered and paid. You can join it again later.

If you delete your Limeta account, under Account, you are signed out everywhere at once and cannot sign in. Seven days later we erase you at every caterer: your name, contact details, children, allergies, messages, enquiries and the reasons you gave for any credit request. Until then, the link in the email we send you cancels the deletion. What remains is the payment record without your name, because the law requires us to keep it. Order and payment records are kept for as long as tax and accounting law requires, which is longer.

When a caterer stops using Limeta we close every account with them and remove what identifies you from that caterer's records: your name, your contact details, your children's names and allergies, your messages, your enquiries, your usual lunches, and the reasons you gave for any credit request. What remains is the payment record itself — the amounts, the dates and the references — because the law requires us to keep it, and because it is your proof of what you paid. You can still open your own receipts.

Your login is not affected. It is held by Fortlyn rather than by the caterer: the caterer's copy of your details is removed, and your account keeps them, with your children's names, for you to use with another caterer on Limeta.

7. Cookies

Limeta sets cookies that keep you signed in and keep your session secure. They are necessary for the service to work, and there are no advertising or tracking cookies. Blocking them will stop you from signing in.

8. Your rights

Under the Data Protection Act 2021 you can ask to:

• see the personal information held about you and your children, including your messages;
• correct information that is wrong (your name and number on your account page, which corrects them at every caterer you use; most other details on the same page);
• have information deleted, where it is no longer needed and the law does not require us to keep it;
• object to or restrict its use, or withdraw consent to reminders, to holding allergy information, or to sharing your child's details with their school.

You can do most of this yourself under Account on my.limeta.io: download everything held about you at every caterer, correct your details, withdraw a consent, stop sharing with a school, leave a caterer, or delete your account.

For anything else, ask your caterer, or email hello@limeta.io. If you are not satisfied with the response, you may complain to the Office of the Data Protection Commissioner of Zambia.

9. Security

Information is encrypted in transit, access is limited by role, and each caterer's data is separated from every other caterer's at the database level. Passwords are stored only as secure hashes.

10. Changes and contact

We will post changes to this policy here and tell you in the app or by email if they are significant. Questions: hello@limeta.io.