Legal and Policy Center

These Security Command Integration Terms (the "Integration Terms") are Supplemental Terms under the CondoHQ Terms of Service (the "Terms"), which Security Command already requires Customer to accept before using Command.

They apply only to connecting a third-party system to Security Command, including monday.com, and any later Security Command integration that uses connect, map, token, webhook, or sync (each a "Command Integration"). The connected system is a "Vendor" and is a Third-Party Service under the Terms.

Capitalized terms not defined here have the meaning in the Terms, including Customer, Customer Data, Protected Parties, Services, Supplemental Terms, User, Authorized Representative, and Third-Party Services. "Including" means "including without limitation." Headings do not affect interpretation. These Integration Terms were drafted for commercial use by a business Customer. Customer waives any rule that ambiguous language is construed against the drafter.

These Integration Terms do not replace the Terms, Privacy Policy, Cookie Policy, Acceptable Use Policy, or any applicable DPA. They do not govern property-scoped partner integrations under the Partner API Agreement. Those remain a separate product, accepted per property under Terms Section 17.

If there is a conflict about Command Integrations, these Integration Terms control under Terms Section 36(c). In all other respects the Terms control, including fees, term, suspension, Protected Parties, warranty disclaimer, limitation of liability, indemnification generally, dispute resolution, records and evidence, changes, assignment, waiver, and entire agreement.

Nothing in these Integration Terms expands CondoHQ's liability under the Terms. If a claim is excluded, released, or disclaimed under the Terms or these Integration Terms, no cap, remedy, or other clause creates that liability.

Connecting, mapping, or activating a Command Integration is optional. Customer may use Security Command without connecting monday.com or any other Command Integration. Customer's sole and exclusive remedy for dissatisfaction with a Command Integration is to disconnect.

Customer may not start an OAuth connection, save a mapping, or activate a release until an owner or admin of the company has accepted the then-current Integration Terms. Acceptance is recorded against the company. A new acceptance is required when the document hash changes, on a material update under Terms Section 35, and before each new Vendor connection if CondoHQ so requires in product. Continued connect, map, or sync after CondoHQ requires re-acceptance is not permitted until that acceptance is recorded.

Customer acknowledges that it is a business or organizational Customer, not an individual consumer in respect of these Integration Terms, that it had a reasonable opportunity to read these Integration Terms in full, to scroll to the end, to print or save a copy, and to obtain independent legal advice before accepting, and that it either obtained that advice or chose to proceed without it.

By clicking accept, checking the recorded boxes, providing name, title, email, signature, and password confirmation, authorizing OAuth, saving a mapping, or activating a release, Customer agrees to these Integration Terms. Signature and password confirmation are required.

Electronic acceptance, including the recorded checkboxes, signer name, title, email, signature, password confirmation, timestamp, Integration Terms version and SHA-256, then-current Terms SHA-256, IP address, user agent, accept-language, and client audit envelope, is conclusive evidence of agreement and of authority to bind the corporation, to the maximum extent permitted by applicable law, including the Electronic Commerce Act, 2000 (Ontario) and equivalent electronic-documents legislation.

The individual who accepts, and any User or Authorized Representative who later connects, maps, or activates, represents, warrants, and covenants on a continuing basis that they are duly authorized to bind the corporation, that the corporation is the controller of the Vendor account being connected, and that Customer has all notices, consents, collective-agreement rights, employment-law rights, and legal bases required to instruct CondoHQ to process the connected data. A User or Authorized Representative who uses a Command Integration binds Customer to that representation. CondoHQ may rely on that representation, on Customer's instructions, and on mapping and configuration in the Services, and has no obligation to draft, provide, deliver, or verify any notice, consent, policy, or legal basis. In-product text, samples, templates, and Mapping Studio copy are conveniences only. They are not notice by CondoHQ, are not legal advice, and do not make CondoHQ responsible for notice or consent.

