Hopp til hovedinnhold

Data residency & compliance

Where does your data go when you use AI?

Most AI vendors send your data to the US. We deliver on Azure Norway East — documents, structured data and the frontier models themselves, all physically in Norway. Below is the full data flow, layer by layer, with sources — not promises.

Last verified 2026-09-06

The data map — where each layer runs

How we deliver client work under a residency guarantee.

Files and documents

🇳🇴 In Norway

Azure Blob Storage · Norway East (Oslo)

Physically in Norway. Encrypted at rest and in transit.

Database and structured records

🇳🇴 In Norway

Azure Database for PostgreSQL · Norway East

All metadata and structured records in the Norwegian region.

AI models (frontier)

🇳🇴 In Norway

Azure AI Foundry · Norway East

Frontier models run inside the Norwegian boundary — the capability without the data leaving the country.

Operations, logging and security

🇳🇴 In Norway

Azure (Norway East) + Microsoft Defender for Cloud

Monitoring and audit trail in the same region.

Alternative hosting (own infrastructure)

🇪🇺 In the EEA

Own server (Hetzner) · Helsinki

For projects without a Norwegian-soil requirement: EEA, on infrastructure we control.

Strict mode (voice, transcription)

🇪🇺 In the EEA

Own STT within the EEA

Raw audio never leaves infrastructure we control.

Full transparency: what leaves the EEA on our side

Our own video receptionist (FULL mode): Video rendering at HeyGen (US, EU-US DPF). On our own site only, never for client data. Offered to clients only in strict EEA mode.

Three tiers of residency

Norwegian soil

Azure Norway East (Oslo)

Every data type and the models themselves region-pinned to Norway. Delivered in production. The strongest guarantee.

EEA standard

Own infrastructure in the EEA

For projects without a Norwegian-soil requirement — on servers we control, not a US cloud platform.

Strict mode

Never leaves our control

Nothing is sent to a third party. For the most sensitive data.

Frontier capability with Norwegian residency, to the letter

We use the latest frontier models for full capability — but run via Azure AI Foundry inside the Norwegian boundary. We structure any data type (documents, tables, email, API data) with AI and deliver it on dashboards you own, with natural-language querying. Frontier-model capability, Norwegian-residency control.

Frequently asked questions

Where is my data stored?

For client delivery: Azure Norway East (Oslo) — files, database, models and operations in the same Norwegian region. For projects without a Norwegian-soil requirement we offer EEA hosting on our own infrastructure.

Can you guarantee data stays in Norway?

Yes, when the delivery runs on Azure Norway East. We have delivered production systems where every data type — documents, structured records and the AI models themselves — is region-pinned to Oslo.

Do you use American AI models?

Frontier models run via Azure AI Foundry inside the Norwegian boundary, so client data does not leave the country. Our own experimental video receptionist uses a US renderer (under the EU-US DPF) — but only on our site, never for client data.

What is "strict mode"?

A delivery mode where nothing leaves infrastructure we control in the EEA — e.g. our own speech-to-text where raw audio is never sent to a third party. For the most sensitive data.

Is this compliant with GDPR and the Norwegian Personal Data Act?

Yes. Norwegian/EEA data residency, a data processing agreement where we handle personal data, and a documented data map like this — we can prove where data goes, not just claim it.

Can you structure and query across any data type?

Yes — documents, tables, email, API data. We structure it with AI and deliver it on dashboards you own, with natural-language querying. Frontier-model capability, Norwegian-residency control.

Information, not legal advice. See also the deadline radar: /frister.