Norway';s data protection landscape shifted noticeably in the final quarter, with the Norwegian Data Protection Authority - Datatilsynet - issuing several enforcement decisions, clarifying its position on AI-driven processing, and signalling tighter scrutiny of cross-border data transfers. For international businesses operating in Norway or directing services at Norwegian residents, the quarter brought both new obligations and useful regulatory guidance. This guide covers the key legal developments, enforcement highlights, practical compliance implications, and what organisations should prioritise going into the next period.
Why norway data protection 2025 matters for international operators
Norway is not a European Union member state, but it is a full participant in the European Economic Area. This means the General Data Protection Regulation applies in Norway through the EEA Agreement, incorporated into Norwegian law via the Personal Data Act (Personopplysningsloven). Datatilsynet enforces GDPR obligations with the same authority as any EU supervisory authority, and its decisions carry real financial and reputational consequences.
For international businesses, Norway';s EEA membership creates a nuanced compliance environment. A company established in Germany or Ireland may assume its lead supervisory authority handles all GDPR matters. In practice, Datatilsynet retains jurisdiction over local establishments and can investigate complaints from Norwegian data subjects independently. Many foreign operators underestimate this dual-track exposure.
The quarter also saw Norway';s participation in the European Data Protection Board';s coordinated enforcement framework become more visible. Datatilsynet contributed to joint investigations and adopted positions consistent with EDPB guidelines, meaning developments at the European level translated quickly into Norwegian enforcement priorities.
Key regulatory decisions and enforcement actions from Datatilsynet
Datatilsynet issued a series of decisions and preliminary findings during the quarter that illustrate its current enforcement priorities. Several of these targeted organisations that had failed to conduct adequate Data Protection Impact Assessments before deploying new processing systems, particularly those involving automated decision-making or large-scale profiling of individuals.
One significant decision concerned a Norwegian public sector body that had implemented a workforce monitoring system without a lawful basis under GDPR Article 6 and without notifying employees in accordance with Article 13. Datatilsynet found that the organisation had relied on a vague legitimate interest assessment that did not adequately weigh employee privacy rights. The authority ordered the processing to cease and required the organisation to revise its internal policies within a defined period.
A separate enforcement action targeted a private sector operator in the financial services space. The investigation found that the company had transferred personal data to a third-country processor without implementing appropriate safeguards under GDPR Chapter V. Specifically, the standard contractual clauses in use had not been updated to the current European Commission versions, and no transfer impact assessment had been completed. Datatilsynet issued a formal reprimand and set a compliance deadline.
In practice, founders and compliance officers should note that Datatilsynet is increasingly focused on documentation quality, not just outcomes. An organisation may have implemented reasonable technical measures but still face enforcement if it cannot demonstrate that a structured assessment process was followed. The authority has made clear that accountability under GDPR Article 5(2) requires contemporaneous records, not retrospective justifications.
AI and automated processing: Datatilsynet';s updated guidance
Artificial intelligence and automated decision-making attracted sustained regulatory attention during the quarter. Datatilsynet published updated guidance on the use of AI tools in employment contexts, building on earlier positions and reflecting the EDPB';s opinion on AI model training published earlier in the year.
The guidance addresses several practical scenarios. Where an employer uses an AI system to screen job applications, rank candidates, or assess employee performance, Datatilsynet';s position is that this constitutes automated decision-making within the meaning of GDPR Article 22 if the output has a significant effect on the individual. In such cases, the employer must identify a lawful basis, provide meaningful information to data subjects, and - where the decision is solely automated - offer the right to human review.
A common mistake among technology companies entering the Norwegian market is to treat AI-assisted processes as falling outside Article 22 simply because a human formally approves the final output. Datatilsynet has indicated that rubber-stamp human involvement does not satisfy the requirement for meaningful human review. The human reviewer must have genuine authority and sufficient information to override the automated recommendation.
The guidance also addresses AI model training using personal data. Organisations that scrape publicly available data from Norwegian websites or social media platforms to train models must assess whether that data constitutes personal data and, if so, identify a lawful basis for the processing. Legitimate interest under Article 6(1)(f) is not automatically available and requires a documented balancing test. Many underestimate the complexity of this assessment when data subjects are identifiable from the training dataset.
If your organisation is deploying AI tools that process personal data of Norwegian residents, a structured legal review is advisable before go-live. We can help structure the setup correctly the first time - contact info@vlolawfirm.com for a consultation.
Cross-border data transfers: current requirements and practical risks
Cross-border data transfers remained a high-priority area for Datatilsynet during the quarter. Norway';s position within the EEA means that transfers to EU member states are unrestricted, but transfers to third countries - including the United States, the United Kingdom post-Brexit arrangements, and others - require a valid transfer mechanism under GDPR Chapter V.
The standard contractual clauses issued by the European Commission remain the most widely used transfer tool for Norwegian organisations. However, Datatilsynet has emphasised that executing SCCs is not sufficient on its own. Organisations must complete a transfer impact assessment to determine whether the legal framework of the destination country provides essentially equivalent protection to that guaranteed under EEA law. Where gaps are identified, supplementary technical or contractual measures must be implemented.
A non-obvious requirement that surfaces frequently in practice is the obligation to reassess existing transfer arrangements when there is a material change in the legal environment of the destination country. This includes changes to surveillance laws, new court decisions affecting data access, or changes in the processor';s corporate structure. Many organisations complete a TIA at the time of contract signature and then treat it as a permanent document. Datatilsynet';s current position is that TIAs should be reviewed periodically and whenever a triggering event occurs.
For organisations relying on adequacy decisions - for example, transfers to countries the European Commission has recognised as providing adequate protection - the position is more straightforward, but organisations should monitor whether those decisions remain in force. Adequacy decisions can be challenged or withdrawn, and organisations that have built transfer arrangements around them should have contingency mechanisms in place.
Practical scenario one: a Norwegian e-commerce company uses a US-based customer relationship management platform. The company has signed SCCs with the platform provider but has not completed a TIA and has not reviewed the arrangement since the SCCs were updated. Under current Datatilsynet guidance, this arrangement is non-compliant and exposes the company to enforcement risk.
Practical scenario two: a multinational with a Norwegian subsidiary uses a centralised HR system hosted in a country outside the EEA. The subsidiary has assumed that the parent company';s group-level data processing agreement covers the Norwegian operation. In practice, the Norwegian subsidiary is itself a controller under the Personal Data Act and must ensure that its own transfer arrangements are documented and lawful.
Data subject rights: handling requests and managing timelines
GDPR grants data subjects a range of rights - access, rectification, erasure, restriction, portability, and objection - and organisations operating in Norway must have processes in place to handle these requests within the statutory timeframes. The standard response deadline is one calendar month from receipt of the request, extendable by a further two months in complex cases, provided the data subject is informed of the extension within the first month.
Datatilsynet received a notable volume of complaints during the quarter relating to organisations that had failed to respond to access requests within the required period, or that had provided incomplete responses. A common pattern involves organisations that acknowledge receipt of a request but then fail to follow through, either because internal processes are unclear or because the request is routed to a team that lacks the authority or information to respond fully.
A practical tip for organisations with a Norwegian customer base: designate a specific individual or team responsible for data subject requests, document the intake and response process, and set internal deadlines that allow buffer time before the statutory deadline expires. Where a request is complex - for example, involving data held across multiple systems or third-party processors - begin the process immediately rather than waiting until the deadline approaches.
The right to erasure under GDPR Article 17 generates particular complexity. Organisations frequently receive erasure requests from former customers or employees and must assess whether any of the exceptions in Article 17(3) apply - for example, where retention is required for compliance with a legal obligation or for the establishment, exercise, or defence of legal claims. Datatilsynet has indicated that organisations must document their reasoning when declining an erasure request, not simply inform the data subject that the request has been refused.
Sector-specific developments: health, finance, and the public sector
Several sector-specific developments during the quarter are relevant to organisations operating in regulated industries in Norway.
In the health sector, Datatilsynet continued its focus on the processing of special category data under GDPR Article 9. Health data is subject to heightened protection, and organisations - including private clinics, health technology companies, and insurers - must identify an explicit condition under Article 9(2) in addition to a lawful basis under Article 6. The authority has noted that consent under Article 9(2)(a) must be explicit and freely given, and that consent obtained as a condition of service is unlikely to meet this standard.
In the financial services sector, the intersection of data protection and anti-money laundering obligations continued to generate compliance complexity. Norwegian financial institutions are required to collect and retain customer identification data under AML legislation, but must also comply with GDPR when processing that data. Datatilsynet has acknowledged this tension and has indicated that processing for AML compliance purposes can rely on Article 6(1)(c) - compliance with a legal obligation - but that the data must not be used for other purposes without a separate lawful basis.
In the public sector, the quarter saw continued scrutiny of municipalities and government agencies that use cloud services provided by non-EEA companies. Datatilsynet has previously issued guidance indicating that public bodies should exercise particular caution when selecting cloud providers, given the sensitivity of the data they process and the potential for third-country government access. Several municipalities received requests for information about their cloud arrangements during the quarter.
FAQ
What are the most significant compliance risks for foreign companies with Norwegian customers?
The most common risks involve cross-border data transfers, inadequate privacy notices, and failure to respond to data subject requests on time. Foreign companies that direct services at Norwegian residents are subject to GDPR as applied in Norway, regardless of where the company is established. Datatilsynet can investigate complaints from Norwegian data subjects and, in appropriate cases, refer matters to the company';s lead supervisory authority in the EU. Organisations that have not reviewed their transfer mechanisms, updated their privacy notices to reflect current processing activities, or established a clear process for handling data subject requests are particularly exposed. A structured compliance review is the most effective way to identify and address these gaps before an enforcement action begins.
How long does a Datatilsynet investigation typically take, and what are the potential consequences?
The duration of a Datatilsynet investigation varies considerably depending on the complexity of the matter and whether the organisation cooperates promptly. Straightforward complaint-based investigations may be resolved within a few months, while complex cross-border cases or systemic investigations can extend significantly longer. Consequences range from informal guidance and recommendations at the lower end, through formal reprimands and orders to bring processing into compliance, to administrative fines. Under GDPR, fines can reach up to four percent of total worldwide annual turnover or a fixed maximum, whichever is higher, for the most serious infringements. In practice, Datatilsynet has shown willingness to take into account the organisation';s cooperation, the steps taken to remediate the issue, and whether the breach was deliberate or negligent.
Should Norwegian subsidiaries of multinational groups maintain separate data protection documentation, or can they rely on group-level policies?
Norwegian subsidiaries should maintain their own documentation, even where the group has comprehensive data protection policies in place. The Norwegian subsidiary is typically an independent controller under the Personal Data Act and is responsible for its own compliance. Group-level policies can provide a useful framework, but they must be adapted to reflect the specific processing activities of the Norwegian entity, the applicable legal bases under Norwegian and EEA law, and any sector-specific requirements. A common mistake is for subsidiaries to adopt group policies without reviewing whether they accurately describe local processing activities or whether the transfer mechanisms referenced are appropriate for the Norwegian context. Datatilsynet will assess the subsidiary';s compliance independently and will expect to see documentation that reflects the actual situation of the Norwegian entity.
Conclusion
The final quarter brought meaningful regulatory activity in Norway, with Datatilsynet reinforcing its focus on accountability, AI governance, and cross-border transfer compliance. Organisations operating in Norway - whether locally established or serving Norwegian residents from abroad - should treat these developments as a prompt to review their current arrangements rather than wait for a complaint or investigation to trigger action.
VLO Law Firms advises international clients on data protection matters in Norway. We can assist with GDPR compliance reviews, transfer impact assessments, data subject rights processes, AI governance frameworks, and regulatory correspondence with Datatilsynet. To request a consultation, contact: info@vlolawfirm.com