Montréal is the largest city in Quebec and the second largest municipality in Canada, with an estimated 1,915,366 residents on July 1, 2025, according to Statistics Canada. For a product team there, two provincial rules decide much of the architecture: how personal information is handled, and which language the user sees.
What does Law 25 change inside an app?
It changes the defaults. The Commission d'accès à l'information (CAI) summarizes the rule this way: privacy settings of a technological product or service offered to the public must provide the highest level of confidentiality by default, without any intervention by the user. Functions that can identify, locate or profile a person must be explained to the user beforehand, and the CAI states that such technologies cannot be activated by default.
For the app, I identify the functions covered by those rules and document their initial settings and activation controls. The statutory privacy-default rule has an exception for browser cookies, which must be assessed under the rules applicable to them. The settings screen is designed first, not added at the end. The data model records why every field exists, which makes the confidentiality policy you publish easier to write and to keep true.
When something goes wrong: the incident register
Every confidentiality incident goes into a register, and serious ones are reported. According to the CAI, when an incident presents a risk of serious injury to the people concerned, the business must promptly notify the Commission and those people. The register covers all incidents, including those without that risk, and the CAI says its entries must be kept for at least five years after the business became aware of the incident. An app can make this workable: access logs, a clear list of which systems hold which personal information, and an export that tells you quickly who was affected.
French first: the Charter of the French Language
French has to be planned into the product, not translated onto it. The Quebec government lists, among businesses' obligations, making software available in French unless no French version exists; drafting product labels, packaging and instructions in French; making catalogues, advertising and websites accessible in French; and drafting contracts, invoices and receipts intended for consumers in French. Businesses employing 25 or more people for six months must register with the Office québécois de la langue française to begin francization.
Your counsel determines what applies to your situation. On the build side, every visible string, push notification, email template, receipt and store listing is held in both languages from the start, and layouts are tested with French text, which often runs longer than English.
Sending data outside Quebec
Hosting outside the province is possible, but it starts with an assessment on your side. The CAI states that before communicating personal information outside Quebec, an organization must conduct a privacy impact assessment and may proceed only if it shows adequate protection. I put the facts that assessment needs in writing: hosting region, every sub-processor, encryption in transit and at rest, and who can access production data.
How a Montreal project runs
Delivery is remote, with the bilingual content model and privacy controls included in the agreed scope.
- Written scope and one fixed price before each step, contract with DigitalFreedom Global LLC in US dollars
- First Version (MVP) from $27,800; an existing app is taken over from $10,500
- French and English content model, privacy-by-default settings and an incident-ready access log
- Remote delivery, decisions in writing, calls by appointment
- Code, cloud accounts and store listings in your company's name
How the work is set up for Canadian buyers in general: the Canada overview.