Overview
The current public version of MeetMate does not require a user account. MeetMate is intended to minimise the collection of personal information and does not sell personal information or use event data to build advertising profiles.
This statement describes the current product. If MeetMate introduces a feature that materially changes how personal information is collected or used, this statement and any relevant collection notice should be updated at that time.
Saved meets and local storage
Saved-meet selections are stored in your browser using local storage. They are not tied to a MeetMate account or uploaded merely because you save a meet. MeetMate may reconcile saved event IDs against the current published event feed so obsolete saved records can be removed from the device.
The Community board and issue-report form may also store a recent-submission timestamp in local storage to reduce accidental repeated submissions from the same browser. That timestamp remains on your device.
Calendar files are generated from published event information in your browser. If you choose a Google Calendar or Outlook Calendar link, you are opening a third-party service and the event details needed to create that calendar item may be passed to that provider through the link you choose to open.
Technical analytics
MeetMate uses lightweight first-party analytics on its Cloudflare-hosted service to understand aggregate traffic and improve the product. The analytics collector records the page path, a broad device class, Cloudflare country code, the referring website hostname for session entries, optional UTM campaign labels and active on-page time. Query strings are not stored as page paths.
To distinguish repeat traffic without building an advertising profile, MeetMate sets a random first-party visitor identifier cookie named mm_vid for up to 12 months and a random session cookie named mm_sid for 30 minutes. Those random identifiers are hashed before they are stored in the analytics database. MeetMate does not store visitors' raw IP addresses in its analytics tables.
Active time is measured while a page is visible and is sent in short intervals, normally about once per minute and when the page is hidden or closed. The private analytics dashboard reports aggregate measures such as pageviews, unique devices, sessions, top pages, countries, traffic sources and average active time.
Requests that carry Global Privacy Control (Sec-GPC: 1) or Do Not Track (DNT: 1) are excluded from MeetMate's first-party analytics collector. Hosting and security providers may still process routine request and security information where reasonably necessary to deliver and protect the service.
MeetMate AI
MeetMate AI has been successfully developed, but live AI responses are currently paused. While live access is paused, questions entered into the AI box are not sent to an external AI API; the app displays a fixed status message instead.
If live AI responses are enabled again, MeetMate may send the user's question, limited in-session context and relevant published event information to an external AI API to generate an answer. This privacy statement will be kept aligned with the live implementation.
Please do not put private contact details, athlete medical information or other sensitive personal information into the AI question box. AI-generated information should always be checked against the current official organiser source before a time-sensitive decision.
Community board
The MeetMate Community board is public. You may leave the display-name field blank and post as Anonymous. If you provide a display name, that name and the message you submit are stored with the posting time and displayed publicly on the board.
Community messages are stored in MeetMate's Cloudflare-hosted database. The form does not ask for an email address. Please do not include private contact details, athlete medical information or other sensitive personal information in a public message.
MeetMate may hide or remove Community messages that are spam, abusive, impersonate another person, expose private information, interfere with the service or otherwise breach the Community rules or these terms.
Issue reports and submissions
The public issue-report form is live. It may collect an optional name and email address, a meet or event reference, an optional page URL, the selected issue type, the correction details you submit and the submission time. Issue reports are stored privately in MeetMate's Cloudflare-hosted database and are not displayed on the public Community board.
The meet-submission form is not currently open. Please do not submit athlete medical information or other sensitive personal information through the issue-report form unless it is genuinely necessary to explain the correction.
Public-source event information
MeetMate is designed around event-level information obtained from publicly available or official swimming sources. It may link to third-party documents that contain names or other information published by organisers. MeetMate does not intentionally extract unnecessary sensitive personal information for ordinary event listings or create participant profiles from those documents.
If you believe personal information linked or displayed by MeetMate is inaccurate, unnecessarily exposed or should be reviewed, use the Report an issue channel.
Third-party services and links
MeetMate uses or links to independent services including Cloudflare hosting and security services, organisers, swimming bodies, registration services, document hosts and calendar providers. If live AI responses are enabled, an external AI API may also process the information described above. When a feature sends information to or opens a third-party service, that provider's own privacy terms and practices apply.
Your privacy rights
Where MeetMate holds personal information about you, applicable privacy law may give you rights to request access to that information and to ask for it to be corrected. MeetMate should keep personal information only for as long as it is reasonably required for the purpose for which it was collected and should take reasonable steps to protect information it holds.
For privacy questions, access requests or correction requests, contact MeetMate at mmeetmate@gmail.com.
MeetMate is operated with New Zealand privacy obligations in mind, including the Privacy Act 2020. This statement is intended to describe actual product practices rather than reduce any rights you have under applicable law.
Last updated: 16 August 2026.