Each acceptance is stored as a durable legal record and is written to the company's Security Command audit log, including signer legal name and title, account email, signature, the exact checkbox statements, Integration Terms version and SHA-256, the then-current Terms SHA-256, the Vendor and company, timestamp, IP address, user agent, accept-language, and client audit. Prior live acceptances of a superseded version are marked superseded and are not deleted. CondoHQ may retain these records, together with mapping releases, board classifications, column titles and types, site confirmations, and schema snapshots, for seven (7) years or longer if required by law, dispute, or investigation. Customer agrees they are business records under Terms Section 33 and admissible to prove acceptance, authority, instructions, and what was mapped. To the maximum extent permitted by applicable law, such records shall be deemed accurate and authoritative absent manifest error.

The Command company Terms of Service acceptance, including the live authority statement "I am duly authorized to bind the corporation to the Terms of Service," remains in force. These Integration Terms add a second recorded acceptance. They do not amend that Command checkbox.

All data CondoHQ receives from a Vendor in connection with a Command Integration is Customer Data under the Terms. Customer, not CondoHQ, determines which Vendor account, workspace, boards, columns, item names, updates, and site values to connect, and how to classify each board. CondoHQ processes only the fields Customer maps, on Customer's instructions as expressed in the activated mapping release. Customer instructs and authorizes any transmission of mapped data between the Vendor and CondoHQ, including transfers outside Canada if the Vendor or its infrastructure is outside Canada. Customer is solely responsible for that instruction.

Customer is the controller of data in the Vendor account. CondoHQ acts as processor, service provider, or equivalent with respect to that Customer Data as described in the Privacy Policy and any applicable DPA. If an applicable DPA exists, it controls solely for matters it expressly addresses, under Terms Section 32.

Customer shall not attempt to send Prohibited Data through a text column, item name, update, file, document, comment, or any other path. Technical blocks in Command do not reduce that duty and are not a warranty that Prohibited Data was kept out.

Customer is responsible for the Vendor account, including who can authorize the connection, which boards exist, renamed columns, Vendor credentials, and the Vendor's own terms. CondoHQ does not receive or store Vendor passwords. Unauthorized Vendor activity caused by Customer's failure to safeguard the Vendor account or credentials is Customer's responsibility. Connecting monday.com also binds Customer to monday.com's terms with Monday.com Ltd. CondoHQ is not a party to that relationship and is not responsible for the availability, performance, security, outputs, actions, omissions, or practices of Third-Party Services, as already stated in the Terms.

A dispute between Customer and a Vendor, including under the Vendor's terms, is solely between Customer and that Vendor.

Customer shall not represent to workers, contractors, applicants, customers, or any other person that CondoHQ is an employer, joint employer, HRIS, payroll provider, staffing agency, or health-record holder. Nothing in a Command Integration creates an employment, joint-employment, fiduciary, or special relationship among CondoHQ, Customer, and any worker or other person.

A Command Integration may sync only operational roster and live coverage data that Security Command already stores when Customer enters it in this app. Nothing in a Command Integration expands what Command is allowed to store.

Allowed roster fields, if Customer maps them: work email, first name, last name, work phone, site (and optional building), operational active or inactive status, and bill-out rate per hour before tax.

Allowed coverage fields, if Customer maps them: person (link to a roster item or Vendor user), site, building, post, shift window or start and end, officers required, and active or inactive status for that shift.

Monday writes, if Customer enables them, go through the same Command rules as this app.

Misclassifying a board as Roster or Coverage, mapping the wrong column, confirming the wrong site value, or connecting the wrong Vendor workspace is Customer's instruction. CondoHQ may rely on it without independent verification.

Bill-out rate is an operational charge-out figure only. Customer represents that it is not a wage, salary, payroll, or statutory-deduction field, and is not Prohibited Data.

A Command Integration must not be used as an HRIS, payroll system, hiring system, identity vault, or health record.

The following must not be connected, mapped, transmitted, stored, or logged through a Command Integration, including as a renamed column, file, document, or free-text dump (collectively, "Prohibited Data"):

• Social Insurance Number, Social Security Number, ITIN, National Insurance number, national ID, or any similar government identifier
• Health card, medical, disability, vaccination, or other health information
• Gender, sex, date of birth, or age
• Passport, driver's licence, or other identity document
• Credit score, credit check, or similar
• Wage, salary, payroll, GST, or HST (except the optional operational bill-out rate in section 4)
• Home or residential address
• Emergency contact or emergency phone
• Resume, CV, or application materials
• Files and documents
• Incidents, dispatch, Duty, roles, and other Command operational records that are not roster or coverage

