Free site audit: your results in 30 seconds, by email too →
From our Instagram? Get your free 30-second site audit →
← The Lab

Bill 96 and Law 25: A Website Checklist for Québec Businesses

What the Charter of the French language and Québec's privacy law ask of a business website, item by item, with the official source for each one.

Two Québec laws decide much of what a business website has to do: the Charter of the French language for language, and Law 25 for personal information. This checklist turns both into items you can verify page by page.

Quick answer

If your business operates in Québec, customers have the right to a complete French version of your website, and any public document you offer in another language must also be available in French on terms at least as favourable. If the site collects personal information, Law 25 requires a privacy policy in clear and simple terms, the title and contact details of the person in charge of personal information, and identification, location or profiling functions that stay off until the person turns them on.

Key takeaways

  • Language: every public page, form, order form and piece of purchase information needs a French version that is at least as easy to reach as any other language.
  • Standard contracts that customers accept as written, such as subscription terms, must be handed over in French first. That rule has applied since June 1, 2023.
  • Privacy: publish a privacy policy, the person in charge's title and contact details, and information about your privacy governance on the site.
  • Tools that identify, locate or profile visitors must be activated by the visitor, not switched on by default.

Language: what the Charter asks of your website

The Charter of the French language was amended in 2022 by the law known as Bill 96. The Office québécois de la langue française (OQLF) states that customers of businesses operating in Québec have the right to be informed and served in French before, during and after a transaction. Its consumer page lists, among those rights, access to a complete French version of a company's website and to French content on its social media.

Section 52 of the Charter covers catalogues, brochures, order forms and similar documents available to the public, whatever the medium. They must be written in French, and a business cannot offer them in another language unless the French version is accessible on terms at least as favourable.

  1. Every public page exists in French

    Service and product pages, forms, order forms, checkout and confirmation emails all need a French version. English or other languages can sit beside it.

  2. French is at least as easy to reach

    Do not make the French version harder to find, slower to load, or thinner than the English one. Section 52 asks for terms at least as favourable.

  3. Purchase information is in French

    Éducaloi summarizes the rule for online sales: all the information customers need to buy must be available in French, including product details, order forms, invoices and receipts.

  4. Standard contracts are handed over in French first

    Since June 1, 2023, a French version of a contract of adhesion must be given to the customer before they can choose to be bound by another language (section 55). Online terms that customers must accept as written, such as subscription terms, are the kind of contract the OQLF describes.

  5. Customer-facing software is available in French

    Section 52.1 requires software to be available in French unless no French version exists. If you are building a portal or app for customers, plan the French interface from the start.

  6. Job postings are written in French

    The OQLF lists writing the job offers you publish in French among business obligations. That includes the careers page.

Language checklist by website element
Website elementWhat to checkSource
Pages and navigationA complete French version, reachable on terms at least as favourableOQLF consumer rights page; Charter s. 52
Product pages, cart and checkoutAll information needed to buy is available in FrenchÉducaloi
Order forms, invoices, receiptsProvided in FrenchOQLF; Charter s. 52
Terms customers accept as writtenFrench version handed over first, since June 1, 2023Charter s. 55; OQLF legislative changes
Customer portal or appAvailable in FrenchCharter s. 52.1
Careers pageJob offers written in FrenchOQLF legislative changes

Privacy: what Law 25 asks of your website

Law 25, adopted in 2021, amended the Act respecting the protection of personal information in the private sector. Several of its rules point directly at the website: what must be published there, what visitors must be told when their information is collected, and what can be switched on by default.

The Commission d'accès à l'information (CAI), Québec's privacy regulator, summarizes these changes on its site. The section numbers below refer to the act itself.

  1. Publish a privacy policy in clear and simple terms

    A business that collects personal information by technological means must publish a privacy policy on its website and give notice of any change to it (section 8.2).

  2. Publish who is in charge of personal information

    By default, the person with the highest authority in the business is in charge of protecting personal information and can delegate the role in writing. The title and contact details of that person must be published on the website (section 3.1).

  3. Publish information about your privacy governance

    Detailed information about the business's policies and practices, including retention and destruction rules, staff roles and how complaints are handled, must be published on the website in clear and simple terms (section 3.2).

  4. Tell people why and how you collect, at the moment you collect

    The CAI lists what to tell people at collection: the purposes, the means, their rights of access and correction, and their right to withdraw consent. Forms are where this usually belongs.

  5. Keep identification, location and profiling off by default

    If a technology can identify, locate or profile the person, you must inform them beforehand and tell them how to activate those functions (section 8.1). The CAI explains that this means the person activates them, not the business.

  6. Ask for consent once per purpose

    Consent must be manifest, free, informed and given for specific purposes, asked for each purpose in clear and simple terms, and presented separately from other information when it is in writing (section 14). A newsletter opt-in bundled into a contact form does not meet that test.

