Skip to main content

Broker guide

Data Processing Agreement for Mortgage Brokers

Putting client files into a new CRM or AI tool? Check the vendor’s data processing agreement covers instructions, subprocessors, breaches and deletion.

Published
Updated

A data processing agreement sets the rules a vendor must follow when it handles borrower information for your brokerage. Get those rules in writing before you upload client files or connect the vendor to a system that holds them.

When a Brokerage Needs One

Ask for a data processing agreement when a vendor stores borrower files or can access them while providing a service. The terms might be in a separate agreement or a binding schedule to the service contract. A customer relationship management (CRM) vendor might host passports and payslips, for example, while a document processing vendor might extract figures from credit records.

If the Privacy Act applies to your brokerage and you still hold the personal information, outsourcing leaves your obligation to protect it under Australian Privacy Principle (APP) 11 in place. The Office of the Australian Information Commissioner’s guide to securing personal information explains how contract terms and checks on the vendor’s security can help you meet that obligation.

Under the regulator’s APP 8 guidance, giving personal information to an overseas contractor is usually a disclosure. Where APP 8.1 applies, take reasonable steps before disclosure to ensure the recipient handles the information in line with the applicable principles. Section 16C of the Privacy Act 1988 can make the brokerage accountable for the overseas recipient’s handling.

In limited cases, sending information overseas counts as a use because the brokerage retains effective control. The regulator gives the example of a storage provider bound to a limited purpose, with equivalent obligations for its subcontractors and effective control retained by the brokerage. Check where people can access the files as well as where the vendor hosts them.

Clauses the Agreement Must Cover

Copy this clause checklist into your vendor review and write the clause number and any gap beside each item.

  • Processing instructions. List the data the vendor can handle, the permitted tasks and how you give further instructions. Require your written approval for a new purpose, including training an artificial intelligence (AI) model.
  • Confidentiality. Restrict access to staff who need it to provide the agreed service and bind them to confidentiality.
  • Security controls. Specify access controls, encryption and logging. State who checks access and who fixes a failure.
  • Subprocessor approval. Identify each subprocessor, meaning another vendor that handles the data for your vendor. Require written approval for changes and equivalent contractual obligations for each subprocessor.
  • Overseas storage and access. List the countries used for hosting, backups and remote support. Set out how the vendor must obtain approval before adding a country.
  • Breach notice. Set a deadline that starts when the vendor becomes aware of a suspected or confirmed breach. Name the contact and require the vendor to share what happened, preserve evidence and help contain the breach.
  • Audit rights. Set out which security reports you can request and when you can inspect controls or commission an audit.
  • Retention. Set retention periods for live files, logs and backups. Require the vendor to identify any copies it must keep by law and restrict access until it can delete them.
  • Deletion on exit. Specify the export format and retrieval window. Set deletion deadlines for live copies and backups, with written confirmation of deletion.

The vendor’s breach notice gives you time to assess the incident. The Notifiable Data Breaches scheme sets separate duties for assessing suspected eligible breaches and notifying the regulator and affected individuals when required.

Check a Vendor’s Standard Terms

Compare the service contract, data schedule and subprocessor list before signing. Check which document governs if the terms conflict, especially where the vendor incorporates a policy it can change online.

Suppose a fictional CRM promises to notify customers of a breach when practicable, without setting a deadline. Its setup guide says an outside service reads uploaded payslips, but the subprocessor list leaves that service out.

Ask for an agreed maximum time for the first notice, measured from when the CRM vendor becomes aware of a suspected or confirmed breach. Ask for a revised subprocessor list naming the payslip service, what it receives, the countries it uses and the obligations it accepts. Have the vendor incorporate those commitments into the agreement.

If the vendor won’t negotiate, take the gaps to the person responsible for privacy at your brokerage or to your licensee. See whether you can remove the affected data or disable the feature, then check the remaining workflow against the terms. If you still can’t meet your obligations on the standard terms, choose another vendor before uploading borrower files.

Keep the Agreement Current

Save the signed agreement and the versions of the schedules and policies it incorporates. Record the review date and the person responsible for the next review in your vendor register.

Ask the vendor to send change notices to that person. Reopen the agreement before enabling a new AI feature or approving a subprocessor change. Follow a borrower file through the revised service and check that each use, access location and retained copy is covered before releasing client data.

Bring policy research and scenario planning together

Ask lender policy questions, plan client scenarios and compare lenders in one conversation, with the policy wording behind each answer.
See how it works14 days free · No credit card