A local-first family health record app is often described in terms of using a device to create, keep and use records. For this guide, however, the label is only a starting point for questions. It does not, by itself, establish where every copy of a family record is held or what happens when information is backed up, exported, synchronised, restored or deleted.
That distinction can matter when a parent or trusted caregiver keeps appointment notes, symptoms, medicines, measurements, documents or other sensitive family information in one place. Before choosing an app, look beyond broad privacy wording and seek clear information about storage, handling and available controls.
This guide offers a practical comparison framework for Australian parents and trusted caregivers. It is general information, not medical advice, legal compliance advice or verification of any particular app.
What “Local-First” Means for Family Health Records
There is no source-backed universal checklist in this guide for the term “local-first”. For this guide, it means an editorial description of an app designed so a useful copy of family records is held and used on a person’s device, rather than ordinary access depending entirely on a vendor-operated database.
Use that description as a prompt to ask what happens at each stage of handling information. Relevant questions include where an entry is first saved, whether ordinary access depends on connectivity, and whether information is later sent to another device or service.
Two products may use similar language while describing different arrangements for synchronisation, accounts, backups, diagnostics or exports. A more useful assessment asks which information is on the device, what other copies may exist, and which controls are available to the family.
Where Records Are Stored and What May Move
Start with the active record: the information the app displays and changes in normal use. Product documentation may identify whether that record is held on a phone or tablet, on a remote service, or in more than one place. Consider any secondary copies separately rather than treating them as part of one undifferentiated record.
Questions about secondary copies can cover device backups, exports saved by a user, synchronisation, account functions, analytics, crash reporting and customer support. These are separate handling purposes or pathways to ask about, even if they concern the same family information.
OAIC mobile privacy guidance addresses privacy information about personal information handling, including collection, storage, purposes, use, disclosure, access, correction and relevant data location. When comparing products, look for explanations that identify those matters in plain language. Do not treat a statement that records are “stored locally” as an answer to every question about transmission or other copies.
What Local-First Does Not Guarantee
The local-first label is not, on its own, verification of privacy, security, continuous access or recoverability. Those matters require product-specific information and may also depend on device settings and the way a family uses an app.
In particular, the label alone does not establish that:
- the app can be used fully without an internet connection;
- no information is sent from the device;
- all records, files, backups and exports have the same protections;
- another household device has a current copy;
- deletion removes every copy held in backups, exports or services; or
- records can be restored after a device is lost or replaced.
OAIC security guidance treats security as an information-lifecycle issue. It identifies distinct considerations including access controls, encryption where appropriate, backups, recovery testing, retention, and destruction or de-identification. Parents and caregivers do not need to audit software code to use this framework: they can ask whether product documentation explains the relevant controls clearly and specifically.
Backups Depend on the App and Device Setup
A backup and the active record are different things to assess. Synchronisation between devices, an export created by a user and a backup intended for recovery should also be considered separately.
Apple documents iCloud backups and computer backups for iPhone and iPad, with differing storage locations and protections. Apple also documents encrypted computer backups as an option that requires a password. These platform documents do not verify whether any particular family health app is included in a backup, excluded from it, or completely restorable in a particular setup.
Before relying on a backup, check the current app documentation and the settings on the device being used. Useful questions include whether app data is eligible for the selected backup method, whether attachments are included, what is needed for restoration and whether the recovery process has been tested. If the documentation does not answer those questions, do not assume that records visible on a device have a recoverable copy elsewhere.
Exports, Restoration and Deletion Are Different Controls
Export, restoration and deletion should be assessed as different controls. An export may provide a copy in a stated format, but it does not by itself show that the same information can be restored into an app. Ask whether an export can be imported, whether attachments and record relationships are included, and whether the exported format can be read without the original app.
Restoration is a separate question. Documentation can identify the event it is designed for, the source used for restoration and any information that may not return afterwards. The existence of an export function alone is not verification of a complete restoration path.
Deletion also needs specific explanation. Ask separately about deleting one entry, removing a profile, clearing app data, uninstalling an app and deleting an account. Ask what each action covers, whether it affects other copies, and whether further steps are needed for user-created exports or backups. Clear documentation should distinguish the scope of a deletion control from copies that it does not cover.
Questions to Ask Before Choosing a Family Health App
Use these questions to turn a broad local-first or privacy statement into a practical comparison:
- Primary storage: Where is the active family record held, and what does the documentation say about access when connectivity is unavailable?
- Network movement: What information is sent from the device, for what purpose, and which organisation receives it?
- Other services: Does the documentation describe account, synchronisation, analytics, crash-reporting or support services, and the information they may handle?
- Device backup: Does the app documentation explain backup eligibility, included data and settings that may affect backup behaviour?
- Export: Which formats are available, are attachments included, and can the files be opened without the app?
- Restoration: Is there a documented method for restoring the record to a replacement device?
- Deletion: What does each deletion option cover, and what does the documentation say about backups, exports and other copies?
- Transparency: Does the privacy information address collection, storage, purposes, access, correction and relevant data location in understandable terms?
Keep the answers for the products being compared. Specific documentation is generally more useful for comparison than broad labels such as “private”, “secure” or “local”. Recheck relevant documentation after changes to an app, device operating system or family setup.
Key Takeaways for Privacy-Conscious Parents
- For this guide, local-first is an editorial design description, not proof that all information remains on one device.
- Assess the active record separately from synchronised copies, device backups, user exports and service-related handling.
- Backup, export, synchronisation, restoration and deletion are different controls to investigate.
- Ask what a deletion control covers rather than assuming it affects every copy.
- Look for current, specific and understandable product documentation.
Sources and verification
The following sources provide general Australian privacy guidance and Apple platform backup guidance. They do not verify the implementation of any particular family health record app.
Office of the Australian Information Commissioner — Guide to securing personal information
Apple Support — Backup methods for iPhone, iPad and iPod touch
Apple Support — About encrypted backups on your iPhone, iPad or iPod touch
