<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hinschg on Whistleblowing Software</title><link>https://whistleblowing-software.pages.dev/tags/hinschg/</link><description>Recent content in Hinschg on Whistleblowing Software</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 04 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://whistleblowing-software.pages.dev/tags/hinschg/index.xml" rel="self" type="application/rss+xml"/><item><title>Mapping HinSchG, Sapin II, and PIDA Onto One Whistleblowing Platform</title><link>https://whistleblowing-software.pages.dev/posts/hinschg-sapin-ii-pida-platform-mapping/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://whistleblowing-software.pages.dev/posts/hinschg-sapin-ii-pida-platform-mapping/</guid><description>&lt;p&gt;A multinational employer operating in Germany, France, and the United Kingdom can run &lt;a href="https://wemoral.com/whistleblowing-software"&gt;secure whistleblowing software&lt;/a&gt; across all three regimes if the admin plane exposes five per-tenant switches: anonymous-acceptance, oral-record format, in-person-meeting SLA, headcount calculation rule, and per-artifact retention period. That five-switch model is the information-gain anchor of this post: each switch is driven by a specific section of HinSchG (Germany, in force 2 July 2023, with the late-2023 anonymous-reporting amendment), by the Sapin II decree of 3 October 2022 in France, or by the structure of PIDA 1998 in the UK. The trap most platforms fall into is treating PIDA as if it mandated a channel; PIDA only protects retaliation, it does not require the employer to operate one.&lt;/p&gt;</description></item></channel></rss>