Does GDPR require data to be stored in the EU? Residency, transfers and the DPA
No. GDPR sets no storage location; it regulates transfers outside the EU. How NUADU handles residency, sub-processors, the DPA and what SOC 2-aligned means.
Does GDPR require data to be stored in the EU? No. The regulation sets no storage location; it sets conditions for transferring personal data to countries outside the EU. Tenders still ask for EU residency, and NUADU's answer is short: EU data residency is the default, other regions on request. What follows is the legal answer, the posture in the words of NUADU's Trust page, and a literal reading of three labels that are easy to over-read — so a compliance lead can put the right line in the right box.
Does GDPR require data to be stored in the EU?
No. The GDPR governs how personal data is processed and when it may leave, not where a server has to stand. The rules that come closest to location are in Chapter V of the GDPR, Articles 44 to 49, and they are rules about transfers: personal data may go to a third country or an international organisation only if the conditions of that chapter are met.
So a tender that asks for EU residency is making a choice the regulation leaves open. It is a reasonable choice. Data that stays in the EU keeps the transfer question narrow, and the questions that remain — who else processes the data, under which contract, for how long — have documented answers a vendor can hand over.
The two ideas are often blurred on vendor pages, and it is worth keeping them apart. Residency is a fact about location. Compliance is a property of the whole processing operation: lawful basis, purpose, retention, contracts, transfers. A vendor can host in the EU and still owe you every other answer.
EU data residency is the default; other regions on request.
Where does NUADU host the data?
On Microsoft Azure, in the region each customer requires. EU data residency is the default: the main application instance runs in the EU. The regions in use include West Europe, North Europe, Sweden Central, Poland Central and France Central, and other regions are available on request, wherever Azure offers a cloud region. Another region is a request, not a menu.
The rest of the posture is stated just as plainly on the Trust & compliance page, which covers data residency, the DPA and sub-processors for procurement and tender review:
- Security: SOC 2-aligned security controls. Data is encrypted in transit and at rest, access is protected by multi-factor authentication and role-based access control, and disaster recovery is built in.
- Retention: configurable per tenant, in the words of the home page, and per data category, in the words of the Trust page. The period is a setting for your tenant.
- Data flows: documented for institutional and regulator review.
Those are the lines a tender form asks for, and each one is stated in writing on NUADU's pages rather than on a slide.
Who else processes the data, and under which contract?
The sub-processors named on the Trust page, under a DPA that NUADU signs with every customer. The page lists each sub-processor with its role:
- Microsoft Azure — hosting, backup, AI services (Azure AI Foundry, AI Search, Document Intelligence, Vision) and Power BI reporting
- Constructor — exam proctoring
- UserWay — accessibility
- Google Tag Manager — website tags
- Crisp — support chat
- Amplitude — product analytics
The list is also provided with the DPA and updated on change. The roles are the page's own; nothing here adds to them.
The contract side takes two sentences on the Trust page, and they are the useful ones: NUADU signs a DPA with every customer, and a request through the contact form returns a signable copy rather than a questionnaire. The GDPR expects processing by a processor to rest on a binding contract (Article 28(3)), and the DPA is that contract. Read it with counsel.
Exam recording raises GDPR questions of its own, taken up in online proctoring under GDPR. For the rest of the file — methodology, per-module AI notes, the DPIA template — an AI vendor due diligence checklist maps each document to the person who reads it.
Is SOC 2-aligned a certification?
No, and the Trust page says so in as many words: SOC 2-aligned describes the controls; it is not a certification claim. The footer carries one badge, GDPR · FERPA · SOC 2-aligned, and each of its three labels reads best literally.
- GDPR-ready. The home page's phrase. The Trust page adds that local data-protection requirements are met per deployment. It describes a posture — residency, retention, sub-processors and data flows, documented — and no certification is claimed.
- FERPA. The home page says aligned with FERPA expectations; the Trust page says the FERPA posture is documented. Neither is a compliance certificate.
- SOC 2-aligned. A description of the security controls listed above. It is not a SOC 2 report, and none is claimed.
The enterprise page adds a fourth label, EU AI Act-ready. It names a set of controls that can be inspected, not a badge, and what the EU AI Act asks of high-risk AI in education is a question of its own.
A reviewer who needs a certificate should read the labels as written and ask for the documents instead. The documents are what a tender can actually evaluate.
Frequently asked questions
Under GDPR, can personal data be stored outside the EU?
Yes, where the transfer meets Chapter V. The main routes are an adequacy decision by the European Commission for the destination (Article 45), appropriate safeguards such as standard data protection clauses adopted by the Commission (Article 46), binding corporate rules within a group (Article 47) and, for specific situations, the derogations in Article 49. NUADU's default keeps the main application instance in the EU; other regions are available on request.
What is EU data residency?
EU data residency is a commitment about location: the data is hosted in data centres inside the EU. It answers where the data is stored. It does not, on its own, answer who processes it, under which contract or for how long; those answers sit in the DPA, the sub-processor list and the retention settings.
What is the difference between data sovereignty and data residency?
Data residency is where data is stored. Data sovereignty is the question of which country's law governs it. The two often travel together, but they are not the same thing. NUADU's certification page uses data sovereignty as the heading for its residency posture — EU residency by default, documented sub-processors, configurable retention, documented data flows — and that list is the whole of the claim.