When your IT or AI supplier gets a new owner: six clauses to ask for
· By Bee Flow · 5 min read
On 25 May the Dutch government prohibited the takeover of IT company Solvinity by Kyndryl. As a customer you rarely hear in time that a supplier changes hands. What a new owner can change, six clauses a small company can ask for, and what to keep in your own hands.

On 25 May 2026 the Dutch State Secretary for Economic Affairs and Climate prohibited the planned takeover of IT company Solvinity by the American firm Kyndryl. She told parliament in a letter dated 26 May (in Dutch). The Bureau Toetsing Investeringen (BTI), the Dutch investment screening office, received a notification from Kyndryl on 21 November 2025, opened an investigation and concluded that the takeover may pose a risk to the public interest, measured against the legal criteria of the Dutch act on undesirable control in telecommunications (WOZT). The BTI advised a full prohibition, and the State Secretary adopted that advice.
The letter gives no reasons of substance. It does explain the timing: the State Secretary had recently received serious indications that the deal was about to be completed. It also stresses that the screening is "country-neutral, risk-based and proportionate" and applies equally to all investors, whatever their country of origin. And it says something every company can use: notifications and investigations under this law are normally not made public, unless a takeover is prohibited outright.
So as a customer, you usually learn that a supplier has changed hands after the fact, if you learn it at all. The BTI screens deals in digital infrastructure. For the software that holds your quotes, customer mail or AI conversations, what counts is mostly what you agreed with the supplier yourself.
What changes when your supplier gets a new owner
Often nothing changes on paper. Your contract is with the same company, only the owner above it is new. After that, things can move. The service goes to another data centre, a new sub-processor appears, the terms are brought in line with the parent company's, or a product that does not fit the new plans is wound down. None of that has to be bad. You just want to know in time, and you want a way out.
This is not legal advice: have a lawyer look at any wording before it goes into a contract.
Six clauses you can ask for
Notice when the owner changes
Agree that the supplier tells you in writing, within a fixed period, when someone else has gained control of the company. Thirty days after the deal closes is a reasonable request. Without that clause you read about it in the paper, or not at all.
The right to leave at that point
Tie a termination right to that notice. Within, say, three months of the notice you may end the contract without a penalty and without buying out the rest of a multi-year term. It gives you time to see whether the new direction suits you.
Your data, in a format you can use
A pile of PDFs is not an export. Ask for your data in a common, machine-readable format such as CSV or JSON, and for documents in their original form. Have the contract list which data that covers. For cloud services, including software you buy as a service, the EU Data Act sets rules here. According to Germany's Bundesnetzagentur, providers must put clear switching terms in their contracts. After you give notice they have at most two months to prepare the technical switch, the transition period is normally at most 30 calendar days, and your data stays retrievable for at least 30 days after that. The European Commission says the Data Act has applied since 12 September 2025 and that switching charges, data egress included, disappear entirely from 12 January 2027.
Deletion on request, with confirmation
If the supplier processes personal data for you, you need a data processing agreement. According to the guidelines of the European Data Protection Board (EDPB), the processor must, at your choice, delete or return all personal data at the end of the service and delete existing copies. The EDPB adds that the processor should confirm the deletion within an agreed timescale. Write that timescale down, and ask for the confirmation to cover what sits with sub-processors too.
Where your data may be processed
A new owner may want to move the service to its own data centres or its own suppliers. The same guidelines say a processor may not engage another processor without your prior written authorisation. Under a general authorisation it must tell you about changes in advance, so that you can object. Transfers to countries outside the EU should be covered in the contract. Put in which countries your data may be stored and processed, and what happens when you object to a change.
Continuity during the transition
Agree that service levels and terms stay the same while a takeover or a switch is under way, that the supplier helps you move to someone else, and that you can keep using the service until your data has been moved. The Bundesnetzagentur writes that you should be able to see before signing which rights you have for exporting, terminating and getting help with the switch.

What to keep in your own hands
A good contract only helps if you can actually leave.
Keep the original documents in your own storage, not only inside the tool that searches them. Run an export once a quarter and open it: an export you have never tried is a promise and nothing more. Put admin accounts, the domain and billing in your company's name, not in the name of one employee or a reseller. And keep a list of which supplier holds which data.
For an AI tool, that list should include what you built in it: instructions, templates and the structure of your knowledge bases. That is work you do not want to redo.
We would not wait for a takeover to make the news. The best moment to arrange this is at renewal, while the supplier still wants your signature. In our piece on where to host an AI workspace we also look at leaving when you choose where your software runs.
Where Bee Flow fits
Bee Flow can run on your own server. Everything it keeps then sits in your own PostgreSQL database, which you back up and restore yourself. Your conversations and knowledge bases stay with you, whoever ends up owning the suppliers around them. You choose the language model: a European provider such as Mistral, another cloud provider, or a model on your own hardware. Switching models does not mean moving your workspace. Knowledge bases are built from your own documents, and answers cite their source. Who is behind Bee Flow is on about us. The self-host or EU cloud page explains how it works, and if you want to know what it means for your company, get in touch.