ClearBreach
On this page

← News & updates

May 2, 2026

AB PIPALegislation

Alberta POPA: Private Sector Implications

Alberta's POPA applies to public bodies, not private businesses, but its requirements signal exactly where PIPA reform is heading.

What happened

The Government of Alberta has published an official implementation guide for the Protection of Privacy Act (POPA), which came into force on June 11, 2025. POPA replaced the privacy portion of Alberta's former Freedom of Information and Protection of Privacy Act (FOIP), consolidating public sector privacy obligations under a single statute. The June 11, 2026 deadline for public bodies to have a formal Privacy Management Program in place is now weeks away.

POPA applies to Alberta public bodies, government ministries, municipalities, school boards, universities, colleges, and other designated entities. It does not replace PIPA, which continues to govern private sector organizations in Alberta.


Who POPA applies to

POPA applies to Alberta public bodies as defined in the Act, including:

  • Government of Alberta ministries and departments
  • Municipalities and municipal agencies
  • School boards and school authorities
  • Post-secondary institutions (universities, colleges, technical institutes)
  • Health authorities and other designated health bodies
  • Other government agencies and boards designated under the Act

Private sector organizations (businesses, professional practices, non-profits engaged in commercial activity) are not subject to POPA. They remain governed by Alberta PIPA (Personal Information Protection Act, SA 2003 c P-6.5), administered by the same regulator: the OIPC Alberta.


What POPA requires

POPA codifies privacy obligations for public bodies across three main areas:

Privacy Management Programs, mandatory by June 11, 2026 Every public body subject to POPA must have a formal Privacy Management Program in place. The program must include a designated privacy officer accountable for compliance, written policies and procedures for the collection, use, and disclosure of personal information, employee privacy training, and documented procedures for managing privacy breaches. The OIPC Alberta has published a Privacy Management Program guide to support implementation.

Privacy Impact Assessments, mandatory template POPA requires public bodies to prepare Privacy Impact Assessments in prescribed circumstances and, where the regulations require it, submit them to the commissioner (s.26). The OIPC Alberta released a mandatory PIA template on March 26, 2026. As of May 1, 2026, the OIPC will not accept PIA submissions that do not use the new template. Organizations that submitted PIAs under the old FOIP framework must now use the POPA template.

Breach notification, real risk of significant harm POPA uses the same test as Alberta PIPA: whether a reasonable person would consider that a real risk of significant harm exists. But who must be told differs. Under POPA s.10(2), a public body must notify, without unreasonable delay, the affected individuals, the commissioner and the minister. Under PIPA s.34.1, an organization must notify the commissioner, who may then require it to notify individuals (s.37.1).


POPA vs. Alberta PIPA, comparison

Alberta POPA Alberta PIPA (current)
Who it governs Public bodies (ministries, municipalities, school boards, universities) Private sector organizations
Administered by OIPC Alberta OIPC Alberta
In force since June 11, 2025 February 1, 2004
Breach test Real risk of significant harm Real risk of significant harm
Who must be notified Individuals, the commissioner and the minister The commissioner; individuals when the commissioner requires it
Privacy Management Program Mandatory (deadline June 11, 2026) Not required
Privacy Impact Assessments Mandatory in prescribed circumstances Not required; good practice

The breach test is the same and so is the regulator, but POPA requires direct notice to individuals and to the minister, which PIPA does not. On the proactive side, POPA mandates privacy management programs and PIAs for public bodies, while PIPA requires neither.


Why private sector organizations need to pay attention

Private sector organizations have two direct reasons to follow POPA closely despite not being subject to it.

Serving public body clients. MSPs and service providers that handle personal information on behalf of municipalities, school boards, or other public bodies are working with clients who now face new statutory obligations. Your public sector clients need Privacy Management Programs, will be conducting PIAs, and must notify individuals, the OIPC Alberta and the minister when a breach meets the same harm test you already know from PIPA. Understanding what they are now subject to is directly relevant to how you support them, and in some cases, your services are within the scope of their PIA obligations.

Where private sector obligations may be heading. PIPA is under review. The legislature's committee made 12 recommendations in February 2025, and the government consulted in early 2026, but no amendment bill has been introduced. POPA is the clearest recent signal of what Alberta expects from organizations that hold personal information: a documented privacy program, assessments before new programs, and direct notice to people at risk.


Where PIPA reform stands

No PIPA amendment bill has been introduced. What exists is the committee's 12 recommendations and the government's 2026 consultation. What any bill will contain, and when, is not known. See Alberta PIPA Reform for the recommendations.

Waiting is still the wrong plan. PIPA already requires a designated person responsible for compliance and reasonable security arrangements. Organizations that have documented their privacy officer, policies and breach procedures will have little to change whatever reform brings.


What to do now

For private sector organizations subject to Alberta PIPA:

  • Designate a privacy officer if you have not already done so. PIPA already requires a designated person responsible for compliance (s.5(3))
  • Document your privacy policies and procedures: written policies covering collection, use, disclosure, retention, and disposal of personal information
  • Build your breach response procedure: documented steps for assessing the risk of harm, reporting to the OIPC Alberta, and notifying affected individuals
  • Review your vendor contracts: if you hold personal information on behalf of clients, understand your contractual and regulatory obligations when a breach occurs
  • Watch for a PIPA amendment bill, and any private sector guidance the OIPC Alberta publishes alongside it

MSP implications

If you are an MSP or IT service provider with public body clients in Alberta, POPA's June 2026 deadline is immediately relevant to your client relationships.

Your public sector clients are now required to have Privacy Management Programs. If you manage their infrastructure, hold their data, or process personal information on their behalf, your services are likely within the scope of their privacy documentation obligations. Clients may request updated data processing agreements, privacy terms in your service contracts, or information about your own privacy practices as part of their compliance work.

For breaches involving public body client data, POPA uses the same harm test you know from PIPA, but your client must notify the affected individuals, the commissioner and the minister directly. Expect them to need your facts quickly.


For guidance on Alberta PIPA breach notification obligations that currently apply to private sector organizations, see Alberta PIPA Breach Notification Requirements.

ClearBreach covers privacy breach obligations under PIPEDA, Alberta PIPA, and BC PIPA for private sector organizations. POPA governs Alberta public bodies and is outside ClearBreach's direct assessment scope. Quebec Law 25 and Ontario PHIPA are also outside scope.

This article is educational and does not constitute legal advice. It is grounded in published guidance from the OPC, OIPC Alberta, and OIPC BC. If your situation involves regulatory investigation, litigation risk, or circumstances not addressed here, engage a qualified privacy lawyer.

Privacy case of the month

Once a month, a five-minute read: a real case a Canadian privacy commissioner investigated, what went wrong, and what to check in your own organization so it doesn't happen to you. Written for organizations under federal, Alberta and BC privacy law. Not written for Quebec.

We send one email to confirm. Nothing else arrives until you confirm, and an unconfirmed address is deleted after 7 days. Sent by ClearBreach Technologies Inc. Mailing address and contact details · Privacy policy