<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DataParade — Shifting privacy and security left</title><link>https://dataparade.io/</link><description>Articles from DataParade on preventing privacy and security problems through solid architecture and a real understanding of the system.</description><language>en</language><lastBuildDate>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://dataparade.io/posts/feed.xml" rel="self" type="application/rss+xml"/><item><title>A Name Isn't an Identity</title><link>https://dataparade.io/posts/a-name-isnt-an-identity/</link><guid isPermaLink="true">https://dataparade.io/posts/a-name-isnt-an-identity/</guid><description>A code scanner finds a hundred places where something called email appears. How many data items is that? Joining on the name alone dropped our grouping precision from 86% to 51%. The fix was to stop trusting names and join only on evidence the parser can show you.</description><pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate><category>Scanner</category><category>Code Analysis</category><category>Precision</category><category>Parser</category></item><item><title>A Decision Model That Walks the Parse Tree</title><link>https://dataparade.io/posts/a-decision-model-that-walks-the-parse-tree/</link><guid isPermaLink="true">https://dataparade.io/posts/a-decision-model-that-walks-the-parse-tree/</guid><description>Sorting data item mentions into data items is an agent task: look at a candidate group, read around it, decide. A frontier coding model does it well and costs too much to run on every scan. We built the same loop around Jev, gave it parse-tree tools instead of a file viewer, and it landed above the…</description><pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate><category>Jev</category><category>Decision Models</category><category>Parse Tree</category><category>Cost Optimization</category></item><item><title>Your Coding Agent Already Knows Where the Password Went</title><link>https://dataparade.io/posts/your-coding-agent-already-knows-where-the-password-went/</link><guid isPermaLink="true">https://dataparade.io/posts/your-coding-agent-already-knows-where-the-password-went/</guid><description>Every decision about how a system handles personal data now gets made in a conversation with a coding agent, and the transcript is sitting on disk. We wrote a tool that reads those transcripts. The next step is an interviewer that forms a hypothesis from them and asks you to confirm it, instead of…</description><pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate><category>BotSpy</category><category>Coding Agents</category><category>Session Traces</category><category>Shift Left</category></item><item><title>We Labeled Six Repos with a Thousand Sub-Agents</title><link>https://dataparade.io/posts/we-labeled-six-repos-with-a-thousand-sub-agents/</link><guid isPermaLink="true">https://dataparade.io/posts/we-labeled-six-repos-with-a-thousand-sub-agents/</guid><description>You cannot improve a scanner you cannot score, and nobody had labeled where the personal data lives in a real codebase. So we had three sizes of model label it, argue about it, and let the biggest one arbitrate. The labels are not perfect. They are a compass needle, and the first thing they found w…</description><pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate><category>Evaluation</category><category>Sub-Agents</category><category>Ground Truth</category><category>LLM Evals</category></item><item><title>The Diagram Is a Projection</title><link>https://dataparade.io/posts/the-diagram-is-a-projection/</link><guid isPermaLink="true">https://dataparade.io/posts/the-diagram-is-a-projection/</guid><description>A dataflow diagram is not the output of a scan. It is a query over a knowledge base, and the gaps in that knowledge base tell you exactly which questions to ask a person. We built an interviewer on that idea. It drew its first system-context diagram after one question. It also makes dumb decisions,…</description><pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate><category>OCSF</category><category>Knowledge Base</category><category>C4 Model</category><category>Interview Engine</category></item></channel></rss>
