update: remove em dashes, plans

apps/web/src/views/privacy.ejs

@@ -22,10 +22,10 @@
         The rest of the industry
       </h2>
       <p class="text-sm text-gray-400 leading-relaxed">
-        Most SaaS monitoring tools are free or cheap because <strong>you're the product</strong>. They're backed by investors who need returns, which means your usage data, your infrastructure details, your URLs, your team — all of it gets fed into ad networks, sold to data brokers, or used to build "anonymized" datasets that aren't actually anonymous.
+        Most SaaS monitoring tools are free or cheap because <strong>you're the product</strong>. They're backed by investors who need returns, which means your usage data, your infrastructure details, your URLs, your team. All of it gets fed into ad networks, sold to data brokers, or used to build "anonymized" datasets that aren't actually anonymous.
       </p>
       <p class="text-sm text-gray-400 leading-relaxed mt-3">
-        They require your email "for alerts" and then spam you, add you to nurture sequences, sell your address, and share it with their parent company's 47 "trusted partners." They embed Segment, Mixpanel, Intercom, Hotjar, Google Analytics, and a dozen other trackers on every page — harvesting your behavior and shipping it to Silicon Valley servers whether you want it or not.
+        They require your email "for alerts" and then spam you, add you to nurture sequences, sell your address, and share it with their parent company's 47 "trusted partners." They embed Segment, Mixpanel, Intercom, Hotjar, Google Analytics, and a dozen other trackers on every page, harvesting your behavior and shipping it to Silicon Valley servers whether you want it or not.
       </p>
       <p class="text-sm text-gray-400 leading-relaxed mt-3">
         That's the industry standard. We think it's garbage.
@@ -36,10 +36,10 @@
 
       <h2>What we collect</h2>
       <ul>
-        <li><strong>Account key</strong> — a UUID you generate at signup. Stored in plaintext. It's your credential.</li>
-        <li><strong>Email (optional)</strong> — only if you provide one for account recovery. Stored as a one-way SHA-256 hash. We cannot read it, search for it, or recover it. It's purely a verification token.</li>
-        <li><strong>Monitors</strong> — the URLs and configurations you create. Obviously.</li>
-        <li><strong>Ping results</strong> — status codes, latency, up/down, error messages. This is the product.</li>
+        <li><strong>Account key</strong> - a UUID you generate at signup. Stored in plaintext. It's your credential.</li>
+        <li><strong>Email (optional)</strong> - only if you provide one for account recovery. Stored as a one-way SHA-256 hash. We cannot read it, search for it, or recover it.</li>
+        <li><strong>Monitors</strong> - the URLs and configurations you create.</li>
+        <li><strong>Ping results</strong> - status codes, latency, up/down, error messages.</li>
       </ul>
       <p>That's it. No device fingerprints, no IP logs, no browser data, no analytics events, no session recordings.</p>
 
@@ -72,7 +72,7 @@
 
       <h2>Payments</h2>
       <p>
-        We accept cryptocurrency. No card data, no billing address, no name — payments can be entirely anonymous. We never store or see your payment details.
+        We accept cryptocurrency. No card data, no billing address, no name. Payments can be entirely anonymous. We never store or see your payment details.
       </p>
 
       <h2>Data retention</h2>
@@ -82,7 +82,7 @@
 
       <h2>Security</h2>
       <p>
-        All data in transit is encrypted via TLS. All data at rest is on encrypted disks. Your account key is the only credential — there's no password database to breach, no hashed passwords to crack, no OAuth tokens to steal.
+        All data in transit is encrypted via TLS. All data at rest is on encrypted disks. Your account key is the only credential. There's no password database to breach, no hashed passwords to crack, no OAuth tokens to steal.
       </p>
 
       <h2>Contact</h2>