Transforming Privacy Artifacts into Accessible Reports for Non-Technical Stakeholders
Zoe Pfister, Clemens Sauerwein, Benedikt Dornauer, Tina Mersch, Christian Wolf, Ruth Breu, Michael Vierhauser

TL;DR
This paper presents a framework that uses Large Language Models to convert technical privacy artifacts into accessible reports, aiding non-technical stakeholders in understanding privacy implications in Industry 5.0 systems.
Contribution
It introduces a novel conceptual framework leveraging LLMs to make privacy threats and mitigations understandable for non-technical stakeholders in industrial systems.
Findings
Initial insights from two industry use cases demonstrate the framework's applicability.
Evaluation shows the generated reports are understandable and informative for non-technical stakeholders.
The approach supports early stakeholder involvement and transparency in privacy management.
Abstract
The transition toward Industry 5.0 is reshaping industrial work environments with an emphasis on human-centricity, enabling close collaboration between humans and machines to enhance productivity and flexibility. However, such systems typically require monitoring of human workers and operators, often involving sensitive data, raising significant privacy concerns. As a result, affected workers and unions frequently reject human-machine collaboration features due to a lack of transparency regarding privacy threats and implemented mitigation strategies. To enable early stakeholder involvement, establish trust, and support informed decision-making, privacy implications must be communicated in a way understandable to non-technical stakeholders. Yet, current Requirements Engineering (RE) practices provide limited methodological support for making privacy threats and mitigations accessible to…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