Hiring, recruiting, onboarding, applicant, and payroll boards must stay excluded.

CondoHQ is not an HRIS. Mapping Studio may lock columns whose titles or types match this list. There is no admin override. If a mapped column is later renamed into a prohibited title, Command may pause sync. Customer must fix the mapping and activate a new release.

If Customer knows or suspects that Prohibited Data entered Command, Customer shall notify CondoHQ promptly, stop the flow, and instruct deletion. CondoHQ may delete or isolate suspected Prohibited Data without liability to Customer or any other person.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, CONDOHQ HAS NO OBLIGATION TO MONITOR, INSPECT, CLASSIFY, SAMPLE, OR VERIFY ANY VENDOR ACCOUNT, BOARD, COLUMN, ITEM, FILE, OR PAYLOAD, INCLUDING FOR PROHIBITED DATA, AND INCLUDING WHERE CONDOHQ OR THE SERVICES HAVE RECEIVED, DISPLAYED, STORED, FILTERED, LOCKED, PAUSED, DELETED, OR BEEN NOTIFIED OF DATA OR A RISK, AND INCLUDING IF CONDOHQ HAS ACTUAL OR CONSTRUCTIVE KNOWLEDGE OF PROHIBITED DATA OR A MISMAPPING.

Filters, locked columns, denied titles, paused sync, schema checks, Mapping Studio copy, in-product warnings, and similar controls are conveniences only. They are not a warranty, representation, covenant, or assumption of duty that Prohibited Data was identified, blocked, or kept out of Command. They do not constitute legal advice. Customer shall not rely on them as a substitute for Customer's own review of the Vendor workspace.

This is true even if CondoHQ designed, offered, updated, failed to offer, or failed to apply a filter, and even if a renamed, coded, concatenated, or free-text field evaded a title or type check.

This allocation of risk is a material part of the bargain. Fees for Security Command do not include HRIS screening, employment-law compliance, privacy-law compliance, or Vendor data hygiene.

Customer and Users expressly assume all risk arising from Command Integrations, including the Vendor workspace, board classification, column titles and types, site confirmation, data that did or did not flow, Prohibited Data, delay, inaccuracy, incompleteness, unavailability, reliance, and Third-Party Services.

Disconnect, pause, deletion, or revocation does not, except where CondoHQ deletes suspected Prohibited Data, remove persons, posts, deployments, or other Customer Data already stored in Command. That data remains Customer Data. Customer remains solely responsible for it.

One monday.com account may be connected per security company unless CondoHQ permits otherwise in product.

CondoHQ stores OAuth tokens only to operate the mapping Customer activated. Webhooks subscribe only to mapped boards. Pause keeps Vendor events stored but not applied. Disconnect revokes the Vendor token, removes webhooks, and keeps every person, post, and deployment already in Command, except suspected Prohibited Data CondoHQ deletes.

A Command Integration does not grant the Vendor access to incidents, dispatch, Duty, roles, or other Command records that are out of scope.

Without limiting Terms rights of suspension, CondoHQ may immediately suspend, pause, restrict, disconnect, or delete from a Command Integration, without prior notice, if it suspects Prohibited Data, a mapping or instruction that would expand Command beyond section 4, a security risk, a legal demand, or a breach of these Integration Terms. CondoHQ shall have no liability for that suspension, pause, restriction, disconnect, or deletion.

Customer shall cooperate promptly with any investigation, including identifying the Vendor account, boards, and columns involved.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, CUSTOMER AND USERS RELEASE AND WAIVE ALL CLAIMS AGAINST CONDOHQ AND THE PROTECTED PARTIES ARISING OUT OF OR RELATING TO A COMMAND INTEGRATION, A VENDOR, CUSTOMER'S MAPPING OR INSTRUCTIONS, FILTERS, LOCKED COLUMNS, PAUSED SYNC, SUSPENSION, DISCONNECT, DELETION, OR DATA THAT DID OR DID NOT FLOW THROUGH A COMMAND INTEGRATION, INCLUDING PROHIBITED DATA AND INCLUDING CLAIMS BASED ON NEGLIGENCE, GROSS NEGLIGENCE TO THE EXTENT WAIVABLE, FAILURE TO WARN, FAILURE TO MONITOR, FAILURE TO DETECT, FAILURE TO BLOCK, FAILURE TO DELETE, OR ALLEGED ASSUMPTION OF DUTY.

