multiRent — Gestion de copropriétésmultiRent — Gestion de copropriétésmultiRent — Gestion de copropriétésmultiRent — Gestion de copropriétés
  • Services
  • Packages
  • Changing managers
  • Partners
  • Our team
  • Blog
  • Contact
  • Français
Portal
✕
28/08/2026
Categories
  • Bill 16 & Legal Framework
Tags
  • Board of Directors
  • Immovable By-Laws
  • Law 25

Bill 25 and IoT Sensors in Condominiums: PIAs and Consent

By Muriel Druart, Client services director

IoT sensors are becoming increasingly common in buildings. In divided co-ownerships in Quebec, they help prevent water damage, optimize energy use and improve security. But as soon as they process personal information, Bill 25 applies. Your board of directors (the board) must then ensure clear governance: a PIA (privacy impact assessment), consent, policies and contracts.

This article guides you step by step through integrating IoT sensors into your condominium while complying with Bill 25 and protecting the common portions, private portions and privacy of co-owners and occupants.

Why install IoT sensors in a condominium?

IoT sensors have several practical applications for a syndicate of co-owners:

  • Detecting water leaks in mechanical rooms, garages or risers.
  • Monitoring temperature and humidity to prevent mould and optimize energy costs.
  • Smart meters (water, energy) to balance common expenses and inform the budget.
  • Opening sensors on exit doors or in stairwells for security.
  • Alert buttons in gyms, swimming pools or parking areas.

These devices reduce losses and support preventive maintenance. They can be integrated into the maintenance logbook/EUC and help the board plan interventions without unnecessarily increasing condo fees. However, if they can identify a person directly or indirectly (e.g., an entry log linked to a unit), Bill 25 imposes specific obligations.

What Bill 25 requires of a syndicate of co-owners

Bill 25 modernizes the Act respecting the protection of personal information in the private sector. It governs the collection, use, disclosure, retention and destruction of personal information. In practical terms, a syndicate must:

  • Designate a person responsible for the protection of personal information (often the board president) and publish their contact information.
  • Adopt a personal information governance policy that is accessible and proportionate to the syndicate’s activities.
  • Keep a register of confidentiality incidents and, where necessary, notify the individuals concerned and, depending on the severity, the authorities.
  • Conduct a PIA for any technology project that presents a high risk to privacy, including the implementation of sensors that make it possible to track individuals.

Under the Civil Code of Québec, the syndicate must also ensure the preservation of the building and the administration of the common portions in the collective interest. The board must therefore reconcile security, maintenance and respect for people’s rights. Refer to the Civil Code of Québec and Act P-39.1 for the official texts:

  • LégisQuébec – Civil Code of Québec
  • LégisQuébec – Act respecting the private sector (P-39.1), modernized by Bill 25

For systems connected to fire safety, verify compliance and maintenance with the RBQ:

  • RBQ – Fire safety systems

Guidelines and best practices for syndicates are also published by the RGCQ:

  • RGCQ – Co-ownership resources

PIAs for your IoT sensors: step by step

A PIA documents privacy risks and mitigation measures. It is conducted before the system goes live and updated when major changes are made (a new type of sensor, a new supplier or interconnection with other systems).

When is a PIA required?

  • The project involves collecting, analysing or disclosing data that may identify an individual (e.g., access cards correlated with a unit, geolocation or time-stamped recordings).
  • The device monitors areas where individuals regularly circulate, even if these are common portions.
  • The data is hosted by a third party or outside Quebec.

If the sensors measure only aggregated parameters that cannot be linked to an individual (e.g., the temperature of a boiler room without an access log), the PIA may be simplified, but a brief written analysis remains advisable.

Minimum content of a PIA

  • Description of the project and its legitimate objectives (loss prevention, compliance and maintenance).
  • Data mapping: what data is collected, where it comes from, to whom it is transmitted and where it is stored.
  • Legal basis: is consent required? Is there a legal obligation? Is it necessary for the safety of individuals or property, where appropriate?
  • Risk analysis: intrusions, re-identification, unauthorized access and excessive retention.
  • Mitigation measures: minimization, encryption, access controls, logging, anonymization and retention/destruction policies.
  • Assessment of transfers outside Quebec and contractual safeguards with suppliers.
  • Communication plan and procedure for responding to access or rectification requests.

A non-technical summary of the PIA should be presented at the AGM and attached to the minutes to ensure transparency for co-owners.

Informed consent from co-owners and occupants

