Law Firm Data Processing Agreements: Use case and AI Confidentiality

A data processing agreement sits beside a software contract and says how a supplier may handle the customer’s personal information: where it is stored, who can see it, how fast the supplier must report a breach and what happens when the contract ends. It is dense and repetitive, so staff paste clauses into ChatGPT or Claude to compare them with a precedent. This page marks every item in the firm’s markup of a property software supplier’s draft that rule 9, privilege and the Privacy Act bear on, explains what each one exposes, and shows how the same agreement is reviewed on Ermos inside the firm.

The data processing agreement

Reviewed when a business client takes on a cloud supplier that will hold customer data, and negotiated before the main contract is signed.

Data processing agreement: markup of the supplier’s draft 2
Customer (our client): · Supplier: · Monday 9 November 2026

Clause 1, roles. The Customer is the “controller” and the Supplier the “processor”. Comment:

Clause 3, data.

Clause 5, location. Comment: We have treated each as an overseas recipient and written steps for APP 8.1, because section 16C can make an overseas recipient’s breach Tidewater’s own.

Clause 7, security.

Clause 8, incidents. The Supplier notifies the Customer within 24 hours of becoming aware of a security incident. Comment:

Clause 9, sub-processors.

Clause 10, end of contract.

Clause 12, liability.

Clause 14.

An invented agreement markup. Hover or tap any highlighted item for the analysis; the full list is below.

Data processing agreement checker

An Agent+ that reads a cloud supplier's data processing agreement beside your clause library and the client's instructions. It checks locations, breach notice, deletion and liability terms against your usual positions, and drafts a list of gaps with proposed wording.

What it does

  1. Reads the supplier's terms and the client's requirements
  2. Compares each term with your clause library
  3. Lists gaps with wording drawn from your precedents

What stays with your people. The solicitor reviews every flagged term and negotiates. A partner approves what goes to the supplier.

An Agent+ is built once and anyone in the practice can run it. It works from your own documents and runs on Ermos Dominion, the AI unit in your office, or on Ermos Edge, your own instance in an Australian data centre.

What leaves the firm

  1. 1
    The client and the supplier

    A named business, its principal and the software provider it is about to depend on. Confidential to the client under rule 9 while the procurement is not public. Rule 9 confidentiality guide.

  2. 2
    The roles clause and the firm’s view of it

    The Privacy Act 1988 does not use the words controller or processor, so the label is a contract convention and the duties come from the APPs. The firm’s advice on how to draft around it is privileged. Legal privilege guide.

  3. 3
    The categories and volume of data

    About 2,100 people’s identity documents, payslips, bank statements and bank details. The agreement itself holds no individual, but it tells a reader exactly what a breach of this supplier would yield. Privacy Act guide.

  4. 4
    The hosting and support locations

    Three countries named as places the client’s data will sit or be seen. APP 8.1 requires an APP entity, before it discloses personal information to an overseas recipient, to take reasonable steps to ensure the recipient does not breach the APPs (other than APP 1), and section 16C can make the recipient’s breach the client’s. Privacy Act guide.

  5. 5
    The security promises

    APP 11.1 requires reasonable steps to protect personal information an APP entity holds from misuse, interference, loss and unauthorised access, modification or disclosure, and APP 11.3 says such steps include technical and organisational measures. The clause is what the client will rely on, and a supplier’s security design is its confidential information. Privacy Act guide.

  6. 6
    The incident notice and the client’s breach clock

    Sections 26WH, 26WC and 26WK of the Privacy Act as they bear on this supplier, with the firm’s advice on the timing the contract should deliver. Privileged advice on the client’s own exposure. Legal privilege guide.

  7. 7
    The overseas subsidiary and the GDPR analysis

    A named foreign subsidiary and the firm’s view that the GDPR does not reach the client. The GDPR’s reach under Article 3 depends on establishment, offering goods or services to people in the EU, or monitoring their behaviour, so the view is a legal opinion about a named client. Legal privilege guide.

  8. 8
    Return and deletion

    APP 11.2 requires an APP entity to take reasonable steps to destroy or de-identify personal information it no longer needs, unless a law requires retention. The clause tells a reader how long data lingers in backups. Privacy Act guide.

  9. 9
    The liability cap and the client’s floor

    The supplier’s cap, what the firm will ask for and the amount the client will accept. The negotiating position in a document the supplier would love to read. Legal privilege guide.

  10. 10
    The governing law clause

    Standard wording with no party, figure or fact in it.

What happens in Frontier Models (ChatGPT, Claude)

  • The whole document is transmitted to the provider’s servers. On personal plans the user cannot choose where it is stored or processed, and for the major providers that has generally meant outside Australia, under that country’s legal process. Some business plans offer storage in Australia, but the provider still receives the content.
  • On consumer tiers, prompts can be retained and used to train future models.
  • The provider’s staff and systems can reach the content under the provider’s own policies.
  • Once sent, the firm no longer controls it. Retention and deletion happen on the provider’s terms.

