Why Swedish municipalities choose a European platform and what you should actually ask your provider

Graphic with the heading "Why municipalities choose a European platform" and four questions: Where is the data stored?, What laws apply to the supplier?, Who can be forced to disclose it?, What happens if that happens?

When a Swedish municipality evaluates a new IT system, the questions have changed. It's still about features, price and support, but now it's just as much about where the data is stored, what laws apply to the supplier and what happens if a non-European decision requires access to your systems.

It's not paranoia. It's a reasonable consequence of GDPR, NIS2, and a new reality where digital sovereignty is part of risk management for the public sector.

This article is a practical buying guide for those evaluating a service management platform for a municipal or regional organization. We'll go over what really matters and what questions you should ask each vendor you talk to.

Why data location is no longer a matter of detail

For many years, the issue of server location was treated as a technical detail. Today, it is a strategic issue.

GDPR clearly requires that personal data of EU citizens be handled within the EU or in countries with equivalent data protection. This is why more and more organizations are choosing to repatriate data to European and Swedish soil.It is not enough for the supplier to be established in Europe if the data processing takes place on servers outside the EEA, or if the parent company is subject to legislation that can give non-European authorities access to your data, such as the CLOUD Act in the USA.

The NIS2 Directive also tightens the requirements for the security of critical IT systems. Municipalities and regions covered by the Directive need to be able to document that their suppliers meet the security requirements and that incident reporting can be done within the timeframes required by the Directive.

The Swedish government cloud policy further reinforces the picture.

What makes a European platform different in practice?

It’s easy to say “we are GDPR compliant.” Most providers do. The question is what that actually means.

A European platform with true data governance means that:

  • All data is stored on servers within the EU – with no exceptions for backup, logging or support
  • The supplier and its subcontractors are subject to European law – not to legislation that can force data access from outside
  • The Data Processing Agreement (DPA) is substantive – an agreement that actually defines what can and cannot be done with your data
  • The exit strategy is clear – you can extract your data in a readable format and exit without being stuck in the supplier's own format

It's not always obvious how to find out, so asking the right questions is more important than marketing's answers.

Questions you should ask every supplier

Use this list as part of your requirements specification or as a basis for supplier dialogue. A reputable supplier will respond without hesitation.

About data location and storage

  • Where is all the data stored – including backups, logs and support cases?
  • Which sub-contractors (sub-processors) are used and where are they established?
  • Do you have servers or data processing outside the EU/EEA? If so – why and under what circumstances?

About law and legislation

  • Under which nation's laws does the parent company operate?
  • Can non-European authorities request access to our data? How is this handled in such cases?
  • Can you provide a full Data Processing Agreement (DPA) in accordance with Art. 28 GDPR?

About NIS2 and security

  • How does your platform support our NIS2 incident reporting?
  • Do you have SOC 2 Type II, ISO 27001 or equivalent certification? Can you show a current certificate?
  • How are we notified of a security incident affecting our data, and within what time frame?

About supplier dependency and exit

  • In what format can we export all our data if we terminate the agreement?
  • How long does a complete data export take?
  • What happens to our data after the end of the contract, and how long is it stored?

About configuration and autonomy

  • Can we configure and customize the system without being dependent on your support?
  • What does it require of us in terms of internal competence?
  • What does the pricing model look like for customizations and expansion of the system?

Why autonomy is part of data security

One aspect that is rarely discussed in connection with data protection is supplier dependency as a risk factor.

If your service management platform requires you to contact the vendor for every customization – new fields, new workflows, new processes – it creates a dependency that affects your freedom of action. This is not only about time and cost, but also security: if the vendor has ongoing access to your configuration and processes, your data and authorization risks are amplified.

A platform that lets your internal team configure and manage the system reduces that exposure. You are in control – technically, legally, and operationally.

What Easit GO means in this context

Easit AB is a Swedish company and Easit GO is operated on servers in Sweden. Data does not leave the country. This allows you to fully digitize sensitive processes, such as social services' visitation cases. We are subject to Swedish and European legislation without exception.

Easit GO is also built for internal management. Your organization configures, adapts and expands the system without being dependent on us for every change. It is a conscious design, not a feature but a basic assumption.

We would be happy to discuss what this means for your specific situation, your specific requirements and your NIS2 obligations.

Contact us for a supplier dialogue

READ MORE

How the platform thinking works in Easit GO and what you can actually build
How Easit GO works as a configurable service management platform that your organization owns and manages internally.

Five signs that your CMDB data is starting to degrade
Configuration management is a central part of NIS2 readiness. Read about how to keep your CMDB up to date.

What is a CMDB and why do you need one?
An introduction to configuration management and why it matters for security and continuity.

Designer Days
Practical training for those who configure and manage Easit GO in your organization.

Fully digitize sensitive processes

Repatriate data to European and Swedish soil

Henrik Traveler

Commercial Product Manager
henrik.resare@easit.com
+46 70 249 36 06

Scroll to the top