Kestryl · Cockpit for Canada
Kestryl Cockpit for Canada brings federal, provincial and territorial privacy work into one operating view. Locate personal information across systems in scope, follow requests and recorded consent decisions into known copies, apply the jurisdiction and statute-family settings approved for the deployment, and assemble evidence your legal and leadership teams can review.
FOURTEEN-JURISDICTION VIEW · TEN PRIVACY-CONTROL OUTCOMES · ENGLISH EDITION
The business problem
A customer record can sit in a CRM, a warehouse, a marketing platform, and a shared document. Changing it in one place does not establish what happened in the others. The leadership question is not simply whether a request was closed, but whether the organization can explain the scope of its answer and the evidence still missing.
Kestryl Cockpit for Canada puts that follow-through in one place: the jurisdiction and statute family associated with a record, the requirement approved for the deployment, the person responsible, the action taken, and the evidence available for review.
What you get
Bring records, sensitive categories, open requests, incidents, and unresolved assignments into one view across the jurisdictions in scope. The basis for each association stays visible; uncertainty is not presented as certainty.
Trace requests and recorded consent decisions across downstream relationships your team declared or imported from an available catalog. Show where follow-through is evidenced and where a copy still needs attention.
Bring decisions, approvals, actions, incidents, and open issues together by run, request, jurisdiction, or matter. Give counsel a record to assess rather than a status colour to interpret.
The operating journey
Coverage
Bring Salesforce and nine other enterprise systems into the agreed operating scope through Informatica IDMC, with attachment relationships declared alongside the records that reference them.
Coverage depends on connector availability, permissions, extraction scope, attachment relationships and the engagement configuration. Connection capability is not automatic access to every field or attachment.
For the broader service and control framework, Explore Privacy Control Outcomes — Canada.
The operating brief
The cockpit connects privacy work that would otherwise be spread across teams. Each outcome has a defined scope and a visible boundary, so leadership can distinguish completed work from a decision still required.
| No. | Business outcome | What the cockpit brings together |
|---|---|---|
| 01 | Know what you hold | Inventory personal information in the connected systems and documents within scope. |
| 02 | Find sensitive data | Bring candidate sensitive categories and potential age-related records into human review. |
| 03 | Track known copies | Follow the downstream relationships your team supplies or imports from an available data catalog. |
| 04 | Scope a rights request | Locate records and linked documents using the identifiers provided for the individual. |
| 05 | Check deletion follow-through | Compare source-system confirmations with follow-up findings across known copies. |
| 06 | Check consent follow-through | Compare recorded withdrawals or limitations with permissions still present in downstream data. |
| 07 | Understand provenance | Record processors, service providers, and declared countries where known copies are held. |
| 08 | Scope an incident | Organize affected records by jurisdiction and category to support the response team. |
| 09 | Make retention accountable | Associate retention decisions with a purpose, an owner, a review date, and exceptions. |
| 10 | Assemble reviewable evidence | Bring findings, decisions, actions, and outstanding issues together by run, request, jurisdiction, or matter. |
These are product outcomes, not ten legal certifications. Customer counsel determines applicability, required response periods, exceptions, and whether the evidence is sufficient.
Approved action
Discovery is the starting point. Action follows review, a recorded approval, and the applicable hold checks. Mask, Vault, and Strip apply only to approved supported structured working data.
Replace an approved value with a protected representation in supported structured working data.
Replace the approved value while retaining an encrypted original for authorized restoration, subject to the retained key and vault record.
Remove the approved value from the supported working output without a vault-based recovery path. This is not erasure from every source or backup.
Documents and attachments can be discovered and evidenced within the agreed scope. Source-document remediation is not represented as automatic unless separately validated for the supported format and deployment.
What changes, and where
Actions in source business systems are executed separately and verified through the operating workflow. The Overview does not represent direct automated changes to source records, automatic attachment replacement, or automatic modification of originals.
Control
Deploy with purpose
Choose the sources, the requests or obligations you need to manage, and the evidence your reviewers expect to receive. Establish that scope with your privacy, security, and data leaders, then expand the operating model as additional systems and jurisdictions are brought under control.
Why Pacific Data Integrators
Kestryl Cockpit for Canada combines Informatica-based data integration with Kestryl discovery, approved action, and evidence workflows. Where a source system is in scope, its confirmations remain part of the source-system process; the cockpit brings available evidence into the wider review.
PDI White Glove supports installation, configuration and scheduled Kestryl operations, with scope, cadence and systems defined in the applicable order form.
Explore the broader Kestryl product and the Canada service framework through the link above.
FAQ
It is an operating view of the federal, provincial and territorial privacy work in scope. It does not mean that every law applies to every record or organization. The cockpit records the approved jurisdiction and statute-family settings, the basis used, and unresolved cases for review.
No. The cockpit applies the jurisdiction and statute-family settings approved for the deployment, records the basis used, and surfaces unresolved cases. Legal applicability, statutory interpretation, exceptions, holds, and required deadlines remain with the customer and counsel.
The shared Kestryl system list includes Salesforce, SAP S/4HANA and ECC, SAP SuccessFactors, SAP Ariba, Oracle E-Business Suite, Oracle NetSuite, Microsoft Dynamics 365, ServiceNow, Workday, and SharePoint Online. Coverage depends on connector availability, permissions, extraction scope, attachment relationships, and the engagement configuration.
No. Downstream copies are declared by the customer or imported from an available catalog. The scanner does not independently discover every downstream copy, so an undeclared copy remains outside the transfer register.
No. Kestryl organizes findings, approved settings, decisions, actions, and evidence for review. The customer and counsel retain legal applicability, statutory interpretation, holds, exceptions, remediation approval, reportability, and acceptance of the evidence.
Actions in source business systems are executed separately and verified through the operating workflow. The Canada Overview does not represent direct automated changes to source records, automatic attachment replacement, or automatic modification of originals.
The Canada edition is currently represented as an English edition. French-language product screens and documentation are not represented as currently delivered. Customers remain responsible for notices and communications through their own channels where required.
Next step
Bring one priority privacy workflow and its source systems to a briefing. Define the required evidence, the decisions that remain with your team, and the exceptions that must stay visible before expanding the deployment.