As a general rule, consent must be express, freely given, informed and provided for specific purposes. Transparency is essential: clearly explain the “why,” “what,” “how” and “how long.”

  • Common portions: signage and an accessible policy may be sufficient when the use is necessary and proportionate (e.g., a flood sensor in a mechanical room). If individual tracking becomes possible, obtain explicit consent.
  • Private portions: avoid installing sensors without authorization. If a building regulation provides for it, ensure that it complies with Bill 25 and the declaration of co-ownership. Prioritize solutions in technical spaces or sensors voluntarily provided to co-owners with information and consent.
  • Tenants and visitors: inform them with clear signage and instructions at the entrance. Provide a contact person for questions.

The board must also:

  • Provide a mechanism for exercising rights (access and rectification) and an address for the person responsible.
  • Document the data life cycle (from collection to deletion) in a policy.
  • Update the building regulations as needed and have changes approved at the AGM, with a mention in the minutes.

Use templates as a starting point, but adapt them to your circumstances. For operational and administrative support, see our services: https://www.multirent.ca/services/#gestion-administrative and https://www.multirent.ca/services/#gestion-des-operations.

Governance, security and contracts: best practices

Technology is not enough; governance makes the difference. Here is a practical framework for your syndicate:

  • Minimization: collect only what is necessary for the legitimate objective. Disable unused functions (audio and precise geolocation).
  • Configuration: by default, set the highest level of privacy compatible with operations (privacy by default).
  • Security: encryption in transit and at rest, key rotation, network segmentation and strong authentication for the manager and board members.
  • Access: follow the principle of least privilege; log and regularly review access.
  • Retention: set limited, justified retention periods and apply automatic deletion.
  • Hosting: favour suppliers offering contractual safeguards suited to Quebec, including incident notification, controlled subcontracting and audits.
  • Testing: run a limited pilot, assess its impact and make adjustments before full deployment.
  • Procedures: integrate the sensors into your maintenance logbook/EUC and your incident response plan.
  • Training: make the concierge, maintenance contractor and managers aware of the actions to take and avoid.

When a system interacts with fire safety or other regulated systems, verify RBQ compliance and work with duly licensed contractors. Also consult the official references for up-to-date texts:

  • LégisQuébec – P-39.1 (Act respecting the private sector)
  • LégisQuébec – Civil Code of Québec
  • RBQ – Fire safety information
  • RGCQ – Resources and best practices

To stay on track and prioritize actions, centralize your documentation (PIAs, contracts, technical specifications and procedures) in a shared repository with controlled access for the board and your manager.

Quick FAQ

– Are we required to obtain an AGM vote to install IoT sensors? This depends on the scope of the work and its impact on the use of the common portions. For transparency, present the project, attach a summary of the PIA to the minutes and have any amendment to the building regulations ratified.

– Can we install sensors in units? Avoid imposing sensors in private portions unless there is a clear obligation in the declaration of co-ownership or validly adopted regulations. Prioritize voluntary measures with written consent and detailed information.

– Who is responsible in the event of a confidentiality incident? The syndicate remains responsible, even when a supplier is involved. Include robust contractual clauses and keep an incident register in accordance with Bill 25.

Would you like to learn more about governance and compliance? Browse our blog: https://www.multirent.ca/blog/ and learn how we organize the day-to-day management of a syndicate: https://www.multirent.ca/services/.

This article provides general information and does not constitute legal advice. Consult a lawyer or notary for your situation.

Do you manage a condominium in Quebec? Explore our plans or contact us to assess your needs.

Managing your condo building with multiRent

  • Bill 16 compliance
  • Condo maintenance logbook
  • Condo management pricing

Areas served: South Shore · Montreal · Laval · Longueuil · Brossard · Boucherville · Saint-Constant · Saint-Amable · Saint-Jérôme

Share

Related posts

09/10/2026

The President’s Casting Vote in a Quebec Co-ownership


Read more
07/10/2026

Unpaid Source Deductions: Directors’ Liability


Read more
06/10/2026

Cooling-off Period for Buying a Condo in Quebec: The Rules


Read more

Comments are closed.

multiRent — Gestion de copropriétés

Services

Administrative management

Financial management

Operations management

Portal

About Us

The multiRent team

Contact us

Notaries

LinkedIn

RGCQCorporate member of the RGCQ

Resources

RGCQ

CORPIQ

Portal
    Manage Consent

    To give you the best possible experience, we use technologies such as cookies to store and/or access information about your device. Consenting to these technologies lets us process data such as browsing behaviour or unique identifiers on this site. Declining or withdrawing your consent may affect certain features.

    Functional Always active
    Technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. Technical storage or access used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your internet service provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    Technical storage or access is required to create user profiles in order to send advertising, or to track the user across a website or several websites for similar marketing purposes.
    • Manage options
    • Manage services
    • Manage {vendor_count} vendors
    • Read more about these purposes
    Manage preferences
    • {title}
    • {title}
    • {title}