TermsKit

Hey IH! 👋 I just launched TermsKit — a generator for Privacy Policy, Terms of Service, and Cookie Policy specifically built for indie SaaS, Chrome extensions, and mobile apps. The story I'm a solo maker in Porto, Portugal. Every time I started a new side project, I hit the same wall — legal docs before launch. Three bad options kept showing up: - Free templates → unprofessional, possibly outdated, no hosting - Termly/iubenda subscriptions → $9-39/month bleeding from a $0-revenue side project - A lawyer → $300-500, not viable until you're profitable So I built the third option I actually wanted: pay €29 once, get GDPR + CCPA-ready docs in 5 minutes, hosted on a stable URL. What's different - €29 one-time, not a subscription - Tailored to the indie hacker stack - GDPR + CCPA out of the box - Hosted on stable URL or downloadable as HTML/Markdown - No signup needed to try The build Tech: Next.js 14, Stripe, SQLite, deployed on a €5/month VPS. Built in a weekend. Honest disclaimer: I'm not a developer. I built this with heavy AI assistance, manually deployed everything, learned PM2/Nginx/Let's Encrypt along the way. If I can do it, you can too. I'm using TermsKit's own docs on TermsKit itself — see the footer at termskit.app. Dogfooding from day one 🐶 I'd love feedback on - Is €29 one-time the right price? - Should I add more site types? (e-commerce, marketplace?) - What other legal docs would you want? (DPA, EULA, Cookie banner?) AMA — happy to share anything about the build, the deploy, the price decision, or what I learned the hard way. — Alexey