Local Government

“I Pay for Claude Myself” Is Not an AI Governance Plan

Daphne

The more local governments I speak to, the more I hear this:

“I just use Claude. I pay for it myself.”

I understand why.

Staff are busy. They discover a tool that can summarize a report, improve an email, compare documents or help draft a policy. The organization has not yet provided an approved AI option, so the employee pulls out a credit card and gets on with the work.

The intention is usually good.

 

The governance problem is not.

Paying for the tool does not make it approved

A personally purchased Claude Pro subscription is still a consumer account. It is not automatically part of the local government’s managed technology environment.

The organization may have no control over:

  • The account and its security settings
  • What information is uploaded
  • Where prompts and outputs are retained
  • Whether model-improvement settings are enabled
  • Who can access the account 
  • Whether records can be retrieved later
  • What happens when the employee leaves
  • Whether the arrangement meets organizational privacy, security and records requirements

Anthropic distinguishes consumer products, including Claude Free, Pro and Max, from its commercial offerings such as Claude for Work and its API. Consumer users can control certain privacy settings, but those individual choices are not a replacement for an organizational contract, approved configuration, administrative controls or internal policy. Anthropic explains its consumer data practices here.

Think about it this way.

Buying your own filing cabinet does not give you permission to take municipal records home and store them in it.

Paying for the cabinet is not the issue.

Taking the information outside the organization’s controlled environment is.

What information is being entered?

AI use becomes particularly concerning when staff enter information such as:

  • Resident correspondence
  • Employee or applicant information
  • HR documents
  • Closed meeting materials
  • Legal advice
  • Procurement submissions
  • Incident reports
  • Financial information 
  • Unpublished council reports
  • Documents containing personal or confidential information

Even when a document looks harmless, it may contain names, email addresses, opinions, identifying details or operational information that should not be placed in an unapproved system.

Removing a person’s name may not be enough if the remaining details could still identify them.

What does Alberta legislation say?

In Alberta, the Protection of Privacy Act, commonly called POPA, governs how public bodies protect personal information. Its scope includes local government bodies.

The legislation controls the collection, use and disclosure of personal information. Alberta’s official guidance also says employees must protect information against unauthorized access, collection, use, disclosure or destruction and ensure that appropriate agreements and safeguards are in place before information is handled by another system or service.

The Access to Information Act, or ATIA, separately governs access to public-body records.

That distinction matters.

POPA asks whether personal information is being protected and handled lawfully.

ATIA raises another practical question: can the local government find and produce its business records when required?

If municipal work is being completed in an employee’s personal AI account, the organization may not be able to search, retrieve, retain or app

 

ropriately dispose of the related prompts and outputs.

You can review the Government of Alberta’s POPA Guide.

What about British Columbia?

In British Columbia, local governments are subject to the Freedom of Information and Protection of Privacy Act, often referred to as FIPPA or FOIPPA.

The Act applies to records in the custody or under the control of a public body. It also requires public bodies to make reasonable security arrangements to protect personal information against risks such as unauthorized access, collection, use, disclosure or disposal.

B.C. also provides specific privacy-protection language for contracts involving service providers and cloud services. That is a useful reminder that moving personal information into a cloud tool should involve more than one employee clicking “subscribe.”

The organization needs to consider the agreement, safeguards, system configuration, access controls and internal policies surrounding the service.

You can review the B.C. Freedom of Information and Protection of Privacy Act and the province’s Privacy Protection Schedule guidance.

Claude is not the problem

 

This is not an article telling local governments to ban Claude.

Claude may be a useful tool. So may Microsoft Copilot, ChatGPT, Gemini or another approved platform.

The brand name is not the governance decision.

The organization still needs to determine:

  1. Which AI tools and account types are approved?
  2. What information may be entered?
  3. What information is prohibited?
  4. Where is the information processed and retained?
  5. Is the account governed by consumer or commercial terms?
  6. Can administrators manage access and settings?
  7. Are prompts and outputs municipal records?
  8. How will those records be retained, searched and disposed of?
  9. Has privacy, security, legal, records and procurement staff reviewed the arrangement?
  10. Who verifies the AI output and remains responsible for its use?

A paid organizational licence will often provide better contractual protections, administrative controls and governance options than a personal consumer account.

But paid does not automatically mean safe.

 

The organization must still examine the terms, configuration and intended use.

Shadow AI is also a leadership signal

When staff are purchasing their own AI tools, they are telling the organization something important.

They need help.

They have found useful technology, but the official environment has not caught up with the operational reality.

Simply telling employees “do not use AI” rarely solves the problem. It may only push the use further out of sight.

A better response is to:

  • Give staff an approved option
  • Publish clear acceptable-use rules
  • Explain what information cannot be entered
  • Provide practical training
  • Create a process for requesting new tools
  • Complete the necessary privacy and security assessments
  • Maintain an inventory of approved AI systems
  • Keep human review and accountability in every workflow

The goal is not to punish curiosity.

The goal is to make responsible use possible.

“I pay for it myself” is a billing arrangement.

It is not an AI governance framework.

If your local government needs help developing an AI policy, assessing approved tools, training staff or introducing practical AI governance, contact Catch the Beat. We can help you create guardrails that protect the organization without shutting down useful innovation.

AI can help with the work.

The organization still owns the risk, and the human still owns the decision.

This article provides general information and is not legal advice.

Contact me for all your AI Training Needs Today