AI Chatbot and Privacy Act: What Data Can a School Collect in Australia?

What an AI chatbot actually collects about your prospects

An AI recruitment chatbot on an Australian university or private higher education provider website begins collecting personal information at the very first interaction — well before a prospect types their name. IP address, session timestamp, typed messages, course consulted: each of these is personal information under the Privacy Act 1988 (Cth) and the 13 Australian Privacy Principles (APPs).

72% of questions submitted to education chatbots are automatable FAQ inquiries, 21% require institution-specific context, and 7% require a human. (Source: automated classification of 12,000 Skolbot conversations, 2025.) Each of those 12,000 conversations is a processing activity subject to the Privacy Act. The chatbot holds a decisive advantage over other channels: average response time of 3 seconds, 24/7, versus 47 hours by email and 72 hours by web form (Source: Skolbot mystery-shopping audit, 2025, 80 institutions). Capturing that advantage requires a privacy-compliant data collection infrastructure.

Typical categories of personal information collected by a chatbot at an Australian higher education institution:

• Conversational data — message text, timestamps, session language, session duration
• Voluntarily provided identifiers — first name, last name, email address, phone number (when the prospect provides these to receive follow-up)
• Interest data — course(s) browsed, target credential level, study mode sought (on-campus, online, combined)
• Voluntarily provided demographics — citizenship status, state or country of residence, ATAR or WAM range (if relevant to admission)
• Technical data — IP address, device type, browser, session identifier

The Office of the Australian Information Commissioner (OAIC) requires that each processing activity carried out via a chatbot rest on a lawful basis, and that individuals be notified of that collection at or before the time of collection (APP 5). Registered higher education providers are also subject to oversight by TEQSA (Tertiary Education Quality and Standards Agency), which can factor privacy compliance into registration decisions. For a complete overview of your institution's personal information processing, see our complete Privacy Act and student data guide.

The legal bases applicable to each data category

The Privacy Act 1988 does not use a "legal basis" framework identical to the GDPR, but APP 3 (Collection of solicited personal information) requires that collection must be reasonably necessary for one or more of the entity's functions or activities. Four grounds cover the vast majority of chatbot processing at an Australian institution:

Consent (APP 3.3 / APP 7) — The individual has provided voluntary, informed, and current consent. This is the appropriate basis for subsequent direct marketing communications (follow-up emails, course information, open day invitations) triggered by chatbot interactions. Consent must be obtained through an active mechanism (unchecked checkbox), and individuals must be able to opt out of direct marketing at any time (APP 7.3). Electronic commercial messages also require consent under the Spam Act 2003.

Directly related to primary purpose (APP 6.1) — Use or disclosure is for the primary purpose for which information was collected. A prospect requesting fee information or entry requirements: processing their email to send the requested documentation is directly related to the collection purpose.

Reasonably necessary secondary purpose (APP 6.2(a)) — The individual would reasonably expect use or disclosure for a related secondary purpose. Aggregating anonymised conversation data to improve the chatbot's response quality generally satisfies this standard. Note: a documented assessment is best practice, particularly before any system upgrade or new use of existing data.

Legal obligation — Required or authorised by Australian law. Relevant where data must be retained to satisfy ESOS Act obligations for international students or TEQSA registration requirements.

For sensitive information — see the following section — APP 3.3 imposes a higher standard: consent is generally mandatory, and the consent must be explicit.

The minimisation principle: collect only what is necessary

The "reasonably necessary" standard in APP 3 functions similarly to the GDPR minimisation principle: collect only what is adequate, relevant, and limited to what is necessary for the identified function. This is the most frequently breached principle in Australian higher education chatbot deployments.

Practical implications for your institution's chatbot:

• The chatbot must not require an email address to answer a question about courses. An email is only necessary if the prospect wants to be followed up or receive documentation.
• Citizenship status should not be collected systematically. It becomes relevant only when a prospect asks about domestic vs. international fee structures, Commonwealth Supported Places (CSP), HECS-HELP eligibility, or student visa requirements under Department of Home Affairs rules.
• Precise date of birth is unnecessary if the chatbot only needs to determine whether the prospect has an ATAR or is applying as a mature-age student. A study-level indicator is sufficient.
• Full conversation logs must not be retained indefinitely. The purpose of retention (service improvement, CRM transfer) must be defined before go-live, not after.

