Cookies, analytics and advertising
This site is built to run five measurement tools: Google Analytics 4, the Google Tag Manager container that carries it, the Meta pixel alongside Meta’s Conversions API — which reports the same enquiry a second time from our own server — Microsoft Clarity and Yandex Metrica. Clarity and Metrica are session recorders: with your consent they record a video of your visit — the pages you open, where your pointer moves, what you click, how far you scroll — and play it back to us. Metrica’s recorder also captures the keys you press in a form, the enquiry form included. Each tool is switched on by configuration, and a deployment with none of them configured loads no analytics or advertising script of any kind. Microsoft and Yandex handle those recordings outside Canada, and information that crosses a border can be reached by the courts and authorities of the country it sits in.
The tools come in two groups. Google Analytics 4 and the Meta pixel measure visits and tell us which pages and adverts lead to an enquiry; they start with the page while a notice says so, and one click on “Only necessary” turns them off for good. Google Tag Manager and the two recorders, Microsoft Clarity and Yandex Metrica, load only after you press “Accept all”. On a French page, or in a browser set to Canadian French, nothing from either group loads until you press Accept, which is how Quebec law asks for it. Your answer is kept in your own browser under the key oh:consent:v1 and mirrored into a first-party cookie named oh_consent, which is how our server knows whether an enquiry you send may be reported onward.
Those tools set their own cookies on this domain — _ga, _ga_* and _fbp, _fbc from the measurement group, and _clck, _clsk, _ym_uid, _ym_d, _ym_isad, _ym_visorc and mdd from the recorders after you accept — which count visits, tie a recording to your session and show us which pages and adverts lead to an enquiry. While measurement is on, a submitted enquiry is also reported to Meta from our server: the event, the page, and a one-way-hashed form of your name, email address and phone number. The hashing happens here, before anything is sent, so Meta can match the event against an account it already holds without receiving those details in readable form.
Change your mind whenever you like through the “Cookie settings” link in the footer, which reopens the banner. Refusing, or withdrawing after accepting, takes effect in the visit you are in: the recorders are switched off where they stand, the cookies above are cleared from this domain, and the browser tags and the server-side report both go quiet. Cookies those companies keep on their own domains sit outside this site’s reach, and your browser’s settings are where they are cleared. The attribution entry in section 03 behaves the same either way: it stays in your browser’s session storage, it travels only with an enquiry you send us yourself, and closing the tab clears it.