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
✕
31/08/2026
Categories
  • Bill 16 & Legal Framework
Tags
  • Board of Directors
  • Immovable By-Laws
  • Law 25

Amazon Key for Business in a Quebec Condominium: Bill 25

By Muriel Druart, Client services director

Deliveries are increasing, and your divided co-ownership must keep pace without compromising security. Amazon Key for Business promises smoother access to common portions for delivery personnel. In Quebec, however, this tool directly affects personal information and access management. Your board of directors (the board) must therefore balance efficiency, Bill 25 and co-owners’ peace of mind.

In this guide, we explain how to assess Amazon Key for Business from a legal (Bill 25), technical and operational perspective, and how to implement it responsibly in a Montreal condominium.

What is Amazon Key for Business in a condominium context?

Amazon Key for Business is a system that allows authorized delivery personnel to remotely open a building’s door to leave parcels in the common portions, such as a vestibule or receiving room. Access generally relies on integration with the existing intercom/access controller and real-time validation by the delivery provider.

What this changes for a co-ownership:

  • Fewer intercom calls and fewer doors left ajar by visitors.
  • Better traceability of door openings (time-stamped access log).
  • More traffic through common portions, requiring clear monitoring and information measures.

What information and events may be processed:

  • Technical device identifiers, access timestamps, the targeted door and opening status.
  • Potentially, the delivery person’s identifier and shipment number (if integrated). These are personal information within the meaning of Bill 25 when they make it possible to identify a person.
  • Usage data useful for diagnostics and cybersecurity.

Your syndicate is therefore responsible for the terms of use, the choice of provider and the retention/destruction procedures for access logs.

Bill 25: your key obligations, from the project through to operation

The Act to modernize legislative provisions as regards the protection of personal information (Bill 25) applies to syndicates of co-owners when they collect, use or communicate personal information through an access system. The Act respecting the protection of personal information in the private sector is available on LégisQuébec (P-39.1).

What your board must plan for before and during use:

  • Appoint a person in charge of the protection of personal information (PPRP) and publish their contact information.
  • Conduct a privacy impact assessment (PIA) before deploying the system, since this is a project involving personal information and technology.
  • Define a legal basis and a serious and legitimate purpose: security, access traceability and reducing parcel losses in the common portions.
  • Minimization: record only the necessary data (e.g., time, door and technical identifier) and avoid collecting anything non-essential.
  • Transfers outside Quebec: if the provider hosts logs in another jurisdiction, conduct an assessment of the factors relating to the communication and require adequate contractual safeguards.
  • Provider agreements: add clauses covering confidentiality, security, subcontracting, retention/destruction and incident notification.
  • Maintain a register of confidentiality incidents and a notification procedure where there is a risk of serious injury.
  • Adopt a clear retention and destruction policy: for example, a short and proportionate period (e.g., 30 to 90 days), except where an incident is ongoing.
  • Transparency: inform occupants and visitors (posting near the door, email notice) about how the system works, the data processed and the PPRP’s contact information.

Roles and responsibilities

  • Syndicate/board: implementation decision, appointment of the PPRP, adoption or updating of the building regulations, provider oversight and accountability.
  • Manager: operational implementation, record-keeping, responses to access/correction requests and incident follow-up.
  • Provider: contractual obligations relating to security, confidentiality, availability and assistance in the event of an incident.

Useful resources:

  • Act respecting the protection of personal information in the private sector (P-39.1) on LégisQuébec: https://www.legisquebec.gouv.qc.ca/fr/document/lc/P-39.1
  • Condominium best practices through the RGCQ for governance and communications with co-owners: https://rgcq.org/

Legal and regulatory impacts in a co-ownership

Automated delivery access affects the use of the common portions. The decision is not limited to technical matters; it falls within the legal framework governing co-ownership:

  • Declaration of co-ownership (DCV) and building regulations: check whether the use of vestibules and access management must be specified or amended. An amendment to the building regulations may require a co-owner vote at the AGM, depending on the rules in your DCV and the Civil Code of Québec.
  • Civil liability and security: the syndicate must take reasonable steps to prevent intrusions, theft or damage. A camera is not mandatory, but proper signage, an access log and response procedures are essential.
  • Technical compliance: the installation or modification of an access controller/intercom should be performed by a contractor holding the appropriate licences and in accordance with applicable Régie du bâtiment du Québec (RBQ) standards.
  • Access to private portions: the tool must not allow entry into units; it is intended exclusively for doors serving the common portions.

Useful references:

  • Civil Code of Québec, provisions on divided co-ownership, on LégisQuébec: https://www.legisquebec.gouv.qc.ca/fr/document/cs/CCQ-1991
  • RBQ, information on contractors and building work: https://www.rbq.gouv.qc.ca/
  • RGCQ, resources on condominium governance: https://rgcq.org/

