Your analytics vendor is an architecture risk

18 november 2026 | Geschreven door Brent Stevens

1200x800
1 oktober 2024

In November 2025 Kyndryl, an American IT services company, agreed to acquire Solvinity, the Dutch hosting provider that runs infrastructure for DigiD and MijnOverheid. The Autoriteit Consument en Markt cleared that transaction on competition grounds. In May 2026 the Dutch State Secretary for Digital Economy and Sovereignty prohibited it anyway, on a substantiation that was never made public.

The short answer

An analytics vendor becomes an architecture risk at the moment an organisation cannot say what it would cost, in weeks and in euros, to collect the same data without that vendor. Three decisions made that concrete: the prohibition of the Kyndryl acquisition of Solvinity in May 2026, the Rijksbreed Cloudbeleid 2026 of 3 July 2026 requiring exit plans, and Chapter VI of the EU Data Act since 12 September 2025.

In short

  • The Dutch State Secretary for Digital Economy and Sovereignty prohibited the acquisition of Solvinity by Kyndryl in May 2026, and the district court in Rotterdam refused to suspend that prohibition on 14 July 2026.
  • The Rijksbreed Cloudbeleid 2026 of 3 July 2026 requires Dutch central government organisations to hold a documented exit plan for material cloud use.
  • Chapter VI of the EU Data Act has applied since 12 September 2025 and requires switching charges to be withdrawn from 12 January 2027.
  • Data residency, transfer legality and jurisdictional control are three separate questions, and a vendor answer to one is not an answer to the other two.

What makes an analytics vendor an architecture risk?

An analytics vendor is an architecture risk when the cost of leaving it is unknown, and that cost is set by the collection layer rather than by the contract.

An analytics platform defines the events, holds the identifiers, and is referenced by tags on every page and screen. Where events are implemented in vendor specific SDK calls and event names, the vendor owns the definition of the business, and replacing it means reimplementing measurement across every template. Where the same events are read from a data layer, which is a structured and vendor neutral description of what happens on a page that every downstream tool reads from, the vendor is a destination and not a dependency. Identical contract, identical price, entirely different exit cost, and that distinction is set out on [What makes a data layer reliable at scale].

Why does a supplier's jurisdiction now show up in procurement?

Because the Dutch state has demonstrated, with dated decisions, that it acts on jurisdiction over a supplier even when the technical service and the competition test are both in order.

Bureau Toetsing Investeringen advised against the Solvinity transaction, and in May 2026 the State Secretary prohibited it under Chapter 14a of the Telecommunicatiewet, the Wet ongewenste zeggenschap telecommunicatie. Public reporting identified the concern as American control over infrastructure serving DigiD and MijnOverheid. On 27 August 2026, six weeks after the court refused to suspend the prohibition, Kyndryl stated that it accepted the Dutch cabinet decision and would not contest it further.

The Rijksbreed Cloudbeleid 2026, sent to parliament on 3 July 2026 by the same State Secretary, reaches many more organisations. For important cloud services it requires a documented exit plan describing how the organisation continues to operate if a cloud service suddenly becomes unavailable, with switching to another provider or continuing independently as the routes out. Existing use has four years to comply, and core tasks may not sit with providers under non European Economic Area law.

Why that matters outside central government is contractual rather than legal. Cloud policy written for central government travels down the supply chain through procurement documents, and it reaches the semi public buyers that dominate Dutch enterprise measurement work: health insurers, pension providers, housing corporations, educational institutions and utilities. An analytics vendor that cannot answer an exit question fails tenders before it fails audits.

Does data residency answer the jurisdiction question?

No. Data residency describes where data is stored, and jurisdiction describes who can be legally compelled to produce it.

The United States CLOUD Act attaches to the provider rather than to the data centre, so a European region does not by itself remove American legal reach over an American controlled provider. On 18 June 2025, under oath before a French Senate inquiry commission, Anton Carniaux of Microsoft France was asked whether he could guarantee that data of French citizens would not be transmitted to American authorities without the French government's agreement. He answered that he could not guarantee it.

The transfer question is settled separately and more favourably. On 3 September 2025 the General Court of the European Union upheld the adequacy decision underpinning the EU US Data Privacy Framework, which makes transfers to certified American recipients lawful, and says nothing about who can be compelled to disclose data.

