
Why on-premises
Client confidentiality is not a setting you tick
With a cloud AI service, your client's documents go to someone else's computers and you rely on a contract to protect them. With AustLaw they stay on yours.
Why it runs inside your practice
Four reasons on-premises is not optional
Your duty of confidentiality stays simple
Nothing is disclosed to an outside AI provider, so there is no third party to assess, contract with or explain to a client.
Nothing goes offshore
Client information is not sent to an overseas recipient, so the cross-border disclosure questions under APP 8 of the Privacy Act 1988 (Cth) do not arise from using it.
TFNs are covered at any size
The Privacy (Tax File Number) Rule 2015 binds every TFN recipient, whatever its turnover. Keeping TFNs on your own systems keeps that obligation in your hands.
Nothing trains a model
Documents and prompts stay on infrastructure you control and are not used to train any external model.
APP 8, Privacy Act 1988 (Cth); Privacy (Tax File Number) Rule 2015. How these apply depends on the practice's circumstances. General information only, not legal advice.
Access and audit
You can show who saw what
Accounts are created and removed by your administrator. Multi-factor sign-in is mandatory. An audit trail records who asked what, and when.
Professional responsibility
It does not pretend to be the practitioner
Every output is a drafted position with its sources attached, for a qualified person to accept, amend or reject. The judgment, and the responsibility, stay with your people.
See what runs on your infrastructure.
We will show you what is installed in your practice, what it connects to, and what never leaves.