<?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: Romain Loupias</title>
    <description>The latest articles on DEV Community by Romain Loupias (@rloupias).</description>
    <link>https://dev.to/rloupias</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3842938%2F597ee882-d5a9-4086-a876-c349e68e7bb1.jpg</url>
      <title>DEV Community: Romain Loupias</title>
      <link>https://dev.to/rloupias</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rloupias"/>
    <language>en</language>
    <item>
      <title>I built a Chrome extension that reads SaaS Terms of Service so you don't have to</title>
      <dc:creator>Romain Loupias</dc:creator>
      <pubDate>Wed, 25 Mar 2026 10:02:39 +0000</pubDate>
      <link>https://dev.to/rloupias/i-built-a-chrome-extension-that-reads-saas-terms-of-service-so-you-dont-have-to-153k</link>
      <guid>https://dev.to/rloupias/i-built-a-chrome-extension-that-reads-saas-terms-of-service-so-you-dont-have-to-153k</guid>
      <description>&lt;p&gt;Every SaaS has a Terms of Service. Nobody reads it.&lt;/p&gt;

&lt;p&gt;I got burned by an auto-renewal clause I missed. Paid for a full year of a tool I'd stopped using 3 months in. When I went back to read the ToS, the clause was in paragraph 14, written in legal language that would take a lawyer to parse.&lt;/p&gt;

&lt;p&gt;So I built Explain Legal, a Chrome extension that does it automatically.&lt;/p&gt;

&lt;p&gt;How it works&lt;/p&gt;

&lt;p&gt;When you land on a SaaS pricing page, the extension:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Detects that you're on a pricing or checkout page&lt;/li&gt;
&lt;li&gt;Silently fetches the Terms of Service from the same domain&lt;/li&gt;
&lt;li&gt;Analyzes it with Claude (Anthropic's API)&lt;/li&gt;
&lt;li&gt;Surfaces the results in a sidebar — no clicking required&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;What it shows you&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A verdict: Safe, Caution, or Avoid&lt;/li&gt;
&lt;li&gt;Up to 3 red flags focused on financial risk (auto-renewal, non-refundable payments, price change rights)&lt;/li&gt;
&lt;li&gt;2 questions to ask support before you commit&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The technical stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Chrome Extension (Manifest V3, vanilla JS)&lt;/li&gt;
&lt;li&gt;Vercel serverless function as a proxy (keeps the API key server-side)&lt;/li&gt;
&lt;li&gt;Upstash Redis for usage tracking (freemium model — 3 free scans)&lt;/li&gt;
&lt;li&gt;Claude API for the analysis&lt;/li&gt;
&lt;li&gt;Stripe for payments&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The interesting engineering problem&lt;/p&gt;

&lt;p&gt;The hardest part wasn't the AI analysis, it was reliably finding and fetching the ToS page from any domain. Some sites link to &lt;code&gt;/terms&lt;/code&gt;, others to &lt;code&gt;/legal/terms-of-service&lt;/code&gt;, others bury it in the footer with non-standard anchor text.&lt;/p&gt;

&lt;p&gt;The current approach: scan for anchor tags containing "terms", "tos", "legal", or "conditions" on the same domain, with a fallback to &lt;code&gt;/terms&lt;/code&gt;. Works for ~85% of sites.&lt;/p&gt;

&lt;p&gt;Try it&lt;/p&gt;

&lt;p&gt;It's live on the Chrome Store: &lt;a href="https://explainlegal.com" rel="noopener noreferrer"&gt;Explain Legal&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;3 free scans included.&lt;/p&gt;

&lt;p&gt;Happy to answer questions about the build.&lt;/p&gt;

</description>
      <category>java</category>
      <category>webdev</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
