- Enforcing jurisdiction
- Slovenia · Geography does not establish applicable law.
- Confirmed applicable legislation
- Privacy topics
DPA case 0612-23/2019/19 – Order (Slovenia, 2022)
Privacy enforcement record
This record is classified outside cookie consent. Subject classification does not confirm an applicable law. It is not included in cookie statistics or the Risk Calculator.
A Slovenian data protection authority investigated a cloud computing provider and found it was acting as a data controller, not just a processor. This means it has more responsibilities for data protection. Companies must understand their roles in data handling.
What happened
The cloud computing provider was determined to be acting as a data controller due to its influence over data processing.
Who was affected
Clients of the cloud computing provider who were using its services to handle data.
What the authority found
The authority concluded that the cloud computing provider was responsible for compliance with data protection rules as it had control over data processing.
Why this matters
This ruling clarifies the responsibilities of companies in data handling. Businesses should clearly define their roles and ensure compliance with data protection regulations.
View original scraped data
Original imported citations before automated processing; the processing history does not establish independent verification.
Source checks
Secondary-source text retrieved.
Automated check recorded — 18 October 2026.
No issues were reported by that automated check.
Retrieved text may be a secondary summary or an announcement. These automated statuses do not establish that the original decision was read or that the record received an independent legal review. How we check sources
The Slovenian DPA initiated an ex oficio investigation of a cloud computing provider. The company acted as an intermediary between clients generating data queries and various different data sources supplying the data itself. It claimed that the clients requesting data were the controllers and that it was merely processing the data on behalf of those clients/controllers. Through its investigation, the Slovenian DPA determined that the basic idea underlying the controller's cloud computing business model was handling of complex technical specifics so as to simplify the technical aspects for its clients, allowing them focus entirely on the content of the data requested. The cloud computing clients, in view of this arrangement, had little to no influence on the technical and organizational measures employed by the cloud computing provider in the handling of data. The DPA emphasised that an entity's status as controller or processor must be a factual determination, not merely a formal designation; if the designated "processor" in fact has some say in the essential purposes and means of processing, it is actually a controller. Article 24 GDPR and Article 5(2) GDPR establish the principle of responsibility, which means that the controller is responsible for compliance with the GDPR. A corollary of this principle is that if an arrangement between two entities makes both responsible for compliance with data protection regulations, both are controllers. In this case, because the cloud computing provider's clients had no power to ensure technical compliance with the GDPR, the cloud computing provider was acting as controller insofar as it determined the technical processes by which data was requested, handled, and transmitted as well as what sub-processors were engaged. As the cloud computing provider and its clients both made determinations of the purposes and means of processing, their arrangement was one of joint controllership. The DPA held that (i) the cloud computi
Outcome
Order
A binding order requiring the controller to take specific action.
Related Enforcement Actions (0)
No other enforcement actions found for DPA case 0612-23/2019/19 in SI
This is the only recorded action for this entity in this jurisdiction.
Details
About this data
Cite as: Cookie Fines. DPA case 0612-23/2019/19 - Slovenia (2022). Retrieved from cookiefines.eu
Last updated: