Compliance

Data residency, explained for growing teams

“Where is my data?” is usually the third question in a sales call. It should be the first. Not because every team has a regulator breathing down its neck, but because the answer is more complicated than the location of a server.

Residency is more than a postcode

A provider can store your primary database in London and still send backups to another continent, route support queries through an offshore helpdesk, or keep metadata in a jurisdiction you did not think about. If your contract only names the data centre, you have checked one box out of several.

The useful question is not “where is the server?” but “where does every copy of the data live, who can reach it, and for how long?” That includes primary storage, snapshots, backups, logs, support attachments and the metadata that describes all of it.

Where our data lives

Customers choose London or Frankfurt when they order. Primary storage, snapshots and backups stay in that region unless replication is explicitly enabled. Account and billing metadata is held in the UK, because that is where the company and its finance team are.

Support access is limited to staff in the UK, Netherlands and Germany. We do not have an offshore first line, and we do not grant support staff standing access to customer data; access is requested per incident and logged. Website logs are kept for 30 days; security and authentication logs for 12 months.

The subprocessor question

We use data centre operators, a payment processor and professional advisers. All are covered by written terms, and we will provide the current list to any customer or prospective customer on request. We do not publish a logo wall because the list is short and changes rarely.

We do not sell personal data. We do not use customer data to train models, and we do not allow our suppliers to use it for anything beyond delivering the service.

Five questions worth asking any provider

  1. Where are the primary and backup copies stored, and can either be moved without my involvement?
  2. Who can access the data, from which countries, and is that access logged?
  3. What happens to my data if I leave, and what happens if the provider is acquired or stops trading?
  4. Which subprocessors touch the data, and how often is the list reviewed?
  5. How is deletion verified, and can I get that in writing?

If a provider cannot answer those in a paragraph each, that is an answer too. “It's complicated” is usually accurate, but it should not be the end of the conversation.

Our answer

We will put the location of primary storage, backups and metadata in writing in your order form. We offer a 30-day export window after termination, followed by deletion under our retention schedule. Business customers can audit the relevant controls once a year with 30 days' notice, under the confidentiality terms in our terms.

If your regulator needs a specific answer in a specific format, email legal@atlantika-company.uk. We have done this before, and we would rather help you complete the form than watch you guess.

← All notes Written by Elena Marsh, Managing Director