Our planned approach to protecting your information

Health information is intended to be held in Australian data-centre regions of a major cloud provider. If any overseas provider is ever introduced, we will name the country and safeguards first, as Australian Privacy Principle 8 requires.

Everything between your device and Nest of Kin travels over current TLS encryption.

Documents and sensitive fields are encrypted where they are stored.

Encryption keys sit in managed key infrastructure, separate from the application database, so a copy of the database alone is not readable.

Backups exist for disaster recovery, stay in Australia, and follow a defined rolling schedule. Deletions flow through to backups within that cycle.

Only the information needed for the function you asked for is processed. Logs record that an action happened, not a second copy of your health information.

Your full record, on any device you sign in from.

Sharing is item by item, off until you turn it on, and revocable at any time. A clinic cannot grant itself access or silently request it.

Inside a connected clinic, access follows role: scheduling staff do not see clinical documents; specialists see the shared record for their patients.

A small number of authorised staff may access systems for support, security or legal obligations, under access control and logging. Routine browsing of records is prohibited.

Hosting and security providers may process information only to run the platform.

Access, sharing changes and sign-ins are recorded, and you can read the log yourself and request it as a PDF.

Categories such as document type, dates, provider, treatment cycle, or laboratory values copied word for word — you tick what is allowed.

Kina receives only the document you ask it to organise — minimum necessary access.

Proposed information is shown to you and must be confirmed line by line. Unconfirmed items are discarded and never shared.

Information Kina adds stays labelled as AI, with its source document retained.

Storage location and processing location are different questions. Your documents are intended to be stored in Australia. When you ask Kina to read one, the text of that document is sent to a third-party AI provider for processing, which today may occur outside Australia. We intend to name the provider and its processing regions in the product, prefer Australian processing regions as they become available, and keep Kina optional so you can decline this entirely.

The intended contractual position is that the provider processes the text to answer your request and does not retain it afterwards or use your information to train general models.

Kina does not diagnose, interpret results, predict outcomes or change medication.

Delete it, and choose whether journey information derived from it goes too.

Remove the entry; the source document stays unless you delete that as well.

Request deletion from Account & data. We aim to action it within 30 days, including within backups on the next cycle.

Minimal records that an action occurred, and anything a legal obligation requires. Documents your clinic copied into its own medical record follow that clinic's retention rules — commonly at least seven years.

Turn off Kina, research contribution or clinic sharing at any time. It stops future use immediately.

Ask for a copy of your information; we aim to respond within 30 days.

Have anything inaccurate or out of date fixed. Most items you can edit yourself.

If a breach is likely to cause serious harm, the Notifiable Data Breaches scheme requires us to tell you and the OAIC.

Where they apply, such as the Health Records and Information Privacy Act 2002 (NSW) and the Health Records Act 2001 (Vic).

At the concept stage there is no live privacy contact channel yet — a named privacy contact and published address will be in place before any real patient information is held. Independently of us, you can always complain to the OAIC or your state health privacy regulator.