Started by GitHub push by younex162264c156533706f135d03479119c61e6af91fa0d2264c156533706f135d03479119c61e6af91fa0drefs/remotes/origin/main2264c156533706f135d03479119c61e6af91fa0d2264c156533706f135d03479119c61e6af91fa0drefs/remotes/origin/main2264c156533706f135d03479119c61e6af91fa0d2264c156533706f135d03479119c61e6af91fa0drefs/remotes/origin/mainhttps://github.com/younex1/blut24-landing.gitfalse#6 2264c152654228038blut24-landing #6 2264c156false65451SUCCESS1785228290744https://jenkins.younex.de/job/blut24-landing/6/app/pages/datenschutz.vue2264c156533706f135d03479119c61e6af91fa0d1785228279000https://jenkins.younex.de/user/infoinfoinfo@logyou.dedatenschutz: name the actual controller, matching the Impressum Both pages must name the same responsible party or they contradict each other, so the Verantwortlicher section now carries the same operator data as the Impressum (Younes Kalakhi, IT Beratung & Dienstleistung, Lahnau) instead of bracketed placeholders. Two judgement calls, both noted in the file: - the e-mail is still a placeholder because it is obfuscated on the source page and could not be read; Art. 13 DSGVO requires a contact route, so it must be filled before this is treated as live - no Datenschutzbeauftragter is claimed - a freelancer of this size is generally not required to appoint one under § 38 BDSG, and asserting one that does not exist would be worse than saying none is appointed Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> 2026-07-28 10:44:39 +02002264c156533706f135d03479119c61e6af91fa0ddatenschutz: name the actual controller, matching the Impressumeditapp/pages/datenschutz.vuegithttps://jenkins.younex.de/user/infoinfofalse7https://jenkins.younex.de/job/blut24-landing/7/5https://jenkins.younex.de/job/blut24-landing/5/