Valdra/Breach & Incidents

Never miss a breach
notification deadline again

PIPEDA requires you to report a breach with a real risk of significant harm to the OPC as soon as feasible after you determine it has occurred. The law sets no fixed number of hours. Our incident log starts your response clock against a recommended 72 hour internal target, which is not a legal deadline, and walks you through every required step.

Built for Canadian businesses
EN + FRBilingual
🍁Hosted in Canada
PIPEDA · Law 25 · CASLBuilt for Canadian law
24 mo

how long PIPEDA requires you to keep a record of every breach — reportable or not

1 PIPEDA Breach of Security Safeguards Regulations

Start Free Assessment
OPC Breach Notification — Draft
47h 23m left
Incident Summary
Unauthorized access to customer database on April 12, 2026. Approximately 1,200 records including names, emails, and account numbers affected.
Records Affected
1,200
Data Types
Name, Email, Account #
Risk Level
Real Risk of Harm
OPC Report
Required

Report as soon as feasible. Start the clock now.

PIPEDA says to report a breach that creates a real risk of significant harm to the OPC as soon as feasible after you determine it has occurred. The law sets no fixed number of hours. Valdra starts your response clock against a recommended 72 hour internal target, which is not a legal deadline, and walks you through every required step.

Request a demo
Affected Party NotificationTemplate · En/Fr

Subject: Important notice about your personal information

Dear [First Name],

We are writing to inform you of a security incident that may have affected your personal information held by [Company].

What happened: On [Date], we discovered that...

Plain language draft · Review before sending
Breach Response Timeline47h 23m to deadline
Breach detected14:02
Contained15:18
RROSH assessed — reportable16:40
OPC notifiedpending
Individuals notifiedpending

Every letter, every document, generated.

OPC notification letters, affected party notifications, and internal incident reports are drafted from your incident data in plain language, ready for your review in minutes, not hours.

Request a demo

Additional features

Request a demo

Auto-Triggered Timer

Your response clock starts the moment an incident is logged, counting toward Valdra's recommended 72 hour internal target. That target is our recommendation, not a legal deadline.

Structured Incident Intake

Guided intake form captures all OPC-required details: nature of breach, personal information affected, number of individuals, risk of harm assessment.

Severity Classification

AI automatically classifies incident severity using OPC's real risk of significant harm (RROSH) criteria to determine notification obligations.

Team Assignment & Escalation

Assign incident investigation tasks to team members with deadline tracking. Auto-escalates to DPO if steps are not completed.

Evidence Preservation

Attach breach evidence, system logs, and investigation notes — all stored with tamper-evident timestamps for regulatory review.

Notification Letter Generation

Auto-generates OPC notification letters and affected individual notices using the incident data already captured in the log.

Frequently asked questions

When do I have to report a privacy breach to the OPC?

Under PIPEDA, you must report a breach to the Office of the Privacy Commissioner of Canada "as soon as feasible" once you determine it poses a real risk of significant harm (RROSH). Valdra starts the clock at intake, runs the RROSH assessment, and generates the OPC report and individual notification letters so you can meet the deadline with evidence.

What is RROSH?

RROSH — the Real Risk of Significant Harm — is the test that determines whether a breach is reportable under PIPEDA. It weighs the sensitivity of the information and the probability of misuse. Valdra walks you through a structured RROSH assessment and records the rationale for your breach file.

Get compliant and build trust

Start free, no credit card.

Start Free — No credit card required

🍁 Canadian data residency · PIPEDA readiness · SOC 2 in progress

Our own compliance

We run our own compliance programme inside Valdra — the product we sell. Our SOC 2, ISO 27001 and ISO 42001 programmes are actively in progress; we do not claim certifications we do not yet hold.

Valdra readiness mark, click to verify
  • PIPEDA
  • Law 25 (Quebec)
  • CASL
  • Data hosted in Canada 🇨🇦
  • AI governance
View our Trust Centre

Measured by Valdra from our own assessments, not audited by a third party. Click the mark to open its verify page and see what it covers.