TRUCOVER INSURANCE & INVESTMENTS INC.
5B Conestoga Dr., Brampton, Ontario L6Z 4N5
Privacy Officer contact: admin@trucover.ca
| Detail | Information |
|---|---|
| Version | 1.0 – consolidated and enhanced |
| Prepared | October 11, 2026 |
| Effective / approved date | ________________________ |
| Approved by | ________________________ |
| Designated Privacy Officer | ________________________ |
| Next review | At least annually or sooner after material change |
| Classification | Internal & confidential |
Adoption note: Management must designate the Privacy Officer, approve this policy, assign responsibility for each control, and confirm the procedures match TruCover’s actual systems and contractual obligations. This document does not certify legal or regulatory compliance.
TruCover Insurance & Investments Inc. (“TruCover”) is committed to respecting privacy, safeguarding personal information and promptly identifying, managing, documenting and, where required, reporting privacy incidents. We handle sensitive insurance, investment and financial-service information only for legitimate, identified purposes with appropriate consent or another lawful basis. Every director, employee, advisor and service provider acting for TruCover must protect information entrusted to the company.
This policy applies to all personal information in TruCover’s custody or control, whether held in paper, electronic, audio, cloud-based or other form, and to information handled on TruCover’s behalf. It binds directors, officers, employees, licensed insurance and investment representatives, temporary staff, contractors, and vendors with authorized access. Advisors must also comply with applicable insurer, managing general agency (MGA), dealer and product-provider rules.
TruCover will assess applicability of the Personal Information Protection and Electronic Documents Act (PIPEDA), relevant provincial requirements, Ontario insurance-sector rules, contractual obligations, and other laws that apply to specific products or activities. Anti-spam obligations, where applicable, are separately assessed under Canada’s Anti-Spam Legislation (CASL). If a legal or contractual requirement imposes a higher standard, that requirement prevails.
| Term | Meaning |
|---|---|
| Personal information | Information about an identifiable individual, including combinations of otherwise non-sensitive data. |
| Sensitive information | Examples: medical history, SIN, identity documents, banking information, financial position and insurance underwriting details. |
| Privacy incident | Actual or suspected loss, unauthorized access, collection, use, disclosure or disposal of personal information. |
| Breach of security safeguards | Loss of, unauthorized access to, or unauthorized disclosure of personal information resulting from breach of safeguards or failure to establish safeguards, as defined under applicable law. |
| RROSH | Real risk of significant harm, the PIPEDA threshold for certain breach reporting and notifications. |
Depending on services requested, TruCover may need contact and identity data; date of birth; family and beneficiary data; occupation; income, assets and liabilities; tax and SIN information where legally required or justified; investment objectives and risk tolerance; banking/payment details; medical and lifestyle data for underwriting; claims and policy details; travel or driving information; and relevant communications and advice records. Do not request medical or SIN information merely because it may be convenient.
Use the minimum necessary information and restrict disclosure to an authorized recipient with a business need, a valid consent or other legal authority. Verify the recipient’s identity, destination and permissions before sending sensitive records. Maintain accuracy through client confirmations, review of critical underwriting facts and documented corrections. Do not modify records to misrepresent client instructions or historical disclosures.
Explain the risks of unencrypted email or other channels when material, and offer appropriate secure alternatives. Authenticate clients before sharing sensitive details by phone or electronically. Marketing text/email communications must comply with CASL where applicable, including consent, sender identification and unsubscribe requirements.
Before enabling a service provider to process personal information, assess access requirements, security posture, subcontracting, breach cooperation, data location, lawful transfers, retention and deletion obligations. Use contracts appropriate to risk that address permitted purposes, confidentiality, safeguards, incident reporting, audit/cooperation and return/destruction. TruCover remains accountable for information under its control even where processed by others.
Where information is processed or accessible outside Canada, evaluate jurisdictional risks and provide meaningful transparency consistent with applicable law. Do not promise that all information stays in Canada unless verified. Website forms, analytics, tracking technologies and marketing lists require separate assessment and an accurate public-facing website notice that describes actual practices.
Direct requests to admin@trucover.ca or the office address. Authenticate the requestor appropriately and log the receipt date, requested records, deadline, decision and response. Where PIPEDA applies, respond within the statutory 30-day period subject to lawful extensions; communicate any extension and reasons as required. Provide access and correction except where law permits or requires refusal, and explain available recourse. Record disagreements about disputed data when warranted.
Withdrawal of consent is subject to legal and contractual restrictions and reasonable notice. Confirm which future uses can cease and which information must remain for legitimate regulatory, legal or dispute-management purposes. Process marketing opt-outs according to applicable requirements.
Acknowledge complaints promptly, investigate impartially, document findings and corrections, and provide a reasoned response with details of applicable external complaint channels, including the Office of the Privacy Commissioner of Canada when relevant. Escalate insurer/MGA-related matters to the responsible organization through approved channels.
All suspected or confirmed incidents must be reported immediately to the Privacy Officer or management. Staff should preserve the original message/file and incident details, take safe steps to limit exposure, and follow containment directions. Reporting must not await proof of harm or a completed incident form.
For a breach of security safeguards involving personal information under TruCover’s control, assess whether it is reasonable in the circumstances to believe the breach creates a real risk of significant harm to an individual. Relevant factors include sensitivity of the information and probability of actual or future misuse. Potential harms include identity theft, financial loss, humiliation, reputation or relationship damage, negative credit impacts, employment/business impacts and threats to safety.
If PIPEDA reporting requirements apply and RROSH exists, report to the Office of the Privacy Commissioner of Canada and notify affected individuals as soon as feasible after determining the breach occurred, in the required form and with required content. Consider notifying other organizations or government institutions capable of reducing or mitigating harm when legally required or permitted. Examine any separate provincial, sectoral or contractual reporting requirements rather than assuming PIPEDA is exhaustive.
Individual notifications should explain, as required by law, the circumstances and timing, the types of personal information affected, measures taken, steps recipients can take to reduce harm, the organization’s contact details and the ability to complain to the appropriate commissioner. The Privacy Officer approves notices and keeps a copy, recipient list, dates and delivery records. Law-enforcement coordination does not automatically suspend legal notice obligations.
Maintain records of every breach of security safeguards covered by PIPEDA, including breaches not meeting RROSH, for at least 24 months after the day TruCover determines the breach occurred; preserve longer when another retention requirement, legal hold or contractual obligation applies. Records must permit an assessment of whether reporting and notification decisions were reasonable.
Retain records only as long as reasonably required for identified purposes and applicable insurance, investment, tax, anti-money-laundering, contractual and litigation obligations. Because requirements vary by record category and product, TruCover will maintain a separate approved retention schedule rather than applying a single arbitrary period to all client files. Suspend disposal when litigation, regulatory inquiry, complaint or investigation creates a legal hold. At expiry, securely delete, anonymize or destroy the information and document material destruction.
Before system access, personnel must acknowledge this policy and complete orientation. Refresher training will occur at least annually and after major incidents or procedural changes, with attendance and topic records retained. Management will review technology and privacy risks at least annually, including access, third parties, incidents, data handling and website practices. Violations may result in access restrictions, remedial training, discipline, termination of engagement and external reporting where appropriate.
Management approval and effective date are required before this manual is considered adopted. This manual should be reviewed by qualified Canadian privacy/compliance counsel and aligned with applicable insurer/MGA and dealer requirements before reliance in an audit.
| Field | Entry |
|---|---|
| Incident ID / status | |
| Reporter / role / contact | |
| Discovery date & time / occurrence date | |
| Affected system / office / vendor | |
| Description of event / probable cause | |
| Data categories / sensitivity / approximate individuals | |
| Actual or potential recipients / evidence preserved | |
| Containment actions / assigned lead / time | |
| RROSH analysis and rationale | |
| OPC / individual notification required? Why? | |
| Insurer / MGA / vendor / police notices (dates) | |
| Remediation / deadlines / verification | |
| Privacy Officer approval / closure date |
| Assessment question | Finding / evidence |
|---|---|
| Types of data and sensitivity | |
| Recipient identity and exposure duration | |
| Encryption / security / recovery facts | |
| Likelihood of access or misuse | |
| Potential harm and affected persons | |
| Real risk of significant harm? Yes / No / Pending | |
| Reasoning and supporting evidence | |
| Reporting/notice timing and owner | |
| Review / sign-off / date |
| Date | Advisor / employee | Topic / delivery | Acknowledged / verifier |
|---|---|---|---|
| Case ID | Date received | Type / identity checked | Deadline / outcome / closed |
|---|---|---|---|
Reviewer: ___________________ Review date: ______________ Follow-up due: ______________
| Version / date | Change summary | Reviewed by | Approved by |
|---|---|---|---|
| 1.0 / Oct 11, 2026 | Combined duplicate source manuals; enhanced operational controls, incident workflow and registers |