Privacy and compliance

Data residency

Data residency is the country or region where data is physically stored. For website forms it decides which legal rules apply to the submissions you collect.

Also called: data location, EU data hosting, data sovereignty

Every submission is stored somewhere: on a server in a data centre, in a particular country. That location matters because the law of the place applies to the data and, for European visitors, the GDPR limits how personal data may leave the European Economic Area (EEA).

What the GDPR does and does not say

The GDPR does not say that data must stay in the EU. It says that when personal data goes to a country outside the EEA, a lawful transfer mechanism must be in place, such as the EU-U.S. Data Privacy Framework or Standard Contractual Clauses. Keeping the data inside the EEA is the simplest way to avoid that question, which is why many European organisations ask for it.

Residency is not the whole picture

Where the main database sits is only part of it. Files, backups, logs and outgoing email can be somewhere else, and so can some providers: a CDN may handle requests at an edge location near the visitor. A trustworthy provider lists all of this, in its data processing agreement and its sub-processor list.

Questions to ask a provider

  • Where are the database, file storage and backups?
  • Which sub-processors are outside the EEA, and which transfer mechanism covers them?
  • Can I see this in writing before I sign up?

In StaticForm

StaticForm stores customer data inside the EEA: the application and database in Germany, and uploaded files, backups and outgoing email in Sweden. Some providers listed in the DPA are established outside the EEA or run a global network, such as the CDN, and for those the DPA names the transfer mechanism it relies on (the EU-U.S. Data Privacy Framework where available, otherwise Standard Contractual Clauses).

Learn more