Privacy, cybersecurity, clarity and bilingual service

1. Complete French, accessible English

The public site is offered in both French and English. The French version must remain complete and self-sufficient for the Quebec market, while the English version must serve anglophone clients with clear, consistent and useful information.

2. Limited collection

Information requested online or during intake must stay tied to the real needs of the file: identity, contact details, technical context, urgency and details needed to assess the case.

3. Accurate online information

Published services, certifications, timelines, contact details and commitments must be accurate, current and understandable. Pricing, payment terms and intervention conditions must be stated clearly at the proper stage. Unverified claims and vague promises do not belong on the site.

4. Reasonable security measures

Personal information and case-related information must be protected by administrative, technical and organizational measures suited to their sensitivity, use and retention context.

5. Secure intake of devices and information

Intake of a device, file or sensitive matter should follow a coordinated, traceable and limited process. Transmission channels, access and initial handling should reduce unnecessary exposure.

6. Incident handling

Any privacy or security incident affecting personal information must be handled quickly, documented and assessed according to applicable obligations, including notice to affected people or authorities when required.

7. Rights and requests

Individuals must be able to request access to or correction of their information and know where to direct a privacy-related request.

8. Ongoing updates

The site must evolve with actual operating practices. Information, privacy, procedure and commitment pages should be reviewed whenever services, tools or obligations change.

9. Clear framework after acceptance

Once a quote or mandate is accepted, the intervention framework must be stated clearly: service scope, known limits, urgency level, planned steps, fees, deposit if any, payment terms, confidentiality and data return.

10. What the site should not do

• Present certifications, guarantees or capabilities that cannot be demonstrated.
• Hide the existence of intermediaries, subcontracting or off-site shipping if that applies.
• Publish inaccurate contact details, timelines or payment terms.
• Use compliance as decoration without real operating practice behind it.