CRM & sales
Alberta PIPA and your website: forms, CRM and breach reporting
What Alberta's PIPA asks of your contact forms, CRM and US-hosted tools, and how mandatory breach reporting to the Commissioner works, with a checklist.
If you run a business in Alberta, your website forms and CRM fall under Alberta's Personal Information Protection Act (PIPA), not the federal PIPEDA, for most of what you do inside the province. Three PIPA rules matter most for a small business online: tell people why you collect their information and who can answer questions, tell them when a service provider outside Canada handles it, and notify the Information and Privacy Commissioner without unreasonable delay when a breach creates a real risk of significant harm. Failing to notify the Commissioner is an offence, with fines of up to $100,000 for an organization.
Here is what that means for a contact form, a CRM, automated follow-up and the day something goes wrong.
Which law applies to you
The federal Office of the Privacy Commissioner lists Alberta, British Columbia and Quebec as the three provinces whose private-sector privacy laws are "substantially similar" to PIPEDA. Organizations covered by Alberta's PIPA are generally exempt from PIPEDA for personal information they collect, use and disclose within the province.
PIPEDA still applies in two situations that matter to many businesses:
- Information that crosses borders. PIPEDA covers personal information transferred across provincial or national borders in the course of commercial activity.
- Federal works and undertakings, such as banks, telecoms and airlines.
When both laws apply, you comply with both. A Calgary company that sells only to Albertans lives mostly under PIPA. One that sells across Canada will meet PIPEDA as well.
What PIPA asks of your website forms
Consent, including the deemed kind
PIPA's starting point (section 7) is that you need consent to collect, use or disclose personal information, and you can't require consent beyond what is needed to provide your product or service.
Section 8 makes this workable. A person is deemed to consent when they voluntarily give you information for a purpose and it is reasonable that they would. Someone who fills in your quote form to get a quote has consented to you using their details to prepare and send that quote. They have not consented to everything else.
Section 8(3) allows an opt-out approach for additional purposes if you give a clear notice, a reasonable chance to decline, and the purpose is reasonable given how sensitive the information is. Adding a quote requester to a monthly newsletter is the classic grey zone. Federal anti-spam law (CASL) also governs commercial emails, so for marketing emails the cleaner path is an unticked opt-in box.
The notice at the point of collection
Section 13 requires you, before or at the time you collect information from a person, to tell them:
- the purposes for which you are collecting it, and
- the name, or position name or title, of someone who can answer their questions about the collection.
In practice, put one or two plain sentences under the form, for example: "We use these details to reply to your request and send your quote. Questions about your information? Contact our privacy officer at privacy@yourbusiness.ca." Then link to a privacy policy that says the same thing in more detail.
The Alberta rule most websites miss: service providers outside Canada
Section 13.1 is specific to Alberta. If you use a service provider outside Canada to collect personal information, or you transfer personal information collected with consent to a service provider outside Canada, you must tell people, before or at the time of collection or transfer:
- how they can get written information about your policies and practices for service providers outside Canada, and
- the name or title of a person who can answer their questions about it.
Most small business tools are hosted outside Canada: many CRMs, email platforms, form builders, chat widgets and scheduling apps run on US servers. If your form posts straight into a US-hosted CRM, section 13.1 applies. The fix is short. Name the practice in your privacy policy ("We use service providers in the United States for our CRM and email; contact our privacy officer for details on how they handle your information") and point to that section from the form notice.
What PIPA asks of your CRM
Security
Section 34 requires reasonable security arrangements against unauthorized access, collection, use, disclosure, copying, modification, disposal or destruction. For a CRM, "reasonable" usually means:
- one login per person, never shared accounts
- two-factor authentication on the CRM, the email platform and the website admin
- user roles, so a summer student can't export the full contact list
- removing access the same day someone leaves
- knowing where exports go, and deleting old CSV files from laptops and shared drives
Retention
Section 35 lets you keep personal information only as long as you reasonably need it for legal or business purposes. After that, within a reasonable time, you must destroy it or make it non-identifying. A CRM that keeps every lead from 2017 "just in case" doesn't meet that standard. Set a rule, for example: unconverted leads are deleted after 24 months without contact, and customer records are kept for as long as tax and warranty obligations require. Then build the rule into the CRM as a recurring task or automation.
Access requests
People can ask for their personal information. Under section 28, you must respond within 45 days of receiving the written request, unless the time is extended under the Act. Treat an unanswered request as serious: the Act says a failure to respond in time is treated as a decision to refuse. A CRM that lets you search a contact and export everything about them, including notes, call logs and messages, turns a stressful request into a 20-minute task.
Automated follow-up
Automated email and SMS sequences use personal information for a purpose. Check that the purpose was disclosed at collection, that the person consented (express or deemed), and that unsubscribes are honoured right away across every tool that sends messages.
Breach reporting: how it works in Alberta
This is the part of PIPA that most clearly sets Alberta apart for small private businesses, because reporting to the Commissioner is a legal duty with a penalty attached.
The test
Section 34.1 requires an organization with personal information under its control to notify the Commissioner, without unreasonable delay, of any loss of or unauthorized access to or disclosure of personal information where a reasonable person would consider there is a real risk of significant harm to an individual.
The OIPC's guidance lists the incidents it sees most: lost or stolen laptops and USB drives, misdirected emails, staff snooping in customer records, hacked websites and servers including ransomware, phishing, and careless disposal of records. For a small business, a compromised email account or a CRM login stolen through phishing is the realistic scenario.
You are responsible even when a vendor holds the data
The duty belongs to the organization that has control of the information, not necessarily the one that holds it. The OIPC explains that a contractor can have custody of data while you keep control, because you decide the purposes, the security and the disposal. If your CRM vendor is breached, you are still the one who must assess and notify. You can authorize a third party in writing to notify on your behalf.
What the notice must contain
Section 19 of the PIPA Regulation lists what your written notice to the Commissioner must include:
| Required item | Practical note |
|---|---|
| Description of what happened | Plain facts, no speculation |
| Date or time period of the incident | Estimate if unsure, and say so |
| Personal information involved | Fields, not just "customer data" |
| Your assessment of the risk of harm | Why the risk is real and significant, or not |
| Estimated number of people at real risk | A range is better than nothing |
| Steps taken to reduce the harm | Passwords reset, access revoked, accounts monitored |
| Steps taken to notify individuals | Or your plan to do so |
| Contact person for the Commissioner | Name and contact details |
The OIPC provides a PIPA Breach Notification Form for this. Its guidance recommends notifying as soon as possible even if your investigation is not finished, rather than waiting until every box can be filled in.
Telling the people affected
The Commissioner can require you to notify affected individuals, and you can notify them on your own initiative. The OIPC reports that since 2012-2013, at least 80% of organizations had already told individuals by the time they reported. The notice to individuals must be given directly and include what happened, when, what information was involved, the steps you have taken to reduce harm, and a contact person.
Penalties
Under section 59, failing to notify the Commissioner as section 34.1 requires is an offence. The maximum fine is $10,000 for an individual and $100,000 for an organization. Once a Commissioner's order against an organization becomes final, affected individuals can also sue for damages under section 60.
A one-page Alberta PIPA checklist
- Name a person responsible for privacy and give them an email address.
- Add a two-line purpose notice under every form, with that contact.
- List your service providers outside Canada and say so in your privacy policy (section 13.1).
- Use an unticked box for marketing emails and texts.
- Turn on two-factor authentication and remove shared logins.
- Set a retention rule for leads and customers, and automate it in the CRM.
- Practise an access request: find one contact and export everything.
- Save the OIPC breach form and a one-page "who does what" plan.
- Ask each vendor how and how fast they will tell you about a breach.
This is a plain-language overview, not legal advice. For an actual breach, or for health or financial information, get advice early.
How PNE fits in
Most of this checklist lives in your CRM and forms: purpose notices, opt-in boxes, user roles, retention rules and clean exports. When PNE builds a pipeline through our Sales Automation & CRM service, those settings are part of the set-up rather than an afterthought, so your team gets the automation without inheriting a privacy problem.
Sources
- Personal Information Protection Act, SA 2003, c P-6.5 (consolidated to September 1, 2025) — Alberta King's Printer
- Personal Information Protection Act Regulation, AR 366/2003 — Alberta King's Printer
- Breach notification — Office of the Information and Privacy Commissioner of Alberta
- Guidance for notifying the OIPC about a privacy breach under PIPA (April 2024) — OIPC Alberta
- Provincial laws that may apply instead of PIPEDA — Office of the Privacy Commissioner of Canada