AI Connection
Terms

These AI Connection Terms apply when you connect an AI application to your BuilderShield account. They form part of the agreement between you and BuilderShield and are read together with our Terms and Conditions and Privacy Policy. If these terms are inconsistent with the Terms and Conditions on a matter about AI connections, these terms apply. Words defined in the Terms and Conditions have the same meaning here.

If you do not understand any of these terms, please contact us before you connect an AI application.

1. Definitions

"AI application" means a third-party artificial intelligence product, such as Claude or ChatGPT, that you connect to your BuilderShield account.

"AI provider" means the company that provides an AI application, such as Anthropic for Claude and OpenAI for ChatGPT.

"AI connection" means a connection you approve in BuilderShield that lets an AI application access your account.

"AI output" means anything an AI application produces using your data, including answers, summaries, notes, reports, counts and drafts.

"Draft" means a SWMS or policy that an AI application creates in your account through an AI connection.

"Your data" means the information in your BuilderShield account, including personal information and sensitive information (such as health information) about your workers, subcontractors, visitors and other people.

2. Switching on AI connections

a) AI connections are off by default. An AI application can only access your account after you switch on AI access, accept these terms and approve that application.

b) You warrant that you are authorised to accept these terms for the Customer and to approve AI connections to the Customer's account.

c) We record which version of these terms you accept and when. If we change these terms, your AI connections stop working until you accept the new version.

d) AI connections are an experimental feature. We may change, limit, suspend or withdraw them where we reasonably need to, including for security, legal or operational reasons. We will give you reasonable notice before we withdraw AI connections permanently, unless we need to act sooner for security or legal reasons. AI connections may need an active subscription.

3. What a connected AI application can do

a) A connected AI application can read the information in your account that you can see in BuilderShield, including personal information about workers and other people.

b) To limit the health information an AI application receives, BuilderShield does not share with it:

(i) the medical conditions field in site inductions; or

(ii) the fields in injury reports that record the injured person's name and contact details, who reported or witnessed the injury, what the injury was and where on the body, and the actions taken and next steps.

An AI application can read a summary of each injury report: the worker's job title, the worksite, when it happened, and the cause and the place on site as the reporter wrote them. The reporter describes the cause and place in their own words, so they can mention the injury, the part of the body or the injured person. The summary can be health information about the worker, particularly on a small site where a job title and date can identify someone. You can view everything that is withheld in the BuilderShield dashboard.

Other notes and descriptions that people type into BuilderShield, such as hazard reports and checklist comments, are shared as written. They can contain health information if the person who wrote them included it.

c) An AI application can create draft SWMS and policies in your account only if you allow it. Drafts stay hidden from workers until you review and publish them. An AI application cannot publish, change or delete any other record in your account.

d) You choose which AI applications to connect. You also choose whether each one may create drafts when you connect it, and you can change that at any time in My Account. You can disconnect an AI application, or switch off AI access completely, at any time in My Account. Disconnecting stops further access but does not recall information already sent (see clause 5).

4. AI output

a) AI output is produced by the AI application, not by BuilderShield. It may be inaccurate, incomplete or out of date. It may misread or leave out information in your data, or state something that is not in your data.

b) AI output is not professional advice. It is not safety, WHS or OHS, legal, medical, engineering or insurance advice, and it does not replace the judgement of a competent person.

c) Before you rely on, publish or share any AI output, you must check it against the records in BuilderShield. Before you publish a draft, you must make sure it is accurate, complete and suitable for the work, the site and the law that applies.

d) When you publish a draft, it becomes your document and you are responsible for its content, as you are for any SWMS or policy you create yourself.

e) Your WHS or OHS and other legal obligations remain your own, as set out in clauses 2(b) and 7(c) of the Terms and Conditions. Using an AI connection does not change them.

5. Your data, your choices and the AI provider

a) You control your data. BuilderShield holds it for you so we can provide the services.

b) When you connect an AI application, you direct BuilderShield to send your data to the AI provider you chose, so you can use it with that AI application. Our role is to provide the connection and to send only what these terms describe. The AI provider is your supplier, not ours. We do not sell your data to AI providers.

c) You are responsible for choosing the AI application and AI provider, the account and settings you use with it, how you and the AI application use your data, and giving any notice or getting any consent the law requires.

d) We are responsible for providing the connection with due care and skill, keeping it secure, and withholding the information described in clause 3(b).

e) When a connected AI application reads your data, that information is sent to its AI provider. The AI provider handles it under its own terms and privacy policy, which you agree to with the AI provider directly. BuilderShield does not control how an AI provider stores, uses or retains information.

f) AI providers may process and store information outside Australia, including in the United States of America.

g) Once information has been sent to an AI provider, BuilderShield cannot recall or delete it. To remove it, use the AI provider's own controls or contact the AI provider.

h) We keep a record of which AI application accessed your account, what kind of request it made and when, for security, support and audit purposes. We do not keep a copy of the information an AI application reads.

6. Your responsibilities

a) You must:

(i) only connect AI applications you trust, from the official provider, using accounts you control, and keep those accounts and your BuilderShield account secure;

(ii) make sure your use of AI connections complies with the privacy laws that apply to you, including giving your workers, subcontractors, visitors and other people any notice, and getting any consent, that those laws require before their personal or sensitive information is disclosed to an AI provider;

(iii) follow the AI provider's terms and usage policies when you use its AI application with BuilderShield; and

(iv) tell us promptly if you suspect an AI connection to your account has been misused.

b) You must not use an AI connection to:

(i) do anything unlawful;

(ii) make decisions that significantly affect a person, such as decisions about their employment or engagement, based only on AI output;

(iii) try to access another person's account or information; or

(iv) overload, interfere with or attack BuilderShield's services.

7. Liability

a) AI connections are provided "as is" and "as available". Subject to the Non-Excludable Conditions, BuilderShield gives no warranty that AI connections or AI output will be accurate, complete, available, free of errors or fit for any purpose.

b) To the extent permitted by law, and except to the extent the loss is caused by our breach of these terms or our negligence, BuilderShield is not liable for any loss arising from or in connection with:

(i) AI output;

(ii) your reliance on AI output, or your decision to publish a draft;

(iii) the acts or omissions of an AI provider, including how it handles information sent to it; or

(iv) any disclosure of your data to an AI provider through an AI connection you approved.

c) Where our liability for a breach of a Non-Excludable Condition can be limited, it is limited, at our option, to supplying the services again or paying the cost of having the services supplied again.

d) You indemnify BuilderShield against any loss arising from your use of AI connections in breach of these terms or of any privacy law, including any claim by a worker, subcontractor, visitor or other person about the disclosure of their information to an AI provider through an AI connection you approved. Your liability under this clause is reduced to the extent BuilderShield caused or contributed to the loss. This clause survives termination.

8. Suspension, changes and ending AI connections

a) We may suspend or disconnect an AI connection, or switch off AI connections for all customers, where we reasonably believe it is needed to protect the security of BuilderShield or your data, to comply with the law, or because an AI connection is being used in breach of these terms. Where we can, we will tell you why. We may also set reasonable limits on how many requests an AI application can make.

b) We may change these terms. We will publish the new version on this page and ask you to accept it in BuilderShield before your AI connections continue. Earlier versions are available on request.

c) You can end AI connections at any time by disconnecting an AI application or switching off AI access in My Account. Changing your password or deleting your account also ends every AI connection. While your subscription is not active, AI connections stop working.

9. Contact

For any questions about these terms, please contact:

Luke Bonnici

[email protected]