Christopher Luxon has used a non-government AI account for official Prime Minister business, a ministerial adviser in his office has confirmed in response to an Official Information Act request, Newsroom reports. As Newsroom puts it, a year ago Luxon didn’t use AI as Prime Minister. Now he does.
The political embarrassment is obvious, coming at the tail end of an election year. The more useful lesson is for business. This happened inside the organisation with arguably the tightest information governance regime in the country. If the rules can bend there, they are almost certainly bending in your company right now.
From denial to quiet adoption
Back in March 2025, Luxon’s office said in an OIA response that it did not use generative AI, apart from standard tools such as spell check, Google and Otter.AI, a transcription tool used on “hundreds, if not more” media standups.
The wider ministry was no different. In January 2026, The Post reported that despite a Microsoft Copilot rollout to ministerial offices from September 2025, complete with training on “the art of prompting”, only Erica Stanford and first-term MP James Meager admitted using AI. Winston Peters, Judith Collins, David Seymour and Shane Reti all said they didn’t.
That gap between official denial and actual behaviour is exactly what boards should worry about. Tools get rolled out, training gets run, and then people use whatever is most convenient.
The rules were already written
This isn’t a policy vacuum. The Cabinet Manual says ministers should not use personal email accounts for ministerial business, and where unavoidable must ensure material is captured for the official record and retrievable for OIA and Privacy Act requests. It also states that public records include all digital formats, including material on personal devices. Those provisions were drafted with email in mind, but an AI account used for official work sits squarely within them.
In 2025, DPMC went further. Its generative AI policy named a single approved tool, banned entering commercially sensitive, privileged or personal information into any Gen-AI tool, and required disclosure when AI contributed to formal work. Yet a September 2025 OIA response showed DPMC’s briefing templates still had no field for disclosing AI use. Policy on paper, no mechanism in practice.
Convenience always wins without enforcement
The pattern predates AI. In May 2025, Stanford admitted using personal email for government business was “not best practice”, citing roughly 8,000 pieces of correspondence. Chris Hipkins, who wrote the 2023 Cabinet Manual update on personal email, said there was “absolutely no justification” for it.
The cost of these shortcuts is real. In July, Chief Ombudsman John Allen ruled it “unreasonable” for the Prime Minister’s Office to withhold a climate lobbying note involving Fonterra and Z Energy that had been sent to a staffer’s private email. He told the office to remind staff of their obligations and review personal accounts for official information. Four months later, a non-government AI account surfaces.
Your staff are already doing this
The Institute of Directors named the private-sector version of this problem in 2025. Its analysis of “shadow AI” warned staff may input confidential data into third-party tools “without realising that information could be stored, used for model training or exposed”, and that boards may be unaware of usage “until a compliance breach or incident occurs”.
The legal exposure lands on directors. Writing for the IoD in 2025, Dentons lawyers pointed out that Companies Act duties of care and diligence don’t transfer to software. If AI fabricates or alters material and the board hasn’t built safeguards, they said, “the liability will rest with the board and the directors, not the AI provider.” They also flagged that many tools send data offshore and reserve rights to use it for training.
Companies don’t face OIA requests, but they do face the Privacy Act, client confidentiality obligations, discovery in litigation and commercial contracts that rarely contemplate a staffer pasting a draft deal into a free chatbot.
Audit, don’t ban
The answer isn’t prohibition. The IoD rightly framed shadow AI partly as a sign staff want to be more productive, and banning it just drives use further underground. The government’s own experience shows the opposite failure too: approved tools and training alone don’t change behaviour.
What works is visibility. Boards should be asking management four questions this quarter. Which AI tools are staff actually using, sanctioned or not? What data goes into them, and where is it stored? Is AI involvement in client work, board papers and contracts disclosed and recorded? And who is accountable when an output turns out to be wrong?
Luxon’s office had the Cabinet Manual, an Ombudsman breathing down its neck and a departmental AI policy, and it still ended up here. A company with a two-page acceptable use policy nobody has read should assume it’s in a worse position, and find out before a client, a regulator or a court does.
Sources
- Newsroom: Luxon used non-government AI account for official Prime Minister business (2026-11-02)
- The Post: AI in government? Just two ministers say they use it (2026-01-01)
- NZ Herald: Ombudsman rules against PM Christopher Luxon in climate lobbying document blunder (2026-07-01)
- NZ Herald: National minister Erica Stanford admits using personal email for work purposes not best practice (2025-05-06)
- FYI: Official Information Act request, Use of AI (2025-03-31)
- DPMC: Response to OIA request OIA-2024/25-1001, Use of AI (2025-08)
- DPMC: Response to OIA request OIA-2025/26-0147, Use of AI in leadership (2025-09)
- Institute of Directors: ‘Shadow AI’ signals a new digital blind spot (2025-07-09)
- Institute of Directors: AI in the boardroom, balancing efficiency with prudence (2025-05-29)
Join the discussion
Add useful context, ask a good question, or challenge an idea — keep it specific and respectful.