What does PIPEDA require of appliance repair bookings in Canada?

What to take away

What PIPEDA covers when a customer books an appliance repair

PIPEDA applies to private-sector organizations that collect, use or disclose personal information in the course of commercial activity. When a customer books an appliance repair, you are collecting personal information: name, phone number, address, unit number and access codes.

That information is protected under the Personal Information Protection and Electronic Documents Act. The law sets out how you must handle it, from the moment the booking is taken to the day you delete the record.

The Office of the Privacy Commissioner of Canada oversees PIPEDA and provides guidance for businesses. It expects you to know what data you hold, why you hold it, and how you protect it.

A booking is not just a scheduling event. It creates a record that includes where someone lives, how to get into their home, and what appliances they own. That combination is sensitive enough to require real safeguards.

PIPEDA applies to any organization that handles personal information in commercial activity, including a two-person appliance repair business.

Your booking process likely spans several tools: a phone, a scheduling app, a spreadsheet, a payment terminal and a technician's mobile device. Each one is a place where customer data can be exposed.

PIPEDA also covers disclosure. If you share customer details with a parts supplier, a subcontractor or a warranty company, that is a disclosure under the Act and it needs a lawful basis.

This article covers the practical duties: what to collect, how to get consent, how to store addresses and access codes, when to report a breach, and how to handle access requests. It also explains when provincial law applies instead.

For a broader view of the rules that apply to a new repair business, including licensing and consumer protection, see our compliance checklist.

The ten fair information principles applied to booking records

The ten fair information principles are the backbone of PIPEDA. They are not abstract. Each one maps to a decision you make when a customer books a repair.

The Office of the Privacy Commissioner of Canada publishes the full text of these principles and how they apply. You can read them on the PIPEDA fair information principles page.

In practice, the principles interact. Limiting collection makes retention easier. Good safeguards reduce breach risk. Clear purposes make consent meaningful.

Your booking form is where most of these principles either hold or fail. If the form asks for too much, consent is vague, or the data goes into an unsecured spreadsheet, you are offside on several principles at once.

A simple test: for every field on your booking form, ask which principle justifies it. If you cannot answer, remove the field.

Consent for marketing: reminders, reviews and repeat-call lists

When a customer books a service call, they consent to the repair. They do not automatically consent to seasonal reminders, review requests or being added to a repeat-call list.

PIPEDA requires meaningful consent for marketing uses. That means the customer must understand what they are agreeing to and why. A pre-checked box on a booking form is not meaningful consent.

There are three common marketing activities in appliance repair, and each needs its own approach.

Service reminders. A reminder that a filter needs changing or a warranty is expiring is marketing if it promotes your services. Ask for consent separately, either at booking or after the job.

Review requests. Asking for a review is generally a marketing use. If the request comes from a third-party platform, check what data you are sharing and whether the customer agreed to it.

Repeat-call lists. Adding a customer to a list for future promotions requires consent. You can ask at the time of service, but the request must be clear and the customer must be able to say no without losing service.

Consent can be express or implied, but implied consent is limited. For marketing, express consent is safer and easier to prove. Keep a record of when and how consent was given.

Customers can withdraw consent at any time, subject to legal or contractual restrictions. Your booking system should make that easy: a one-click unsubscribe, a note in the customer record, and a process to stop future marketing.

If you use a booking system that sends automated reminders or review requests, check its default settings. Many tools opt customers in by default, which can put you in breach of PIPEDA.

Marketing consent also interacts with Canada's anti-spam law, which has its own consent rules for commercial electronic messages. PIPEDA and anti-spam law are separate, but they often apply to the same email or text.

For more on setting up procedures that keep consent and service delivery consistent, see our guide to keeping operations consistent every day.

Storing customer details: addresses, access codes and unit numbers

Addresses, unit numbers and access codes are the most sensitive data in an appliance repair booking. They tell someone exactly where a customer lives and how to get inside.

PIPEDA requires safeguards proportionate to the sensitivity of the information.

Start with collection. Do you need the access code stored after the job? Often you do not. If the customer will not be home, you may need it for the visit, but you can delete it once the work is done.

