<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Soham Banerjee</title>
    <description>The latest articles on DEV Community by Soham Banerjee (@sohambannerjee8).</description>
    <link>https://dev.to/sohambannerjee8</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4252509%2F14d7a19c-48c4-4e94-9a3b-b0b51f29d738.jpg</url>
      <title>DEV Community: Soham Banerjee</title>
      <link>https://dev.to/sohambannerjee8</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sohambannerjee8"/>
    <language>en</language>
    <item>
      <title>I turned privacy policies into a haunted house with Kiro</title>
      <dc:creator>Soham Banerjee</dc:creator>
      <pubDate>Wed, 18 Nov 2026 19:24:04 +0000</pubDate>
      <link>https://dev.to/sohambannerjee8/i-turned-privacy-policies-into-a-haunted-house-with-kiro-10kn</link>
      <guid>https://dev.to/sohambannerjee8/i-turned-privacy-policies-into-a-haunted-house-with-kiro-10kn</guid>
      <description>&lt;p&gt;&lt;em&gt;I wrote this post for the Kiroween 2026 hackathon (category: Costume Contest).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Like almost everyone, I click "I agree" without reading. Privacy policies and terms are long on purpose, and the clauses that matter most hide in plain sight. So for Kiroween I built &lt;strong&gt;The Haunted Clause&lt;/strong&gt;: paste any Terms &amp;amp; Conditions or privacy policy, and it becomes a haunted house.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Try it:&lt;/strong&gt; &lt;a href="https://the-haunted-clause.vercel.app" rel="noopener noreferrer"&gt;https://the-haunted-clause.vercel.app&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Code:&lt;/strong&gt; &lt;a href="https://github.com/sohambannerjee8/the-haunted-clause" rel="noopener noreferrer"&gt;https://github.com/sohambannerjee8/the-haunted-clause&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;p&gt;The house has eight rooms, one per kind of clause: data selling in The Cellar, tracking in The Watching Portraits, auto-renewal in The Coin Vault, forced arbitration in The Silent Court, and four more. Every risky clause becomes a ghost, and the worse the clause, the scarier the ghost.&lt;/p&gt;

&lt;p&gt;My one design rule was that every spooky element has to carry information. A ghost's size, shape, colour, motion and the numeral on it all show its severity, from a calm wisp (0: checked, looks fine) to a tattered ghost with glowing eyes (3). Colour is never the only signal. Click a ghost and you get the exact clause, a plain-English explanation and why it matters. "Lights on" mode shows the same findings as a plain, accessible list, and the whole house works with a keyboard.&lt;/p&gt;

&lt;p&gt;Above the house sits the Haunt Score. My worst sample company scores &lt;strong&gt;97 · Run&lt;/strong&gt;; the mildest scores 14 · Mostly quiet. (All three sample companies are invented, and the app says plainly that it's not legal advice.)&lt;/p&gt;

&lt;h2&gt;
  
  
  How it reads a policy
&lt;/h2&gt;

&lt;p&gt;The analysis runs entirely in your browser. A splitter breaks the text into clauses, then 48 rules give each risky clause a room and a severity. Reassuring clauses like "We do not sell your data" are lowered to a faint wisp, unless a word like &lt;em&gt;but&lt;/em&gt; or &lt;em&gt;except&lt;/em&gt; follows in the same clause. So "We do not sell your data, but we may share it with advertising partners" stays scary, as it should.&lt;/p&gt;

&lt;p&gt;Nothing you paste is stored, and the app works fully without any API key. If you opt in, only the flagged clauses go to Gemini for a plainer reading.&lt;/p&gt;

&lt;h2&gt;
  
  
  Building it with Kiro
&lt;/h2&gt;

&lt;p&gt;I didn't start by prompting for code. I started with a brief, and Kiro turned it into three &lt;strong&gt;specs&lt;/strong&gt; (clause analyzer, LLM explainer, haunted-house UI), each with requirements, design and tasks. I approved each step before any code was written.&lt;/p&gt;

&lt;p&gt;The design step changed the product. While designing the score, Kiro simulated a realistic long policy and found my planned formula gave it 97, which would make every long policy look terrible. Now each room's worst ghost caps how much that room can add, so a long but mild policy stays low.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Steering files&lt;/strong&gt; kept every session on the same page: the hackathon rules, a design language with colour contrast ratios worked out in advance, and a testing policy (every property test runs 1,000 cases; no test is ever skipped or weakened).&lt;/p&gt;

&lt;p&gt;My favourite part was the &lt;strong&gt;custom agents&lt;/strong&gt;. I set up five verification agents with no write tool, so they could check the work but never change it: a spec reviewer, test verifier, security reviewer, UI and accessibility reviewer, and rules auditor. Every phase ended with a gate they had to pass, and they caught real things. The UI reviewer used the app in a real browser through &lt;strong&gt;Playwright MCP&lt;/strong&gt; and noticed that the reassuring clause "We do not sell your data" was being explained as "This clause lets the company sell what it knows about you." I'd never have spotted that from the tests.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hooks&lt;/strong&gt; ran tests on every save, scanned every saved file for API keys, and kept my build log in step with finished tasks. &lt;strong&gt;Property-based tests&lt;/strong&gt; (36 of them, 1,000 runs each) found a splitter bug no unit test had: a policy starting with a blank line produced a clause made only of whitespace. And &lt;strong&gt;Vercel MCP&lt;/strong&gt; let Kiro create and deploy the live site.&lt;/p&gt;

&lt;h2&gt;
  
  
  What went wrong
&lt;/h2&gt;

&lt;p&gt;Not everything worked first time, and I think the failures taught me the most.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A gate that kept failing.&lt;/strong&gt; The spec reviewer failed my specs three times in a row, each time listing different requirements that had no named test. Patching only what each review mentioned kept missing others. The fix was a traceability matrix of all 236 requirements and a script that fails if any is missing. The fourth review passed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An AI that said too much.&lt;/strong&gt; Gemini's explanations kept adding claims the clause never made, like saying a company "is not responsible" for fees when the clause said nothing of the sort. For an app about reading fine print honestly, that wasn't acceptable. The sample houses use checked rule-based readings, and the AI is an opt-in extra.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Real policies are messier than my samples.&lt;/strong&gt; When I tested against real privacy policies, one room filled up with 35 ghosts (cookies, mostly) and stretched the whole house. Busy rooms now show their 12 worst ghosts with a "+N more" button, and I added rules for clauses the samples never had, like changing the policy without notice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Some tools didn't connect.&lt;/strong&gt; The Context7 docs server timed out every time, and a hook I'd tied to Kiro's spec task panel never fired, so I moved it to trigger when a task file is saved.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I learned
&lt;/h2&gt;

&lt;p&gt;Building from specs with independent review agents felt very different from prompting for code. The agents caught gaps I would have shipped, and when a gate failed three times, it forced me to fix the cause rather than the symptoms. I also learned that "AI can explain it" is not the same as "AI explains it accurately."&lt;/p&gt;

&lt;p&gt;By the end, the project had 883 unit and property tests and 93 end-to-end tests, all passing.&lt;/p&gt;

&lt;p&gt;If you've ever clicked "I agree" without reading, paste your favourite app's privacy policy into the house and see how haunted it is.&lt;/p&gt;

</description>
      <category>kiro</category>
      <category>nextjs</category>
      <category>hackathon</category>
    </item>
  </channel>
</rss>