Question What it governs What answers it
Where is the data stored? Region of storage and processing Vendor configuration and a contractual region commitment
Is the transfer lawful? Legal basis for sending personal data outside the EEA The adequacy decision upheld on 3 September 2025
Who can compel disclosure? Legal reach over the provider and its parent Corporate ownership and extraterritorial law
What does leaving cost? Exit time and reimplementation effort Chapter VI of the EU Data Act, plus your own architecture

What has the EU Data Act changed about switching?

It converted vendor exit from a commercial negotiation into a contractual entitlement with deadlines.

Chapter VI of Regulation (EU) 2023/2854, the EU Data Act, has applied since 12 September 2025 to providers of data processing services, a category covering infrastructure, platform and software services. Contracts must let a customer switch after a notice period of at most two months, within a transition period of at most 30 days. Until 12 January 2027 a provider may charge for switching up to the costs directly incurred, and from 12 January 2027 switching charges must be withdrawn. The Autoriteit Consument en Markt has supervised the EU Data Act in the Netherlands since 21 November 2025. From 12 January 2027 the vendor side of the exit price approaches zero, which leaves only the cost you built yourself.

What this means for you

Four checks, roughly one day of work. Every date and obligation above comes from a public source; the claim that exit cost sits in the collection layer rather than in the contract is an observation from Cloud Nine Digital implementation work and is not a measured finding.

  1. Name the legal entity operating your analytics platform, its ultimate parent, and the law that parent falls under, for the platform and for every subprocessor receiving raw event data.
  2. Count how many of your 20 most important events are defined in vendor specific SDK calls and how many are read from a vendor neutral data layer. That ratio is your exit cost.
  3. Ask your vendor for the switching terms required by Chapter VI of the EU Data Act: notice period, transition period, charges before 12 January 2027, and export format.
  4. Execute one export of 30 days of raw event data and confirm it is usable outside the platform. An export capability that has never been run is a claim.

If steps 1 and 2 cannot be answered in a day, that is the finding.

Key points

  • The acquisition of Solvinity by Kyndryl was prohibited in May 2026 under the Wet ongewenste zeggenschap telecommunicatie and abandoned by Kyndryl on 27 August 2026.
  • The Rijksbreed Cloudbeleid 2026 of 3 July 2026 requires a documented exit plan for important cloud services in Dutch central government, with four years for existing use.
  • Chapter VI of the EU Data Act has applied since 12 September 2025 and requires switching charges to be withdrawn from 12 January 2027.
  • The exit cost of an analytics platform is determined by whether events are read from a vendor neutral data layer or implemented in vendor specific SDK calls.

FAQ

Does storing analytics data in the European Union remove the American jurisdiction question? No. The United States CLOUD Act attaches to the provider rather than to the location of the data, so an American controlled provider can remain subject to American legal process while operating a European region.

Is Google Analytics 4 a compliance risk for European companies? The transfer question for American analytics providers is answered by the adequacy decision underpinning the EU US Data Privacy Framework, which the General Court of the European Union upheld on 3 September 2025. The open questions are whether the consent covers what is done with the data, and what the organisation would do if that adequacy decision were annulled.

What does the EU Data Act require my analytics vendor to offer? Chapter VI of Regulation (EU) 2023/2854, applicable since 12 September 2025, requires providers of data processing services to allow a customer to switch after a notice period of at most two months, within a transition period of at most 30 days, and from 12 January 2027 to charge nothing for the switch.

Why did the Dutch government block the acquisition of Solvinity by Kyndryl? The State Secretary for Digital Economy and Sovereignty prohibited the acquisition in May 2026 under the Wet ongewenste zeggenschap telecommunicatie, following a negative advice from Bureau Toetsing Investeringen, citing a risk to the public interest connected to infrastructure serving DigiD and MijnOverheid. The substantiation was classified.

How do I reduce dependency on a single analytics vendor? Implement each event once in a vendor neutral data layer and treat every platform as a destination reading from it, instead of implementing events separately in each vendor's own SDK and event schema.

About the author

Brent Stevens is Commercial Director at Cloud Nine Digital, a data and analytics consultancy in Amsterdam and part of LevelUp Group that builds, validates and monitors data collection layers. Cloud Nine Digital measured what happens before the visitor's choice on 2,450 Dutch domains on 5 October 2026.

Cloud Nine Digital ranked first in the Data Science and Analytics Agencies category of the Emerce 100 in 2026, with 6 out of 7 stars, based on an image study by Motivaction among decision-makers in the Dutch market.

[Author page link to be inserted before publication.] This article is not legal advice.

If you want to know what leaving your current analytics platform would actually cost, Cloud Nine Digital maps that dependency at event level as a fixed-scope assessment.