On August 20, 2025, the US administration announced sanctions against four members of the International Criminal Court, including judges Kimberly Prost and Nicolas Guillou. The Court firmly rejected them. The Associated Press reported that the Canadian judge lost access to her credit cards and that her Alexa assistant stopped responding.
The circumstances are exceptional. They do not predict what will happen to a small business in Quebec. They do show that a decision made outside a service can change its users’ access to it.
Preparing for a loss of access
An organization can protect its accounts well and still lose access to a tool because of a provider’s decision. A billing-related suspension or contract dispute can also interrupt work without a security incident being involved.
Features and pricing naturally receive much of the attention when choosing a service. Account suspension and closure terms also deserve a review. They help explain when the provider may stop serving the organization and what happens to its data afterwards.
Preparation can begin with the tools the team needs every day: email, shared files, calendars and administrative access. For each one, record the contracting supplier, the data location and the person who holds the access needed to act.
This inventory helps people find the information they need if an account becomes inaccessible. It needs updating whenever the team changes providers or assigns a new person to manage a service.
The inventory becomes more useful when it follows a working day. A small organization might use email to receive requests, confirm appointments and recover access to other accounts. Losing that email service can therefore affect several activities at once. Mapping those connections helps establish the order in which access needs to be restored.
It is also useful to establish who can be reached when the usual service is unavailable. A procedure kept only in an inaccessible tool would be difficult to consult when needed. The point is to check that contact details and the information required remain available to people authorized to act.
Trying a sample data export
Export conditions are another part of the review. What can be retrieved varies: messages may be available without all account settings, or files without all their associated access permissions. Organizations need to check what the service actually allows them to transfer.
A test with a small sample helps establish this. Export a few items, then check whether they remain readable without the original service. The result indicates what could be kept and what would require more work when leaving.
It is also useful to check who can perform the export. If only one person’s account can retrieve the organization’s data, their absence could complicate an urgent response.
Planning to resume work
Retrieving files is one step; being able to work with them is another. An export may be readable but still require time to recreate accounts, assign permissions or organize documents in a useful way. A limited trial can reveal that work before it has to be done under pressure.
An organization does not need to replace every tool at once to start preparing. It can first identify the service whose interruption would have the greatest effect, check its recovery options and record the limits it finds. That initial review provides a practical basis for deciding where to focus the next effort.
Reviewing a local provider’s dependencies
A Quebec provider still depends on the companies it works with. Hosting locations, software and subcontractors should therefore be part of the discussion, alongside the contract terms.
We began this review at Shelter Bay in 2025. It led us to replace tools, operate more services ourselves and develop Béluga. Our own infrastructure still has dependencies, which we describe in our journey. We want organizations to have that information when they evaluate our services.