Built TermsGuard to explain contracts in plain English — looking for feedback
Most people never read the terms they accept. I built TermsGuard to turn contracts, ToS, and privacy policies into plain-English summaries, risk flags, Q&A, and PDFs. The product works — the hard part is whether the pain at “I Agree” is strong enough to change behavior.
Trending on Indie Hackers
The pain question is the right one to be worried about. People know they're signing something they didn't read, and they do it anyway, so the discomfort clearly isn't enough on its own to change behavior.
Where it might flip is when there's a specific decision attached. Nobody reads a social app's terms. But someone about to sign a lease, a freelance contract, or a service agreement with a cancellation clause has an actual thing at stake in that moment. That feels like a different user than "person who wants to be more informed in general."
Are your early users coming in with a specific document they're worried about, or are they mostly just curious and testing it on something random? That split would tell you a lot about which one you're actually building for.
The “I Agree” moment is a very specific point of friction. Curious what users actually ask TermsGuard about most when they put a real contract through it.