Implementing a compliant and secure system

Here is a proven framework for an Amazon Key for Business project, from analysis through operation:

1) Analysis and PIA

  • Map the targeted access points (doors, vestibule and parcel room), the data generated and the recipients.
  • Assess risks and mitigation measures: limited access logs, encryption, retention periods and human oversight.

2) Decision-making framework and documents

  • Board resolution detailing the purpose, scope and security measures.
  • Update the building regulations as needed (e.g., receiving area, occupants’ obligations for collecting parcels and mandatory signage). Submit the matter to the AGM if required and record it in the minutes.
  • Notice to co-owners and occupants: how the system works, contact persons and access rights to information.

3) Contracts and compliance

  • Add a confidentiality addendum with the provider covering retention, destruction, incidents, subcontracting, data location and audits.
  • Require proof of compliance and technical safeguards (logging, access controls and penetration testing where available).

4) Installation and testing

  • Have the system installed by a qualified contractor. Test access scenarios (delivery, failure and loss of connectivity) and fallback mechanisms.
  • Check compatibility with the intercom and door (complete closing, anti-pry protection and limited opening time).

5) Operations and continuous improvement

  • Maintain a register of access events, incidents and information requests. Destroy logs when the prescribed period expires.
  • Review the PIA, contractual clauses and occupant notice annually. Adjust them based on feedback and incidents.

Decision-making table

Access option Advantages Risks Bill 25 measures
Traditional intercom (without integration) No new data flows; manual control More calls; doors sometimes left open Minimal notice; incident register as needed
Parcel box/mechanical key Simplicity Lost/duplicated key; limited traceability Holder register; strict policies
Amazon Key for Business Traceability; efficiency; fewer disturbances Data logging; provider dependence PIA, contractual clauses, limited retention and transparency
Third-party access app managed by the syndicate Greater control; possible integration Management complexity and costs PIA, IT governance and periodic audits

Governance tip: include this system and its maintenance in your maintenance logbook (EUC) to plan updates, tests and mechanical inspections.

multiRent resources to help you:

  • Discover our administrative management services to structure resolutions, minutes and communications: https://www.multirent.ca/services/#gestion-administrative
  • See how operations management integrates security, access and maintenance: https://www.multirent.ca/services/#gestion-des-operations
  • Compare our packages according to your syndicate’s needs: https://www.multirent.ca/#forfaits

Governance, operational security and ongoing communication

Beyond the initial deployment, success depends on clarity and discipline:

  • Signage: post a notice near the door explaining the mechanism, purpose and PPRP contact information.
  • Procedures: define who may activate/deactivate access, how to respond to an incident and how to suspend the service in the event of abuse.
  • Physical security: periodically check the door closer, magnet/handle, power supply and UPS. Avoid settings that leave the door ajar.
  • Annual review: provide the board with a brief report (aggregated access log, incidents, requests received and improvements). Inform the AGM as needed.
  • Individual rights: establish a simple procedure for responding to requests for access to or rectification of personal information.

Useful links for further information:

  • LégisQuébec – Act respecting the protection of personal information in the private sector (P-39.1): https://www.legisquebec.gouv.qc.ca/fr/document/lc/P-39.1
  • LégisQuébec – Civil Code of Québec (divided co-ownership): https://www.legisquebec.gouv.qc.ca/fr/document/cs/CCQ-1991
  • RBQ – Contractors and compliance of work: https://www.rbq.gouv.qc.ca/
  • RGCQ – Condominium resources and best practices: https://rgcq.org/

FAQ – Amazon Key, co-ownership and Bill 25

Q: Can the board decide on its own to implement Amazon Key?

A: The board may manage the security of the common portions, but a change to the rules governing their use (e.g., delivery areas and access procedures) may require an update to the building regulations and a co-owner vote at the AGM, depending on your DCV and the Civil Code of Québec. Have the decision recorded in the minutes and clearly communicate the changes.

Q: Do we need to obtain the consent of every co-owner?

A: Bill 25 permits the processing of personal information when the purpose is serious and legitimate and the collection is proportionate. In an access-security context, transparency, minimization and proper signage are essential. Provide feedback mechanisms and strictly limit retention.

Q: Where is the data stored and for how long?

A: Confirm the hosting location with the provider. If the data leaves Quebec, conduct the required assessment and govern the communication contractually. Adopt a short and justifiable period (e.g., 30 to 90 days), then securely destroy the data unless an incident is being handled.

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

Do you manage a condominium in Quebec? Discover our packages 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}