Security summary
Champ is a shared online space for the team around a child who needs extra support, of any kind: parents and carers, and everyone on a child's team. It is run by Champ Limited (NZBN 9429053962515), a small New Zealand company set up by 2 parents, and was designed and built in Aotearoa New Zealand.
This summary is for IT, privacy and risk teams deciding whether their staff can use Champ. It follows the headings of the New Zealand Information Security Manual (NZISM) so it can be compared with other systems. Champ has not been independently certified or tested against the NZISM or any other standard; this is our own account of how it works, and the last section says plainly what is not in place yet.
Questions go to our privacy officer, Jan-Paul de Groot, at hello@champ.kiwi.
1. Information Champ holds
About the adults who use it: name, email address, a scrambled (hashed) password, and optionally a photo, phone number, address and workplace.
About children, only what their team chooses to add: name, date of birth, school or early learning centre and class if added, photos, descriptions of what helps and what is hard, goals and progress, documents such as reports and plans, meeting notes, messages between team members and, where a parent switches that section on, Keep track: medication details with a dose log, and short entries about eating, sleep or other things the family keeps track of. Much of this is health and disability information, which we treat as sensitive information under the Privacy Act 2020 and the Health Information Privacy Code 2020.
Children do not have accounts. A child's parents or guardians hold the keys to their child's profile. If someone who works with the child starts it, the keys pass to the parents when they join, and that person becomes an ordinary team member.
2. Where information is stored and processed
The database and uploaded files are held by Supabase in its Sydney, Australia region, on Amazon Web Services infrastructure.
The website and its server code run on Netlify, with the server code in Sydney, Australia.
A small number of other services process information for one purpose each: Resend sends Champ's emails and receives the calendar invites that people forward to a child's private calendar address (only the subject, time, place and join link are kept) and the files emailed to add@champ.kiwi (only the files are kept, never the email); Deepgram turns meeting recordings into text; Anthropic's AI drafts plain-language summaries and meeting notes, sorts a pile of scanned paperwork into documents, and checks the name and date of birth in files emailed in; Google Analytics counts visits to the public pages only, never a page about a child. ImprovMX forwards email to hello@champ.kiwi to a Google mailbox, and email to add@champ.kiwi to Resend, without keeping it. Several of these companies are based in the United States.
Every provider stores and processes information only on our instructions and is contractually barred from using it for its own purposes, including training AI models. Sending information to Australia and the United States is a disclosure outside New Zealand under the Privacy Act; principle 12 of our Privacy Act statement explains why we are satisfied it is protected to a comparable standard.
3. Encryption
All traffic between a person's device and Champ is encrypted with TLS (HTTPS). Browsers are told to use HTTPS only (HTTP Strict Transport Security).
Supabase encrypts the database, uploaded files and backups at rest with AES-256.
Passwords are stored only as a salted hash by Supabase's sign-in system; nobody, including us, can read them.
Files are never public. Opening a document gives the browser a private link that expires after 2 minutes, and only after the database has confirmed the person may see it.
4. Access control
Every child has a team. The people who manage a profile (normally the parents) invite each member and give them one of 3 levels: manages everything, can add and update, or can see everything. They can also limit a person to particular parts of the profile or particular documents. The Keep track section (medication, eating, sleep) is switched off for everyone until a manager turns it on for the people who need it.
These rules are enforced inside the database with row-level security on every table, not only on the screen. A person cannot reach a profile they are not on, even by calling the database directly.
An organisation's supervisor (for example at a practice or school) can see which children their staff work with, but must join a child's team, visibly, to open the profile, and the parents are told. The same rule applies to the 2 people who run Champ: we open a profile only when a family asks us to help, by joining the team visibly, and leave when done.
Everyone with access is listed on the child's Team page. There are no hidden viewers.
5. Signing in
Anyone can create an account. Accounts are made by Champ's own server, and an email address counts as proven only once the person has used the invitation link sent to it, or tapped once on a confirmation email. People sign in with an email address and a password of at least 8 characters, or with a one-time link sent to their email.
An invitation is matched to an account only once the person has proven the email address is theirs, by using a link sent to that inbox: the invitation link itself, or a one-tap confirmation. Typing someone else's address into a sign-up form or the demo gives no access to anything sent to that address. Demo accounts are never matched to invitations, and Champ's own administration opens only for the named administrators, with a proven address and 2-step sign-in.
2-step sign-in offers a choice: a 6-digit code from an authenticator app, or a 6-digit code sent by email. Text message may be added later. Email codes work once, expire after 10 minutes, allow only a few tries, and are stored only as a fingerprint (hash). A person can tick 'Remember this device for 30 days', after which that device skips the second step until the 30 days are up or the password changes.
2-step sign-in is optional for parents and carers. It is required for anyone who is not a parent and is on the teams of 2 or more children (a therapist or specialist, for example), for organisation supervisors, and for the people who run Champ. A person who must use it cannot switch it off. For people who use an authenticator app, the database itself refuses a session that has skipped the code. Email codes are checked by Champ's server.
There are no recovery codes to keep. Someone whose phone is not to hand can get a code by email instead. If they cannot do either, the Champ team switches 2-step sign-in off only after checking who they are, logs how it was checked, and emails the person.
Changing a password signs the account out on every other device and forgets every remembered device. Unused accounts can be identified and closed.
6. Administration of the systems behind Champ
Only the 2 people who run Champ can reach the hosting, database and email accounts, each protected with 2-step sign-in.
Service keys and passwords live in the hosting provider's protected settings, never in the code. The build process scans for secrets accidentally included in the code and stops if it finds one.
7. Logging and monitoring
Each child's profile keeps an activity history of what was added or changed and by whom, and an access log of who opened each document and when. Both are visible to the parents. When an item is deleted, its lines in both go with it. The parents are notified when someone joins the team, adds something or records a meeting. Every 2-step reset done by the Champ team is logged, with how we checked who the person was.
Supabase and Netlify keep their own logs of sign-ins, database activity and requests, which we can review if something looks wrong. Champ does not have round-the-clock security monitoring.
8. Backups and recovery
Supabase backs up the database automatically every day and keeps each backup for 7 days. Uploaded files are held on Supabase's redundant storage; they are not part of the daily database backup.
The people who manage a profile can download everything in it, documents included, at any time from the profile's About page.
9. Keeping and deleting information
A profile stays as long as its team wants it, because continuity as people and services change is the point of Champ. The parents can delete it at any time; it is removed straight away, apart from backups, which roll off within the backup period.
Meeting audio is deleted as soon as it has been turned into text, usually within minutes. A file emailed to Champ that a parent turns down is deleted straight away, and one nobody sorts within 14 days is deleted then, with nothing kept. The scans in a pile of paperwork are deleted once its documents are added, and a pile nobody adds is deleted after 14 days. Demo accounts, which contain only a fictional child, are deleted after 14 days. Requests for access are deleted once the person has joined, or after 90 days.
A person can delete their own account at any time from Settings. Their name, email address, contact details and sign-in are removed, including from every timeline and access log; what they added to a child's profile stays, shown as from a former team member, unless the profile is deleted. We keep only a count of people leaving. If Champ ever closes, the parents on every profile get at least 90 days' notice and a way to download everything, after which all data, files and backups are deleted.
10. Artificial intelligence
AI is used for 5 things only: plain-language summaries of documents, draft notes and suggested to-dos from meeting transcripts, sorting a pile of scanned paperwork into documents (with the date each was written, leaving out pages about another child), checking that a file emailed to Champ is about the child it was sent for (by its name and date of birth), and, when a parent asks, a first draft of the About sections. Nothing an AI writes is shown to the team until a person has checked and approved it, and a file emailed in always waits for a parent.
Text and audio are sent to Anthropic and Deepgram only to produce that result, and neither uses it to train its models. Every request to Deepgram opts out of its model improvement programme, so audio is kept only as long as the transcription takes. Anthropic deletes text from its systems within 30 days under its commercial terms (longer only if it were flagged as breaking Anthropic's usage rules). Champ never uses information to train anything, and never sells it or uses it for advertising.
11. Incidents and privacy breaches
We have a written breach response plan. If we become aware of a privacy breach that has caused, or is likely to cause, serious harm, we notify the Office of the Privacy Commissioner and the people affected as soon as practicable, as Part 6 of the Privacy Act requires, and tell them plainly what happened and what we are doing about it.
Organisations whose staff use Champ can ask to be told directly of any incident affecting their people.
12. Building and changing Champ
Champ is built by the 2 people who run it, using well-supported open-source frameworks and managed services rather than self-run servers, so operating-system and database patching is done by the providers.
Each change is built and checked before it goes live, including automated accessibility checks. Standard protective web headers are sent on every page.
13. What is not in place yet
We would rather say this than have it found. Champ has not had an independent penetration test or a certification such as ISO 27001 or SOC 2. There is no round-the-clock monitoring. 2-step sign-in is optional for parents and carers; it is required for people who are not a parent and are on the teams of 2 or more children, and for the people who run Champ. A code sent by email is only as safe as the inbox it goes to, so we recommend an authenticator app. A remembered device skips the second step for up to 30 days. Champ is run by 2 people, which keeps access tight but means a small team.
If your organisation needs more before its staff use Champ, tell us what. We are happy to answer a security questionnaire, talk to your IT team, and consider an independent test with an organisation that plans to adopt Champ.
Privacy Act 2020 statement
This statement sets out how Champ Limited meets the 13 information privacy principles of the Privacy Act 2020. Because Champ holds health and disability information about children, we also follow the Health Information Privacy Code 2020, which applies the same 13 rules to health information with extra care; each principle below covers the matching rule of the code.
It sits alongside our public privacy policy at champ.kiwi/privacy, which says the same things for families, and the security summary, which covers the technical side.
Agency: Champ Limited, NZBN 9429053962515, Wellington. Privacy officer: Jan-Paul de Groot, hello@champ.kiwi.
Principle 1: Purpose of collection
Collect personal information only for a lawful purpose connected with what the agency does, and only what is necessary.
Champ collects information for one purpose: so the people around a child can share what they know and keep it when someone leaves. Everything held supports that child.
There are no required fields beyond a name and email for adults and a first name for a child. Phone, address, photos and the Keep track section are optional.
Principle 2: Source of information
Collect information directly from the person concerned, unless an exception applies.
Most information about a child comes from their parents, or from professionals the parents have invited or who started the profile on the family's behalf, acting as the child's representatives, which the Act and the code allow.
Adults provide their own details when they create an account or accept an invitation. Anyone invited to a team is told by email who invited them and to which child's team.
Principle 3: Collection of information from the person
Make people aware of the collection, its purpose, who will receive it and their rights.
The privacy policy is written in plain English and linked from the home page, the sign-up page, the page where an invited person joins, and Settings. Invited people are told who invited them and to which child's team, and can decline.
The parents are notified whenever someone joins, adds something or records a meeting. Before a recording starts, Champ announces out loud that it is recording.
Principle 4: Manner of collection
Collect information lawfully, fairly and without unreasonable intrusion, taking particular care with children and young people.
Champ is used by adults about children; children have no accounts. Teams are encouraged to involve a child in what is written about them where the child is old enough.
Meeting recording is announced aloud and anyone present can ask for it to be deleted. There is no tracking or analytics on any page about a child.
Principle 5: Storage and security
Protect information against loss, misuse and unauthorised access with safeguards that are reasonable in the circumstances.
Encryption in transit and at rest, access rules enforced in the database, 2-step sign-in (required for people on the teams of 2 or more children who are not a parent, and for the people who run Champ), private file links that expire in two minutes, and daily backups. The security summary gives the detail.
Service providers act only on our instructions under contract.
Principle 6: Access to personal information
People can ask for access to information about them.
Parents can see and download everything on their child's profile at any time. Anyone can ask us for a copy of what is held about them or their child; we respond within 20 working days and there is no charge.
A young person can ask to see what is held about them; we work out with them and their parents how best to do that.
Principle 7: Correction of personal information
People can ask for information to be corrected.
Parents can edit everything on the profile directly. Other requests go to hello@champ.kiwi. Where we do not make a correction, we attach a statement of the correction sought if asked.
Principle 8: Accuracy
Take reasonable steps to check information is accurate, up to date, complete and not misleading before using it.
Everything on a profile shows who added it and when. AI summaries and meeting notes are drafts until a person who knows the content checks and approves them, and they sit alongside the original document or transcript.
Principle 9: Retention
Keep information no longer than needed for the purpose.
A profile is kept while its team wants it and deleted when its parents ask. Meeting audio is deleted as soon as it is transcribed, files emailed in that are turned down straight away (or after 14 days if nobody sorts them), demo accounts after 14 days, and email sign-in codes after 10 minutes. The access log is kept with the profile and deleted with it. Backups roll off automatically.
Principle 10: Limits on use
Use information only for the purpose it was collected for, unless an exception applies.
Information is used only to support the child's team. It is never sold, never used for advertising, never used to train AI, and not analysed across children for products, research or statistics without asking first.
Principle 11: Limits on disclosure
Disclose information only for the purpose it was collected for, with authorisation, or where another exception applies.
Information on a profile is disclosed only to the people its parents have invited, at the level they chose. The one narrow exception is a meeting guest link, which shows the child's first name and the meeting's details and nothing else, and the parents are told.
Neither the people who run Champ nor an organisation's supervisor (for example at a practice or school) can open a profile without joining the team visibly.
Principle 12: Disclosure outside New Zealand
Send information overseas only where it will be protected by comparable safeguards.
Champ's data is held in Australia, whose privacy law is broadly comparable to New Zealand's. A few providers in the United States process information for a single purpose each (emails, email forwarding, transcription, AI drafting and checking, public-page visit counts). We choose providers that commit by contract to protect information to a standard at least as strong as New Zealand law requires, and to not use it for their own purposes.
Principle 13: Unique identifiers
Assign unique identifiers only where necessary, and do not reuse another agency's identifier.
Champ gives people and profiles random internal identifiers used only inside Champ. It does not collect or use National Student Numbers, NHI numbers or any other agency's identifier.
Privacy breaches
We keep a written breach response plan. A notifiable privacy breach, one that has caused or is likely to cause serious harm, is reported to the Office of the Privacy Commissioner and to the people affected as soon as practicable, as Part 6 of the Act requires.
Complaints
Anyone unhappy with how we have handled their information can raise it with our privacy officer at hello@champ.kiwi, and can complain to the Office of the Privacy Commissioner at privacy.org.nz.
Anything else your team needs to know? Write to hello@champ.kiwi and a person will answer, usually within a working day.