NOTHING IN THE SERVICES CREATES A DUTY OF CARE OWED BY CONDOHQ TO CUSTOMER, USERS, WORKERS, CONTRACTORS, APPLICANTS, RESIDENTS, OCCUPANTS, VISITORS, OR ANY OTHER PERSON IN CONNECTION WITH A COMMAND INTEGRATION, A VENDOR, OR PROHIBITED DATA.

Customer waives any right to seek contribution, indemnity, impleader, or allocation from a Protected Party in respect of a Command Integration, except for that party's willful misconduct or fraud.

These terms apply to the maximum extent permitted by applicable law and are in addition to the disclaimers, indemnity, and limitation of liability in the Terms. If a court refuses to enforce any part of this Section against a particular person or claim, the rest of this Section still applies.

In addition to, and without limiting, Terms Section 27, Customer shall defend, indemnify, and hold harmless the Protected Parties from and against any claim, demand, action, investigation, proceeding, or regulatory matter, including any third-party claim and any claim by a User, worker, contractor, employee, applicant, union, resident, occupant, visitor, director, officer, property manager, Vendor, or other person, and including class, collective, or representative claims, and including all resulting liabilities, damages, losses, judgments, settlements, penalties, fines, costs, and expenses (including reasonable legal fees, the costs of enforcing this indemnity, and forensic, notification, credit-monitoring, regulatory, and public-relations costs), arising out of or relating to, without limitation:

• a Command Integration or Vendor account Customer connects, including the Vendor's acts, omissions, security practices, or data handling
• data Customer maps, classifies, confirms, or allows to flow, including misclassification of a board and mapping of the wrong column or workspace
• Prohibited Data, including SIN, SSN, health, payroll, identity documents, and other HRIS fields, including where a filter did not catch them
• employment, labour, human rights, occupational health and safety, workers' compensation, employment-standards, privacy, PIPEDA, substantially similar provincial privacy legislation, Quebec Law 25, PHIPA, or similar claims, in any jurisdiction
• missing notices, consents, collective-agreement rights, or legal bases
• a dispute between Customer and a Vendor
• breach of these Integration Terms, including any misrepresentation of authority at acceptance

This indemnity includes allegations of missing authority, permission, consent, or legal basis, inaccurate, delayed, incomplete, or unavailable information, reliance, and Third-Party Services, regardless of the legal theory, including contract, tort, negligence, gross negligence to the extent waivable, strict liability, statute, regulation, or equity.

To the maximum extent permitted by applicable law, this indemnity applies even if a claim is caused in whole or in part by the negligence of a Protected Party, including gross negligence to the extent waivable, and even if CondoHQ designed, offered, updated, failed to offer, or failed to apply a filter. It does not require Customer to indemnify a Protected Party for that party's willful misconduct or fraud.

Customer's obligations under this Section are not subject to Terms Section 29, section 11 of these Integration Terms, or any other limitation of liability, and are not limited to fees paid. They are continuing and unlimited to the maximum extent permitted by applicable law. CondoHQ may set off amounts owing under this Section against any amounts CondoHQ owes Customer.

Customer shall maintain insurance reasonably adequate to support these indemnity obligations. CondoHQ has no duty to verify that insurance.

CondoHQ will notify Customer of a claim subject to indemnification. Any failure or delay in notification relieves Customer of its obligations only to the extent Customer is materially prejudiced by it. Customer shall assume the defence promptly upon written request. CondoHQ may participate in or assume control of the defence, using counsel of its choosing, where reasonably necessary to protect the interests of a Protected Party. If CondoHQ assumes control, Customer remains responsible for all resulting liabilities and for reasonable legal fees of counsel CondoHQ retains for that matter. Customer shall not settle in a manner that admits fault or liability of a Protected Party, imposes an obligation or payment on a Protected Party, restricts a Protected Party's operations, or otherwise adversely affects a Protected Party, without CondoHQ's prior written consent.

Filters, locked columns, Mapping Studio copy, suspension, disconnect, and deletion do not reduce this indemnity.

