By · Last updated 2026-06-05

Rudi kwa BlogGDPR & Ufuatiliaji

OPC Kanada: PIPEDA hadi Muswada C-27

OPC ya Kanada inatekeleza PIPEDA wakati Bunge inachakata Sheria ya AI na Data ya Muswada C-27. Kanada inashikilia kutosha kwa GDPR ya EU chini ya mapitio ya 2026.

June 5, 202610 dakika kusoma
Canada OPCPIPEDA Bill C-27SIN detectionCanadian privacy lawEU adequacy

Sheria ya faragha ya Kanada inabadilika. Ofisi ya Kamishna wa Faragha (OPC) inatekeleza PIPEDA leo. Muswada C-27 ungechukua nafasi ya PIPEDA na kanuni kali zaidi. Makubaliano ya uhamishaji wa data ya EU ya Kanada pia yako chini ya mapitio mwaka 2026. Hapa kuna unachohitaji kujua.

Sheria ya Sasa ya Faragha ya Kanada

PIPEDA ni sheria kuu ya faragha ya sekta binafsi ya Kanada. Imekuwa ikitekelezwa tangu 2001. Inashughulikia makampuni katika tasnia zilizodhibitiwa na shirikisho. Pia inatumika katika majimbo yasiyokuwa na sheria zao za faragha.

Majimbo matatu yana sheria zao: Alberta, British Columbia, na Quebec.

Sheria ya 25 ya Quebec ndiyo kali zaidi. Ilianza kutumika kwa awamu mwaka 2022 na 2023. Inahitaji mapitio ya athari za faragha na afisa wa faragha aliyetajwa. Iko karibu zaidi na GDPR ya EU kuliko PIPEDA ya zamani ilivyokuwa.

OPC ilishughulikia malalamiko zaidi ya 400 ya PIPEDA mwaka 2024. Ilitoa amri zinazofunga dhidi ya Tim Hortons kwa kukusanya data ya eneo bila idhini. Waendeshaji kadhaa wa programu za afya pia walipokea amri mwaka huo.

Muswada C-27: Sheria Tatu Mpya

Muswada C-27 unapita Bungeni. Una sehemu tatu.

Sheria ya Kulinda Faragha ya Watumiaji (CPPA) inachukua nafasi ya PIPEDA. Mabadiliko muhimu:

  • Mipaka ya kusudi na kanuni za kupunguza data.
  • Kanuni kali zaidi za idhini.
  • Faini hadi 3% ya mauzo ya kimataifa au CAD $10M — lolote zaidi.
  • Haki za ubebaji wa data.
  • Kanuni za ufafanuzi kwa maamuzi otomatiki.

Sheria ya Akili Bandia na Data (AIDA) inaongeza kanuni za AI:

  • Kanuni zinazotegemea hatari kwa mifumo ya AI.
  • Mapitio ya hatari yanayohitajika kwa AI yenye athari kubwa.
  • Kanuni za ufafanuzi kwa AI inayoathiri watu.
  • Marufuku ya AI iliyoundwa kusababisha madhara.

Sheria ya Bodi ya Kulinda Taarifa za Kibinafsi na Data inaunda chombo kipya cha rufaa. Hii inachukua nafasi ya mchakato wa sasa wa Mahakama ya Shirikisho.

Angalia jinsi Kanada inavyolinganishwa na sheria zingine za faragha katika mwongozo wetu wa uzingatiaji wa faragha duniani.

PII ya Kanada: Nini cha Kutambua

Faili za Kanada zina aina za kipekee za vitambulisho. Zana yako lazima ishughulikie zote.

SIN (Nambari ya Bima ya Jamii): Tarakimu tisa. Umbizo: XXX-XXX-XXX. Inatumia ukaguzi wa Luhn. SIN inaonekana katika fomu za kodi, rekodi za malipo, na faili za manufaa. Ni kitambulisho cha Kanada chenye usiri zaidi.

Nambari za kadi za afya za majimbo: Kanada ina majimbo na maeneo 13. Kila moja linatumia umbizo tofauti. Hakuna kiwango cha shirikisho. Umbizo muhimu:

  • OHIP ya Ontario: tarakimu 10 pamoja na nambari ya herufi 2.
  • AHCIP ya Alberta: Nambari ya Afya ya Kibinafsi ya tarakimu 9.
  • Kadi ya Huduma za BC: PHN ya tarakimu 10.
  • RAMQ ya Quebec: herufi 12 — inasimba herufi za awali za jina la ukoo na tarehe ya kuzaliwa.

Zana inayozingatia lazima isaidie umbizo zote 13.

Nambari ya Biashara ya CRA: Tarakimu tisa. Imetolewa na Shirika la Mapato la Kanada.

PII ya Lugha Mbili: Kiingereza na Kifaransa

Kanada ina lugha mbili rasmi. Fomu za shirikisho mara nyingi zinachanganya lugha zote mbili katika ukurasa mmoja.

