Privacy policy
Last updated 18 October 2026
KaiPlan holds information about the adults who use it and the organisations they work for. It holds nothing that identifies a child. This policy explains what we collect, why, where it is kept, who helps us process it, and what you can ask of us.
Who we are
KaiPlan is provided by Julia Scott, a New Zealand registered dietitian trading as Julia Scott Dietitian (NZBN 9429051009113). In this policy “we” and “us” means her business. We are responsible for the personal information KaiPlan holds, and you can contact us about it at hello@kaiplan.co.nz.
This policy covers the KaiPlan app, at app.kaiplan.co.nz, and the KaiPlan website, at kaiplan.co.nz.
The short version
- We hold the names and email addresses of the people who use KaiPlan, the staff details an organisation chooses to keep in it, and the records it keeps.
- We never hold children’s names, health information or allergy details. KaiPlan counts children by age group only.
- KaiPlan’s database and files are stored in Sydney, Australia.
- We do not sell personal information, show advertising, or use tracking or analytics cookies.
- You can ask to see or correct the information we hold about you.
What we collect
About the people who use KaiPlan
- Your name, email address, and the organisation, area or centre you belong to, with your role there.
- Sign-in details: when you signed in, and, if you use one, your two-step sign-in method. If your organisation signs in with Microsoft or Google, those services tell us your name and email address.
- What you do in KaiPlan that it records: for example, who confirmed a day’s food record, recorded a food safety check, approved a recipe or changed a setting, and when.
About staff, entered by their organisation
An organisation can keep a staff register in KaiPlan: each person’s name and role, when their first aid certificate expires, their training (the topic, the date and who provided it), and when they read the documents staff are asked to read. Records kept in KaiPlan, such as the daily food record and food safety checks, include the name of the person who made them.
What organisations write and upload
Recipes, menus, documents and files an organisation writes in KaiPlan or uploads to it, including any names or other information in them. Please do not put anything about a child in a recipe, a note or a document: KaiPlan has no place for it, and if we find any we will remove it.
From the website
If you use the form on kaiplan.co.nz, we receive your name, email address, organisation, role, how many sites you have and your message. It is emailed to us and is not stored in KaiPlan.
What we do not collect
No information that identifies a child. Centres enter how many children are expected in each age group, which is a number and not personal information. We do not collect payment card details: invoices are paid outside KaiPlan.
Why we use it
- To provide KaiPlan to your organisation: to show each person what their role allows, keep your records, and let your dietitian review your recipes and menus.
- To keep accounts secure, and to investigate and fix problems.
- To send the emails KaiPlan sends: invitations, sign-in and password emails, and reminders your organisation has switched on.
- To answer an enquiry from the website.
- To meet our legal obligations.
We do not use personal information for advertising, and we do not sell it or give it to anyone to market to you.
How artificial intelligence is used
Some features use Claude, an artificial intelligence model made by Anthropic. When you upload a recipe or a menu, its contents are sent to Anthropic to be read into a draft. The model also helps check recipe notes and draft parts of menu review reports. Anything in what is sent, including a name in a document, goes with it. Under Anthropic’s commercial terms this content is not used to train its models. A person always checks what the model produces: it never approves a recipe, sets an allergen or signs anything off.
Who else processes it
We use these companies to run KaiPlan. Each processes personal information only to provide its service to us.
- Supabase: the database, sign-in and file storage, hosted in Sydney, Australia.
- Vercel: hosts the website and the app, with its servers in Sydney, and counts visits to the website anonymously. Vercel is a United States company.
- Resend: sends KaiPlan’s emails, from the United States.
- Anthropic: the artificial intelligence features described above, from the United States.
- Microsoft or Google: only if your organisation signs in with them.
Within your organisation, its administrators can see who has an account and what is recorded, according to their role. Your dietitian sees your organisation’s recipes, menus and records to provide her service. We will also share information if the law requires it.
Information sent overseas
KaiPlan’s data is stored in Australia, and some of the companies above process it in the United States. We use these companies because they protect personal information in ways that, overall, give comparable safeguards to those in the Privacy Act 2020.
How we protect it
- Information is encrypted when it travels to and from KaiPlan, and is stored by providers that encrypt it at rest.
- Each organisation can see only its own information, and the database enforces that, not just the screens.
- Accounts are by invitation only. The dietitian’s account uses two-step sign-in.
- Records such as the daily food record are never rewritten: a correction adds a new entry, so the history stays intact.
How long we keep it
We keep an organisation’s information while it uses KaiPlan. Licensing rules ask centres to keep food records for at least three months, and food control rules ask for food safety records to be kept for four years, so KaiPlan does not delete records while an organisation uses it. When a person’s account is removed, records they made keep their name, because the record needs to show who made it.
When an organisation stops using KaiPlan, we can give it a copy of its records, and on request we will delete its information, apart from anything the law requires us to keep. Copies in our providers’ backups expire on their normal schedule. Website enquiries are kept in our email for as long as we need them to answer you.
Cookies and storage in your browser
KaiPlan uses one cookie, to keep you signed in. It also keeps a few conveniences in your browser, such as the names of recent recorders on a shared kitchen tablet and the items ticked on a shopping list. These stay on your device. We use no analytics, advertising or tracking cookies.
The KaiPlan website (not the app) counts its visits with Vercel Web Analytics, which sets no cookies and does not identify you: it records which pages are read, roughly where visitors are and what device they use, and how many enquiries are sent, so we can see what is useful.
Your rights
You can ask to see the personal information we hold about you, and ask us to correct it. Your organisation’s administrator can change most details directly, or you can email us at hello@kaiplan.co.nz. We will respond within 20 working days. If you are not happy with how we handle your information, please tell us first. You can also complain to the Office of the Privacy Commissioner.
Organisations’ responsibilities
An organisation decides what it keeps about its staff in KaiPlan, and is responsible for telling its staff that it keeps it and why. It must not enter information about children.
Changes to this policy
If we change how KaiPlan handles personal information, we will update this page and the date at the top, and tell organisations about any significant change.
Contact
Julia Scott, trading as Julia Scott Dietitian, a sole trader in New Zealand (NZBN 9429051009113).
Email: hello@kaiplan.co.nz