Canadian data residency for customer sign-in
Sign-in holds some of the most sensitive data in your app. Here is what Canadian privacy law asks about where it goes, what “stored in Canada” does and does not promise, and the questions to put to any provider.
. This guide explains Canadian rules in general terms for people who build software. It is not legal advice: for your own situation, talk to a lawyer.
What sign-in data includes
Sign-in is more than a password table. A typical setup stores, or passes along:
- email addresses and phone numbers used as identifiers
- password hashes, passkey public keys and one-time code records
- sessions, refresh tokens and device details
- IP addresses and sign-in history, kept for security
- audit logs and support notes
- the email and text messages that carry codes and links, which pass through mail servers and phone carriers on the way
Each of these can live somewhere different: the main database, a cache, backups, log storage, an analytics tool, the email or SMS provider. An answer about residency covers all of them, or it covers less than it sounds like.
What PIPEDA says
Personal Information Protection and Electronic Documents Act, S.C. 2000, c. 5.
PIPEDA does not require personal information to stay in Canada. The Office of the Privacy Commissioner’s guidance on cross-border processing says so plainly: transferring information to a provider in another country for processing is allowed.
What PIPEDA requires is accountability. You stay responsible for information you hand to a provider, you must use contracts or other means to give it a comparable level of protection, and you should tell people that their information may be processed in another country and be accessible there to courts, police and national security agencies.
PIPEDA also requires you to report a breach that creates a real risk of significant harm to the Commissioner, and to tell the people affected, whoever’s servers it happened on.
Alberta, British Columbia and Quebec have their own private-sector privacy laws, and public bodies and their suppliers often face stricter rules or contract terms on where data may be stored. Check the laws and contracts that apply to you.
What Quebec’s Law 25 adds
The Act respecting the protection of personal information in the private sector, as amended by Law 25.
Quebec’s private-sector privacy law does not require residency either, but it formalises transfers. Before personal information is communicated outside Quebec, the business must carry out a privacy impact assessment that weighs how sensitive the information is, why it is going, how it will be protected (including by contract) and the legal framework where it is going. The transfer must then be covered by a written agreement.
“Outside Quebec” includes the rest of Canada. A data centre in Montréal keeps information in Quebec; one in Toronto, or in Virginia, does not.
Law 25 also asks you to tell people, when you collect their information, if it may be communicated outside Quebec, and to report confidentiality incidents that present a risk of serious injury to the Commission d’accès à l’information and to the people concerned.
What “stored in Canada” means, and what it does not
When a provider says data is stored in Canada, it usually means the databases and backups that hold it sit in a Canadian data centre. That is a real, checkable claim. On its own, it does not tell you:
- where requests are processed before the data is stored, for example on application servers in another country
- where logs, error reports and analytics go
- which subprocessors see the data, such as email and SMS delivery, content delivery networks and support tools
- which country’s laws apply to the provider itself: a company subject to the US CLOUD Act can be compelled to produce data it controls even when that data is stored outside the United States
None of this makes storage in Canada meaningless. It means the claim should come with the rest of the picture.
How HonkIO words it
Our own wording is meant to be that picture: customer data is stored in Canada, in Beauharnois, Quebec, with encrypted backups in Toronto, API requests are processed in Beauharnois too, and some subprocessors, such as the one that routes text messages, process data outside Canada. The privacy policy lists each subprocessor and what it handles.
HonkIO Auth, our hosted sign-in, follows the same rule: users’ data is stored in Canada, requests are processed in Quebec, and Cloudflare handles TLS for sign-in hostnames as a processor. Where HonkIO Auth data lives lists each piece.
Questions to ask an identity provider
Ask them in writing, and keep the answers with your privacy assessment.
- Where are user records, sessions and backups stored, by region?
- Where are sign-in requests processed, and do they cross a border before they are stored?
- Where do logs, error reports and analytics go, and how long are they kept?
- Which subprocessors handle user data, in which countries, and for what?
- Which legal entity signs your contract, and which countries’ laws can compel it to disclose data?
- How are codes and sign-in links delivered, and through which email and SMS providers?
- Can you export and delete users, and how fast will a breach be reported to you?
Choosing a setup
If your customers or contracts require Canadian storage, pick a provider that stores sign-in data in Canada and says where it is processed, then do the paperwork the law asks for: a contract that gives comparable protection, an assessment for Quebec users if anything leaves Quebec, and a privacy notice that says where data may go.
If nothing requires it, storage in Canada is still a sensible default for a Canadian user base: the stored data sits in a Canadian jurisdiction, and the answer to “where is my data?” is one line.
Whichever you choose, keep the sign-in methods in view. Codes and links sent by email or SMS travel through other providers’ networks, and those hops belong in your privacy notice too. The guide to passwordless sign-in methods compares them.
Questions
- Does PIPEDA require data to be stored in Canada?
- No. PIPEDA allows transfers to other countries for processing, but you stay accountable for the information, need contracts that give it comparable protection, and should tell people it may be processed and accessed in another country.
- Does Quebec’s Law 25 require data to be stored in Quebec?
- No. Before personal information is communicated outside Quebec, including to another province, you must carry out a privacy impact assessment and have a written agreement covering the transfer. You must also tell people when you collect their information if it may leave Quebec.
- If my provider stores data in Canada, is that enough?
- It covers storage. Also ask where requests are processed, where logs and backups go, which subprocessors see the data, and which countries’ laws apply to the provider itself.
- Does a data centre in Montréal keep data in Quebec?
- The stored data, yes: Montréal is in Quebec. Whether a setup as a whole communicates information outside Quebec depends on the rest of the chain, such as where requests are processed, who can access it and which subprocessors see it, so assess the whole flow.
- Is this guide legal advice?
- No. It describes the law in general terms. For your own obligations, talk to a privacy lawyer or your privacy officer.
Sources
The laws, regulator guidance and standards this guide draws on, checked in October 2026. If something has changed, tell us at support@honkio.ca and we will correct it.
- Personal Information Protection and Electronic Documents Act, S.C. 2000, c. 5 (Justice Laws)
- Guidelines for processing personal data across borders (Office of the Privacy Commissioner of Canada)
- Act respecting the protection of personal information in the private sector, CQLR c. P-39.1 (LégisQuébec)
- Commission d’accès à l’information du Québec
- CLOUD Act resources (US Department of Justice)
HonkIO