https://oliseus.com/tags/privdev/Recent content in PrivDev on Oliseus BlogHugo -- gohugo.ioensimon.bernbeck@gmail.com (Simon Bernbeck)simon.bernbeck@gmail.com (Simon Bernbeck)© 2024 Simon Bernbeck. All rights reserved.Mon, 05 Oct 2026 00:00:00 +0000https://oliseus.com/digital-odyssey/posts/privdev-cryptography-and-context/Mon, 05 Oct 2026 00:00:00 +0000simon.bernbeck@gmail.com (Simon Bernbeck)https://oliseus.com/digital-odyssey/posts/privdev-cryptography-and-context/<p>Cryptography often appears in privacy discussions as a single checkbox: encrypted or not encrypted. Software findings are rarely that complete. A scanner can identify a suspicious storage path or a call to an unsafe primitive, but it does not automatically know what data is involved, who can read it, which controls exist outside the analysed code, or whether the data needed to be stored in the first place.</p> <p>That gap is a useful case for <a href="../privdev-privacy-research-introduction/">PrivDev</a>, my research on connecting technical findings to privacy concepts. The project&rsquo;s implemented first layer maps scanner data-type labels to a common vocabulary. A later research question asks how findings about software weaknesses could support developer guidance without turning a technical clue into a legal verdict. Cryptography exposes why this distinction matters.</p>