Canada’s first stand-alone digital trade deal exists as a political conclusion and two press releases. Until the text appears, no software or AI seller should change a contract because of it.
The Canada-EU Digital Trade Agreement was concluded in Montréal on October 30, 2026, and as of the next morning neither government had published the text a business would need to read it. What exists is a Prime Minister’s release, a European Commission announcement, a Global Affairs Canada web page and five short reports from the negotiating rounds. That is enough to know the subjects. It is not enough to know the obligations.
Our view is narrow and, we think, useful: treat the agreement as a direction of travel for data flows and source code, keep every current European contract on the legal footing it already has, and put the open questions in writing for counsel now, while the lawyers in Brussels are still doing what the Commission calls “legal scrubbing”.
What Ottawa and Brussels concluded in the Canada-EU Digital Trade Agreement
They concluded negotiations, which is a political step rather than a legal one. The Commission’s October 30 announcement says the agreement covers trusted cross-border data flows, electronic contracts, signatures and invoices, and rules against unsolicited commercial messages and deceptive online practices. Ottawa adds selling software and digital products. Neither release attaches a text, a signature date or an in-force date.
The Prime Minister’s release on the Alliance for the Future places the agreement among more than twenty measures announced at the summit, alongside Canada’s entry into the European supercomputing network that we examined in our reading of the EuroHPC and JUPITER access rules. International Trade Minister Maninder Sidhu’s quote in that release describes it as Canada’s first agreement dedicated entirely to digital trade, and adds a qualifier worth keeping: each side “can continue to regulate in the public interest”.
That qualifier matters more than the adjectives around it. A trade agreement binds governments. It limits what Ottawa or an EU member state may require of a business, such as storing data locally as a condition of operating. It does not bind, say, a German hospital procurement office that simply prefers a supplier with servers in Frankfurt, because that preference is a contract term, not a government measure.
Concluded is a status, and it is not “in force”
Nothing in the agreement applies to a Canadian business today. The Commission says it will now carry out legal scrubbing, translate the text into every EU language, and only then submit a proposal to the Council and the European Parliament. Ottawa has not published a timetable for its own steps. Any date for entry into force is therefore a guess, and we will not offer one.
The Commission’s document page for the negotiations holds the only drafting a business can read: the EU’s own textual proposal and the five round reports. The proposal is useful for vocabulary and nothing more. It says data flows “shall not be restricted between the Parties” by local storage or local computing requirements, but it is one side’s starting position, and Canada’s final wording may differ. Citing it to a client as the agreed text would be a mistake.
Speed deserves a note too. From the March 5 launch to the October 30 conclusion is 239 days, just under eight months, which is quick for a trade text. It also means the text has had little public airing. The only drafting on the record is one side’s proposal, so a definition such as “computing facilities” or the reach of a security exception is still unknown to anyone outside the two negotiating teams.
Two governments, two digital trade figures
Ottawa and Brussels describe the same trade with numbers that do not line up, so a business should quote neither as the whole picture. Ottawa says Canadian businesses exported nearly $15 billion in digitally deliverable services to the EU in 2024. The Commission, citing Eurostat, puts EU imports of digitally delivered services from Canada at €8.6 billion in 2025.
The words differ (“deliverable” against “delivered”), the years differ, the currencies differ, and one figure is measured from each side of the Atlantic. The gap is not evidence of growth or decline. The more telling number is the direction: by the Commission’s count, the EU sold €11.2 billion of digitally delivered services to Canada in 2025 and bought €8.6 billion, so Europe ran a surplus of €2.6 billion on this trade. We would expect a deal that lowers friction both ways to help the side with more sellers first, and on Brussels’ figures that is not yet Canada.
What a Canadian software or AI seller should put in writing now
Write down what your European contracts rely on today, so that when the text appears counsel can compare it line by line. For most Canadian software and AI firms that means data transfer terms, any hosting promises, and any clause where a client asks to inspect code. None of these change on October 30, and none should be renegotiated on the strength of a press release.
- Personal data. Note that transfers of personal data from Europe to your company rest on the EU’s adequacy decision for Canada, which the European Commission lists for Canadian commercial organisations. The trade agreement does not replace it. Canadian privacy law still governs what you do with the data once it arrives; we looked at where that law stands in the Privacy Commissioner’s AI warning to Parliament.
- Hosting promises. List every contract where you promised EU-only storage. Those are commercial commitments the agreement will not undo.
- Source code. Flag any client or regulator request to inspect source code, and note separately any request for model weights, which no published document addresses. Source code protection was a negotiating subject in both of the last two rounds, and Global Affairs Canada’s stated aim is that countries not require access to source code for market access. Wait for the wording before relying on it.
- E-signatures and e-invoices. Ask whether your European customers still demand wet signatures or paper invoices. That is where the agreement may save the most staff time.
- Owner and date. Name the person who will read the text the week it is published, and send this list to counsel before then.
The data point connects to a broader argument we made in why data sovereignty became a board-level AI issue: in our view, where data sits is settled far more often in procurement than in treaties. Policy readers can follow the rest of the summit’s measures through our Canadian AI policy hub.
The case for reading it as good news already
There is a fair argument that a business should welcome the agreement now rather than wait. The Commission describes a framework for trusted data flows between the EU and Canada as vital for companies, particularly small and medium-sized ones, and says the agreement creates binding commitments that complement CETA, which has applied provisionally since 2017.
We accept most of that. The direction is good for Canadian sellers, and the summit paired it with the European compute access and the federal Cohere stake we covered in Ottawa’s equity stake in Cohere. Our disagreement is about timing and reliance. A sales team that tells a client in Lyon that “the new deal guarantees” anything about data has made a promise on a text it has not read, and neither has the client.
FAQ
Is the Canada-EU Digital Trade Agreement in force?
No. Canada and the EU concluded negotiations on October 30, 2026. The agreement still needs legal scrubbing, translation and approval by the Council and the European Parliament on the EU side, plus Canada’s own procedures. No signature or in-force date has been announced.
Where can I read the Canada-EU Digital Trade Agreement text?
Nowhere yet. As of October 31, 2026, neither government had published the concluded text. The European Commission’s negotiation documents page holds the EU’s own proposal and five round reports, which show the subjects but not the final wording.
Does the agreement change how my company receives personal data from Europe?
Not today. Transfers of personal data from the EU to Canadian commercial organisations rely on the EU’s existing adequacy decision for Canada. The trade agreement covers data flows between the two parties, but it does not replace that decision.
What does the agreement cover for software and AI companies?
According to the two governments, it covers cross-border data flows, selling software and digital products, e-contracts, e-signatures and e-invoices, and online consumer protection. The negotiating round reports also list protection of software source code and of personal data and privacy.
Should we change our European contracts now?
No. Keep current contracts on their existing legal footing, list the clauses that touch data transfers, hosting and source code, and have counsel compare them with the text once it is published. Our Canadian AI policy hub tracks related rules.
The next document worth waiting for is the published text, and the first clause to read in it is the exceptions article, because that is where “the right to regulate” becomes specific. Until it appears, the useful work is the five-line list above, sent to counsel with a name beside it.
Facts in this column were checked on October 31, 2026 against the Prime Minister’s October 30 release, the European Commission’s announcement and negotiation documents, the Commission’s adequacy decisions page and Global Affairs Canada’s digital trade page.
