Practice area
Privacy, Data Protection & CyberPrivacy, data protection and cyber
Establish the actual information, processing activity and incident facts before choosing a response. Verify applicable duties and time limits, and keep access, training use, retention and disclosure conditions distinct.
Key facts
- Tasks covered
- 32
- Tasks with a step-by-step checklist
- 17
- Local differences
- 3 jurisdictions where this area changes
Jurisdiction
Tasks
GreenLawyer reviewYellowClose supervisionRedLawyer-led
| Task | How AI is used | Human involvement | What the lawyer must review |
|---|---|---|---|
| Build a privacy-law gap table against the principles that apply | Map the client's described practices and policies to the privacy principles the lawyer has listed, and mark missing notices, security measures and retention rules. | YellowClose supervision |
|
| Map a US privacy file to the statutes that actually apply | From the client’s data map, list possible triggers: HIPAA PHI, GLBA financial information, CCPA consumer personal information, Colorado ADMT, Rule 1.6 client information. | YellowClose supervision |
|
| Map a New Zealand client's privacy duties to the IPPs | Produce an IPP-by-IPP issues list from the client's described data flows. | YellowClose supervision |
|
| Draft or review a privacy policy and collection notice | Produce a first-draft policy or notice mapped to the required disclosure headings, using only the processing facts the client has supplied. | YellowClose supervision |
|
| Assess a suspected data breach and draft the notification pack | The statement to the regulator and the notice to individuals are the lawyer's to write and the tool writes no part of either. Organise the incident record into a source-referenced assessment table — what was accessed, whose information and which systems, every row referenced to the document or log it comes from and set beside the statutory serious-harm factors with a column for each factor — and list the facts that still need a source, the notification route chosen, and whether any other entity is being treated as covered by this notification. Check the lawyer's own statement against each prescribed content item and the regulator's notification form, compare the notice to individuals against that statement and flag anything the statement says that the notice does not carry, and flag anything the drafts assert that the incident record does not support, or that the two drafts say differently. | RedLawyer-led | Decide whether the incident is notifiable under the current statute. Deadlines and 'serious harm' are lawyer calls, and so are the notification route and whether any other entity is covered by this notification. The lawyer writes the statement to the regulator and the notice to individuals, and confirms every fact and every remediation step asserted in them is true at the moment of issue. |
| Assess a notifiable data breach and draft the OAIC notification pack | Build an NDB table (access, personal information, likely serious harm), draft OAIC and individual notices, note the 30-day assessment and any 72-hour ransomware report. | RedLawyer-led |
|
| Assess a notifiable privacy breach under the Privacy Act 2020 | Extract what was disclosed, to whom, and the categories of people affected. | RedLawyer-led |
|
| Handle a US health-privacy incident as HIPAA plus Rule 1.6 | Sort the incident facts into covered-entity / business-associate / other, and list data elements that may be PHI. | RedLawyer-led |
|
| Draft a data-breach incident response plan | Produce a plan covering detection, containment, assessment, notification and post-incident review, with a RACI and template notices. | YellowClose supervision |
|
| Build a vendor AI and subprocessors risk questionnaire | Generate a questionnaire covering residency, subprocessors, training on client data, retention, deletion and audit rights, and score the returned answers into a table. | YellowClose supervision |
|
| Assess a generative-AI vendor against Rule 1.6 before any client input | Extract retention, training-use, subprocessors and breach-notice terms from the vendor documents into a table. | YellowClose supervision |
|
| Draft a privacy or data-protection impact assessment | Structure a PIA or DPIA from the project description: information flows, risks, mitigations and sign-off questions. | YellowClose supervision |
|
| Draft a privacy impact assessment against the OAIC PIA guide | Structure a PIA from the project description using the OAIC five-stage guide (description, flows, analysis, solutions, sign-off), with questions for each APP. | YellowClose supervision |
|
| Build a privacy-tort and misuse-of-information issues table | From the facts, list candidate elements of a privacy tort, misuse of information or statutory interference claim, with the documents that support each row. | YellowClose supervision |
|
| Map automated decisions that use personal information | From the system description, list decisions that use personal information, whether a human reviews them, and what the privacy notice currently says. | YellowClose supervision |
|
| Advise on automated decision-making under Colorado SB26-189 | Identify whether the system materially influences a consequential decision and whether the client is a developer or a deployer. | YellowClose supervision |
|
| Build a cross-border transfer mechanism table | List destinations, recipients, transfer tools (clauses, adequacy, other) and residual risks from the DPA and architecture papers. | YellowClose supervision |
|
| Build a cross-border transfer table under APP 8 | List destinations, recipients and APP 8 pathways (APP 8.1 reasonable steps or an APP 8.2 exception) from the DPA and architecture, and draft binding-scheme clauses. | YellowClose supervision |
|
| Check overseas disclosure against IPP 12 before a tool processes client data | Extract the vendor's stated storage locations and subprocessors from the contract. | YellowClose supervision |
|
| Draft a response pack for a privacy-regulator investigation | From the Commissioner's notice and the incident file, the tool schedules every question, document category and due date the notice sets, and maps the file's documents, system logs and policy versions against each item so what is held, what is missing and what may be privileged is visible. It writes no part of the response: the lawyer drafts the submission, and the tool only compares that draft against the notice's questions and the underlying documents and lists assertions the file does not support. | RedLawyer-led | Read the draft response against the notice question by question: confirm nothing concedes a serious or repeated interference with privacy, or any other characterisation of the entity's conduct, beyond what the file compels, and that every date, log reference and remediation step matches its source document. Confirm privilege is claimed consistently with how each forensic report was commissioned and used, check that the schedule of documents produced answers every category in the notice, and settle who signs the response and the date it must be served. |
| Draft a response pack for an OAIC investigation | From the OAIC’s notice, schedule every question, document category and due date it sets, and index the file’s documents, system logs and policy versions against each item, flagging what is missing and what may be privileged. The tool writes no part of the response to the OAIC: no draft, no first draft, no skeleton, no outline, no suggested paragraphs. Once the lawyer has written the submission, check it against the notice question by question and list every assertion the file does not support. | RedLawyer-led |
|
| Map employee-monitoring and workplace-surveillance duties | From the proposed monitoring description, list the surveillance, privacy and employment rules the lawyer has named and the notice or consent steps already taken. | YellowClose supervision |
|
| Map employee-monitoring duties under the APPs, Fair Work Act and state surveillance law | List the state surveillance, APP employee-records and Fair Work Act rules the lawyer has named and the notice or consent steps taken, and draft a monitoring policy. | YellowClose supervision |
|
| Map critical-infrastructure cyber reporting duties for the asset | From the asset description, line the client's systems up against the infrastructure classes and reporting clocks the lawyer has listed, and mark gaps. | YellowClose supervision |
|
| Map SOCI Act cyber-reporting duties and CIRMP gaps for the asset | Match systems to the 22 asset classes under the SOCI Act 2018 (Cth), list reporting clocks, and draft a CIRMP for cyber, personnel, physical and supply-chain hazards. | YellowClose supervision |
|
| Build a record of processing from the interviews and system list | Turn the interview notes and system inventory into a processing record: purposes, categories, recipients, locations, retention and security measures. | YellowClose supervision |
|
| Assemble an access, deletion or correction response pack | From the request and the systems list, draft a search log, a proposed response and a list of items that may be withheld, with reasons to check. | YellowClose supervision |
|
| Draft a data-processing agreement from the processing facts | Produce a first-draft DPA covering instructions, security, subprocessors, deletion and audit from the processing description and the client's precedent. | YellowClose supervision |
|
| Build a 48-hour incident chronology from the tickets and emails | Extract times, systems, actors and decisions from the incident tickets and correspondence into a chronology, marking gaps. | YellowClose supervision |
|
| Run a privacy impact assessment before a client deploys a commercial AI product | Draft a PIA structure from the vendor documents and data flows: personal information in, outputs, APP 1, 5, 6, 8, 10 and 11 touchpoints. | YellowClose supervision | Confirm what personal and sensitive information actually flows; decide whether the use is necessary and lawful. |
| Audit a client privacy policy for AI disclosures and chatbot labelling | Compare the policy and collection notices to the client's AI uses and list gaps, including unlabelled public-facing chatbots. | GreenLawyer review | Check each gap against the actual system and approve wording. |
| Assess whether a client may use held personal information to train or fine-tune a model | Organise the original collection notices and purposes into a primary/secondary-purpose table for APP 6 analysis. | RedLawyer-led | Decide reasonable expectations and whether consent or opt-out is needed. |
| Prepare an ADM disclosure for a privacy policy by 10 Dec 2026 | Identify automated decisions and draft disclosure. | YellowClose supervision | Lawyer confirms against APP 1. |
| Conduct AI product due diligence for privacy | Assess a commercial AI product's data handling. | YellowClose supervision | Ongoing review, not set-and-forget. |
| Advise on client-data exposure from consumer AI tools | Assess exposure and remediation. | YellowClose supervision | Lawyer settles. |
| Update collection notices for AI chatbots | Draft chatbot notices. | GreenLawyer review | Check APP 5. |
| Build an AI privacy impact assessment | Draft PIA for an AI system. | YellowClose supervision | Lawyer confirms. |
| Assess privacy compliance of a commercially available AI product | Apply OAIC guidance to the product terms. | YellowClose supervision | Lawyer advises. |
| Draft a law firm policy against putting client data into free AI tools | Draft rules on data security. | GreenLawyer review | Principal approves. |
| Draft a notifiable data breach assessment involving AI tools | Assess serious harm. | RedLawyer-led | Lawyer settles. |
| Draft the statement to the OAIC about a notifiable data breach from the incident log | Draft the statement using only facts written in the incident log. | YellowClose supervision | Match every affected group and every step to the log and to the OAIC notifiable data breaches page. |
| Compare a privacy-policy draft with the OAIC's APP 1 chapter | List policy clauses beside the headings in the APP 1 chapter. | YellowClose supervision | Open the APP 1 chapter and decide which clauses meet it. Do not rely on a generated summary of the chapter. |
| List the personal information a client-intake chatbot would collect and check it against the Privacy Act 1988 | List the fields the chatbot asks for. | YellowClose supervision | Read the Privacy Act compilation before advising whether the collection is allowed. The list is not that advice. |
| Prepare the file note deciding whether an AI-tool incident is a notifiable data breach | Set out the incident facts from the log. Do not decide whether notification is required. | RedLawyer-led | The lawyer decides, using the incident log and the OAIC notifiable data breaches page. |
| Draft the transparency paragraph of a privacy policy and check it against the OAIC APP 1 chapter | Draft a transparency paragraph from the client's description of the tool. | YellowClose supervision | Check the paragraph against APP 1 as the chapter explains it, and against what the tool actually does. |
Firm-wide obligations
| Obligation | What it covers |
|---|---|
| Trust accounting & handling client money | Checks that apply across files. |
| Costs, billing & litigation funding | Checks that apply across files. |
| Client-facing & access-to-justice AI tools | Checks that apply across files. |
| Incoming evidence — deepfakes & synthetic documents | Checks that apply across files. |
| AI decision systems | Checks that apply across files. |
| Confidentiality & client information | Checks that apply across files. |
| AML/CTF — the practice as a reporting entity | Checks that apply across files. |
What changes in Australia
| Topic | What changes |
|---|---|
| Legal sources | Privacy Act 1988 (Cth) and its 2024 amendments, the APPs, the Notifiable Data Breaches scheme, the Cyber Security Act 2024 (Cth) and the Security of Critical Infrastructure Act 2018 (Cth). |
| Moving law | The regime is layered and changing fast, so an invented authority flows straight into compliance advice. |
| Client data | Putting client data into an AI tool can itself be the breach the firm is advising on. Treat tool use as a confidentiality and governance question. |
What changes in New Zealand
| Topic | What changes |
|---|---|
| Governing law | Privacy Act 2020 and the information privacy principles, not the APPs. IPP 12 covers disclosure outside New Zealand. |
| IPP 3A | Notification of indirect collection, in force since 1 May 2026. |
| Breaches | If a breach has caused or is likely to cause serious harm, notify the Privacy Commissioner and affected people as soon as practically able. Not the OAIC NDB scheme. |
| Commissioner's AI expectations | Privacy impact assessment before use; human review before acting on output; no personal input unless the provider confirms it will not retain or disclose it. |
| Limits on AI assistance |
|
- OPC: Privacy Act 2020 information privacy principles · 2026-09-23
- OPC: Artificial Intelligence and the Information Privacy Principles · 2026-09-23
- OPC: Generative artificial intelligence (15 June 2023) · 2026-09-23
- OPC: IPP 3A guidance · 2026-09-23
- OPC: sorting out privacy breaches · 2026-09-23
What changes in United States
Known here as: Privacy, data protection and cyber
| Topic | What changes |
|---|---|
| No general statute | No federal equivalent of the Privacy Act 1988 (Cth). Start with Rule 1.6, then the sector statute that covers the data. |
| Sector statutes | HIPAA for PHI; GLBA for non-public financial data; CCPA as amended by the CPRA (know, delete, correct, opt out of sale or sharing, limit sensitive data). |
| Colorado | SB26-189 (signed 14 May 2026) repeals and re-enacts SB24-205; ADMT duties from 1 January 2027. HB26-1263 (signed 1 July 2026) adds chatbot duties from the same date. |
| Vendor AI | Formal Opinion 512: understand retention, training use and access before you input client information. |
| Limits on AI assistance |
|
- ABA Model Rule 1.6, Confidentiality of Information · 2026-09-23
- ABA Formal Opinion 512, Generative Artificial Intelligence Tools (29 July 2024) · 2026-09-23
- California Attorney General: California Consumer Privacy Act (CCPA) · 2026-09-23
- HHS: HIPAA covered entities and business associates · 2026-09-23
- Colorado Attorney General: Automated Decision-Making Technology and Chatbot Safety rulemaking · 2026-09-23
- Colorado Senate Bill 26-189 (became law 14 May 2026) · 2026-09-23
Precedents for this area
- Data breach response plan (Notifiable Data Breaches scheme, with cyber reporting clocks) (Policy, AI use Yellow). A ready-to-tailor plan that tells the response team how to contain, assess, notify and review a data breach under Part IIIC of the Privacy Act, and lists the other reporting clocks that may run at the same time.
- Notifiable data breach statement to the OAIC: completion guide for the online form (Form, AI use Red). Practical guide to completing the OAIC's online Notifiable Data Breach form: what goes in the mandatory statement (Part one), what to add in the optional Part two, what to attach, and the traps that lead to a non-compliant statement.
- APP privacy policy with AI and automated-decision disclosures (APP 1.4 and APP 1.7 to 1.9) (Policy, AI use Yellow). A complete APP privacy policy for an Australian organisation that covers every APP 1.4 heading and the automated-decision disclosures required from 10 December 2026 under APP 1.7 to 1.9, with plain-English AI and chatbot sections.
- Serious invasion of privacy (statutory tort, Privacy Act Sch 2): claim assessment checklist (Checklist, AI use Yellow). Checklist for assessing a claim, or a threatened claim, under the statutory tort for serious invasions of privacy: limitation, exemptions, each element, defences, remedies and the damages cap, forum, evidence and AI-specific scenarios such as deepfakes.
- Data protection clause for service providers, including AI vendors (no training, retention, offshore disclosure) (Clause, AI use Yellow). An Australian-law data protection clause for a services or SaaS agreement that controls how a supplier, including an AI provider, uses, stores, moves and deletes customer data, with no-training and breach-cooperation terms that fit the Privacy Act.
- AI and automated decisions clause for privacy policies and collection notices (Clause, AI use Yellow). Modular privacy policy wording on AI: how AI is used, chatbot labelling, the APP 1.7 to 1.9 automated-decision disclosure required from 10 December 2026, AI-inferred information, training and overseas AI providers, plus a short chatbot collection notice.
- Privacy impact assessment checklist for an AI tool (supplement to the OAIC PIA tool) (Checklist, AI use Yellow). A structured PIA checklist for deploying an AI product: project description, information flows (prompts, outputs, logs, training), an APP-by-APP analysis including APP 1.7, AI-specific risks, vendor checks, a risk register and sign-off.
All precedents for Privacy, Data Protection & Cyber. Signed-in accounts can read the full text.