The OAIC's guidance on privacy by design and the Privacy Act Review 2022 emphasise that organisations should embed privacy-protective practices into system design from the outset — minimisation must be architectural, not a post-deployment correction.

Sensitive information: citizenship, health, disability

Some information collectible via an Australian higher education chatbot constitutes sensitive information under Section 6 of the Privacy Act, attracting the higher APP 3.3 consent standard.

Racial or ethnic origin: citizenship is not inherently sensitive information, but where collection could reveal or be used to infer a person's racial or ethnic origin, APP 3.3 applies. A chatbot segmenting prospects by citizenship for targeted marketing must assess whether this constitutes indirect collection of racial or ethnic information.

Health and disability: prospects seeking information about accessibility services, special consideration for exams, or disability support services may disclose health information within the chatbot. The system should be configured to not record such disclosures in unprotected free-text fields. Where collection is genuinely necessary (routing to a disability support coordinator), it must rest on express consent under APP 3.3 with full prior notification.

Financial situation: questions about Youth Allowance, Austudy, FEE-HELP eligibility, or fee waivers may reveal financial circumstances. While not strictly "sensitive information" under the Act, such data requires a robust collection basis and appropriate security safeguards under APP 11.

Practical rule: configure your chatbot to detect sensitive topic keywords and redirect to a human agent or secure form, rather than capturing this information in the standard conversational interface.

Data categories, legal bases, and retention periods

Privacy Impact Assessment: when does your chatbot require one?

The Privacy Act does not mandate PIAs in all cases, but the OAIC strongly recommends a Privacy Impact Assessment for any project involving new or substantially changed information-handling practices. For Australian higher education chatbot deployments, a PIA is effectively required where any of the following apply:

• Large-scale collection: a chatbot processing thousands of conversations monthly at a university or TAFe/private provider readily qualifies as large-scale processing
• Profiling: if the chatbot scores or classifies the prospect (warm/cold, course recommendation, enrolment probability) from their interaction data, this is automated profiling that warrants a PIA
• Sensitive information: any collection of health, disability, racial, or financial information
• Overseas disclosure: if your chatbot provider stores data or uses language models on servers outside Australia, APP 8 (cross-border disclosure) applies — and a PIA should assess whether the overseas recipient meets APP-equivalent standards

The PIA documents: purpose and data flows, risks and likelihood, and mitigation measures. Where residual risks remain high, the OAIC recommends consulting before proceeding.

For the full technical and organisational checklist, see our Privacy Act audit checklist for Australian schools.

Implementing compliant data collection: the chatbot interface

Privacy Act compliance for a chatbot operates at three levels: collection notice, consent mechanism, and individual rights.

Collection notice (APP 5)

Before the first exchange, the chatbot must display a notification including:

• The identity of the collecting organisation (the institution)
• The purposes of collection (answering questions, qualifying the prospect)
• Whether disclosure to overseas recipients is likely, and if so, which countries
• How individuals can access or correct their personal information and make complaints
• The disclosure that the interlocutor is an artificial intelligence system (aligned with emerging obligations under Australia's AI Safety Standards and the OAIC's guidance on automated decision-making)

Compliant example: "I'm [Chatbot Name], [Institution]'s AI assistant. We collect your information to answer your enquiries. See our [privacy policy] or contact privacy@[institution].edu.au to access or correct your information."

Integrated consent mechanism

Where the chatbot collects email or phone number, an active consent mechanism must precede that collection:

• Unchecked checkbox for marketing communications
• Separate disclosure for each purpose (re-engagement, course newsletter, open day invitation)
• Timestamp and retention of consent evidence

Individual rights: access, correction, deletion

Under the Privacy Act, individuals have the right to access personal information (APP 12) and request correction (APP 13). Requests must be responded to within 30 days. A deletion or de-identification request should cover all systems: chatbot logs, CRM, email platform, analytics, and backups.