Privacy checklist by website element
Website elementWhat to checkSource
Footer or legal pagesPrivacy policy in clear and simple termsAct s. 8.2; CAI
Privacy policy or contact pageTitle and contact details of the person in charge of personal informationAct s. 3.1; CAI
Privacy or governance pageRetention and destruction, roles, complaint processAct s. 3.2; CAI
FormsPurposes, means, rights and withdrawal of consent stated at collectionCAI transparency obligations
Checkboxes and opt-insOne consent request per purpose, separate from other textAct s. 14
Tracking, location and profiling toolsOff until the visitor activates them, with notice beforehandAct s. 8.1; CAI

Cookies and analytics: what the texts say and what they leave open

Section 9.1 requires the privacy settings of a technological product or service offered to the public to provide the highest level of confidentiality by default. The same section says this rule does not apply to the privacy settings of a cookie.

The profiling and location rule in section 8.1 still applies to the technology itself. Whether a given analytics, advertising or session-recording tool counts as identifying, locating or profiling a visitor depends on what it does and how it is configured. That is a question for a qualified advisor, with the CAI's guidance in hand.

Before personal information is communicated outside Québec, the CAI says an organization must carry out a privacy impact assessment. If your forms, CRM or hosting send data to providers outside Québec, ask your advisor whether that applies to your setup.

How to work through this checklist

Start with an inventory rather than a redesign. List every public page in each language, every form and what it collects, every third-party script that loads on the site, and every document a customer can download or accept.

Then mark each item against the two tables above. Most gaps on small business sites are fixable without a rebuild: a missing French page, a bundled consent checkbox, a privacy policy without the person in charge, or a tracking script that loads before the visitor has a say.

  1. Pages and documents

    Compare the French and English sitemaps, then check downloadable PDFs, order forms and emails.

  2. Forms and consent

    For each form, write down what it collects, why, where it goes, and whether consent is asked per purpose.

  3. Scripts and vendors

    List analytics, ads, chat, booking and recording tools, what they collect, and where their servers are.

  4. Published privacy information

    Check that the policy, the person in charge and governance information are on the site in both languages.

Frequently asked questions

Does my website need a French version if most of my clients speak English?

If your business operates in Québec, the OQLF says customers have the right to a complete French version of its website. Éducaloi adds that a business with an address in Québec must publish a French version of its site. Other languages can be offered alongside it.

Can the English version be the one that loads first?

The Charter text reviewed for this guide does not say which version loads first. Section 52 says a document cannot be offered in another language when the French version is not accessible on terms at least as favourable. In practice, make both versions equally easy to reach.

Does Law 25 require a cookie banner?

The act does not name a banner. It requires informing people before using technology that can identify, locate or profile them and letting them activate those functions themselves (section 8.1). The default-settings rule in section 9.1 excludes cookie settings. Whether your tools need a consent step depends on what they do, so check with a qualified advisor.

Who is the person in charge of protecting personal information?

By default, the person with the highest authority in the business. That person can delegate the role in writing, in whole or in part. The title and contact details must be published on the website (section 3.1).

What are the fines under the Charter?

Éducaloi reports fines of $3,000 to $30,000 for each day a violation continues, doubled for a first repeat offence and tripled for further ones.

Method note

This guide summarizes the official texts and regulator pages listed below, as they read on November 14, 2026. It is not legal advice. Rules and their interpretation change, so confirm your situation with the OQLF, the CAI or a qualified advisor.

Sources (last checked November 14, 2026)

Related pages

Next step

Shape the bilingual model before redesign.

Decide which pages need equal depth, how EN/FR routes should work, and where bilingual SEO needs support.

Plan the bilingual siteAudit EN/FR SEO
EN/FR routeshreflangAdapted copy