Engineering for Canadian companies.
Canada buys like the US and regulates like Europe. PIPEDA plus Quebec's Law 25 make privacy impact assessments and explicit transfer disclosure a normal part of a supplier conversation — straightforward when the answers already exist as documents. The time zone is the hard part, and we cover it by shifting engineers rather than by claiming an overlap that does not exist.
- Daily overlap
- 09:00–12:30 ET (shifted)
- Contract currency
- CAD or USD
- Data regime
- PIPEDA, and Quebec's Law 25 where applicable
- Regulator
- Office of the Privacy Commissioner of Canada, and the Commission d'accès à l'information du Québec
- Working language
- English
Hours, money,
and paperwork.
The three things that decide whether a cross-border engagement works, answered before you ask. Everything here is specific to Canada rather than a global average.
Time overlap
09:00–12:30 ET (shifted)
Eastern Canada is ten and a half hours behind IST on standard time, which means a normal Indian day — 10:00 to 18:00 IST — runs 23:30 to 07:30 ET and overlaps your working day by nothing at all. The 09:00–12:30 ET window exists because engineers assigned to your engagement work a shifted day at 19:30–23:00 IST, named in the engagement rather than left to goodwill. Vancouver teams take the same window at 06:00–09:30 PT. Written reporting carries everything outside it.
Currency and tax
CAD or USD
Quoted and invoiced in Canadian or US dollars. Indian GST is not levied on exported services, so it never appears on your invoice, and as a non-resident supplier we charge neither GST/HST nor QST — self-assessment applies on your side where relevant.
Data protection
- Governing law
- PIPEDA, and Quebec's Law 25 where applicable
- Authority
- Office of the Privacy Commissioner of Canada, and the Commission d'accès à l'information du Québec
- Our role
- Processor, on your instructions
Named sub-processors, written consent before any addition.
We process on your instructions under a data processing agreement naming every sub-processor. PIPEDA requires you to remain accountable for data transferred to a processor abroad, so the agreement gives you comparable protection contractually rather than leaving the accountability unbacked. Where Quebec's Law 25 applies, we support your privacy impact assessment for the transfer and accept the disclosure obligations that come with it. Canadian data residency is available and fixed at contract.
Answered
before you ask.
The questions we are asked most often from Canada, answered straight. Where we do not hold something, it says so.
Transfer accountability under PIPEDA
Handled contractually. You remain accountable for data you transfer to us, so the DPA gives comparable protection in writing and names every sub-processor. We do not treat the accountability question as your problem alone.
Law 25 privacy impact assessment
We supply what the assessment needs: processing purposes, categories, retention, sub-processor list, security controls and the ISO 27001 certificate number. Completing the assessment is yours; giving you accurate inputs is ours.
Canadian data residency
Available. Canadian cloud regions are supported and residency is written into the agreement rather than set by provider default.
Bilingual interfaces
French and English interfaces are engineered as a bilingual content model with locale-aware formatting rather than duplicated screens. French copywriting is commissioned through a specialist partner and named in the engagement.
Certificate numbers, accreditation status and the verification route are published on our trust page. Check them without asking us.
The problems
that arrive.
The work that comes to us from Canada most often. If one of these is yours, send us the brief.
Platform modernisation with a compliance trail
Systems that must keep running while they change, in sectors where the audit trail is part of the deliverable. Decision records and change control are standard.
Applied AI with explainability
Model-backed features that legal will sign off because outputs cite their sources and an evaluation harness existed before rollout.
Embedded engineering capacity
A Canadian lead who needs more engineers than headcount allows, with named people in the repository rather than a rotating pool.
Why Canada works with us
- The PIPEDA transfer-accountability question answered in the contract rather than deflected, plus Law 25 assessment inputs supplied without being chased.
- ISO 27001 with a verifiable certificate number, and ISO 20000-1 for the service management side once the software is live.
- Bilingual delivery treated as an architectural decision rather than a translation task bolted on at the end.
No Canadian entity or office, and no standing on federal or provincial procurement vehicles. Your working day and ours do not naturally intersect, so the three and a half hour window is bought with a shifted evening in India — a real commitment, but not the same thing as a shared day. French content is authored by Quebec specialists, not by us; we build the bilingual system that carries it.
Asked from
Canada.
Answers open with the answer. The general set — pricing, process, IP, security — is on the FAQ.
- Does PIPEDA allow us to send personal data to India?
- Yes, with the accountability that PIPEDA places on you as the organisation transferring it. Our data processing agreement gives comparable protection contractually and names every sub-processor, so that accountability is backed by something rather than assumed. Canadian data residency is available and fixed at contract where you would rather the data not leave.
- Can you support a Quebec Law 25 privacy impact assessment?
- Yes. We supply the inputs the assessment requires: processing purposes, data categories, retention periods, the full sub-processor list, our security controls, and the ISO 27001:2022 certificate number for independent verification. Completing and signing the assessment stays with you; providing accurate and complete inputs is on us.
- Can you meet Quebec's French-language requirements?
- We can build for them; the legal determination stays with your counsel. Under the Charter of the French Language as amended by Bill 96, commercial software and public-facing interfaces offered in Quebec generally have to be available in French on terms at least as favourable as any other language. Practically that means French cannot be a later phase: it shapes the content model, the QA matrix and the release process from the start, and French must ship at the same time as English rather than behind it. Quebec French is also not interchangeable with European French, so authorship comes from a Quebec-based specialist named in the engagement.
Where else
we work.
Working hours, currency and data protection, covered for every market we serve.
Working with Canada.
Contracted in CAD or USD, governed by PIPEDA, and Quebec's Law 25 where applicable, delivered inside the 09:00–12:30 ET (shifted) overlap window.
Cognimit Technologies LLP · Monday to Friday, 10:00–18:00 IST · IST (UTC+5:30)