This Privacy Policy explains how Helitronics Limited, a New Zealand company and the developer of Elixir Check-in (“we”, “us”, “our”), collects, uses, stores and discloses personal information through the Elixir Check-in tablet app for Android and iOS and the Elixir Check-in admin website at www.elixircheckinapp.com.
Elixir Check-in is a self check-in kiosk for New Zealand medical practices. A tablet in the waiting room lists the patients expected in the next little while, and a patient taps their own name to tell the practice they have arrived. The app connects to the practice’s existing Elixir practice management system through Elixir’s official interface. Elixir Check-in is an independent product made by Helitronics Limited. It is not made by, and is not affiliated with, the developer of the Elixir practice management system.
In short
- Your clinic is responsible for your health information. We hold a small working copy of it on the clinic’s behalf, only around the time of your appointment, so the kiosk can work.
- From the clinic’s booking system we keep only your title, first name, surname, “known as” name, appointment times, the clinic and practitioner, and your arrival status. The booking system sends your whole patient record when we look up your name, and we discard the rest of it straight away: we never store your NHI number, date of birth, contact details, clinical notes, alerts, diagnoses, referrals or invoices.
- The waiting-room tablet shows your first name, the first letter of your surname and your appointment time. Nothing is saved on the tablet.
- Some practitioners work from another clinic’s rooms but run their own separate practice. If yours has chosen to, your appointment can show on the tablet in those rooms. Your own practitioner stays responsible for your information.
- Your information is stored on Google Cloud servers in Sydney, Australia, encrypted, and used only to run the check-in service. We do not use it for advertising, we do not sell it, and we do not use it to train AI.
- Clinic staff who sign in to the admin website give us their name and email address. Staff never see patient names on the website.
- You can always check in at reception instead of using the tablet.
- Questions, access and correction requests and complaints: info@elixircheckinapp.com.
1. Who we are
Elixir Check-in is developed and operated by Helitronics Limited, a company incorporated in New Zealand (NZBN 9429043337231). In this policy “Helitronics”, “we”, “us” and “our” all mean Helitronics Limited.
Our Privacy Officer handles privacy questions, access and correction requests and complaints: info@elixircheckinapp.com. Our postal address is available from the Privacy Officer on request.
App identifiers: the iOS bundle identifier and Android package name are com.helitronics.elixircheckin. The app is
published in the Apple App Store and Google Play under the name “Elixir Check-in”.
2. New Zealand law that applies
Helitronics Limited is an “agency” under the New Zealand Privacy Act 2020. This policy is written to meet:
- the Privacy Act 2020, as amended by the Privacy Amendment Act 2025, including Information Privacy Principles 1 to 13 and the new IPP 3A (telling you when personal information about you is collected from someone other than you), which applies to information collected on or after 1 May 2026;
- the Health Information Privacy Code 2020 (HIPC), including Amendment No 2 and its rule 3A, which replaces the Information Privacy Principles for health information held by or for health agencies such as your clinic;
- Part 6 of the Privacy Act (notifiable privacy breaches), the Privacy Regulations 2020 and the Office of the Privacy Commissioner’s guidance;
- the access and correction timeframes in the Privacy Act and the HIPC: we respond as soon as reasonably practicable and within 20 working days.
Your clinic must also keep your health records for at least 10 years after it last treats you under the Health (Retention of Health Information) Regulations 1996. Those records live in the clinic’s practice management system, not in Elixir Check-in. The copies we hold are short-lived working copies described in section 12.
We design and run Elixir Check-in with reference to the Health Information Security Framework (HISO 10029:2022) published by Health New Zealand, including its guidance for suppliers (HISO 10029.4), and the Health Information Governance Guidelines (HISO 10064:2017).
3. Your clinic and us: who is responsible
Your clinic is a health agency under the HIPC. It decides to use Elixir Check-in, it owns its booking records, and it remains responsible for your health information. When your clinic’s booking system sends us the names and appointment times the kiosk needs, we hold that information solely as the clinic’s agent, for processing on its behalf (Privacy Act 2020, section 11). We do not use it for our own purposes. In law, that information is treated as held by the clinic.
Helitronics Limited is itself the agency responsible for the information it collects for its own purposes: the accounts of clinic staff who use the admin website, records about each tablet, security and activity logs, and any support correspondence with us.
Some practices work from rooms belonging to another clinic. Where both use Elixir Check-in, the visiting practice can choose to show its patients on that clinic’s tablets (an external connection). An Admin at each practice must agree first, and either can end it at any time. The practice you are seeing stays responsible for your information, and we act on its instructions as its agent. In this policy, “your clinic” means the practice you have your appointment with. The two practices’ records stay separate.
| Information | Who is responsible | Who to contact |
|---|---|---|
| Patient names, appointment times and arrival status shown on the kiosk | Your clinic (health agency). We process it as the clinic’s agent. | Your clinic’s Privacy Officer or reception. We will help the clinic answer you. |
| Clinic staff accounts on the admin website, tablet records, activity logs, support emails | Helitronics Limited | info@elixircheckinapp.com |
| Your full clinical record, contact details, NHI, invoices and everything else in the clinic’s practice management system | Your clinic. Elixir Check-in never keeps this (see section 4.2). | Your clinic |
4. If you are a patient
4.1 What the waiting-room tablet shows
The tablet lists the appointments due at that clinic within a short window around the current time, including patients of any separate practice working from those rooms that has an external connection with the clinic. By default it shows appointments that started up to 20 minutes ago and appointments starting in the next 30 minutes; your clinic can change these numbers. For each appointment it shows the patient’s first name, the first letter of their surname and the appointment time, for example “Jane D. · 10:30”. When you tap your name, a confirmation asks “Is this you?” and shows your full name, your appointment time and your practitioner’s name so that you can be sure you are checking in the right person. Once you confirm, your name leaves the list.
Because the tablet is in a shared space, other people in the waiting room may see first names and initials on the screen, in the same way they hear names called at reception. We keep what is shown to the minimum needed to recognise yourself. If you prefer not to use the tablet, check in with reception.
If your practitioner uses an external connection, the people who can see your name, appointment time and practitioner on the tablet include the staff of the clinic that owns the tablet, in the same way as anyone else in that waiting room. Your practice agrees to this before the connection starts, and it covers only the clinics and practitioners your practice chooses. Those staff cannot see your appointments on the admin website.
4.2 Information we receive from your clinic’s booking system (indirect collection)
We do not collect anything from you directly. Everything the kiosk shows comes from your clinic’s Elixir practice management system, which sends us a message whenever an appointment or patient record is created, changed or cancelled, and which we also check every ten minutes for the current day. We keep a copy of an appointment only from about 4½ hours before it starts until 4½ hours after; a booking made further ahead is not stored until it comes into that window. Messages about patients with no appointment copied are ignored, and your name is deleted the night after the last copy of your appointments goes. This is collection from a source other than you. Your clinic is responsible for telling you about it under HIPC rule 3A, and this policy is part of how that is done.
From your clinic’s booking system we keep only:
- the booking system’s internal record number for you and for your appointment (not your NHI). Your record number stays on our servers: on the copies tablets receive it is replaced by a code (see section 15);
- your title, first name, surname and “known as” name;
- the appointment start time, the clinic it is at and the practitioner’s name;
- whether the appointment is marked arrived, cancelled or deleted, and when it was last updated.
We never store your NHI number, date of birth, sex or gender, address, phone number, email address, next of kin, ethnicity, clinical notes, alerts, diagnoses, referrals, appointment notes, invoices, custom fields or any other part of your clinical record. When the booking system gives us your record so that we can read your name, the rest of the record is discarded immediately and is never written to our database or our logs.
While a clinic’s connection is first being set up, we may briefly record the complete messages its booking system sends us, so that we can confirm their format. Those recordings are deleted as soon as the format is confirmed and in any case within 14 days.
4.3 What happens when you check in
When you confirm your name, the tablet tells our server which appointment was tapped. Our server marks that appointment as “arrived” in your clinic’s booking system, so reception and your practitioner can see you are here, and records in the clinic’s activity log that a check-in happened, with the appointment’s record number and the tablet that was used. The activity log never contains your name.
If you check in through an external connection, your arrival goes to your own practice’s booking system, and its activity log records which tablet was used. The clinic that owns the tablet is not told who checked in: its log shows only that a check-in for another practice happened on that tablet, and its booking system is not changed. Its reception may not know you have arrived unless you tell them.
4.4 Children
Clinics treat patients of all ages. A parent or guardian normally checks a child in. We hold the same limited information about a child as about an adult, and nothing else.
5. If you are clinic staff using the website
The admin website is where a clinic manages its tablets and its staff access. Accounts are invite-only: an administrator at your clinic adds you before you can create a login. We collect:
- your first name, surname and email address, entered by the administrator who added you;
- your access level (User or Admin) at each clinic, whether your access is active, and when you were added and by whom;
- your password, which is stored only as a one-way hash by Google’s Firebase Authentication, never in a readable form;
- the two-step verification you set up: the secret shared with your authenticator app, held by Firebase Authentication, and, if you choose to add one, your mobile phone number, which Firebase Authentication uses only to text you a sign-in code;
- invitation, email-verification and password-reset links sent to your email address, each of which can be used once;
- when you last signed in, and an entry in the clinic’s activity log, with your email address, for each change you make;
- technical sign-in data that Firebase Authentication keeps for security, such as your IP address and browser type, for a few weeks;
- anything you send us when you ask for support.
Website accounts can never see patient names, appointments or the messages the booking system sends. Staff see tablets, settings, the staff list for their clinic (including colleagues’ names and email addresses) and the activity log.
If your clinic uses external connections, staff also see the name of the other practice, and which of its clinics and practitioners are shared. Admins at both practices are emailed when a connection is requested, approved, changed or ended. To start one, each clinic has a private Company ID that its Admins can give to another practice. Anyone holding that ID, and signed in as an Admin of another clinic, can see the clinic’s name and send it a request. There is no list of clinics.
6. Tablets
A tablet joins a clinic by entering a one-time enrolment code that an administrator creates on the website. Codes expire after 24 hours. On enrolment we record a label for the tablet (such as “Front desk”), its make and model, operating system and app version, and we give it its own sign-in identity that is locked to that one clinic. An external connection doesn’t change this: the tablet never signs in to the other practice, and it holds none of that practice’s credentials. Every five minutes while it is running, the tablet reports that it is still online, with its app version, and it reports whether it is locked to the check-in app when that changes. The clinic sees this on the website so it knows which tablets are active, and its website staff can change each tablet’s settings remotely, including which clinics it shows and its lock mode.
The tablet keeps only its own identity in the device’s secure storage. The appointment list is streamed to the screen and is not written to the tablet’s storage. The clinic’s credentials for its booking system are never on the tablet. The staff PIN that opens the tablet’s settings is checked on our server and is never stored on the tablet; wrong attempts are counted and the tablet is locked out after too many. A clinic can disconnect a tablet from the website at any time, for example if it is lost; the tablet then signs out immediately and shows nothing.
7. What we do not collect
The Elixir Check-in app does not ask for, and does not use:
- location, camera, microphone, contacts, calendar, photos, files, Bluetooth or motion sensors;
- advertising identifiers, App Tracking Transparency permission or any cross-app tracking;
- third-party analytics, advertising or crash-reporting software development kits;
- cookies or similar tracking on the tablet.
The admin website uses no third-party analytics or advertising and sets no tracking cookies (see section 16).
8. How we use information
We use personal information only to:
- show the right appointments on the right tablet and let patients check themselves in;
- tell the clinic’s booking system that a patient has arrived;
- keep the appointment list current as the clinic’s bookings change;
- let authorised clinic staff sign in and manage their tablets and colleagues;
- secure the service: verify identities, apply rate limits, detect misuse, keep an activity log and investigate incidents;
- support clinics and fix faults;
- meet our legal obligations.
We do not use personal information for marketing or advertising, we do not sell it or rent it, we do not build profiles, and we do not use it to train artificial-intelligence or machine-learning models. We do not pass it to any AI service.
9. Who we share information with
We share personal information only with:
- your clinic: arrival status goes back into the clinic’s booking system, and clinic staff see tablet records, the staff list and the activity log on the website;
- another clinic, if your practice has an external connection with it: your first name, surname, appointment time and practitioner’s name are shown on that clinic’s tablet, as described in section 4.1. This happens only on your practice’s instruction, and we do not share anything else with that clinic;
- service providers who host and run the service for us, listed below. They act as our agents, process the information only on our instructions and may not use it for their own purposes;
- authorities, where the Privacy Act or another New Zealand law requires or permits disclosure, for example to prevent a serious threat to someone’s life or health, or in response to a lawful demand. We will tell the clinic unless the law prevents it.
| Service provider | What it does for us | Where |
|---|---|---|
| Google Cloud / Firebase: Cloud Firestore, Cloud Functions, Cloud Scheduler, Cloud KMS, Cloud Logging | Hosts our database and server code, runs the scheduled checks of the day’s appointments and the scheduled deletion of expired records, encrypts the clinic’s booking-system credentials, and keeps server logs | Sydney, Australia (region australia-southeast1) |
| Google Cloud / Firebase: Firebase Authentication (Identity Platform) | Sign-in for website staff and for each tablet’s own identity. Holds staff email addresses and password hashes and tablet identities, with short-lived security logs | United States |
| Google Cloud / Firebase: Firebase Hosting | Serves the admin website. Keeps request logs, including IP addresses, for a few months to detect abuse | Global content delivery network |
| Twilio SendGrid | Sends invitation, email-verification and password-reset emails to website staff. Receives the recipient’s name and email address only. Never used for patient information | United States |
| Elixir practice management system (operated by your clinic) | The clinic’s own booking system. Sends us the appointment and name details described in section 4 and receives the “arrived” status back | As set out in the clinic’s agreement with Elixir |
| Apple App Store, Google Play | Distribute the tablet app. They receive no information from the app about patients or clinics | Global |
Google is independently certified against ISO 27001, SOC 1, SOC 2 and SOC 3 for these services (and ISO 27017 and ISO 27018 for most of them) and processes personal information under its Cloud Data Processing Addendum.
10. Information held outside New Zealand
There is no Google Cloud region in New Zealand. Our database, server code and encryption keys are in Sydney, Australia. Sign-in services and account emails are provided from the United States. These providers hold the information as our agents for storage and processing only, so under section 11 of the Privacy Act and the Privacy Commissioner’s guidance this is not a disclosure outside New Zealand under IPP 12 or HIPC rule 12. We nevertheless choose providers that are bound by written data-processing terms, encrypt information in transit and at rest, and are independently audited, so that it is protected to a standard comparable to New Zealand law.
We do not otherwise disclose personal information to anyone outside New Zealand. Patient names and appointment details are never sent to the United States: they stay in the Sydney region.
11. Security
We take reasonable safeguards against loss, misuse and unauthorised access, modification or disclosure (IPP 5 and HIPC rule 5), including:
- encryption of all connections (HTTPS/TLS) between tablets, the website, our servers, the clinic’s booking system and our providers;
- encryption of all stored data at rest by Google Cloud, and additional envelope encryption of each clinic’s booking-system credentials with a key held in Google Cloud KMS;
- strict separation between clinics: a tablet can only read its own clinic’s appointments, for the clinics ticked on that tablet, plus appointments another practice has chosen to share with its clinic through an active external connection, enforced by server-side security rules on every read. Ending a connection stops that access immediately;
- data minimisation: only the fields listed in section 4 are ever written to our database, and patient names are kept out of logs and the activity log;
- tablets never hold the clinic’s booking-system credentials or the staff PIN, and can be disconnected remotely at any time;
- single-use enrolment codes that expire after 24 hours, single-use invitation links that expire after 30 days, mandatory email verification, rate limiting of sign-in and invitation requests, and lock-out after repeated wrong PINs;
- two-step verification on every website sign-in (an authenticator app, or a text message as the backup), checked by our servers on every request; website sessions end after 20 minutes without activity and 12 hours after signing in;
- all changes made through server code that checks the caller’s identity and level; website users and tablets cannot write to the database directly;
- an activity log of significant events for each clinic, which the clinic can review on the website;
- access to production systems limited to Helitronics personnel who need it, protected by multi-factor authentication;
- no third-party software development kits in the app that could carry information elsewhere.
No system is perfectly secure. If something goes wrong we follow the breach process in section 14.
12. Retention and deletion
We keep personal information only as long as it is needed for the purposes above (IPP 9 and HIPC rule 9). The copies we hold are working copies; the clinic’s own records, and the 10-year retention that applies to them, live in the clinic’s booking system.
| Information | Kept for |
|---|---|
| Appointment records (times, arrival status, check-in record) | Deleted 4½ hours after the appointment’s start time (checked every ten minutes). Appointments more than 4½ hours ahead are not copied at all; each one is loaded as it comes into that window |
| Patient names cached from the booking system | Deleted when the booking system tells us the patient record was deleted, and otherwise on the night after the copy of the patient’s last appointment is deleted (within two days of the appointment) |
| Recordings of booking-system messages made during connection set-up | Deleted when the format is confirmed, and no later than 14 days after capture |
| Log of messages received from the booking system (message number, type, time received and the record number it concerned, not its content) | 30 days |
| Tablet records | While the tablet is connected; 12 months after it is disconnected |
| Staff accounts | While the account is active; 12 months after it is deactivated, or sooner on request, unless we need it to investigate an incident |
| Unused invitations | 30 days, then the invitation is void; the record is removed when an administrator cancels it |
| Clinic activity log | 12 months |
| External connection records (the two practices, what was shared, and who approved it) | While the connection is active; 12 months after it ends or is declined. Shared appointments are not copied: they follow the appointment records above |
| Server logs (Cloud Logging) | 30 days |
| Firebase Authentication security logs and Firebase Hosting request logs | A few weeks and a few months respectively, on Google’s schedule |
| Everything for a clinic that stops using Elixir Check-in | Deleted within 30 days of the clinic’s written request, except what we must keep by law or to resolve a dispute |
Deleted information may persist in encrypted backups for a short period until those backups are rotated, and is not used in the meantime. We delete securely, including from backups, in line with the Privacy Commissioner’s guidance on disposal of health information.
13. Your rights: access, correction and choice
Patients
- You can ask your clinic to confirm what information it holds about you, to see it, and to have it corrected (HIPC rules 6 and 7). Because everything we hold comes from the clinic’s booking system, corrections made there flow through to us automatically, usually within a minute.
- You can ask your clinic, or us, what Elixir Check-in holds about you. We will answer the clinic’s request, or yours with the clinic’s agreement, as soon as practicable and within 20 working days, at no charge.
- Using the tablet is optional. You can check in at reception instead.
Clinic staff
- You can see and change your own name on the website. Your administrator can change your access level or deactivate your access. To change the email address on your account, ask us.
- You can ask us for a copy of the information we hold about you, or to correct it, at info@elixircheckinapp.com. We respond within 20 working days.
- You can ask us to delete your account once your administrator has deactivated it. We will do so unless we need the record to investigate an incident, and we will tell you if that is the case.
If we refuse a request we will tell you why and how to complain. If we correct something we will note the correction and, where you ask, attach a statement of the correction you sought.
14. Privacy breaches
A privacy breach is unauthorised or accidental access to, disclosure, alteration, loss or destruction of personal information, or an action that stops a clinic from accessing it. If we become aware of a breach affecting Elixir Check-in we will:
- contain it immediately, for example by disconnecting a tablet, revoking credentials or taking a function offline;
- tell every affected clinic without delay, so the clinic can meet its own obligations as the health agency;
- assess whether the breach is likely to cause serious harm. If it is, it is a notifiable privacy breach under Part 6 of the Privacy Act, and we (or the clinic, for its information, with our help) will notify the Office of the Privacy Commissioner as soon as practicable, which the Commissioner expects to be within 72 hours, and notify affected people unless an exception in the Act applies;
- record what happened and what we changed to stop it happening again.
Clinic staff who suspect a breach should contact us straight away at info@elixircheckinapp.com and tell their clinic’s Privacy Officer.
15. Unique identifiers
We never use the NHI number. We use the record numbers that the clinic’s booking system has already assigned to patients and appointments, as the clinic’s agent, to match the two systems. A patient’s record number is kept only on our servers. On the appointment copies that tablets receive, it is replaced by a code worked out from it with a secret key for each clinic. The code can’t be turned back into the record number, means nothing outside Elixir Check-in, and is used only to find that patient’s appointments. Tablets, including another clinic’s tablet where an external connection is active, receive the appointment’s record number and that code in memory, and never display them. Each tablet and each staff account has its own identifier that we create and that is not used by any other agency (IPP 13 and HIPC rule 13).
16. Cookies, diagnostics and advertising
The admin website keeps your sign-in session, and the time of your last activity, in your browser’s own storage so that you stay signed in for up to 20 minutes between actions; it sets no cookies of its own. We do not use analytics, advertising or social-media cookies, and we do not use advertising networks. The tablet app uses no cookies and includes no analytics or crash-reporting kits, and it sends no diagnostic reports. Faults are recorded in our server logs, which never contain patient names. This page sets no cookies.
17. What your clinic is responsible for
Clinics using Elixir Check-in remain the health agency for their patients. In particular, a clinic should:
- tell patients, in its own privacy statement and with a notice beside the tablet, that it uses a self check-in tablet and that names and appointment times are shown on it, which satisfies HIPC rules 3 and 3A for this information;
- before sharing through an external connection, be authorised to do so, tell its patients their name appears on a tablet at that location, and share only the clinics and practitioners needed;
- if it shows another practice’s patients on its tablets, switch that on only for tablets in the right rooms, use it only for check-in, and pass any patient queries to that practice;
- keep its Company ID private, and replace it if it reaches someone it shouldn’t;
- position tablets so that the screen is not readable from a distance, and keep the appointment window short;
- give website access only to staff who need it, use the Admin level sparingly, deactivate staff who leave, and change the staff PIN when they do;
- disconnect any tablet that is lost, stolen or repurposed, and use the device’s own kiosk or guided-access lock;
- keep its booking-system credentials secure and tell us immediately if they may have been compromised;
- have a Privacy Officer and a privacy breach process, and handle patients’ access and correction requests;
- tell us if it wants its data deleted when it stops using Elixir Check-in.
18. Changes to this policy
We may update this policy as the service or the law changes. The version number and dates at the top show when it last changed. For material changes we will tell each clinic’s administrators by email before the change takes effect, and clinics can ask us for earlier versions. The current version is always at www.elixircheckinapp.com/privacy.
19. Contact and complaints
- Privacy Officer
- Helitronics Limited, New Zealand · info@elixircheckinapp.com
- Patients
- Contact your clinic first. Its Privacy Officer is responsible for your health information, and we will help the clinic answer you.
- Not satisfied?
- You can complain to the Office of the Privacy Commissioner, New Zealand: www.privacy.org.nz, phone 0800 803 909, email enquiries@privacy.org.nz.