If you must keep an access code for a return visit, store it separately from the customer's name and address where possible. Limit who can see it to the technician assigned and the dispatcher.

Unit numbers and buzz codes are similar. They are operational details, not marketing data. Keep them out of any system that sends bulk messages or shares data with third parties.

For rental and strata properties, privacy duties can involve the landlord or property manager as well as the tenant. The Office of the Privacy Commissioner of Canada has guidance on landlords and tenants that is useful when a repair booking crosses those lines.

If a property manager books a repair for a tenant, clarify who is the customer and whose consent you need. The tenant's personal information still belongs to the tenant.

Physical safeguards matter too. Paper work orders with addresses and codes should be locked up or shredded after entry. Technician vehicles should not carry visible customer lists.

Digital safeguards include password protection, encryption on mobile devices, and role-based access in your booking system. Not every staff member needs to see every customer's access code.

Retention is part of storage. Decide how long you keep booking records and stick to it. A common approach is to keep service records for warranty and tax purposes, then delete the rest.

When you delete, delete properly. Deleting a customer record from your booking app may leave copies in backups, email or a technician's phone. Include those in your retention policy.

Breach reporting duties and record-keeping timelines

A privacy breach is any loss, unauthorized access, disclosure or alteration of personal information. It can be a hacked booking system, a lost phone, a misdirected email or a break-in at your office.

PIPEDA requires you to report a breach to the Office of the Privacy Commissioner of Canada if it poses a real risk of significant harm to an individual. You must also notify affected individuals if there is a real risk of significant harm.

Significant harm can include identity theft, financial loss, humiliation or damage to reputation. The test weighs the sensitivity of the personal information and the probability it will be misused. A leaked access code combined with an address could facilitate a break-in, which is significant harm.

You must also keep a record of every breach, even ones you do not report. The record must include the date, the nature of the breach, what was involved, and what you did about it.

Keep each record for 24 months after the day you determine the breach occurred. That period comes from the Breach of Security Safeguards Regulations.

The Privacy Commissioner can ask to see these records. If you cannot produce them, you are in breach of the record-keeping duty.

Reporting must be done as soon as feasible after you determine a breach has occurred. Do not wait to complete a full investigation before making the report. Report what you know and update as you learn more.

File the report through the OPC's online breach report form. The form asks for the date of the breach, the personal information involved, how many people are affected, and the steps you took.

If the breach involves a service provider, such as your booking software vendor, you still have reporting duties. Contracts should require the vendor to notify you promptly so you can meet your obligations.

Record retention timelines are not one-size-fits-all. Tax records have their own retention rules under the Canada Revenue Agency. Privacy records, including breach logs and consent records, should be kept long enough to demonstrate compliance.

A practical approach: keep consent records for as long as you rely on them, and service records for your warranty period plus any tax requirement.

If you are not sure whether a breach is reportable, err on the side of reporting. The Privacy Commissioner would rather see a report than hear about a cover-up.

Training matters here. Staff must know how to recognize a breach and who to tell. A technician who loses a phone should report it the same day, not at the end of the month.

For a fuller picture of how privacy fits into daily operations, including dispatch and follow-up, see our workflow for owners.

Provincial privacy commissioners and when provincial law applies instead

PIPEDA applies across Canada, but it is not the only privacy law. Some provinces have their own private-sector privacy laws that have been deemed substantially similar to PIPEDA.

In those provinces, the provincial law applies instead of PIPEDA to most private-sector organizations. The provinces with substantially similar private-sector laws include Quebec, Alberta and British Columbia.

Quebec's law is An Act respecting the protection of personal information in the private sector. Alberta has the Personal Information Protection Act. British Columbia has its own Personal Information Protection Act.

Ontario has privacy laws for the public sector and health information, but its private-sector privacy law is not substantially similar to PIPEDA for general businesses. That means PIPEDA applies to most Ontario appliance repair businesses.

Other provinces, including Manitoba, Saskatchewan, Nova Scotia and Newfoundland and Labrador, have health information privacy laws, but general private-sector organizations fall under PIPEDA.

