Privacy policy
How the Rythmo apps, this website, the forms and the Rythmo email and Instagram accounts handle information.
Effective 14 November 2026
The short version. The Rythmo breathing rate apps do not collect, send or share any information about you or anyone you measure. Readings stay on your device. Rythmo Triage MCI, which is licensed to organisations, checks its licence with our licence server. On every setup it also shares each incident's patients, their triage categories and times with that organisation's commanders through our commander server. That information belongs to the organisation, and only its commanders can see it. The only personal information Rythmo receives is what you choose to give: answers in a survey or form, an email, or a message on Instagram. It is never sold.
Who we are
Rythmo is a business name of Lachlan Sallabank, a sole trader in Victoria, Australia, ABN 69 631 803 003. In this policy, "Rythmo", "we" and "us" mean Lachlan Sallabank trading as Rythmo. You can reach us at hello@rythmo.com.au.
A business of our size may not be bound by the Australian Privacy Principles, but we follow them anyway, and the rights in this policy apply to everyone, wherever you live.
What this policy covers
- The Rythmo breathing rate apps for iPhone, Apple Watch, Android, Wear OS and Garmin watches.
- Rythmo Triage MCI for iPhone, which is licensed to organisations for their health professionals, and its licence server.
- Rythmo Command, which is licensed to organisations for their event medical teams, ski patrols and rescue organisations, and its commander server.
- This website, rythmo.com.au, including the tap demonstration.
- The survey, the register of interest form and the Rythmo Triage MCI enquiry form, which run on Tally.
- Email to hello@rythmo.com.au, and the @rythmo.au Instagram account.
The breathing rate apps
This section is about the Rythmo breathing rate apps for iPhone, Apple Watch, Android, Wear OS and Garmin watches. Rythmo Triage MCI has its own section below.
What the apps do not do
- No accounts or sign in.
- No analytics, advertising, tracking or crash reporting, and no third party code that does any of those things.
- No network access. The breathing rate apps send nothing over the internet and work with no connection.
- No access to Apple Health, Health Connect, your location, contacts, camera, microphone or photos.
- No patient identifiers. There is nowhere to enter a name, an age, a note or a patient ID.
What the apps store, and where
When you finish a measurement of 3 taps or more, the app saves a history entry holding the rate per minute, the time it was saved, how long it took, how many taps you made, the confidence level and whether the taps were flagged irregular. The app keeps the last 10 entries and your settings, such as whether vibration is on.
This is stored only on the device running the app: in the app's private storage on iPhone, Android, Wear OS and Apple Watch, and in the app's storage on a Garmin watch. Rythmo cannot see it. On iPhone it may be included in your own device backup, such as iCloud, depending on your settings. That backup belongs to your Apple account and Rythmo has no access to it.
Deleting app data
Use Clear all on the History screen (iPhone, Android, Wear OS and Apple Watch) or Clear history in the menu (Garmin). Uninstalling the app also deletes its history.
Links in the phone apps
The iPhone and Android apps contain links to rythmo.com.au, this privacy policy, the device register of interest on Tally (labelled as a survey in current versions of the apps), and the @rythmo.au Instagram account. A link opens in your web browser, or in the Instagram app if you have it, outside Rythmo. No link carries a tag, a price, a reading, a time, anything from your history or anything about your device. The Apple Watch, Wear OS and Garmin apps contain no links. Once you follow a link, that service's own privacy policy applies.
App stores
Apple, Google and Garmin handle downloads and updates under their own privacy policies. They give developers summary statistics, such as download counts, and crash reports where you have chosen in your device settings to share them with developers. Rythmo does not receive your name or contact details from any app store.
Rythmo Triage MCI
Rythmo Triage MCI is a mass casualty triage app for iPhone. It is licensed to organisations, such as ambulance services, for their registered health professionals, and the organisation decides how it is used. Patient information entered in the app belongs to that organisation and is handled under its own privacy policy, not this one.
What stays on the phone
Incidents, patients, their triage categories, tag numbers, location notes and times are stored in the app's private storage on the phone, and are left out of device backups. The details set out below also go to our commander server, so the organisation's commanders can see them. Otherwise they leave the phone only if the responder exports an incident through the share sheet, to wherever their organisation has approved. From then on they are in the organisation's own records.
What the app sends to Rythmo
The app contacts our licence server to activate, and then about once a day, or when the responder taps Check for updates, to check that the organisation's licence is current. It never checks in during an open incident. If the responder taps Leave this service, or This isn't my service straight after activating, it contacts the server once more to say the phone has left, so the organisation's place for it is freed.
- When activating, once: the organisation's activation code, a random install ID the app makes up when it is installed, the app version and the platform.
- When checking in: the organisation's ID, the install ID, the licence and protocol version the phone holds, and the app version.
- When leaving the service: the organisation's ID, the install ID and the app version.
The licence server refuses any other information, and nothing about a patient or an incident goes to it. There is no account or sign in, no analytics, advertising, tracking or crash reporting, and no third party code that does any of those things. The app uses the camera only to read a code: a triage tag's barcode, or a QR code to join an event or sign in as a commander, instead of typing the code. It takes and keeps no picture.
What the licence server keeps, and why
For each phone: the install ID, the organisation, the platform, the app version, when it was activated, when it last checked in, whether it has been withdrawn, and when it left the service if it did. The install ID is not linked to a name, email address or phone number, and it is not the phone's own identifier: deleting the app deletes it, and reinstalling makes a new one. For about a day, we keep a scrambled form of the internet address of a failed activation, to stop people guessing codes. It is deleted the next time anyone tries to activate after the day has passed, so in a quiet week it can stay a little longer. We also keep a log of activations, refused activations, phones leaving and licence changes. For each, it records the time, the install ID, the app version and, as needed, the platform, the licence and protocol version the phone reported, and the reason for a refusal. That includes the install IDs of phones that were refused and never activated.
We use this only to run the licence: to activate phones up to the organisation's limit, to let an organisation withdraw a lost phone, to free a phone's place when it leaves the service, and to deliver protocol updates its clinical lead has approved. We do not use it for analytics or advertising, and we only share it with the organisation that holds the licence, if it asks which of its phones are active.
Where it is held
The licence server runs on Cloudflare. Its database is held in Cloudflare's Oceania region, and requests pass through Cloudflare's global network.
Sharing with the commander view
Every setup shares with the organisation's commander view, for mass casualty triage and for Rythmo Command, in simulation and in real use. The commander view is a web page, or the commander screens in the app, where the organisation's commanders see an incident or event as it happens. For each patient the app sends:
- the tag number, and the patient's number on that phone;
- the triage category the app suggested and the one the responder chose, and whether they differ;
- the times, and the patient's status, with the destination if one is entered;
- the patient's estimated age and sex, if the clinician enters them;
- the phone's location when the category was set, if the responder allows location.
On an event setup it also sends the triage note, what's happened (from fixed lists: the complaint, body areas, and whether the patient is conscious, breathing normally, bleeding or pregnant) and the plan: Medical or Injury and a note. It also sends the incident's or event's name and start time. On other setups, notes stay on the phone. Answers to the triage questions always stay on the phone. Tapped breathing and pulse rates stay on the phone too, except in a training incident set up by a commander, where the tapped rates go to the commander view for the after action review. The server refuses anything else.
Commanders can also add notes to a patient, the destination and who transported them. These are kept on the commander server with the rest of the incident.
Our commander server keeps:
- this information;
- the install ID and the app version;
- a label for each phone, such as "Phone 3";
- a scrambled form of each phone's access token and of each commander's sign-in session.
For about a day, it also keeps a scrambled form of the internet address of a failed sign-in or join, to stop guessing. Only that organisation's commanders can see the incident or event, after signing in with the organisation's commander code. The commander server runs on Cloudflare, separately from the licence server, with its database in Cloudflare's Oceania region. How long it is kept is set out below.
The commander page shows a map. To draw it, the commander's browser loads map pictures from a map company: OpenStreetMap for the street map, and Esri for the satellite view. Those requests show the map company the area being looked at and the commander's internet address, never the patients' positions, which the page draws itself. A commander can also open a place in Google Maps, which sends that one position to Google only when they click it.
To put names on the map, our commander server keeps a list of Victorian place names, such as racecourses, showgrounds, parks, halls and towns, built from Vicmap and OpenStreetMap open data. When an event's area is set up, or grows, our commander server sends only the outline of that area, a box on the map, to Vicmap Address, the Victorian Government's open address service, so the street addresses inside it can be copied to our server. The request comes from our server, not from anyone's phone or browser, and carries nothing about a person. Nothing about an incident or a patient is ever sent to an outside service.
Rythmo Command: events and exercises
Rythmo Command runs events and exercises, in simulation and in real use. Phones join an event as a crew or a post, and the commander follows it on the commander page or on their own phone. On those setups, as well as the patient details above, our commander server keeps:
- the event's teams, which phone is in which team, and each crew's status with its time;
- each incident, the teams sent to it and when they accepted, and handovers between teams;
- the call taken for an incident: the answers as the caller gave them, a free-text notes box and the short brief built from them;
- the commander's log entries and notes, and free-text pages sent to a team;
- the event's landmarks, bases and site plan picture;
- for each crew phone, an Apple push token so it can be paged, and the alert level and page sound chosen on that phone;
- for a phone signed in with the commander code, its Apple push token, so pages from the commander page reach it. It is kept with that sign-in and deleted when the sign-in ends: when the commander signs out, when the event ends, or after 24 hours. It isn't kept in the server's audit log and isn't used for anything else;
- each crew phone's rough location, as below.
The notes boxes are free text, so anything typed there is kept. Please don't type names or other identifying details into them. Pages and handovers reach a phone through Apple's push notification service.
Location. If the responder allows location while using the app, a phone on a crew in an active event sends a rough position about every 5 minutes while the app is open, and when the crew taps a status. It uses the "While using the app" permission, never Always. It stops when the phone leaves the event, the event ends, the phone joins a post, or location is turned off. A post phone sends a place only when someone sets the post's place to where the phone is. The server keeps only the latest location for each phone, replacing the one before, and deletes it when the event ends. Refusing location changes nothing else.
Face ID. On a commander's phone, the commander screens lock with Face ID or the phone's passcode. Face ID runs on the phone's own secure hardware. The app only learns whether the lock opened, and no face data is stored or sent.
Dictation. A commander can dictate a log entry on their phone. The speech is recognised on the phone itself and the audio never leaves it. If the phone can't do that, the microphone button doesn't show. Only the finished text is kept, in the log. That's the app's own Dictate button. The microphone on the iPhone keyboard is Apple's dictation, and Apple may send that speech to its servers.
How long commander records are kept. The commander page is a working view of an event or exercise. It is not the organisation's patient record, which the organisation keeps itself. Commander records are not deleted because of their age. They stay until the organisation deletes them: signed in with the organisation's commander code, a commander can delete an incident once it is closed, or an event once it has ended. Records closed more than 12 weeks ago are marked "12+ weeks" as a reminder to delete them. Ending an event deletes its phones' push tokens. If the organisation's licence ends, everything it has on the commander server is deleted 3 months later, unless it renews and a phone rejoins within that time. We can set this up to suit an organisation's own requirements. A deleted record can stay in our encrypted backups for up to about 5 weeks (we make a backup every night and keep the newest 35).
How long we keep it
We keep a phone's record while its organisation's licence is in force. Once a month we delete the phone records of every organisation whose licence ended more than 12 months earlier, so a record is deleted 12 to 13 months after the licence ends. A phone withdrawn while the licence is still in force is kept until then, because its record is what stops it being activated again. A phone that leaves the service stops counting towards the organisation's limit straight away, and its record is deleted on the same schedule. The log of activations and licence changes is kept longer, as a record of which protocol each organisation used and when. When a phone's record is deleted, its install ID in that log is replaced with a plain number, so the log no longer identifies the phone.
A deleted licence or account record can stay in our encrypted backups for up to about 3 months (we make a backup of the licence server once a month and keep the newest three).
Questions
Responders should ask their own organisation first about patient records and exports. For anything about the app or the licence server, email hello@rythmo.com.au.
This website
Hosting
This site is hosted by Cloudflare. Like any web host, Cloudflare processes technical request data, such as your IP address, browser type and the pages requested, to deliver the site and protect it from abuse.
No cookies, one optional video, no third party fonts
The site sets no cookies. Until 29 September 2026 the link at rythmo.com.au/survey set one functional cookie that remembered the survey price you were shown. That survey is no longer linked, and the link now leads to the register of interest and clears the old cookie if your browser still has it.
Fonts are served from this site, so your browser makes no requests to Google or any other font service. The Instagram links are plain links.
The Rythmo Command page has a video. Nothing is requested from YouTube when the page loads. The video loads only after you press play, and then it comes from YouTube's privacy-enhanced address (youtube-nocookie.com), so YouTube receives your IP address and browser details and may store its own data under Google's terms. If you would rather not, do not press play; the page also links to the video on YouTube.
Analytics
We use Cloudflare Web Analytics to count page views and similar totals, such as which pages are visited and which links are followed. It does not use cookies or local storage, does not build a profile of you, and does not track you across other sites.
The tap demonstration
The demonstration runs entirely in your browser. Your taps are not sent anywhere and nothing is saved.
The survey and the forms
The survey, the register of interest form and the Rythmo Triage MCI enquiry form run on Tally, a form service from Tally BV in Belgium, which stores responses on our behalf. Tally says form data is stored in Europe, and lists Google Cloud hosting in Belgium among its subprocessors. See Tally's GDPR page and Tally's privacy policy.
The call buttons on our pages, including the button at the top of every page, open a booking page on Cal.com, a scheduling service from Cal.com, Inc. in the United States. When you book, Cal.com collects your name, email address, the time you choose and anything you add in the booking form, and shares the booking with us. The button carries a tag for the page you came from. Please do not include patient information. See Cal.com's privacy policy.
What each form collects
- Rythmo Triage MCI enquiry form: your name, work email, organisation, role, the kind of organisation, what you would like to talk about and any message you add, with a tag for the button you came from.
- Register of interest: your email address, any optional answers you choose to give, a tag for the page or app you came from, and, if you ask to test an app, the platform you chose.
- Survey (no longer linked since 29 September 2026): your role, your work setting, your answers, the price shown in the survey, a tag for the page or app you came from and, if you chose to leave it, your email address.
Why
The Rythmo Triage MCI enquiry form is used only to reply to you about Rythmo Triage MCI. The other forms are used to decide what gets built, and, if you register your interest, to email you if there's news about the device or an app test build. If you ask to test an app, we also use your email to invite you to the test. If you left your email in the survey to hear how Rythmo goes, we use it to send you updates. Survey answers are only ever reported as totals, never in a way that identifies you.
How long we keep it
Rythmo Triage MCI enquiries are kept while we are in touch with you or your organisation, and deleted when you ask. Register of interest emails are kept until the list has served its purpose or you ask to be removed, whichever comes first. Survey responses are kept to inform product decisions.
Email to hello@rythmo.com.au runs on Google Workspace. Your message is kept in that account so it can be answered.
Email updates
Updates to people who asked for them in the survey or the register of interest are sent through Brevo, an email service from Sendinblue SAS in France, which holds your email address on our behalf to send them. Brevo says it stores data in the European Union. Brevo records whether each email was delivered and opened and which links were clicked, which we use only to check the update arrived. Every update has an unsubscribe link, and once you unsubscribe you won't get another. See Brevo's privacy policy.
If you follow, message, tag or comment on @rythmo.au, that information is handled by Meta under Instagram's terms and privacy policy. Rythmo sees what Instagram shows any account, such as your username and the messages you send us.
Sharing
We do not sell, rent or trade personal information, and we do not share it for advertising. Information is only handled by the service providers named in this policy, for the purposes described here, or where the law requires it.
Information held outside Australia
Some of these providers store or process information outside Australia: Cloudflare runs a global network and is based in the United States, although the Rythmo Triage MCI licence and commander databases are held in its Oceania region; Tally stores form data in the European Union; Cal.com is based in the United States; Brevo stores email update lists in the European Union; Google Workspace and Meta store data in the United States and other countries. Each handles information under its own privacy terms.
Your rights
Email hello@rythmo.com.au to ask what information we hold about you, to correct it, to have it deleted, or to be removed from the register of interest. We will reply within 30 days. We may need to confirm it is you before acting on a request. Readings in the breathing rate apps are never held by Rythmo, so delete those with Clear all, Clear history or by uninstalling the app. Rythmo Triage MCI is different. Our commander server keeps a working copy of the patient details set out above (tag number, category, times, status, estimated age and sex, location and notes) until it is deleted. It is a working copy for the service, not the organisation's own record, which the organisation keeps itself. A commander can delete a closed incident or an ended event, or the organisation can ask us to.
Complaints
If you are unhappy with how your information has been handled, email hello@rythmo.com.au first. If that does not resolve it, you can contact the Office of the Australian Information Commissioner at oaic.gov.au. If you live outside Australia, you can also contact the data protection authority where you live.
Children
Rythmo is made for adults, particularly health professionals and trainees. It is not directed at children and does not knowingly collect information from them.
Changes to this policy
If this policy changes, the new version will be posted on this page with a new effective date. If an app ever starts collecting more information than this page describes, this page will say so before that version is released.