Privacy
Your information should have a clear purpose and destination.
Last reviewed September 2026
This statement explains what the New Zealand Aquatics Collective collects through the Wellbeing Hub, why, where it goes and how long it is kept, as required by the Privacy Act 2020. Each part of the hub handles information differently, so it is set out by pathway.
The short version: browsing collects nothing personal, the assistant keeps no history, and each form sends exactly what you type to the people responsible for that kind of matter, with nothing forwarded between pathways.
Browsing the hub
Published pages, resources, policies, stories and the public Team Managers pages are open information. Viewing them does not require an account and does not create a record about you. Essential browser state may remember a display preference or protect a form from automated abuse; see the Cookies page. The hub uses no advertising cookies, no analytics that profile you, and never sells personal information.
Asking the assistant
Your question and relevant hub excerpts are processed by an AI model to generate an answer, under zero-data-retention and no-training settings. The hub does not save a chat history or create a profile. See AI and your privacy for the detail.
Be Heard: concerns and complaints
Be Heard collects the type of concern, its urgency, your role if you give it, what happened, and, only if you choose a named submission, your name and at least one of an email address or phone number. Anonymous submissions do not ask for contact details, and any contact fields are removed on the server before delivery; the words you write may still identify you.
Your submission is emailed, protected in transit, to the receiving inbox approved by the Collective for concerns and complaints, as a readable message with a PDF record of your answers attached. The named contact details you give are used only to follow up with you. The hub does not keep a copy of a Be Heard submission; the receiving inbox is the only record, so its retention follows the Collective's records policy.
Health and safety incident reports
An incident report collects the incident details, the reporter's name and contact details, the person affected, any witness, what happened, treatment and follow-up, and an optional uploaded file. Reports submitted from a Team Managers event workspace also carry that event's name and dates.
Each report is stored in the hub's private database, encrypted at rest with a key held only in the hosting environment, and is emailed as a readable message with the PDF record and the uploaded file attached to the approved health and safety inbox. Only signed-in administrators of the hub can open stored reports; team managers see only a reference and delivery status. Reports are not public and are never available to the assistant. The receiving team may contact the people named to follow up and may share the report with those responsible for responding, including WorkSafe New Zealand or emergency services where the law or safety requires it.
Police vetting applications
The Police vetting consent and disclose form is currently open to Swimming New Zealand members. It collects the personal information the New Zealand Police Vetting Service requires (full name, gender, date and place of birth, previous names, residential address and, where given, a driver licence number), your signature, your club, role and contact details, and any identification and application documents you upload.
Your application is stored in the hub's private database, encrypted at rest, and emailed as a readable message with the PDF record, your signature and your uploaded documents attached to the approved Police vetting inbox, from where Swimming New Zealand submits the request to the Police Vetting Service. Only signed-in administrators can open stored applications. The application and identity documents are kept only as long as Swimming New Zealand's retention schedule requires for vetting purposes, then deleted. The full privacy notice is shown on the form before you consent.
Content requests
A content request collects the part of the hub it concerns, the sport, the audience, your suggestion and an optional email address. It is retained in the hub's private database, encrypted at rest, for signed-in administrators to review and download. A notification and PDF record are also emailed to the hub's content team. An email address you give is used only to reply about that suggestion.
Team Managers workspaces and administrator accounts
Team managers and hub administrators sign in with an email address and password held by our authentication provider. The hub records the account's email, name, role, and when it last signed in, plus an audit of who set up each account and each form's receiving address. Event workspaces hold the forms managers complete for their event; those responses are visible to the event's managers and to administrators.
Who processes information for us
The hub runs on Vercel (hosting and the AI gateway), Supabase (database and sign-in), Resend (email delivery) and Cloudflare Turnstile (bot protection on forms). Each processes information only to provide its service to the Collective. Some of these providers store data on servers outside New Zealand; the Collective relies on their contractual and security commitments, which provide protections comparable to the Privacy Act 2020.
Nothing you submit through the hub is automatically forwarded to an outside body. Where the Integrity Code, the Health and Safety at Work Act 2015, safeguarding duties or another law requires disclosure, the receiving organisation applies its own approved process. The Sport Integrity Commission's independent complaints route is entirely separate: choosing it sends nothing from the hub, and the Commission's own privacy practices apply.
Your rights and how to contact us
You can ask to see the personal information the Collective holds about you, ask for it to be corrected, or ask a question about this statement by emailing info@aquaticscollective.com.
If you submitted to Be Heard anonymously, the Collective has no way of knowing it came from you: no name, contact details or account is attached, and the hub does not record who sent it. The reference shown when you submitted, also included on your downloadable PDF copy, can help locate the record. If you do not have it, provide any details that may help us search. A reference alone does not establish that you sent the submission or that its contents can be released to you.
For every other submission, where it is held depends on the form. A named Be Heard submission or a content request exists only as the email in the receiving inbox, with its PDF record attached; the hub keeps no copy. An incident report or vetting application is held both as that email and as an encrypted record in the hub's database. Include your reference if available and describe the information you want. We may need to confirm your identity or authority before releasing personal information, and coordinate with the team holding the records; for a Police vetting application that is Swimming New Zealand.
If you are not satisfied with how a privacy matter is handled, you can complain to the Office of the Privacy Commissioner at privacy.org.nz.