PII ya Kifaransa ina mahitaji yake:

  • Majina: Majina ya Kifaransa yanatumia herufi zenye lafudhi. Zana inayokosa lafudhi itakosa maneno.
  • Anwani: Anwani za Quebec zinatumia istilahi za Kifaransa — Rue, Avenue, Boulevard, Chemin. Wasambazaji lazima washughulikie hizi.
  • Nambari za RAMQ: Nambari ya afya ya Quebec inasimba herufi za awali za jina la ukoo. Utambuzi lazima uwe na ufahamu wa Kifaransa.

Kwa mtazamo wa rika, angalia jinsi DPDPA ya India inavyoshughulikia PII ya lugha nyingi.

Hatari ya Kutosha kwa EU 2026

Uamuzi wa kutosha kwa EU wa Kanada ni wa 2001. Ulikuwa wa kwanza kabisa ulioidhinishwa na Tume ya Ulaya. Umepita kila mapitio hadi sasa.

Mapitio ya 2026 ni tofauti. Masuala mawili yanajitokeza.

Kwanza: Sheria ya usalama wa mtandao ya C-26 ya Kanada (2024) inahitaji makampuni ya msingi kuripoti matukio kwa CSE. CSE ni shirika la ujasusi wa ishara la Kanada. Tume itakagua ikiwa ufikiaji wa CSE kwa data hiyo unakinzana na GDPR.

Pili: Kanada bado inafanya kazi chini ya PIPEDA. Tume imeorodhesha utekelezaji wa PIPEDA kama dhaifu. CPPA bado haijatekelezwa.

Ikiwa kutosha kusimamishwa au kufutwa, uhamishaji wote wa EU-Kanada lazima ubadilishe hadi SCC au BCR mara moja.

Anza kupanga sasa. Kusubiri uamuzi ni kuchelewa sana.

Kwa muktadha wa jinsi hatari ya kutosha imedhuru makampuni, angalia mwongozo wetu wa faini za GDPR.

Mahitaji ya Chini ya Uzingatiaji

Kwa mashirika yenye shughuli za Kanada, msingi wa kiufundi ni:

  1. Utambuzi wa SIN wenye ukaguzi wa Luhn.
  2. Usindikaji wa PII wa Kiingereza na Kifaransa wa lugha mbili.
  3. Utambuzi wa kadi ya afya ya OHIP ya Ontario.
  4. Utambuzi wa kadi ya afya ya RAMQ ya Quebec.
  5. Umbizo zote 13 za majimbo kwa utayari kamili wa CPPA.

Vyanzo

Tayari kulinda data yako?

Anza kuanonymisha PII na aina 285+ za vitu katika lugha 48.

About this page

We update this page when our platform or the law changes.

Read our founder note for how we work.

Each change shows up in the timestamp at the top.

Related reading

We follow these rules

  • GDPR (EU 2016/679).
  • ISO/IEC 27001:2022.
  • NIS2 (EU 2022/2555).
  • HIPAA safe harbor under 45 CFR § 164.514(b)(2).

Our promise

We do not sell your data.

We do not train models on your text.

We store your files in Germany.

You can delete your account at any time.

You own your work.

Where we run

Our servers live in Falkenstein, Germany.

We use Hetzner. They hold ISO 27001 certification.

All data stays in the EU.

Backups run every day.

Need help?

Email support@anonym.legal.

We reply within one business day.

How we test

We run a full check suite on every release.

Each surface gets its own sweep script and report.

Human reviewers spot-check the output each week.

We track recall and precision on a labelled set.

Bad runs block the deploy.

What we never do

  • We never sell your information to third parties.
  • We never train models on what you upload.
  • We never keep your work after you delete it.
  • We never share keys with any outside firm.
  • We never run ads inside the product.

Plans in plain words

We sell credits, not seats.

One credit covers one short job.

Long jobs use a few credits each.

You can top up at any time.

Unused credits roll over each month.

Read the plans page for current rates.

Who built this

A small team of engineers and lawyers built this.

We ship from Europe and work in the open.

Our founder note spells out why we started.

Where to start

How the parts fit

A browser add-on cleans text inside Chrome.

A Word plug-in handles drafts in Office.

A small desktop tool works on whole folders.

An agent protocol link feeds large models safely.

All four share one core engine and one rule set.

Words from our team

We started this work after a lunch about cookies.

One friend kept getting odd ads on her phone.

We asked why a court file leaked through a draft.

We sketched the first build on a napkin that week.

By month three we had a tiny demo for a friend.

She used it on her first case the next day.

Common questions we hear

Can the tool read scanned PDFs? Yes, with OCR.

Does it work on long files? Yes, in small chunks.

Can I roll my own rule set? Yes, save it as a preset.

Does it run offline? The desktop build runs offline.

Do you keep my files? No, the cloud build wipes after each run.

Will it learn from my work? No, we never train on inputs.

A short tour of the workflow

Upload a file or paste a snippet of prose.

Pick the entities you want gone from the draft.

Choose a method: replace, mask, hash, encrypt, or redact.

Press run and watch the side panel show each hit.

Skim the result and tweak any rule that misfired.

Save the cleaned file or send it to a teammate.