Melbourne, Australia.

[email protected]
SignalControl5 July 2026

Need a policy for your tools?

Yes, you need a policy for the software tools your team uses, and it fits on one page. It answers three questions: which information never goes into an outside tool, which tools are allowed, and which actions need a person before they reach a customer.

In July 2026 Alibaba reportedly told its teams to stop using Claude Code, Anthropic's coding assistant, from 10 July, classed it as high-risk software, and pointed them to its own tool instead (TechCrunch, 4 July 2026). You are not Alibaba. The question behind its move is still one every business now faces: who decides which tools touch your information?

What is the risk?

Information leaving your control. Most online tools send what you type to someone else's servers, and the terms for what happens next vary by product and by plan. Free consumer versions are often the loosest.

Then there are the tools nobody chose. Someone pastes a client list into a free tool to draft follow-ups, or drops a file with a live password into one to fix an error. Nothing looks broken, so nobody notices.

The third risk is plain inconsistency. Ten people, ten tools, ten ways of doing the same job, and none of it repeatable.

What goes in the policy?

  • What never goes in. Your customers' personal information, passwords and keys, unreleased financials, anything under a contract or the Privacy Act. If it would hurt to see it leaked, it stays out.
  • Which tools are allowed. A short list, on business plans whose terms you have read, with training on your inputs switched off where that setting exists.
  • What needs a person. Anything that reaches a customer, changes a price or moves money.
  • When it gets reviewed. Every quarter. The tools change faster than that.

Should you ban them all?

No. A blanket ban mostly moves the use onto personal phones, where you can see none of it. A short allowed list, on terms you understand, keeps the use where you can see it.

What goes wrong?

Writing it without asking. Before the policy, ask the team, without blame, which tools they already use and for what. The honest answers are more useful than any template.

One step for this week

Spend twenty minutes with your team listing every outside tool anyone uses for work, and what information goes into each one. The riskiest line on that list is your first rule.

The privacy policy changes due by 10 December 2026 may apply too. If the Privacy Act covers your business and a tool on that list uses personal information in decisions that could reasonably be expected to significantly affect someone, the policy has to name the kinds of personal information and decisions involved.

Every system we build keeps a record of what it did and who sent it. That is what Accountable means to us.

OBSERVE.

ORCHESTRATE.

OUTPERFORM.

Every system we build starts with one call.