Does the Privacy Act apply to your business?
The OAIC says most small businesses, meaning those with an annual turnover of $3 million or less, are not covered by the Privacy Act, and that turnover includes all income from all sources. Some businesses are covered regardless of turnover, including health service providers, businesses that trade in personal information and contractors providing services under a Commonwealth contract. If you are covered, the Australian Privacy Principles apply to how an AI system handles personal information. If you are not, the OAIC's guidance is still a sensible standard to work to.
Are staff HR files exempt?
A private sector employer's handling of employee records is exempt from the Australian Privacy Principles where the act or practice is directly related to a current or former employment relationship. The OAIC notes limits. The exemption does not cover unsuccessful job applicants, contractors handling the personal information of another organisation's employees, or volunteers. Whether a particular AI search use falls inside the exemption depends on the facts, so get advice before relying on it. HR files rarely belong in a general staff knowledge search in any case, because most staff should not see them.
Can customer or patient records go into AI search?
The OAIC says APP 6 applies when personal information is put into an AI system. Information can be used for the purpose it was collected for. A secondary use needs the person's consent, or must be one they would reasonably expect that is related to the original purpose (directly related, for sensitive information). Staff searching job files to answer that customer's question may fit the original purpose. Feeding the same files into a tool for an unrelated purpose may not. Record your reasoning for each document set before it is indexed.
What does the OAIC expect before you adopt an AI product?
The OAIC's guidance on commercially available AI products asks organisations to do due diligence on whether a product suits its intended use. That includes whether it has been tested for that use, how human oversight will work, the privacy and security risks, and who will have access to personal information that is entered or generated. The OAIC recommends a privacy by design approach that includes a Privacy Impact Assessment, and updating privacy policies with clear information about the use of AI. Put these questions to any vendor.
- Has the product been tested for answering questions from your kind of documents?
- Who at the vendor and its subprocessors can access passages, questions and answers?
- Where are passages, questions and logs stored, and for how long?
- How will a person check answers that affect a customer, patient or employee?
What security steps does APP 11 require?
APP 11 requires reasonable steps to protect personal information from misuse, interference and loss, and from unauthorised access, modification or disclosure. The OAIC asks organisations to take active steps to make sure an AI system will not expose their personal information holdings. For knowledge search, exposures to check include an index that ignores source permissions, question logs that record personal details and copies of passages held by a model provider. Filter retrieval by each user's access, limit who can read the logs, set a retention period and confirm in writing what the provider stores.
Why not use public AI chatbots for this?
The OAIC recommends, as best practice, that organisations do not enter personal information, and particularly sensitive information, into publicly available generative AI tools, because of the significant and complex privacy risks involved. It also says that AI output about an identified or reasonably identifiable person, including incorrect or artificially generated information, is personal information. Staff pasting a customer complaint into a free chatbot to draft a reply create exactly that risk. Give staff an approved tool and a short written rule about what may be entered.