The same document on Ermos

Ermos Dominion

The document is drafted on a unit in your office, from your own templates and the matter file. Every marked item stays on the unit, which keeps working with the internet switched off. Nothing in it is transmitted to an AI provider, so there is no disclosure to analyse: the confidentiality work is the same as for your file server.

Ermos Edge

Your documents, the index and your access boundaries stay on your own instance in an Australian data centre. When a staff member asks for this draft, only their question and the excerpts they are permitted to see go to a named Australian provider, who is contractually barred from keeping the content or training any model on it. Nothing is processed outside Australia.

Frontier Models (ChatGPT, Claude)Ermos EdgeErmos Dominion
Where the document is processedProvider servers, generally offshore on personal plansYour instance in an Australian data centre; answers generated in AustraliaThe unit in your office
Who can read itProvider staff and systems, under policyYour staff, within the boundaries you set. The named Australian provider processes only permitted excerpts, under contract, and keeps nothingYour staff only
Is it keptOn the provider’s termsKept on your instance; the provider is barred from retaining itStays on the unit
Can it train a modelOn consumer tiers, yesNo, by contractOnly your own unit learns from it, on your hardware

Part of Use cases in law firms. See how this works in practice: Supplier contracts on Ermos.

Common questions

Do ChatGPT and Claude use the information in a data processing agreement?
Whatever is pasted in is sent to the AI company's servers and processed there to produce a reply. As at October 2026, whether a conversation on a personal plan (ChatGPT Free, Plus or Pro; Claude Free, Pro or Max) can be used to train the models depends on a setting each user controls. Business plans (ChatGPT Business and Enterprise, Claude Team and Enterprise) and the developer APIs sit under commercial terms, and OpenAI and Anthropic each say they do not train on that content by default (OpenAI, Anthropic). On either product, the thumbs up and thumbs down buttons can send a whole conversation back for training. This markup carries the client's floor of $1,000,000 on the supplier's liability, the three countries where its tenants' data would sit or be seen and the firm's advice on the 24 hour incident notice.
Is it safe to paste a data processing agreement into ChatGPT or Claude?
Not safely, because the markup carries privileged advice on the roles clause, the GDPR and the breach clock, and it is confidential to the client under rule 9. The Office of the Australian Information Commissioner (OAIC) recommends in its guidance on commercially available AI products 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. The agreement names no tenant, but it lists the identity documents, payslips and bank statements of about 2,100 people, which tells a reader what a breach of this supplier would yield.
Does a ChatGPT Business or Claude Team plan make it safe for a data processing agreement?
Not on its own. On a personal plan the user cannot choose where conversations are stored or processed. Some business plans let an organisation choose to store data at rest in Australia (OpenAI), which still leaves the content with the AI company. A business plan changes the default on training, but it does not change who receives the content. This markup is the client's attempt to control who receives its customers' data, and sending it to an AI company would hand the firm's own advice to another recipient. The OAIC's guidance also tells organisations to review carefully the terms and settings that will apply to their use of any AI product. Our comparisons with ChatGPT Enterprise and Claude weigh the trade-offs.
How can a law firm use AI for a data processing agreement without sending it to ChatGPT or Claude?
Ermos is built so the document stays under your control. On the Dominion AI unit it is drafted inside your office and none of it is sent to an AI provider. On Ermos Edge your documents and index stay on your own instance in an Australian data centre, and only the question and the excerpts the user is permitted to see go to a named Australian provider that is contractually barred from keeping them or training any model on them. The markup is drafted from the supplier's draft and the firm's own precedent clauses. A solicitor checks each duty against the Australian Privacy Principles and decides every position.
Does Australia's Privacy Act require a data processing agreement?
The Privacy Act 1988 does not use the terms controller and processor and does not prescribe a data processing agreement. An APP entity that discloses personal information to an overseas recipient must take reasonable steps to ensure the recipient does not breach the Australian Privacy Principles other than APP 1 (APP 8.1), and a written contract is a common way to do that. APP 11.1 separately requires reasonable steps to protect information the entity holds.
Who is responsible if an overseas supplier mishandles personal information?
Under section 16C of the Privacy Act, if an APP entity discloses personal information to an overseas recipient, APP 8.1 applies, the APPs do not otherwise apply to the recipient and the recipient does something that would breach them, that act is taken to be the APP entity's own breach. Where APP 8.1 applied to the disclosure, section 26WC also treats information held by the overseas recipient as held by the entity for the notifiable data breach scheme.
When does the GDPR apply to an Australian business?
Article 3 of the GDPR applies to processing in the context of an establishment of a controller or processor in the EU, and to controllers or processors outside the EU where they offer goods or services to people in the EU or monitor their behaviour there. An Australian business with no EU establishment and no EU-facing offering is generally outside it, although a supplier with EU operations may apply it to its own processing.

See Dominion answering from your own documents.

A demonstration takes 30 minutes, uses no client data, and comes with no obligation.

Book a demo