{"id":2979,"date":"2026-10-26T10:38:04","date_gmt":"2026-10-26T09:38:04","guid":{"rendered":"https:\/\/blog.eprivacy.eu\/?p=2979"},"modified":"2026-10-26T10:38:04","modified_gmt":"2026-10-26T09:38:04","slug":"we-didnt-want-the-data-court-decision-on-sensitive-data-in-ai-chatbots","status":"publish","type":"post","link":"https:\/\/blog.eprivacy.eu\/?p=2979","title":{"rendered":"\u201cWe didn\u2019t want the data\u201d \u2013 Court decision on sensitive data in AI chatbots"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Anyone deploying an AI chatbot must expect users to enter health data, religious beliefs or details about their sex life. A judgement by the Cologne Regional Court dated 17 September 2026 (Case No. 33 O 120\/24, not yet final) in the legal dispute against Snapchat highlights the data protection risks: simply asking users not to enter sensitive data is not sufficient to prevent unlawful processing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The problem: sensitive data despite a lack of intent<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Snapchat\u2019s AI chatbot \u2018My AI\u2019 is also aimed at young people aged 13 and over and invites them to ask \u2018all sorts of questions\u2019. The Federation of German Consumer Organisations took legal action against this because the service processed special categories of personal data without explicit consent in accordance with Article 9 of the GDPR.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Regional Court of Cologne upheld the claim. According to the court\u2019s assessment, with a chatbot that invites free-form input, it is to be expected that users will also disclose sensitive information. The fact that the provider did not specifically intend to collect this data, but that it is entered as part of the service\u2019s use, does not automatically exonerate it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Legal classification: Article 9 of the GDPR as the key hurdle<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Article 9 of the GDPR generally prohibits the processing of special categories of personal data. These include, amongst other things, health data, information on religious or philosophical beliefs, and data relating to sexual life and sexual orientation. Processing is only permitted if an exemption under Article 9(2) of the GDPR applies.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A legitimate interest under Article 6(1)(f) of the GDPR is not sufficient on its own. Both provisions must be considered together: in addition to a legal basis under Article 6 of the GDPR, a relevant exemption to the prohibition in Article 9(1) of the GDPR is generally also required. For many commercial chatbot applications, explicit consent under Article 9(2)(a) of the GDPR is particularly relevant. However, whether this is required or whether another exemption applies depends on the specific processing operation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Added to this is the broad interpretation of Article 9 of the GDPR by the ECJ, including in the Lindenapotheke case. Information from which sensitive characteristics can be indirectly inferred may also fall within the scope of the provision. This is particularly relevant for AI applications: even seemingly harmless inputs can allow conclusions to be drawn about a person\u2019s state of health, religious beliefs or sexual orientation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The way consent is structured is also crucial. A mere \u2018OK\u2019 button or pre-ticked checkboxes do not, in themselves, constitute valid explicit consent. Consent must be given voluntarily, in an informed manner, specifically, and through a clear, active action.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What deployers of AI chatbots should bear in mind<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Take unsolicited input into account<\/strong>: Bear in mind that users may disclose sensitive information even when this is not explicitly requested.<\/li>\n\n\n\n<li><strong>Review technical safeguards:<\/strong>\u00a0Investigate whether sensitive content can be detected as soon as it is entered, excluded from further processing or, where possible, handled in a manner that promotes data minimisation.<\/li>\n\n\n\n<li><strong>Do not rely solely on warning messages:\u00a0<\/strong>The message \u2018Please do not enter any sensitive data\u2019 is no substitute for a sound legal basis or appropriate technical and organisational measures.<\/li>\n\n\n\n<li><strong>Document the legal basis and exemptions:<\/strong>\u00a0For each relevant processing operation, check which legal basis under Article 6 of the GDPR and which exemption under Article 9(2) of the GDPR applies.<\/li>\n\n\n\n<li><strong>Monitor chat histories and data flows:\u00a0<\/strong>Scrutinise retention periods, access rights, transfers to external model providers, and any potential use for advertising, analysis or model training.<\/li>\n\n\n\n<li><strong>Check for a data protection impact assessment:\u00a0<\/strong>Clarify whether a DPIA under Article 35 of the GDPR is required, particularly when processing sensitive data.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Conclusion<\/strong><br>From a data protection perspective, it is not merely a question of what data a provider specifically wishes to collect, but also of what processing their service actually enables and gives rise to expectations of. Deployers of AI chatbots should therefore begin by addressing the design of the input function, the technical processing and storage.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Anyone deploying an AI chatbot must expect users to enter health data, religious beliefs or details about their sex life. A judgement<\/p>\n<p class=\"link-more\"><a class=\"myButt \" href=\"https:\/\/blog.eprivacy.eu\/?p=2979\">Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2979","post","type-post","status-publish","format-standard","hentry","category-eprivacy-news-en"],"_links":{"self":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/2979","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2979"}],"version-history":[{"count":1,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/2979\/revisions"}],"predecessor-version":[{"id":2980,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/2979\/revisions\/2980"}],"wp:attachment":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2979"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2979"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2979"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}