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): Tidewater Realty Pty Ltd (Lorraine Gatt, Principal)1 · Supplier: Halyard Property Software Pty Ltd1 · Monday 9 November 2026
Clause 1, roles. The Customer is the “controller” and the Supplier the “processor”. Comment: These are GDPR labels. The Privacy Act 1988 uses neither word, and Tidewater’s duties sit with it as an APP entity whatever the agreement calls the parties, so we kept the labels but tied each duty to the Australian Privacy Principles.2
Clause 3, data. Tenancy applications for about 1,900 current and former tenants and 240 landlords: names, dates of birth, driver licence and passport images, payslips, bank statements and landlords’ bank details.3
Clause 5, location. Production data is hosted in Singapore with backups in Dublin, and support is provided by Supplier staff in Manila and Dublin.4 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. The Supplier will protect the data with technical and organisational measures, including encryption in transit and at rest and multifactor authentication for every administrator.5
Clause 8, incidents. The Supplier notifies the Customer within 24 hours of becoming aware of a security incident. Comment: Once Tidewater suspects an eligible data breach it has 30 days to complete its assessment (s 26WH), and, where APP 8.1 applied to the disclosure, information the overseas supplier holds is treated as Tidewater’s own for that scheme (s 26WC). The 24 hours is what makes the 30 days workable. Ask for the detail needed for a statement under s 26WK.6
Clause 9, sub-processors. Halyard Europe Ltd, the Supplier’s Irish subsidiary, supports the platform. The GDPR reaches processing in the context of an EU establishment (Article 3(1)) and a business outside the EU only if it offers goods or services to people there or monitors their behaviour (Article 3(2)). Tidewater does neither, so we have not made it a GDPR controller, but have kept Article 28-style sub-processor terms.7
Clause 10, end of contract. Within 30 days of termination the Supplier returns the data as CSV files and deletes it, including backups within 90 days, and certifies the deletion.8
Clause 12, liability. The Supplier’s liability is capped at 12 months of fees ($38,400). Ask for $2,000,000 for privacy claims or an uncapped indemnity for breach of clause 7. Lorraine will accept $1,000,000 as the floor.9
Clause 14. This agreement is governed by the law of New South Wales.10
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
- Reads the supplier's terms and the client's requirements
- Compares each term with your clause library
- 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
- 1The 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.
Frontier Models (ChatGPT, Claude) Transmitted to the provider, generally offshore on personal plans Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Data processing agreement checker. Compares the supplier's data processing terms against your clause library and the client's requirements, and lists gaps with suggested wording from your precedents. See the use case - 2The 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.
Frontier Models (ChatGPT, Claude) The firm’s advice on the roles clause transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Data processing agreement checker. Compares the supplier's data processing terms against your clause library and the client's requirements, and lists gaps with suggested wording from your precedents. See the use case - 3The 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.
Frontier Models (ChatGPT, Claude) The kinds and volume of tenants’ data, and so the size of a breach, transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Data processing agreement checker. Compares the supplier's data processing terms against your clause library and the client's requirements, and lists gaps with suggested wording from your precedents. See the use case - 4The 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.
Frontier Models (ChatGPT, Claude) Locations named, but they come from the supplier’s own draft; moderate value alone Ermos Edge Locations are the supplier’s; a person must check them against the supplier’s actual hosting Ermos Dominion Locations are the supplier’s; a person must check them against the supplier’s actual hosting Use case Data processing agreement checker. Compares the supplier's data processing terms against your clause library and the client's requirements, and lists gaps with suggested wording from your precedents. See the use case - 5The 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.
Frontier Models (ChatGPT, Claude) The supplier’s own security wording; a supplier’s confidential design may be inside it Ermos Edge The AI can draft security wording but cannot test the supplier’s controls; a person must Ermos Dominion The AI can draft security wording but cannot test the supplier’s controls; a person must Use case Data processing agreement checker. Compares the supplier's data processing terms against your clause library and the client's requirements, and lists gaps with suggested wording from your precedents. See the use case - 6The 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.
Frontier Models (ChatGPT, Claude) Privileged advice on the client’s breach exposure transmitted; on consumer tiers it can train future models Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Data processing agreement checker. Compares the supplier's data processing terms against your clause library and the client's requirements, and lists gaps with suggested wording from your precedents. See the use case - 7The 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.
Frontier Models (ChatGPT, Claude) A legal opinion about a named client transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Data processing agreement checker. Compares the supplier's data processing terms against your clause library and the client's requirements, and lists gaps with suggested wording from your precedents. See the use case - 8Return 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.
Frontier Models (ChatGPT, Claude) A contract promise with no individual named; low value alone Ermos Edge A person must check the deletion period against what the supplier can actually do Ermos Dominion A person must check the deletion period against what the supplier can actually do Use case Data processing agreement checker. Compares the supplier's data processing terms against your clause library and the client's requirements, and lists gaps with suggested wording from your precedents. See the use case - 9The 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.
Frontier Models (ChatGPT, Claude) The liability floor now on a third party’s servers Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Data processing agreement checker. Compares the supplier's data processing terms against your clause library and the client's requirements, and lists gaps with suggested wording from your precedents. See the use case - 10The governing law clause
Standard wording with no party, figure or fact in it.
Frontier Models (ChatGPT, Claude) Standard wording with no party or figure in it; nothing to expose Ermos Edge Standard text either way; a person must check it matches the deal Ermos Dominion Standard text either way; a person must check it matches the deal Use case Data processing agreement checker. Compares the supplier's data processing terms against your clause library and the client's requirements, and lists gaps with suggested wording from your precedents. See the use case
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 Edge | Ermos Dominion | |
|---|---|---|---|
| Where the document is processed | Provider servers, generally offshore on personal plans | Your instance in an Australian data centre; answers generated in Australia | The unit in your office |
| Who can read it | Provider staff and systems, under policy | Your staff, within the boundaries you set. The named Australian provider processes only permitted excerpts, under contract, and keeps nothing | Your staff only |
| Is it kept | On the provider’s terms | Kept on your instance; the provider is barred from retaining it | Stays on the unit |
| Can it train a model | On consumer tiers, yes | No, by contract | Only 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?
Is it safe to paste a data processing agreement into ChatGPT or Claude?
Does a ChatGPT Business or Claude Team plan make it safe for a data processing agreement?
How can a law firm use AI for a data processing agreement without sending it to ChatGPT or Claude?
Does Australia's Privacy Act require a data processing agreement?
Who is responsible if an overseas supplier mishandles personal information?
When does the GDPR apply to an Australian business?
See Dominion answering from your own documents.
A demonstration takes 30 minutes, uses no client data, and comes with no obligation.
Book a demo