Without limiting Terms Sections 28 and 29, Command Integrations are provided "as is" and "as available."

WITHOUT LIMITING ANY OTHER DISCLAIMER, RELEASE, INDEMNITY, OR LIMITATION OF LIABILITY, AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, CONDOHQ AND THE PROTECTED PARTIES SHALL NOT BE LIABLE TO CUSTOMER, USERS, OR ANY OTHER PERSON FOR ANY CLAIM ARISING OUT OF OR RELATING TO A COMMAND INTEGRATION, A VENDOR, CUSTOMER'S MAPPING OR INSTRUCTIONS, FILTERS, LOCKED COLUMNS, PAUSED SYNC, SUSPENSION, DISCONNECT, DELETION, OR DATA THAT DID OR DID NOT FLOW THROUGH A COMMAND INTEGRATION, INCLUDING WITHOUT LIMITATION DELAY, INACCURACY, INCOMPLETENESS, UNAVAILABILITY, RELIANCE, PROHIBITED DATA, AND THIRD-PARTY SERVICES, REGARDLESS OF THE LEGAL THEORY, INCLUDING CONTRACT, TORT, NEGLIGENCE, GROSS NEGLIGENCE TO THE EXTENT WAIVABLE, STRICT LIABILITY, STATUTE, OR EQUITY, AND EVEN IF CONDOHQ HAS BEEN ADVISED OF THE POSSIBILITY OF THE CLAIM OR DAMAGES. THIS LIMITATION APPLIES EVEN IF A REMEDY FAILS OF ITS ESSENTIAL PURPOSE. THIS LIMITATION DOES NOT APPLY TO A PROTECTED PARTY'S WILLFUL MISCONDUCT OR FRAUD TO THE EXTENT THAT EXCLUSION IS REQUIRED BY APPLICABLE LAW.

TO THE MAXIMUM EXTENT PERMITTED BY LAW, CONDOHQ SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, PUNITIVE, OR ENHANCED DAMAGES OR FOR ANY LOSS OF PROFITS, REVENUE, BUSINESS, OPPORTUNITY, GOODWILL, DATA, SAVINGS, ANTICIPATED BENEFITS, OR EXPECTED OUTCOMES, ARISING OUT OF OR RELATING TO A COMMAND INTEGRATION.

Without limiting the foregoing, and without increasing any liability otherwise excluded, disclaimed, or limited, CondoHQ's aggregate liability arising specifically out of or relating to Command Integrations shall not exceed CAD $500. Multiple claims do not enlarge that amount. This Section does not increase any liability otherwise excluded, disclaimed, or limited under the Terms or these Integration Terms.

Without limiting Terms Section 31, Customer acknowledges that connection of Prohibited Data, expansion of a Command Integration beyond section 4, or refusal to disconnect after notice may cause irreparable harm for which monetary damages alone would be inadequate. CondoHQ may seek injunctive or other equitable relief in any court of competent jurisdiction without first submitting that claim to arbitration, and without being required to prove actual damages or post a bond to the extent a court may waive it.

Customer shall pay CondoHQ's reasonable legal fees and costs of enforcing these Integration Terms against Customer.

Dispute resolution, class-action waiver, jury-trial waiver, governing law of Ontario, and seat of arbitration in Toronto remain as set out in Terms Section 31. Rights under these Integration Terms are cumulative and in addition to rights under the Terms.

Sections 2 through 12 survive disconnect, suspension, revocation, deletion, and termination of the Command Integration, and survive termination or expiration of the Terms to the extent they by their nature should survive.

If any provision or portion of these Integration Terms is determined by a court or tribunal of competent jurisdiction to be invalid, illegal, or unenforceable, that provision or portion will be severed only to the minimum extent necessary, and the remaining provisions will continue in full force and effect. If a court refuses to enforce any part against a particular person or claim, the rest still applies.

A failure or delay by CondoHQ in exercising any right does not constitute a waiver. A waiver is effective only if expressly made in writing by CondoHQ and applies only to the specific circumstance for which it is given.

The Protected Parties are intended third-party beneficiaries of sections 9, 10, and 11. No worker, contractor, applicant, Vendor, resident, or other person is a third-party beneficiary of these Integration Terms or of any filter, warning, or mapping rule.

The English language version controls.