Data residency

"Where is our data?" is usually the first question from procurement and data protection. The answer is data residency: the place where data is stored and processed. It is a property of architecture and contract, not just a promise.

#More than a storage location

Customer service data comes in many forms: master data, conversation content, recordings, transcripts, logs, backups. Real data residency covers all of them, media and backups included, not only the database.

It also covers processing, not just storage. Where does transcription run, where the language model, where the analytics? Each of these stations belongs in the answer.

#Residency, transfer, access

Remote access from a third country can also count as a transfer. The GDPR requires a legal basis for that, such as an adequacy decision or standard contractual clauses.

Data residency is not the same as data sovereignty. Residency answers the question of where. Sovereignty also asks who controls the data and the keys, and which law applies when it matters.

#Why organisations care

#The right questions

Do not ask only about the region; ask about every station. Where do media and backups live? Where do AI and transcription run? Where does support access come from? Which sub-processors are involved?

#Data residency with Univerx

Univerx is designed for operation in EU regions. You choose the region; the platform is designed so that data and media stay in it. Exceptions for individual services are named in the sub-processor list. Hosting in Germany is planned. That list is available on request.

More in the Trust Center under Data residency & hosting in Germany, on regions & availability and in Data residency: the five questions procurement and privacy ask.