CRM & sales
BC PIPA for small businesses: what your website and CRM must do
BC's PIPA in plain words for small businesses: consent on forms, a named privacy contact, 30-day access requests, retention, breaches and your CRM set-up.
British Columbia's Personal Information Protection Act (PIPA) applies to most private businesses in the province, whatever their size, and it reaches straight into your website and CRM. In practice it asks five things of a small business: tell people why you collect their information before you collect it, get consent that is real (not tricked), name someone responsible for privacy and publish how to reach them, answer access requests within 30 days, and keep personal information only as long as you need it, but at least a year if you used it to make a decision about someone. Set up your forms and CRM around those five and you have covered most of what PIPA asks day to day.
Does BC PIPA apply to your business
The federal Office of the Privacy Commissioner lists British Columbia, Alberta and Quebec as the three provinces with private-sector privacy laws considered substantially similar to PIPEDA. A BC business is generally governed by PIPA for personal information it collects, uses and discloses within the province. PIPEDA still applies when personal information crosses provincial or national borders in commercial activity, and to federally regulated businesses. Where both apply, you comply with both.
PIPA also covers employee information, with its own rules. This article sticks to customers and leads.
Rule one: name a privacy contact and write it down
Section 4 of PIPA makes the organization responsible for personal information under its control, including information it doesn't physically hold. That covers data sitting in your CRM vendor's cloud. Section 4 also requires you to:
- designate one or more people responsible for compliance, and
- make their position name or title, and contact information, available to the public.
Section 5 adds that you must develop and follow the policies and practices you need to meet the Act, have a process for handling privacy complaints, and make information about both available on request.
For a ten-person company this can be one page and one email address. The OIPC's guide for businesses suggests making sure every staff member knows who the privacy officer is and including that contact in your privacy policy.
On your website: a privacy page that names the role ("Privacy Officer") and gives an email address such as privacy@yourbusiness.ca.
Rule two: consent that holds up
Tell people before you collect
Under section 10, on or before collecting personal information from someone, you must tell them the purposes for collecting it and, if they ask, the title and contact information of someone who can answer their questions. Section 7 ties these together: a person hasn't given consent under PIPA unless you've given them that information first.
Section 7 also says consent obtained with false or misleading information, or through deceptive practices, is not valid. A form that says "Get your free quote" and then quietly enrols people in a sales sequence for unrelated products is the kind of set-up that puts consent at risk.
Implicit consent covers the obvious purpose
Section 8(1) deems a person to consent when the purpose would be obvious to a reasonable person at the time and they voluntarily give the information for that purpose. A person who books an estimate online obviously expects you to use their address and phone number to do the estimate.
It does not stretch to a different purpose. Section 8(4) says so directly.
Opt-out consent has conditions
Section 8(3) allows you to use information for other specified purposes if you give an understandable notice, offer a reasonable opportunity to decline, the person doesn't decline in the time allowed, and the use is reasonable given the sensitivity of the information. The OIPC's guide recommends express consent whenever possible, especially for sensitive information.
For marketing email and texts, federal anti-spam law also applies, so the practical answer for a BC business is the same as anywhere in Canada: an unticked opt-in box.
Withdrawal
Under section 9, people can withdraw consent on reasonable notice, and you must tell them the likely consequences. Once they withdraw, you stop the collection, use or disclosure unless the Act allows it without consent.
Rule three: access requests within 30 days
Section 23 gives individuals the right to request their personal information under your control, information about how it has been and is being used, and the names of people and organizations it has been disclosed to. Section 29 sets the deadline: respond no later than 30 days after receiving the request, unless the time is extended under section 31. Individuals can also ask you to correct information.
The OIPC guide says you may charge only a minimal fee for access, it must never generate a profit, and you must give a written estimate first. You can't charge for a request for someone's own employee information.
Thirty days goes fast when the information is spread across a CRM, a shared inbox, a phone system and a spreadsheet. This is where the CRM set-up pays off.
Rule four: security
Section 34 requires reasonable security arrangements to prevent unauthorized access, collection, use, disclosure, copying, modification or disposal. The OIPC publishes a security self-assessment tool for organizations. For a small business CRM, reasonable usually means individual logins, two-factor authentication, role-based permissions and closing accounts the day someone leaves.
Rule five: retention, with a BC twist
Section 35 has two parts that pull in different directions:
- If you use someone's personal information to make a decision that directly affects them, such as approving or declining an application, you must keep that information for at least one year after using it, so they have a reasonable chance to request access.
- Otherwise, destroy personal information, or remove what links it to a person, as soon as it is reasonable to assume the purpose is no longer served and you no longer need it for legal or business purposes.
So "delete everything after 90 days" can be wrong, and "keep everything forever" is wrong too.
How your CRM should be set up for BC PIPA
| PIPA requirement | CRM or website set-up |
|---|---|
| Purpose disclosed before collection (s. 10) | Short purpose line under each form; source of each lead saved in the contact record |
| Consent for marketing | Separate, unticked opt-in field stored with the date and form name |
| Withdrawal (s. 9) | Unsubscribe and "stop" replies update one field that every sequence checks |
| Access requests in 30 days (s. 29) | Ability to export a contact's full record, notes and messages in one go |
| Security (s. 34) | Individual users, two-factor authentication, roles, export limits |
| One-year minimum after a decision (s. 35) | Tag records used for a decision; block deletion for 12 months |
| Destroy when no longer needed (s. 35) | Automated review of stale leads, for example after 24 months without contact |
| Privacy contact (s. 4) | Named role and email in your privacy policy and form notices |
Most modern CRMs can do every item in this table. What usually goes wrong is the set-up: consent stored as a free-text note nobody can filter, or unsubscribes honoured in the email tool but not in the SMS tool.
What about breaches
BC's PIPA, as consolidated in October 2026, does not contain a mandatory duty for private businesses to report privacy breaches to the Commissioner, unlike Alberta's law. That doesn't mean you can ignore a breach. The Act still requires reasonable security, and the OIPC for BC publishes a toolkit for private organizations with four steps: contain the breach, evaluate the risks, decide on notification, and prevent a repeat. It also gives an online form, or a checklist to send by email, if you decide to report.
On notifying the people affected, the OIPC suggests doing it as soon as possible, preferably directly by phone, letter or in person, and considering whether legislation or contracts require it. If PIPEDA also applies to the information, for example because it crossed provincial or national borders, PIPEDA's breach rules can come into play: report breaches that pose a real risk of significant harm to the federal Commissioner, notify affected people, and keep a record of every breach for two years. That is another reason to get advice quickly.
Penalties
Section 56 makes certain acts offences: using deception or coercion to collect personal information, disposing of information to evade an access request, obstructing or misleading the Commissioner, and failing to comply with a Commissioner's order. Fines go up to $10,000 for an individual and $100,000 for an organization. Under section 57, once a Commissioner's order or a conviction against an organization becomes final, affected individuals can also sue for damages for actual harm.
Training your team
People search for "PIPA BC training" because staff are where most privacy mistakes happen: a misdirected email, an export left in a download folder, a password reused across tools. The OIPC for BC offers free educational material through its PrivacyRight program, with webinars, videos and podcasts on PIPA obligations. Thirty minutes covering your own forms, your CRM roles and what to do if something goes wrong is more useful than a generic course.
This is a plain-language overview, not legal advice.
Where PNE fits
The CRM table above is the part we build. When PNE sets up a pipeline through our Sales Automation & CRM service, consent fields, unsubscribe handling across email and SMS, user roles and retention rules are configured from the start, so following PIPA is the default rather than a cleanup project.
Sources
- Personal Information Protection Act, SBC 2003, c 63 (current to October 13, 2026) — BC Laws
- A Guide to B.C.'s Personal Information Protection Act for Businesses and Organizations — OIPC BC
- Privacy breaches: tools and resources for the private sector — OIPC BC
- For private organizations — Office of the Information and Privacy Commissioner for British Columbia
- Provincial laws that may apply instead of PIPEDA — Office of the Privacy Commissioner of Canada
- What you need to know about mandatory reporting of breaches of security safeguards — Office of the Privacy Commissioner of Canada