If you operate in more than one province, you may need to comply with more than one law. A repair business serving customers in Quebec and Ontario must follow Quebec's law for Quebec customers and PIPEDA for Ontario customers.

The practical differences matter. Quebec's law has specific requirements for privacy officers, consent and breach reporting. Alberta and British Columbia have their own breach reporting rules and timelines.

Provincial privacy commissioners enforce their own laws and can investigate complaints. The Office of the Privacy Commissioner of Canada handles PIPEDA complaints and can work with provincial counterparts.

When a customer complains, the first question is which law applies. That depends on where the customer lives and where your business operates. Get advice if you serve multiple provinces.

The Office of the Privacy Commissioner of Canada provides guidance for businesses on its privacy for businesses page, including how PIPEDA interacts with provincial laws.

Practical booking system setup for PIPEDA compliance

Your booking system is where privacy compliance either works or fails. Configure it deliberately, not by default.

Start with data fields. Collect only what the job needs: name, contact number, service address, appliance type and a description of the problem. Avoid collecting date of birth, social insurance number or payment card details unless you have a clear need and safeguards.

Separate access codes from the main customer record. If your system allows custom fields, put door codes and alarm codes in a restricted field that only dispatch and the assigned technician can see.

Set retention rules. Most booking systems let you archive or delete records after a set period. Decide your retention period and automate deletion where possible.

Control user access. Use role-based permissions so technicians see only their assigned jobs, and office staff see only what they need. Review permissions when staff leave.

Turn off default marketing. Check whether your booking tool automatically adds customers to email lists or sends review requests. If it does, change the setting to opt-in.

Log access to sensitive records. If your system can record who viewed or exported customer data, enable it. Logs help you investigate a breach and show accountability.

Prepare for access requests. A customer can ask what personal information you hold about them. Your system should let you search by name, phone or address and export the record.

Use a checklist before you go live with any new booking tool:

Put a plain consent sentence on the booking form. For example: 'I agree that the company may use my contact details to schedule and complete the repair I booked.' Keep any marketing request as a separate, unchecked box.

A one-page policy can follow this skeleton:

If you are comparing tools, our notes on choosing appliance repair software cover privacy settings alongside scheduling and reporting features.

Test the setup with a real booking. Walk through the customer experience: what they see, what they consent to, where their data goes, and how you would delete it.

Train staff on the system. A well-configured tool fails if a technician writes an access code on a paper napkin or shares a login.

Handling access requests from customers in your booking database

Under PIPEDA, customers have the right to access the personal information you hold about them. They can also ask you to correct errors.

An access request can come by phone, email or in person. You should have a written process for handling it, and staff should know who to route it to.

When you receive a request, acknowledge it promptly. You have 30 days to respond, though you can ask for an extension in limited circumstances. An extension can add up to 30 days when meeting the deadline would unreasonably interfere with operations, when you need to consult others, or when records must be converted to another format.

Before releasing information, verify the requester's identity. You do not want to send a customer's address and access code to someone impersonating them.

Provide the information in an understandable form. That can be a printout, a PDF or an email summary. Explain any codes or abbreviations used in your records.

If the customer says something is wrong, correct it. Send the correction to anyone you disclosed the information to in the previous year, if they can reasonably be expected to rely on it. If you disagree, note the correction request in the file and tell the customer what you did.

There are limited exceptions. You can refuse access if it would reveal personal information about another person, or if the information is protected by solicitor-client privilege. Other narrow grounds include information generated in a formal dispute resolution process and information collected under a government contract for law enforcement.

You can charge a minimal fee for access, but it must be reasonable and you must tell the customer in advance. Many businesses waive the fee for simple requests.

The Office of the Privacy Commissioner of Canada explains these rights on its accessing personal information page. The same page covers how to complain if a business refuses access.

If a customer is unhappy with your response, they can complain to the Privacy Commissioner. A clear, documented process reduces the chance of a complaint escalating.

Keep a log of access requests: date received, requester, what was provided, and any corrections. This log is part of your accountability record.

Access requests are also a service quality issue. How you handle a customer's data request reflects on how they handle their repair. Our article on keeping service quality honest looks at the broader picture.

Common questions